We're developing an IronPython WPF/XAML app; it works fine in .NET 3.5 but now trying to move to IronPython 2.6.1 for .NET 4.0. We have a .csproj which we've updated to 4.0 - it mainly bundles our XAML and resources into a .dll - and everything works fine
if we run interactively from the command prompt:
but when we try to build it into a standalone .exe using the pyc.py tool:
C:\hs\dev\program>ipy.exe "c:\Program Files (x86)\IronPython 2.6 for .NET 4.0\Tools\Scripts\pyc.py" /main:program.py /platform:x86 /target:winexe program.py main_window.py model.py presenter.py wpf_helpers.py pyevent.py dialogs.py login.py k_ticket.py
hs_quantity.py hssecdll.py debug_settings.py version_info.py
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 paths as appropriate to reference 3.5)
in .NET 3.5, but is now a total 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 or where to look for problems appreciated! Trying to get this over to customer ASAP.
View Complete Post