If I understand the issue correctly, the options to build IronPython from source are
1) Build with VS 2010 Beta and/OR Build with VS 2008 SP1 and .NET 3.5 SP1 2) Build with VS 2008 and .NET 3.5 I vote for option 1 On Mon, Jul 27, 2009 at 3:44 PM, Dave Fugate <[email protected]> wrote: > As it stands today, the .NET 3.5 version of msbuild (or Visual Studio > 2008) is required to build IronPython 2.6 Beta 2 from sources. One cannot > build IronPython.sln from the latest beta of Visual Studio 2010 without > irreversibly upgrading all C# project files to Visual Studio 2010. We’re > hoping to change that… > > > > .NET 3.5 *Service Pack 1* introduced a new feature which allows one to > build Visual Studio 2010 C# project files using .NET 3.5 SP1. All we need > to do take advantage of this is change the “ToolsVersion” attribute of C# > project files from “3.5” to “4.0”. There’s one unfortunate side effect > we’ve discovered thus far – we can no longer build IronPython.sln with > anything less than .NET 3.5 *SP1* or Visual Studio 2008 *SP1*. > > > > We understand it’s a bit late in the IronPython 2.6 release cycle for this > type of change, but feel it would provide a lot of value to those trying out > Visual Studio 2010. The question we have for everyone is does the benefit > of being able to build IronPython under Visual Studio 2010 Betas outweigh > the cost of no longer being able to build on .NET 3.5 without Service Pack 1 > installed? We’d love to hear any feedback you might have as this will > strongly influence whatever decision we end up taking. > > > > Thanks, > > > > David Fugate > > Microsoft - IronPython > > http://knowbody.livejournal.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
