Consider adding a target for net461 — why?

[qbit86]

> Using .NET Standard 2.0 from .NET Framework has some issues that were addressed in .NET Framework 4.7.2.

Could you please elaborate more on this? Which issues? What exactly are we solving by targeting net461 in addition to just netstandard2.0?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 5b3638c9-ea3c-1c9e-2763-5c3e8e965663
• Version Independent ID: aff99d6b-9471-9277-160b-670ee8028b53
• Content: Cross-platform targeting for .NET libraries
• Content Source: docs/standard/library-guidance/cross-platform-targeting.md
• Product: dotnet
• GitHub Login: @JamesNK
• Microsoft Alias: mairaw

[JamesNK]

@terrajobst Do you know of a blog post or article that discusses the issues netstandard2.0 has with net461? I'll add a link to it in the docs.

[terrajobst]

Not yet :-(

[gallivantor]

I thought .NET 4.7.1 fully implemented .NET Standard 2.0... if this is not the case then more detail should definitely be provided about what the problem is

The best I can find about 4.7.1 is this comment on this blog post: https://blogs.msdn.microsoft.com/dotnet/2018/04/30/announcing-the-net-framework-4-7-2/

The .NET Framework 4.7.1 added eight properties to the System.Net.Http.HttpClientHandler class. However, two threw a PlatformNotSupportedException. The .NET Framework 4.7.2 now provides an implementation for these properties. The properties are:

• CheckCertificateRevocationList
• SslProtocols

In .NET Framework 4.7.2 we have addresses the known runtime issues with .NET Standard 2.0. We made changes to the runtime to ensure that you don’t need additional files deployed along with your .NET Standard library. This would also remove the need to have binding redirects generated in your application that consumes a .NET Standard library.

[mairaw]

@terrajobst is there a quick explanation here you can add on why we're recommending this?

[dotnet-bot]

This issue has been closed as part of the issue backlog grooming process outlined in #22351.

That automated process may have closed some issues that should be addressed. If you think this is one of them, reopen it with a comment explaining why. Tag the @dotnet/docs team for visibility.