The current status of System.Net.Http vs. Microsoft.Net.Http
<p>I am confused with packaging of <code>HttpClient</code>. Earlier it was distributed as a part of <code>Microsoft.Http.Net</code> NuGet package while <code>System.Net.Http</code> was considered legacy. Looks like now it's the opposite: there is a fresh <code>System.Net.Http</code> package for all platforms and <code>Microsoft.Net.Http</code> has not been updated in a while and according to folks at Microsoft development team is going to be deprecated.</p>

<p>Questions then:</p>

<ul>
<li>Can we replace dependencies on <code>Microsoft.Net.Http</code> NuGet package with (the newest) <code>System.Net.Http</code>?</li>
<li>Should legacy .NET 4.0 platform still use <code>Microsoft.Net.Http</code>?
What about non-Windows platforms (iOS, Android)? The new <code>System.Net.Http</code> supports them, but I remember with <code>Microsoft.Net.Http</code> I had to install additionally <code>Microsoft.Bcl.Build</code> and <code>Microsoft.Bcl</code> in order to get cross-platform stuff to work. <code>System.Net.Http</code> doesn't depend on them. Can Bcl packages be skipped?</li>
<li><code>System.Net.Http</code> lacks some Http extension methods, like <code>SupportsPreAuthenticate</code>, and an attempt to call these method results in runtime errors (missing method). How should we deal with this?</li>
</ul>