News

Microsoft Open Sources .NET CoreCLR

The ongoing effort to open source .NET Core gets clearer, as the team adds the "execution engine" that drives .NET apps to the Github repository.

Microsoft's .NET Team said in a blog post that it has added the .NET Core Common Language Runtime repository, or .NET CoreCLR, to Github. The move is another significant step in an ongoing process to fully open source .NET that was put in motion near the beginning of 2014.

The .NET team calls .NET CoreCLR the "execution engine for .NET apps," and includes Intermediate Language byte code loading, compilation, garbage collection, native interoperability and other .NET runtime components. It currently runs only on Windows, but the general plan outlined in November is to eventually port platform-specific components for Linux and Mac.

The process of open sourcing .NET was started back in November last year starting with the .NET CoreFX repository that contains all the class libraries on Github. Even so, the team laid the groundwork much earlier in the year, with other releases to the Microsoft Codeplex open source project hosting site. ASP.NET was open sourced in March 2014, while the "Roslyn" .NET Compiler Platform was open sourced a month later. Over the last year, both projects were moved over to the more popular Github open source project hosting site.

Moving projects from Codeplex to Github from a perception standpoint appears to have made a difference in community participation. Microsoft program manager Immo Landwerth blogs of a project that he was working on that got more attention once he posted it to Github. "During the two years it was on CodePlex I've only received a single pull request." he wrote. "Five days after I moved to GitHub I already received three pull requests and found two other contributors." (Landwerth in December wrote a comprehensive blog that spells out the complexity of simplifying the fragmented .NET Framework into the more open-source-friendly and unifying .NET Core and it offers insights into the process that's worth reading.)

Because the .NET CoreCLR repository includes both C# and C++ code collections, the team said that developers will need "multiple toolsets to build both C# and C++ code, including tools that do not ship with Visual Studio." A work-in-progress developer guide that lists the tools and requirements are here for those who want to start digging in and forking projects.

Developers can find out more next month, as the team is expected to provide an update on their open source efforts at dotnetConf, a free virtual event hosted by Microsoft on March 18-19. For more info, click here.

About the Author

You Tell 'Em, Readers: If you've read this far, know that Michael Domingo, Visual Studio Magazine Editor in Chief, is here to serve you, dear readers, and wants to get you the information you so richly deserve. What news, content, topics, issues do you want to see covered in Visual Studio Magazine? He's listening at [email protected].

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube