[Ironpython-users] Compiling IronPython for .NET 2.0

Jeff Hardy jdhardy at gmail.com
Wed Jul 27 18:40:10 CEST 2011

Also, there might be some changes that require 3.5 (use of Linq, etc.)
since I don't know if anyone was testing on plain-old .NET 2.0 (I
think the v2 targets are actually set for 3.5). There are supposed to
be targets on the build server that build .NET 2, but I'm not sure if
they're working. Of course, I'd also like to get artifact generation
working properly on the build server as well.

This ties into Mono 2.6 support, since I don't know what .NET version
it maps to.

- Jeff

On Wed, Jul 27, 2011 at 9:13 AM, Jimmy Schementi <jschementi at gmail.com> wrote:
> We do still have the v2Debug build configuration available in the csproj
> files, and IronPython.Mono.sln still allows building it:
> msbuild Solutions\IronPython.Mono.sln /p:Configuration=v2Debug
> However, current sources fail to build in a few places. Looks like you can
> put #if !CLR2 around those areas and it should still work against CLR2
> runtimes.
> ~Jimmy
> On Jul 27, 2011, at 2:28 AM, Markus Schaber wrote:
> It seems that IronPython 2.7 beta 2 can only be compiled for .NET 3.5, but
> will not work any more when the projects are converted to be pure .NET 2.0
> projects (using SharpSVN).
> Is this a known issue?
> Or is there an error on my side?
> Thanks,
> Markus
> _______________________________________________
> Ironpython-users mailing list
> Ironpython-users at python.org
> http://mail.python.org/mailman/listinfo/ironpython-users

More information about the Ironpython-users mailing list