Edit: This happens only when using .NET Framework. In .NET Core/Standard land, the latest System.Net.Http
assembly version seems to be always 4.1.2.0 – there is no 4.2.0.0 version available.
The issue regarding System.Net.Http is way, way more complicated then the answers here seem to imply…
- Yes, there is a
System.Net.Http
NuGet package, but no, it will not install the latest version of the same assembly (it contains version 4.1.1.2 of theSystem.Net.Http
assembly, not 4.2.0.0).
Update 19Mar2022: the latest NuGet package Version 4.3.4 has assembly version 4.1.1.3, assembly version 4.2.0.0 still is not directly installed. - Latest Microsoft Visual Studio (or Microsoft Visual Studio Build Tools) provides version 4.2.0.0, but that does not mean your .csproj will always use it…
- For some reason (which I was not able to understand yet), the only guaranteed way of using 4.2.0.0 is by referencing certain NuGet packages that uses it, such us
System.Buffers
(version 4.5.0 worked for me).
TL;DR:
Add System.Buffers
4.5.0+ NuGet reference to your project, if you want to make sure it is using System.Net.Http
4.2.0.0 assembly.
References: