Everything works correctly when I use the Remote Debugger rather than
debugging inside VS2012. I haven't had to use the remote debugger
since VS2005, but glad it does the job
Thanks for your patience
John Davidson
On Wed, Feb 13, 2013 at 6:47 PM, John Davidson wrote:
> Some more followup detail
Some more followup detail. I added the Frames and FullFrames option to
the engine creation. This allows me to now get the full stack trace
into the IronPython.dll
The process is hanging in
IronPython.dll!IronPython.Runtime.Operations.PythonTypeOps.GetBuiltinFunction(System.Type
type = {Na
Thank you for the response.
There is no error when running in the debugger. The process just hangs
at the line "source.Execute(scope)". When I do a manual break in the
debugger the error I get is "Cannot evaluate expression because a
native frame is on top of the call stack". The information retur
First thing I would check is to make sure it is trying to load the right
version of IronPython. If you are deploying the assemblies to your
application's bin folder then you will also want to verify that no versions are
also loaded in the GAC. Likewise, if your application is using references to
