Misleading documentation for ServicePointManager.ReusePort

Dotnet documentation for ServicePointManager.ReusePort is misleading. It currently indicates

Setting this property value to true causes all outbound TCP connections from HttpWebRequest to use the native socket option SO_REUSE_UNICASTPORT on the socket

However, as @wfurt has indicated on another thread,

HttpClient does not use ServicePointManager @aaronla-ms. The whole strategy changes and .NET Core does not depend or use single global setting and ServicePointManager is obsolete.

This documentation should be updated to indicate accurate information for various framework versions. E.g. indicate in netcore / net5.0+ that the API no longer functions as described, and is obsolete (though not attributed as such). For NET Standard, should indicate that the API only functions as intended on .NET Framework, and is nonfunctional on .NET Core / net5.0+

Target framework

• .NET Core
• .NET Framework
• .NET Standard

The documentation is accurate for .NET Framework. The behavior change was an intentional one made during dotnet core development, so documentation update is only needed for .NET Standard and .NET Core.

dotnet --info output or About VS info

<replace>

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Dotnet documentation for ServicePointManager.ReusePort is misleading. It currently indicates

Setting this property value to true causes all outbound TCP connections from HttpWebRequest to use the native socket option SO_REUSE_UNICASTPORT on the socket

However, as @wfurt has indicated on another thread,

HttpClient does not use ServicePointManager @aaronla-ms. The whole strategy changes and .NET Core does not depend or use single global setting and ServicePointManager is obsolete.

This documentation should be updated to indicate accurate information for various framework versions. E.g. indicate in netcore / net5.0+ that the API no longer functions as described, and is obsolete (though not attributed as such). For NET Standard, should indicate that the API only functions as intended on .NET Framework, and is nonfunctional on .NET Core / net5.0+

Target framework

• .NET Core
• .NET Framework
• .NET Standard

The documentation is accurate for .NET Framework. The behavior change was an intentional one made during dotnet core development, so documentation update is only needed for .NET Standard and .NET Core.

dotnet --info output or About VS info

<replace>

Author:	aaronla-ms
Assignees:	-
Labels:	:watch: Not Triaged, Pri3, area-System.Net
Milestone:	-

[rgroenewoudt]

Most properties on ServicePointManager aren't implemented in .NET Core/5+: https://github.com/dotnet/runtime/blob/a8a10f81bfc289a346ed815f9d064967f9537a30/src/libraries/System.Net.ServicePoint/ref/System.Net.ServicePoint.cs#L42

For example DefaultNonPersistentConnection says "This field is constant but is no longer used as of .NET Framework 2.0". I would expect something similar for all properties in ServicePointEndManager telling readers that it's not used in .NET Core or .NET5+.

[MihaZupan]

We should mark all the unused static members as [Obsolete] as well

[MihaZupan]

The ServicePointManager type was obsoleted in dotnet/runtime#103456