I used to think that would be great back when I used py2exe, but once I built a script to build an MSI, the need went away. For me having real install/uninstall, shortcut and registry setting capabilities trumps a single exe file.
Bruce On Fri, Aug 28, 2009 at 12:58 PM, Dino Viehland <[email protected]> wrote: > You might be able to use al.exe to link them together – but otherwise > no. Is the problem having both Main.dll + Main.exe (which we could > presumably fix)? Or is it just the large number of assemblies overall? > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Prabhu Mohan > *Sent:* Friday, August 28, 2009 6:39 AM > *To:* [email protected] > *Subject:* [IronPython] Generating executables out of IronPython script > > > > Hi, > > I have been using IronPython 2.0.2 to develop a Microsoft SharePoint > application. I use IronPython studio (Integrated with Visual Studio 2008). > When I build the project, I get an executable along with IronPython.dll and > IronMath.dll which I need to redistribute with the executable. But when I > try to create an executable using PYC I get an executable along with a dll > (say Main.dll with Main.exe). In this case, I need to redistribute Main.dll, > IronPython.dll, IronMath.dll, IronPython.Modules.dll, > Microsoft.Scripting.Core.dll, Microsoft.Scripting.dll etc., So I need to > know if it is possible to get the same way as IronPython studio provides > without using the studio (using command line or any other tool) > > -- > Kind Regards, > Prabhu > > _______________________________________________ > Users mailing list > [email protected] > http://lists.ironpython.com/listinfo.cgi/users-ironpython.com > >
_______________________________________________ Users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
