New versions of the .NET platform are released annually, typically in November. The most recent version of .NET is .NET 11, released in November 2026, which is a short-term support version, and is scheduled to receive updates until November 2028.[6] while the latest long term support release is .NET 10.
In the late 1990s, Microsoft began developing a managed code runtime and programming language (C#) which it billed together as part of the ".NET platform", with the core runtime and software libraries comprising the .NET Framework.
At the heart of the .NET Platform is the .NET Framework, a high-productivity, multilanguage development and execution environment for building and running Web services with important features such as cross-language inheritance and debugging.[7]
On November 12, 2014, Microsoft introduced .NET Core—an open-source, cross-platform[8] successor[9] to .NET Framework—and released source code for the .NET Core CoreCLR implementation, source for the "entire [...] library stack" for .NET Core,[10] and announced the adoption of a conventional ("bazaar"-like) open-source development model under the stewardship of the .NET Foundation. Miguel de Icaza describes .NET Core as a "redesigned version of .NET that is based on the simplified version of the class libraries",[11] and Microsoft's Immo Landwerth explained that .NET Core would be "the foundation of all future .NET platforms". At the time of the announcement, the initial release of the .NET Core project had been seeded with a subset of the libraries' source code and coincided with the relicensing of Microsoft's existing .NET reference source away from the restrictions of the Ms-RSL. Landwerth acknowledged the disadvantages of the formerly selected shared license, explaining that it made codename Rotor "a non-starter" as a community-developed open source project because it did not meet the criteria of an Open Source Initiative (OSI) approved license.[12][13][14]
.NET Core 1.0 was released on June 27, 2016,[15] along with Microsoft Visual Studio 2015 Update 3, which enables .NET Core development.[16].NET Core 1.0.4 and .NET Core 1.1.1 were released along with .NET Core Tools 1.0 and Visual Studio 2017 on March 7, 2017.[17]
.NET Core 2.0 was released on August 14, 2017, along with Visual Studio 2017 15.3, ASP.NET Core 2.0, and Entity Framework Core 2.0.[18].NET Core 2.1 was released on May 30, 2018.[19] NET Core 2.2 was released on December 4, 2018.[20]
.NET Core 3 was released on September 23, 2019.[8] NET Core 3 adds support for Windows desktop application development[21] and significant performance improvements throughout the base library.
In November 2020, Microsoft released .NET 5.0.[22] The "Core" branding was abandoned and version 4.0 was skipped to avoid conflation with .NET Framework, of which the latest releases had all used 4.x versioning for all significant (non-bugfix) releases since 2010.
.NET Core Runtime roughly uses semantic versioning, the major.minor.patch format. Major versions are incremented with "significant changes", API-breaking changes, or with the major version increase in an existing dependency. It should happen yearly. Minor versions are incremented with the addition of API features, dependencies, or with the minor version increase in an existing dependency. Patch versions are given for bug fixes, new platform support, or other changes not included above.[34] As of 2019, runtime versions are backwards-compatible within the same major version number. For example, .NET Core 2.2 is able to run programs built for .NET Core 2.1. Runtime versions in the same minor version.[35] This appears to have relaxed since .NET 5. A "roll-forward" behavior allows any .NET program to be run on any newer version given the correct settings.[34]
The SDK does not use semantic versioning. As of 2019, it supports targeting every runtime version prior to its maximum supported version.[35] As of 2020, this extends down to .NET Framework runtimes as well, though downloading an additional "targeting pack" from NuGet may be necessary.[36][37] The major and minor versions of an SDK always matches the major and minor versions of the runtime it contains or is aligned for.[34]
OS and architecture support
Alpine Linux, which primarily supports and uses musl libc,[38] is supported since .NET Core 2.1.[39]
Windows Arm64 is natively supported since .NET 5. Previously, .NET on ARM meant applications compiled for the x86 architecture and run through the ARM emulation layer.[22]
Linux .NET runs on Power ISA to some extent since .NET 7, officially no support is claimed by Microsoft but .NET does contain code for Power ISA compatibility for Linux systems and is able to be compiled for Power ISA systems specifically 64-bit little-endian variant.[40]
.NET fully supports C# and F# (and C++/CLI as of 3.1; only enabled on Windows) and supports Visual Basic .NET (for version 15.5 in .NET Core 5.0.100-preview.4, and some old versions supported in old .NET Core).[41]
VB.NET compiles and runs on .NET, but as of .NET Core 3.1, the separate Visual Basic Runtime is not implemented. Microsoft initially announced that .NET Core 3 would include the Visual Basic Runtime, but after two years the timeline for such support was updated to .NET 5.[42][43]
.NET supports use of NuGet packages. Unlike .NET Framework, which is serviced using Windows Update, .NET used to rely on its package manager to receive updates.[44] Since December 2020, however, .NET updates started being delivered via Windows Update as well.[47]
NuGet serves as the primary distribution mechanism for libraries and tools in the .NET ecosystem, including third-party components that extend core functionality. Among these are ADO.NET-compatible data providers, which offer database connectivity for systems beyond the default SQL Server support. These providers enable direct access to databases such as Oracle, MySQL, PostgreSQL, and others, and are commonly used in applications that require cross-platform data access, integration with ORM technologies, or support for specific database features.
As an implementation of CLI's Standard Libraries,[52] CoreFX shares a subset of .NET Framework APIs, however, it also comes with its own APIs that are not part of the .NET Framework.[44] A variant of the .NET library is used for UWP.[53]
The official community mascot of .NET is the .NET Bot (stylized as "dotnet bot" or "dotnet-bot"). The dotnet bot served as the placeholder developer for the initial check-in of the .NET source code when it was open-sourced.[56] It has since been used as the official mascot.
Notes
↑The prefix "Ryu" is the Japanese word for "dragon" (竜, ryū), and is a reference to the book Compilers: Principles, Techniques, and Tools (commonly known as the dragon book, from an early cover design), as well as to a character from the video game Street Fighter.[50]
↑Landwerth, Immo (November 12, 2014). ".NET Core is Open Source". .NET Framework Blog. Microsoft. Archived from the original on March 1, 2016. Retrieved December 30, 2014.
↑"dotnet/corefx". GitHub. Archived from the original on July 3, 2018. Retrieved November 16, 2014.
12Kang, M. "Is .NET Core Runtime backwards compatible with previous releases?". Stack Overflow. ...NET Core runtime updates are compatible within a major version 'band' such as 1.x and 2.x. [...] ".NET Core 2.1" refers to the .NET Core Runtime version number. The .NET Core Runtime has a major/minor/patch approach to versioning that follows semantic versioning.
↑Landwerth, Immo (December 4, 2014). "Introducing .NET Core". .NET Framework Blog. Microsoft. Archived from the original on February 24, 2016. Retrieved February 27, 2015.
↑Wang, Abel (September 9, 2020). What is the dotnet bot? (Podcast). Microsoft. Event occurs at 4 seconds in. Archived from the original on March 8, 2023. Retrieved March 9, 2021.
Further reading
Arif, Hammad; Qureshi, Habib (2020). Adopting .NET 5: Understand modern architectures, migration best practices, and the new features in .NET 5. Packt Publishing. ISBN978-1800560567.
Metzgar, Dustin (2018). .NET Core in Action. Manning Publications. ISBN978-1617294273.
Price, Mark J. (2021). C# 10 and .NET 6 – Modern Cross-Platform Development. Packt Publishing. ISBN978-1801077361.
Price, Mark J. (2020). C# 9 and .NET 5 – Modern Cross-Platform Development. Packt Publishing. ISBN978-1800568105.
Price, Mark J. (2019). C# 8.0 and .NET Core 3.0 – Modern Cross-Platform Development. Packt Publishing. ISBN978-1788478120.
Price, Mark J. (2017). C# 7.1 and .NET Core 2.0 – Modern Cross-Platform Development. Packt Publishing. ISBN978-1788398077.
Price, Mark J. (2017). C# 7 and .NET Core: Modern Cross-Platform Development. Packt Publishing. ISBN978-1787129559.
Price, Mark J. (2016). C# 6 and .NET Core 1.0: Modern Cross-Platform Development. Packt Publishing. ISBN978-1785285691.
You are visitor 01402503 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.
