You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I see that you changed from .NET Standard 2.0 to 2.1 in 1d99a30. Why was this done? I don't see any other commits that use functionality that doesn't exist in .NET Standard 2.0.
We'd like to use this library, but since we are targeting .NET Standard 2.0 (and since it doesn't require extra configuration, testing on .NET Core 2.1) it is not compatible with all of our targets. To prevent versioning conflicts, it has always been Microsoft's recommendation to target the lowest version you can when building shared libraries. On the .NET Standard page:
We recommend you target the lowest version of .NET Standard possible.
Of course, .NET Standard 1.x is pretty much moot since .NET Core 1.x went out of support, but .NET Standard 2.0 is still the "standard" way that most libraries use to eliminate multi-targeting.
The text was updated successfully, but these errors were encountered:
NightOwl888
added a commit
to NightOwl888/LiquidTestReports
that referenced
this issue
Nov 17, 2020
I see that you changed from .NET Standard 2.0 to 2.1 in 1d99a30. Why was this done? I don't see any other commits that use functionality that doesn't exist in .NET Standard 2.0.
We'd like to use this library, but since we are targeting .NET Standard 2.0 (and since it doesn't require extra configuration, testing on .NET Core 2.1) it is not compatible with all of our targets. To prevent versioning conflicts, it has always been Microsoft's recommendation to target the lowest version you can when building shared libraries. On the .NET Standard page:
Of course, .NET Standard 1.x is pretty much moot since .NET Core 1.x went out of support, but .NET Standard 2.0 is still the "standard" way that most libraries use to eliminate multi-targeting.
The text was updated successfully, but these errors were encountered: