Free tools Windows power users keep installed
One-click scans. No signup required.
Microsoft’s November 12, 2014 announcement open-sourced the full server-side .NET stack and extended .NET development to Linux and Mac. It did not move the existing Windows .NET Framework wholesale to Linux: the cross-platform technology was a new, modular stack called .NET Core. .NET Core was renamed .NET starting with .NET 5, so today’s Linux developers use current .NET releases rather than a product still named .NET Core.
What did Microsoft open-source in 2014?
Microsoft announced on November 12, 2014, that it was “open sourcing the full server-side .NET stack” and expanding .NET development to Linux and Mac. The company listed ASP.NET, the .NET compiler, the .NET Core Runtime, framework, and libraries among the components. It said future improvements would be developed with the open-source community through the .NET Foundation. Microsoft’s announcement describes that scope.
The distinction between the server-side stack and the existing .NET Framework matters: this was a move toward a shared, cross-platform implementation, not a wholesale Linux port of every Windows .NET application or desktop feature.
Was the existing .NET Framework ported to Linux?
No. In its December 2014 technical explanation, Microsoft described .NET Core as a new, modular stack, supported on Windows, Linux, and Mac OS X. It characterized .NET Core as a fork of .NET Framework designed for component factoring and cross-platform development. The company separately described .NET Framework as Windows-only and as the platform for rich desktop applications at that time. Microsoft’s explanation of .NET Core sets out the difference.
#1 Best Overall
That distinction also explains the relationship to Mono, an existing open-source reimplementation of .NET Framework that could run on Linux and Mac. Microsoft released parts of .NET Framework Reference Source under an open-source-friendly license to help Mono address compatibility gaps, but said it was not making the entire .NET Framework a GitHub project or accepting pull requests for it.
| Technology in the 2014 discussion | Role and platform scope as described at the time |
|---|---|
| .NET Framework | Windows-only platform, including support for rich desktop applications. |
| .NET Core | New modular stack for cross-platform development on Windows, Linux, and Mac OS X. |
| Mono | Existing open-source reimplementation of .NET Framework usable on Linux and Mac. |
These are historical descriptions from Microsoft’s 2014 material; they should not be read as a complete guide to present-day compatibility or support.
Rank #2
Why did Microsoft make the change?
Microsoft’s stated case focused on cross-platform development and a stronger shared ecosystem, not a measured performance or adoption result. Its November 2014 blog post argued that a collaborative codebase could reduce duplicated work and make design discussions, code reviews, and fixes more visible. The post on open-sourcing .NET Core gives the company’s rationale.
The modular design also addressed deployment and reuse. Rather than ship one monolithic package, Microsoft planned to distribute small components as NuGet packages. A unified API could still rely on platform-specific implementations where necessary—for example, for file-system behavior. Microsoft presented these as design goals and rationale, not as independently measured results.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteIn the announcement, S. Somasegar, then Microsoft corporate vice president of Developer Division, said: “With billions of devices in the market today, developers need tools that target many different form factors and platforms.” He added that Microsoft was committed to tools for building and managing applications across devices and platforms. Brian McCallister, then Groupon’s chief technology officer, described a cross-platform CLR as opening options for large server-based systems.
What does the announcement mean for .NET on Linux today?
The .NET Core name was replaced by .NET beginning with .NET 5. Microsoft’s lifecycle page, as listed on September 30, 2026, gives .NET 10 support through November 15, 2028, and .NET 8 and .NET 9 support through November 11, 2026. These are lifecycle dates, not a guarantee that every distribution offers every release or package through the same route. Check Microsoft’s .NET lifecycle information for current status.
Linux installation and package ownership vary by distribution. Microsoft’s installation guide, last updated April 23, 2026, lists package-manager installation, Snap, manual installation, and container images. It lists Microsoft repository packages for Azure Linux, Debian, openSUSE Leap, and SUSE Enterprise Linux; Alpine, CentOS Stream, Fedora, Red Hat Enterprise Linux, and Ubuntu are listed as distributions that publish their own .NET packages. Snap packages are provided and maintained by Canonical. Consult Microsoft’s Linux installation guide for the route and version currently supported for your distribution.
Package source and support provider are not interchangeable. Microsoft’s current open-source overview says .NET is maintained by Microsoft and the .NET community, while also noting that Red Hat supports .NET on RHEL. It says repositories typically use MIT or Apache 2 licenses, with the individual repository determining the applicable license. Microsoft further distinguishes building from source from using official releases, which it says are built and tested on Microsoft-maintained Azure servers. See .NET’s open-source overview for those details.
How to choose a Linux .NET installation route
- Start with your distribution: check its current package instructions and Microsoft’s Linux guide rather than assuming the same repository or release is available everywhere.
- Check who supplies the package: depending on the distribution and route, packages may come from Microsoft, the distribution, or Canonical for Snap.
- Match the route to deployment: package-manager installs suit system-managed environments; manual installs and containers offer other deployment choices, but have different update and maintenance responsibilities.
- Verify lifecycle and support: confirm the release’s support dates and whether Microsoft or another provider supports the specific distribution/package combination you intend to run.
For legacy applications, separately check their .NET Framework APIs and platform dependencies before planning a move to Linux. The 2014 announcement established a cross-platform direction; it did not promise that existing Windows applications would run unchanged.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
