Sorry but we messed up. We tried to make .NET Framework 4.6.1 retroactively implement .NET Standard 2.0. This was a mistake as we don't have a time machine and there is a tail of bugs.
If you want to consume .NET Standard 1.5+ from .NET Framework, I recommend to be on 4.7.2.
If you want to consume .NET Standard 1.5+ from .NET Framework, I recommend to be on 4.7.2.
https://twitter.com/marcgravell/status/1031867348876189696
Note that that this has nothing to do with missing APIs (although .NET Framework 4.6.1 misses about 100 APIs). It's all about binding policy, assembly identities, and treatment of framework assemblies in tooling (MSBuild, ClickOnce, test runners etc).
The lesson learned here is simple: once shipped, a given version of a .NET implementation must not change the support level of .NET Standard. IOW, the supported .NET Standard number is an immutable property. Supporting a higher version requires shipping a new version.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
