Home/ Questions/Q 5849951
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-22T13:04:22+00:00

The website says it is for .NET 4.0 but that I could compile it

  • 0

The website says it is for .NET 4.0 but that I could compile it for use with 3.5, however that is ALL it says on the topic as far as I can tell.

What files do I need? Any unique settings? Do I compile it in Visual Studio? Thanks..

I downloaded from here https://github.com/IronLanguages/main

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Used to work on the IronPython Team at Microsoft, but I know quite a bit has changed since 2.7 Alpha 1…

    My suggestion is to stick with .NET 4.0 unless the machines you deploy to really cannot have 4.0 installed (e.g., lacking admin privileges to do the .NET install). To attempt to make a really long story short, the guts of IronPython and IronRuby, the Dynamic Language Runtime, were added to .NET with version 4.0. What this means for IronPython 2.6/2.7 is that it runs faster on .NET 4.0 when compared to .NET 3.5/3.0/2.0. There’s other good reasons to use the .NET 4.0 based assemblies as well, but this is the most compelling.

    If you’re just interested in compiling IronPython 2.7 and don’t have Visual Studio 2010 installed…that’s actually not a problem. Install the full version of .NET 4.0 on your machine and use the version of msbuild that comes with it. Path should be something like C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild

    Finally, if you really must build against .NET 3.5, there used to be something like a “/version:3.5” flag you could pass to msbuild when compiling IronPython.sln. Things have changed so much since the project left Microsoft’s hands I really have no idea if this still works. This is more likely to work with the last 2.6 release though – see http://ironpython.codeplex.com/releases/view/41236. Flag for this might be “/version:2.0”?

    • 0