case and I don't have an
> easy place to send it to.
>
>
> > -Original Message-
> > From: Jeff Hardy [mailto:jdha...@gmail.com]
> > Sent: Monday, August 08, 2011 12:35 PM
> > To: Igor Brejc
> > Cc: ironpython-users@python.org; Dino Viehland
> &
-
> From: Jeff Hardy [mailto:jdha...@gmail.com]
> Sent: Monday, August 08, 2011 12:35 PM
> To: Igor Brejc
> Cc: ironpython-users@python.org; Dino Viehland
> Subject: Re: [Ironpython-users] AccessViolationException on
> Python.CreateEngine() call
>
> Two quick answers:
> 1. It
Two quick answers:
1. It's not critical, unless you need access COM objects (like
Word/Excel automation or something).
2. The exact same code is in 2.7, and I think it's still active.
3. I can't understand why it would break like that when examining
those assemblies.
Dino? Thoughts?
- Jeff
On Mo
Well in the end I built it from the ZIP package :).
Anyway, here are some results. IP always breaks down when
examining System.Runtime.Hosting.ActivationArguments type, on the
if (type.IsImport && type.IsInterface)
line. This is the only type the method breaks down on.
PublishComTypes examin
IronPython_2_6 should be all you need. The rest is the start of 2.7
that later got moved to GitHub.
- Jeff
On Mon, Aug 8, 2011 at 10:50 AM, Igor Brejc wrote:
> Hi Jeff,
> One question: I'm looking at the codeplex SVN repository (since I assume
> this is where 2.6.2 code still resides). What exac
Hi Jeff,
One question: I'm looking at the codeplex SVN repository (since I assume
this is where 2.6.2 code still resides). What exactly do I need to check out
in order to be able to build it? IronPython_2_6 directory or the whole
repository? There seems to be a lot of stuff in the IronPython_Main
Hi Jeff,
Thanks for responding. I'll update the SO question if/when someone (I guess
it will probably have to be me) figures out what the problem is.
One update: we did some more debugging. The user installed IronPython 2.6.2
msi (.NET 2.0) and ipy64.exe breaks down when run. I guess this exclude
Hi Igor,
The exception is occurring somewhere in IronPython's COM interop code,
but I'm not exactly sure why - the code where the exception occurred
pulls COM types out of interop assemblies. You'll have to (somehow)
figure out what assembly is getting loaded in the AppDomain when the
exception ha
