In 2016, Microsoft announced. Net standard. It is an API that all. Net platforms must implement. It unifies the. Net platform and prevents future fragmentation.Recent blog updateMicrosoft says it will not release a new version of. Net standard in the future.
. net 5 will be a single product with a unified set of functions and APIs, which can be used for Windows desktop applications, cross platform mobile applications, console applications, cloud services and websites. . net 5 and all future versions will continue to support. Net standard 2.1 and earlier. You can think of. Net 5 as. Net standard vNext.
For developers, what should be. Net standard and. Net 5? Microsoft suggests the following.
● use netstandard2.0 to share code between the. Net framework and all other platforms.
● use netstandard2.1 to share code between mono, xamarin, and. Net core 3. X.
Use net5.0 for code sharing.
Wrote in the blog post
Net5.0 is for code that can run anywhere. It combines and replaces the names of netcoreapp and netstandard. We also have platform specific frameworks, such as net5.0-windows (later net6.0-android, net6.0-ios).
Since there is no difference between the standard and its implementation, you will be able to take advantage of new features faster than using the. Net standard. And because of naming conventions, you'll be able to easily know who can use a given library -- without consulting the. Net standard version table.
Although. Net standard 2.1 will be the last version of. Net standard,. Net 5 and all future versions will continue to support. Net standard 2.1 and earlier. You should see net5.0 (and future versions) as the basis for future shared code.