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
Currently, the library supports three Target Framework Monikers:
NET45
NET46
NETSTANDARD1.5
However, this seems a bit redundant. If we support .NET 4.5, the lowest full framework TFM we can target at the moment, we also implicitly support 4.6, 4.6.1, 4.7, etc. Why do we explicitly specify .NET 4.6 then?
Currently, the library supports three Target Framework Monikers:
However, this seems a bit redundant. If we support .NET 4.5, the lowest full framework TFM we can target at the moment, we also implicitly support 4.6, 4.6.1, 4.7, etc. Why do we explicitly specify .NET 4.6 then?
With .NET Standard 1.5 we can run on the full framework in any application targeting .NET 4.6.2 or higher and in .NET Core 1.0 or higher. For consumers being stuck (for the moment?) at older versions of .NET we can give them 4.5.
So, in summary: Wouldn't it be enough to just target NET45 and NETSTANDARD1.5?
The text was updated successfully, but these errors were encountered: