DocaLabs.Http.Client
1.0.1.2
There is a newer version of this package available.
See the version list below for details.
See the version list below for details.
dotnet add package DocaLabs.Http.Client --version 1.0.1.2
NuGet\Install-Package DocaLabs.Http.Client -Version 1.0.1.2
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="DocaLabs.Http.Client" Version="1.0.1.2" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add DocaLabs.Http.Client --version 1.0.1.2
The NuGet Team does not provide support for this client. Please contact its maintainers for support.
#r "nuget: DocaLabs.Http.Client, 1.0.1.2"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install DocaLabs.Http.Client as a Cake Addin #addin nuget:?package=DocaLabs.Http.Client&version=1.0.1.2 // Install DocaLabs.Http.Client as a Cake Tool #tool nuget:?package=DocaLabs.Http.Client&version=1.0.1.2
The NuGet Team does not provide support for this client. Please contact its maintainers for support.
Strong typed HTTP client. The main goal of the library is to minimize plumbing code to bare minimum.
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET Framework | net is compatible. |
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.
This package has no dependencies.
NuGet packages (1)
Showing the top 1 NuGet packages that depend on DocaLabs.Http.Client:
Package | Downloads |
---|---|
DocaLabs.Http.Client.with.NewtonSoft.Json.Serializer
Strong typed HTTP client with provider using. The main goal of the library is to minimize plumbing code to bare minimum. |
GitHub repositories
This package is not used by any popular GitHub repositories.
removed charset from application/json serialization as it shouldn't be there. According http://www.ietf.org/rfc/rfc4627.txt can be figured out from the first character.