IronPython and IronRuby are two dynamic language implementations for the .NET Framework that Microsoft has incubated internally over the last few years .
Several versions of both language environments, and all of the source code, have been released under open source licenses.
Thursday, October 21, new components and project leaders were announced for IronPython and IronRuby, in an effort to increase the opportunity for community members to contribute their own code and actively participate in these projects to advance them even further.
New Components of IronPython and IronRuby
Changes have been made to the CodePlex projects for IronPython and IronRuby to make it easier for the community to be involved.
For both IronPython and IronRuby, we’ve made changes to the CodePlex projects to allow community members to make contributions without Microsoft’s involvement or sponsorship by a Microsoft employee.
We also have enabled a full release work flow to produce builds and releases straight from the CodePlex projects. (Previously, these only could easily be done from Microsoft’s own source depots. )
The community now can make source contributions to any component of IronPython and IronRuby.
In addition, we have fixed a lot of infrastructure so the community should be able to regression test all language updates using our tests.
IronRuby Tools for Visual Studio
Microsoft has already released the IronPython Tools for Visual Studio that were developed under Apache 2.0 and on Thursday, October 21, we released the prototype code for IronRuby Tools for Visual Studio.
Microsoft has received great early feedback on the IronPython language service for Visual Studio, and we expect similar feedback for the IronRuby tools.
Releasing these components under the Apache 2.0 license allows community members to use the functionality and also contribute to the IronPython and IronRuby language services.
Looking forward, Microsoft has done a lot of ground work for the next version of IronPython (v2.7) and IronRuby (v1.9).
Project Leaders of IronPython and IronRuby
New project leaders external to Microsoft will take over the IronPython and IronRuby projects and provide leadership going forward.
All of them have worked with or on the Iron projects since their inception.
The CLR has always been a great environment for dynamic languages and over the last several years Microsoft has built out additional dynamic language support for the .NET Framework through efforts like the Dynamic Language Runtime (DLR) and language implementations on top of the DLR. The DLR shipped earlier this year as a built-in component of .NET Framework 4, and there are now have several great language implementations built on top of it.
The IronPython and IronRuby projects began as an effort to improve support for dynamic languages in the .NET Framework and to diversify Microsoft’s portfolio of programming languages.
These language projects have helped thousands of people since they began, and they have added value to the .NET Framework.
They helped create the Dynamic Language Runtime in the .NET Framework 4, on which we have also built C#s new ‘dynamic’ keyword and improved Visual Basic’s late-binding support.
Microsoft will continue to invest in making the .NET Framework a great runtime environment for dynamic languages going forward.