tep will be downgrading my application to 3.5.
>
>
>
> Or do you have better idea?
>
>
>
> Zoltan
>
>
> *From:* Jeff Hardy
> *Sent:* Friday, January 11, 2013 4:54 PM
> *To:* Zsidó Zoltán
> *Cc:* [email protected]
> *Subject:* Re: [Ironpython-use
my next step
will be downgrading my application to 3.5.
Or do you have better idea?
Zoltan
From: Jeff Hardy
Sent: Friday, January 11, 2013 4:54 PM
To: Zsidó Zoltán
Cc: [email protected]
Subject: Re: [Ironpython-users] crash on Win8 64bit at IronPython expression
evaluation
What version of .NET is installed on the Windows 7 machines? I wonder if
this is a .NET 4.5 vs. .NET 4 issue and not a Win8 vs Win7 issue.
- Jeff
On Thu, Jan 10, 2013 at 11:43 PM, Zsidó Zoltán wrote:
> Keith, you are absolutely right. Not the background thread causes this
> error.
>
> I trie
Keith, you are absolutely right. Not the background thread causes this error.
I tried to make a simpler application that throws the same exception but I was
not able to do it.
Then I tried to debug it in Visual Studio 2010 but if I debug then the error
does not appears.
I cannot post the full
Are you able to narrow down the problem to a small script that reproduces it?
The code pointed to in that call stack doesn't really have many ways of failing
in that way (null reference). The most likely thing is that
DefaultContext.DefaultPythonContext is not being set. But I think that is done
