.NET Standard

.NET Standard
Microsoft · Public domain · source
Name	.NET Standard
Developer	Microsoft
Initial release	2016
Latest release	2.1
Implemented by	Microsoft .NET, Mono, Xamarin
License	MIT License

'.NET Standard

.NET Standard is a formal specification that defined a uniform set of APIs for software libraries to enable code sharing across multiple implementations of the .NET platform. It provided a baseline for library authors and implementers, aiming to reduce fragmentation between ecosystems such as Microsoft, Mono, and Xamarin while interacting with projects from companies like Novell, Intel, and Canonical. Designed amid coordination between engineers from Microsoft, Xamarin, and the .NET community, the specification influenced tooling in Visual Studio, Visual Studio Code, and MSBuild.

Overview

.NET Standard served as an API specification describing a standardized set of publicly available APIs that library developers could target so their assemblies would run on multiple runtime implementations. The specification was produced and maintained by engineers at Microsoft and contributors from Xamarin, Mono, and the .NET Foundation, and it related to tooling such as NuGet, MSBuild, and Roslyn while affecting ecosystems including Azure, Windows, and Linux distributions. It aimed to reconcile differences between implementations like .NET Framework, .NET Core, Mono, and Xamarin.iOS while guiding platform owners at Apple, Google, and Canonical on interoperability.

History and Development

The initiative to create a unified API abstraction arose as efforts from Microsoft and the open source community evolved, influenced by projects such as .NET Core, Mono, and Xamarin.Android and stakeholders like Miguel de Icaza, Scott Guthrie, and Anders Hejlsberg. Announced during a period of transition in the Microsoft developer ecosystem alongside conferences such as Microsoft Build and Connect, the development process involved the .NET Foundation, GitHub repositories, and contributions from firms including Red Hat, JetBrains, and Intel. Over successive releases the specification was adjusted to reflect feedback from Visual Studio team members, Azure engineers, and enterprise customers at banks, insurers, and government agencies.

Specification and Versions

The specification defined versioned API sets that increased in breadth across releases, with milestones that guided adoption by platform implementers and library authors. Key published marks aligned with work on .NET Core, Xamarin, and Mono as engineering teams at Microsoft, Xamarin, and Novell conferred on compatibility matrices used by NuGet package maintainers and package authors at GitHub, GitLab, and Bitbucket. Versioning decisions were informed by language and compiler teams associated with C# and F#, runtime teams governing CLR and CoreCLR, and platform product groups responsible for Windows, macOS, and Linux distributions.

Relationship to .NET Implementations

Implementations such as Microsoft's .NET Framework, .NET Core, Mono, and Xamarin adopted the specification to varying extents, enabling libraries targeting the standard to run across Android, iOS, Windows, macOS, and Linux. Platform teams at Microsoft, Xamarin, and the Mono project implemented API surfaces consistent with the specification while interacting with ecosystem projects like ASP.NET, WPF, and UWP and organizations such as Azure, GitHub, and the .NET Foundation. Cross-company integrations involved contributors from JetBrains, Red Hat, Canonical, and Apple who addressed platform-specific concerns on mobile and desktop stacks.

Compatibility and Versioning

Compatibility between library targets and runtime implementations was governed by a mapping of .NET Standard versions to platform versions maintained by implementers and reflected in tooling such as NuGet, MSBuild, and IDEs like Visual Studio and Visual Studio Code. Engineers from Microsoft, Xamarin, and the Mono project coordinated with package maintainers on GitHub and NuGet.org to clarify which versions of .NET Framework, .NET Core, and Xamarin platforms satisfied particular API sets. Versioning debates involved language teams for C#, F#, and Visual Basic as well as runtime architects responsible for CLR and CoreCLR to balance stability for enterprise customers in banks, healthcare providers, and government agencies.

Adoption and Impact

Adoption of the specification by library authors and vendors including Microsoft, Xamarin, JetBrains, Red Hat, and numerous open source projects on GitHub reduced duplication of effort and facilitated code sharing between server, desktop, and mobile ecosystems. Enterprise adoption influenced projects at Azure, Amazon Web Services partners, banks, and insurance companies, while tooling vendors such as JetBrains, Microsoft, and Red Hat integrated support into IDEs and CI systems. Community projects maintained on GitHub and package ecosystems on NuGet.org reflected broad uptake across diverse organizations including Canonical, IBM, and academic labs.

Deprecation and Successor Technologies

With the consolidation of platform efforts into a unified runtime and SDK under a later unified platform strategy led by Microsoft engineering teams, the community and vendor focus shifted toward newer approaches and consolidated tooling such as a unified SDK and runtime unifying CoreCLR and Mono workstreams. Successor directions influenced roadmaps at Microsoft, the .NET Foundation, and partners like Xamarin and JetBrains and led implementers and package maintainers on NuGet and GitHub to move toward the consolidated platform implementations and modern SDK tooling embraced by cloud providers like Azure and large enterprises.

Category:Microsoft Category:Software development