DocaLabs.Http.Client 2.0.0.1

.NET Framework
There is a newer version of this package available.
See the version list below for details. 
dotnet add package DocaLabs.Http.Client --version 2.0.0.1
NuGet\Install-Package DocaLabs.Http.Client -Version 2.0.0.1
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="2.0.0.1" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
paket add DocaLabs.Http.Client --version 2.0.0.1
#r "nuget: DocaLabs.Http.Client, 2.0.0.1"
#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=2.0.0.1

// Install DocaLabs.Http.Client as a Cake Tool
#tool nuget:?package=DocaLabs.Http.Client&version=2.0.0.1

Strong typed HTTP client. The main goal of the library is to minimize plumbing code to bare minimum.

Product 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.

Version Downloads Last updated
3.0.0 17,323 10/28/2013
2.0.1.2 1,412 9/19/2013
2.0.0.1 1,586 9/16/2013
1.0.1.2 1,196 9/6/2013
1.0.1.1 1,703 4/2/2013
1.0.1 1,272 2/28/2013
1.0.0 1,272 2/23/2013

There are a lot of changes and enhancements. Some major improvements:
* Ability to map a model properties into the URL's path, e.g. if the RUL is specified like http://foo.com/accounts/{id} and the model as a property named id then the value of that property will be mapped into the path in place of {id}.
* Ability to specify that some properties must be added as headers, a property must be either marked by the RequstUse(RequestUseTargets.RequestHeader) attribute or be of WebHeaderCollection type.
* Ability to supply credentials in the model, a property should be of ICredentials type
* Special treatment of Stream as input or output models.
* HttpClientFactory will be able to generate plumbing to service call methods that have more than one argument - it'll generate a model class with properties for each argument.
* Binding is made more flexible, it's possible to do custom binding per model type for each step in the pipeline - mapping properties to the URL, headers, credentials, writing to request body.
* Ability to get some information about the response - headers, etag, status code