Cool, I’ll try and see if I can repro the issue w/ 2.6.1 w/ a simple hello world app.
Regarding when we’ll have the build to EXE support in tools – I doubt it’ll happen for v1 of the tools unfortunately. In general P2 features mean we’ll do them in a future version. From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Ken MacDonald Sent: Monday, October 04, 2010 2:24 PM To: Discussion of IronPython Subject: Re: [IronPython] difference in compiling ipy in 3.5 vs. .NET 4.0? Hm, well whatever happened in 2.7, it now seems like I can get a working .exe as output from pyc.py. All I have is a really simple test app, but it's doing .NET 4.0 stuff, and running from the .exe. I have no idea what changed from 2.6.1 to make it workable again. Anyway, hopefully I can move over the whole app tomorrow and have some better luck with that. Ken On Mon, Oct 4, 2010 at 4:06 PM, Ken MacDonald <drken...@gmail.com<mailto:drken...@gmail.com>> wrote: Hi Dino, Thanks for the info / pointers on VS integration. I looked at the schedule in the spec, and it appears that "build to .exe" support is not going to be integrated for some time, whenever "P2" is; is there a schedule for that? I got that stuff installed, and was able to get a very simple app (hello, world-ish) up and running in VS/IronPython, but I'm still unable to do a build-out from VS and get a real .exe out of the deal, which was what I was hoping to be able to do with the VS integration. We are sort of at a crossroads here where we want to see if we can stay w/IP as our dev platform, or if we need to port the whole beast to C#, which seems like a large pain. Ken On Mon, Oct 4, 2010 at 1:27 PM, Dino Viehland <di...@microsoft.com<mailto:di...@microsoft.com>> wrote: 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> [mailto: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<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
