Microsoft announces general availability of .NET Core 2.0, .NET Standard 2.0, and ASP.NET Core 2.0
Microsoft is rolling out .NET Core 2.0, .NET Standard 2.0 and ASP.NET Core 2.0, advancing the company's goal of more of a common .NET platform everywhere.
Context & Ripple Effects
The 2.0 release is the payoff of a two-year open-sourcing arc that began with Microsoft pushing the door wider via CoreCLR in 2015 and culminated in the cross-platform .NET Core 1.0 launch in June 2016. What changed with 2.0 is scope: .NET Standard 2.0 gives the fragmented .NET ecosystem a single shared API contract, so libraries written once run across .NET Framework, .NET Core, and Xamarin.
That matters because the 1.0 release left a gap — the API surface was too thin for many existing Windows .NET applications to port. Closing it is what turns .NET Core from an experiment into a credible production target on Linux and macOS, setting up the consolidation later visible in .NET 5 and the Visual Studio 2022 / .NET 6 generation.
First-order effects
- Developers maintaining existing .NET Framework codebases gain a realistic porting path: with the Standard 2.0 API contract in place, ASP.NET Core 2.0 apps can be deployed to Linux servers rather than requiring Windows infrastructure.
Second-order effects
- Third-party .NET library authors are pushed to re-target against .NET Standard or risk losing relevance as the install base splits between the legacy framework and the new cross-platform runtime.
Third-order effects
- If the pattern holds — open source, then convergence, then a unified versioned platform — Microsoft's server-side developer franchise stops being a Windows lock-in asset and becomes a multi-cloud one, with Azure competing for Linux workloads running its own stack.
The trend: Microsoft's developer platform strategy is converging on a single open-source, cross-platform .NET runtime, trading Windows exclusivity for reach across clouds and operating systems.