Is Path on your ScriptSource non-null? That should be the only other thing which has an effect.
From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Daniel Jennings Sent: Tuesday, February 01, 2011 12:51 PM To: Discussion of IronPython Subject: Re: [IronPython] Disabling optimized methods Alright, we're using DebugMode = true already (when the application starts with the debugger attached) so we must be seeing something else that is causing us to get the 'function has been optimized' message. Thanks From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Dino Viehland Sent: Tuesday, February 01, 2011 12:50 PM To: Discussion of IronPython Subject: Re: [IronPython] Disabling optimized methods You can use -X:Debug now to specifiy this at the command line. If you want to do it while you're hosting you can set the DebugMode option to true on the ScriptRuntimeSetup object used to create the ScriptRuntime. You'll need to make sure the ScriptSource's you create have filenames though. From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Daniel Jennings Sent: Tuesday, February 01, 2011 11:55 AM To: Discussion of IronPython Subject: [IronPython] Disabling optimized methods I was reading an old post by Dino here: http://www.mail-archive.com/users@lists.ironpython.com/msg04829.html that mentions that using -X:StaticMethods will force methods into types so that you can get the typical CLR-style debugging. I was wondering two things: 1. Is this still relavant to 2.7A1? 2. How do you specify such a flag when you're embedding IronPython in your application (building your own engine.) Thanks!
_______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
