What are the standard .NET version rules?

Question

The .NET Standard prescribes an API that all .NET platforms must implement. What are its version control rules? This breaking.addingin which 1.4adds and remains backward compatible with 1.3, while 2.xnot backward compatible with 1.x?

The documentation for this is not clear. Some Microsoft docs point to pure backward compatibility:

For the .NET Standard Library version, you can use libraries designed for the same or lower version. (highlighted by me)

Now that 2.0 is missing, the above does not seem to be correct. This, as they say, is a post on the release blog :

From a library targeting the .NET Standard, you can refer to the [library targeting] .NET Standard if their version is less than or equal to the targeting of your version. (highlighted by me)

The same blog post contradicted saying:

In order for .NET Framework 4.6.1 to support .NET Standard 2.0, we had to remove all the APIs from .NET Standard that were implemented in .NET Standard 1.5 and 1.6.

Now that 2.0 is missing, what are the rules for version control? It seems to be breaking.adding. Where did the MSFT document this?

Answer 1

​​On.NET .NET.

, .NET Standard:

• .NET , . , API.NET Standard , API.
• .NET .NET Standard.
• .NET :
  • , API-
  • , .NET .

? , .NET Standard 1.x . .NET Standard 1.5 1.6 . ,.NET Standard 2.0 .NET Standard 1.4.

. .NET Standard 2.0: .NET Framework 4.6.1 .NET Standard.a >

. . .NET Standard FAQ.