When running w/ windbg a couple of tips would be to first issue the command:
.loadby sos clr Then do: sxe clr And then: g And when you break on each exception do: !pe Those will load the SOS debugging extension for the CLR, enable breaking on 1st chance CLR exceptions, run the program, and then !pe will print the current exception. There’s almost certainly an exception in there somewhere which is causing things not to work. For the VS integration – it doesn’t work w/ the express SKUs simply because the express SKUs don’t allow extensions. But it does work w/ the free integrated shell which you can download here http://www.microsoft.com/downloads/en/details.aspx?FamilyID=8e5aa7b6-8436-43f0-b778-00c3bca733d3&displaylang=en There’s information on the tools over here http://www.ironpython.net/tools/ including a walk through the spec. The documentation for it isn’t yet integrated into the CHM which comes w/ 2.7. I think lots of people have gotten it to work. You’ll need to have VS installed before you install 2.7 or you’ll need to re-run the 2.7 installer after installing to install the tools. From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Ken MacDonald Sent: Monday, October 04, 2010 7:56 AM To: Discussion of IronPython Subject: Re: [IronPython] difference in compiling ipy in 3.5 vs. .NET 4.0? Hi, We tried windbg, but weren't able to get anywhere with it. We have pretty much given up on trying to get IP 2.6.1 to work with .NET 4.0 as an .exe (works WONDERFULLY in 'ipy foo.py' mode), and we are now going to try running this with the 2.7 Alpha of IP. I've just installed this, and skimmed through the entire docset, and while 2.7 supposedly has integration with Visual Studio, there is no mention of it in the docs. Anybody out there tried this and gotten it to work? Also, is the full VS 2010 product needed or can this be run with VS Express? Thanks, Ken On Fri, Sep 17, 2010 at 3:19 PM, Lukas Cenovsky <cenov...@bakalari.cz<mailto:cenov...@bakalari.cz>> wrote: I would try to run it via WinDbg to see all exceptions raised. -- -- Lukáš On 17.9.2010 19:43, Ken MacDonald wrote: We're trying to get a WPF/IPY project converted from .NET 3.5 to 4.0 using IPY 2.6 for .NET 4.0. I got it running fine yesterday using IPY interactively: ipy etms.py bring up all dialogs, connects to DB, works great. but I try to compile it into an executable using the 'pyc.py' tool: C:\hs\tally\etms>ipy.exe "c:\Program Files (x86)\IronPython 2.6 for .NET 4.0\Tools\Scripts\pyc.py" /main:etms.py /platform:x86 /target:winexe etms.py main_window.py model.py presenter.py wpf_helpers.py pyevent.py dialogs.py login.py kitchen_ticket.py hs_quantity.py hssecdll.py debug_settings.py version_info.py and it completes 'successfully' but then if I attempt to run it, the command prompt returns immediately and not even the login dialog appears. There are no error messages, or indications of a problem. This worked fine (with path changes to reference 3.5) in .NET 3.5, but is now a mystery. I've tried a variety of pyc.py flags that seemed possibly relevant, but nothing makes it work. Suggestions for what this could be appreciated. Ken _______________________________________________ Users mailing list Users@lists.ironpython.com<mailto:Users@lists.ironpython.com> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com _______________________________________________ Users mailing list Users@lists.ironpython.com<mailto:Users@lists.ironpython.com> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
_______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
