Having dealt with certain non-US banks over the last couple years, I know that at least some of them have yet to upgrade to doing wire transfers via some mechanism other than paper. I suspect we geeks are closer to the "real" world than they are. ;) The retargetting feature in Orcas is pretty neat, though. I used it on one project recently to make sure I didn't have any framework version dependencies beyond those the software I was targetting had.
________________________________ From: [EMAIL PROTECTED] on behalf of Michael Foord Sent: Wed 11/28/2007 9:46 AM To: Discussion of IronPython Subject: Re: [IronPython] [Bulk] IronPython.sln and .NET3.5/Visual Studio2008 Keith J. Farmer wrote: > You mean someone *hasn't* downloaded .NET 3.5? :) > > The only impediment I can think of would be whether Mono's tools can handle > it. I haven't touched Mono in ages, so I don't know one way or the other. > A lot of our customers are banks and the like. *Most* of them (but by no means all) have upgraded to .NET 2, few if any will have progressed to 3. That isn't really relevant for this question (none of them will be building IronPython from source) - but just a reminder that us geeks live in a world far removed from 'the real one' (whatever that might be...). My only concern would be that IronPython remains buildable with both Express 2005 and Express 2008 (plus Mono tools of course). Michael http://www.manning.com/foord > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Robin > Lauryssen-Mitchell > Sent: Wednesday, November 28, 2007 9:31 AM > To: 'Discussion of IronPython' > Subject: Re: [IronPython] [Bulk] IronPython.sln and .NET 3.5/Visual Studio2008 > > No problem for lil 'ol me :) > > Robin > > >> -----Original Message----- >> From: [EMAIL PROTECTED] [mailto:users- >> [EMAIL PROTECTED] On Behalf Of Dave Fugate >> Sent: 28 November 2007 18:10 >> To: Discussion of IronPython >> Subject: [Bulk] [IronPython] IronPython.sln and .NET 3.5/Visual Studio >> 2008 >> >> Hello IronPython Community, a couple months ago we began using the beta >> versions of .NET 3.5 and Visual Studio 2008 for IronPython development. >> With respect to the IronPython sources this means that we had to upgrade >> the Visual Studio 2005 solution file, IronPython.sln, to Visual Studio >> 2008. We are *not* using any new C# 3.0 features at this time and >> actually pass a flag to the msbuild tool ensuring that we're building and >> testing against .NET 2.0. >> >> Since this change occurred, we've been backporting solution file >> modifications to the 2005 version and testing the 2008 version as well for >> the 2.0 Alpha releases. Now that .NET 3.5 and Visual Studio 2008 have >> been officially released, we'd like to begin distributing only the 2008 >> solution file. The major reason for wanting to do this is so that we can >> get IP releases out more quickly (i.e., no need to rerun all of our tests >> on sources built under VS2005 or manually modify the 2005 solution file). >> >> The impact on Windows users who build IronPython from sources would be: >> * It will be necessary to install .NET 3.5 or Visual Studio 2008 to get >> the new version of msbuild >> * When building IronPython.sln from the command-line, you'll need to pass >> in an extra argument - "/ToolsVersion:2.0" - to msbuild >> >> We felt it would be best get feedback from users who build IP from sources >> before making this change. Ideally we'd like to make the switch for the >> next Alpha release (which should be available around the third week of >> December), but the change could be delayed if there are many objections. >> All comments are welcome! >> >> The IronPython Team >> _______________________________________________ >> 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 > _______________________________________________ > 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 _______________________________________________ Users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
