Issue with resolving between .NET Standard 2.0 and .NET Standard 2.1 about standard HOT 3 CLOSED

Well, I think this is the correct behavior, since .NET Standard 2.1 is higher than .NET Standard 2.0 , and .Net Core 3.1 can use .NET Standard 2.1,
this is because .NET Standard 2.1 has much more api than .NET Standard 2.0 (the Span<T> and more) so library that target .NET Standard 2.1 can more optimization （for example , use Span<T> related type and api）

from standard.

Well, I think this is the correct behavior, since .NET Standard 2.1 is higher than .NET Standard 2.0 , and .Net Core 3.1 can use .NET Standard 2.1,
this is because .NET Standard 2.1 has much more api than .NET Standard 2.0 (the Span<T> and more) so library that target .NET Standard 2.1 can more optimization （for example , use Span<T> related type and api）

But from the project dependency hierarchy, it should be clear that ClassProject1 targets .NET Standard 2.0 only so shouldn't ClassProject2 be more restrictive by targeting .NET Standard 2.0 instead of 2.1?

from standard.

A method (ClassProject2Test1) on ClassProject2 is hidden behind a #if NETSTANDARD2_0 preprocessor directive.

This is a violation of normal versioning rules. If you multitarget for A and B (and B > A) than B must not have fewer APIs than A. Replace .NET Standard with .NET Core and then it should be easy to understand:

• TestProject1 targeting netcoreapp3.0
• ClassProject1 targeting netcoreapp2.0
• ClassProject2 targeting both netcoreapp2.0 and netcoreapp3.0

The application (TestProject1) will run on .NET Core 3.0. That means it will use the netcoreapp2.0 build of ClassProject1 (because it's the only option) and the netcoreapp3.0 of ClassProject2 (because it's the better match).

Does this make sense?

Closing as by-design.

from standard.