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
funcType = Function |
AlwaysVisible, System.Reflection.MemberInfo[] mems =
{System.Reflection.MemberInfo[3]}) + 0x5e8 bytes
I had also tried enabling the ExceptionDetail, ShowClrExceptions and
MTA options, but they do not change behavior or give any additional
details
John Davidson
On Wed, Feb 13, 2
s running.
This is not yet running on a target server but is ongoing development
on VS2012 in Windows 8.
John Davidson
On Wed, Feb 13, 2013 at 11:05 AM, Keith Rome wrote:
> First thing I would check is to make sure it is trying to load the right
> version of IronPython. If you are deployi
y properties||
This is a wiki table text showing the result of reflecting the
contents of the DSL at its inception.
The application code has identical inputs to ExecuteBehavior as the
unit test has. I have tried Python.CreateEngine with or without the
"debug" option and also with and without the &
