In general I think this is a good idea. Not only will it improve support in interop scenarios but it also helps with thinks like debugging, profiling, etc... for those of us doing lots of that w/ VS and IronPython. Personally I always use an x86 IronPython on my 64-bit machines simply because the tools tend to work much better with it.
I've opened a CodePlex issue to track it (9158 - http://www.codeplex.com/IronPython/WorkItem/View.aspx?WorkItemId=9158) but I don't think we'll do this until v2.0. Thanks for the suggestion and sorry we didn't get back to you the 1st time. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dan Shechter Sent: Monday, March 26, 2007 8:14 AM To: 'Discussion of IronPython' Subject: [IronPython] IronPython x86/x64 Hi, Since I didn't receive any comments regarding my proposal last time I will try to re-iterate it once again. I think it would be very helpful for IP official builds/project files to contain two versions of the ipy.exe and ipw.exe ipy.exe / ipyw.exe - Targeted for all architectures ipy-x86.exe / ipyw-x86.exe - Targeted for x86 processors specifically. Having the additional *-x86.exe versions will allow developers needing to interface with 32-bit DLLs / COM objects on a x64 bit system do so without having to recompile and tinker with IP project files. Any official comment / discussion would be greatly appreciated. _______________________________________________ users mailing list 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
