Update static usage remarks

[rasitha1]

Summary

Static usage is not the only best option and can be problematic for long running apps. Provide awareness of the HttpClientFactory to the reader and other safe ways of instantiating HttpClient along with using DI.

Fixes #1326

[ghost]

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

Issue Details

---

Summary

Static usage is not the only best option and can be problematic for long running apps. Provide awareness of the HttpClientFactory to the reader and other safe ways of instantiating HttpClient along with using DI.

Fixes dotnet/docs#1327

Author:	rasitha1
Assignees:	-
Labels:	area-System.Net.Http
Milestone:	-

[opbld33]

Docs Build status updates of commit 0ca56b0:

✅ Validation status: passed

File	Status	Preview URL	Details
xml/System.Net.Http/HttpClient.xml	✅Succeeded	View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

[CarnaViire]

Hi @rasitha1
The team's current view is that HttpClientFactory is not a recommended way for a general case. Especially if the app doesn't use DI and has no need in it.
The recommended way to overcome DNS problems is to use PooledConnectionLifetime property of SocketsHttpHandler.
Unfortunately the latter is not well advertised in the moment.
We have an issue in our pipeline to rework current HttpClient documentation: dotnet/docs#26510. Please feel free to discuss your suggestion in that issue.