.NET Standard 2.1

Original author: Immo Landwerth
  • Transfer
Since we released .NET Standard 2.0 about a year ago, we have updated .NET Core 2.1 twice and are preparing for the release of .NET Core 2.2. It's time to upgrade to Standard: include some of the new concepts, as well as a number of small improvements that will make your life easier to work with many .NET products.

Read on to learn more about what's new in the latest version, and what you need to know about platform support, management and coding.

What's new in .NET Standard 2.1?

Only about 3 thousand new API plans will be added to .NET Standard 2.1. Most of them are new APIs. But there are old ones from other .NET implementations. They were added to bring together different .NET.

Here are the highlights:

  • Span <T>.
  • Foundational-API, working with Span.
  • Reflection emit.
  • SIMD.
  • ValueTask and ValueTask <T>.
  • DbProviderFactories.
  • Other cool improvements.

For more information, you can check out the list with all the API differences between .NET Standard 2.1 and .NET Standard 2.0. You can also use apisof.net to quickly check whether this API will be included in .NET Standard 2.1.

.NET concept

If you missed our updates on the concept of .NET Core 3.0 and .NET Framework 4.8 , more about this below:

  • The .NET Framework is a .NET implementation installed on more than one billion devices, and therefore must remain as compatible as possible. Because of this, the platform is developing more slowly than the .NET Core. Even security and error fixes can cause gaps in applications, because applications depend on previous settings. We will ensure that the .NET Framework always supports the latest network protocols, security standards, and Windows features.
  • The .NET Core is an open, cross-platform, and fast-paced version of .NET. Because of its nature, it can evolve in ways that we do not dare to develop the .NET Framework. This means that .NET Core will always receive new APIs and language support faster than the .NET Framework. At Build, we showed a demo of how much faster the API is in .NET Core. If we made the same changes to the .NET Framework, we could break existing applications, and we don't want to do that.

Authors of libraries that need to support .NET Framework clients must remain on .NET Standard 2.0. In fact, most libraries should be able to work on .NET Standard 2.0. However, this does not mean that authors cannot take advantage of the pluses of these APIs, even if they must support the .NET Framework.

For targeting recommendations, see the new cross-platform targeting documentation .


The formation of .NET Standard 2.1 continues. You can watch our progress on github .

If you want to quickly check if there is a specific API in the .NET Standard (or any other .NET platform), you can use apisof.net . You can also use the .NET Portability Analyzer to test the ability to transfer an existing project to .NET Standard 2.1.

Good coding!

Also popular now: