Skip to main content
microsoft.net.http package icon

microsoft.net.http

This package provides a programming interface for modern HTTP applications on .NET Framework 4, Silverlight 4 and 5, Windows Phone 7.5 and 8. This package includes HttpClient for sending requests over HTTP, as well as HttpRequestMessage and HttpResponseMessage for processing HTTP messages. This package also supports Portable Class Libraries. This package is not supported in Visual Studio 2010, and is only required for projects targeting .NET Framework 4.5 or .NET for Windows Store apps when consuming a library that uses this package. For known issues, please see: http://go.microsoft.com/fwlink/?LinkID=279987.

Total Downloads
145.1M
145,083,754
Published
Feb 18, 2013
Latest stable version

Install

.NET CLI
dotnet add package microsoft.net.http --version 2.1.3-beta
Package Manager Console
Install-Package microsoft.net.http -Version 2.1.3-beta
PackageReference
<PackageReference Include="microsoft.net.http" Version="2.1.3-beta" />

Frameworks

.NETFramework4.0 .NETFramework4.5 Windows8.0 .NETPortable0.0-net45+win8

Dependencies

[1.0.16-rc, )
[1.0.0-rc, )
Microsoft.Bcl.Build
.NETFramework4.0
[1.0.0-rc, )

Adoption guide

A verified publisher signal is available. Assess fit from the package's supported frameworks, license and dependency graph rather than popularity alone.

This version is marked prerelease. Validate its API and upgrade path before production use.

NuGet marks this package as deprecated. Review the publisher's migration guidance before adopting it.

No SPDX license expression is published. Review the license text and your organisation's policy before redistribution.

Compatibility metadata lists 4 target frameworks; confirm the exact target used by your application.

How to read this guidance

Sources: published NuGet v3 registry metadata and explicit NuBrowse editorial guides. Refresh: package metadata is refreshed from NuGet when the page loads. Limit: this is not a security, legal or compatibility guarantee; validate the selected version in your project.

Useful next steps

Move from package metadata to a concrete selection or review workflow.