DocaLabs.Http.Client.with.NewtonSoft.Json.Serializer
2.0.0.1
See the version list below for details.
dotnet add package DocaLabs.Http.Client.with.NewtonSoft.Json.Serializer --version 2.0.0.1
NuGet\Install-Package DocaLabs.Http.Client.with.NewtonSoft.Json.Serializer -Version 2.0.0.1
<PackageReference Include="DocaLabs.Http.Client.with.NewtonSoft.Json.Serializer" Version="2.0.0.1" />
paket add DocaLabs.Http.Client.with.NewtonSoft.Json.Serializer --version 2.0.0.1
#r "nuget: DocaLabs.Http.Client.with.NewtonSoft.Json.Serializer, 2.0.0.1"
// Install DocaLabs.Http.Client.with.NewtonSoft.Json.Serializer as a Cake Addin #addin nuget:?package=DocaLabs.Http.Client.with.NewtonSoft.Json.Serializer&version=2.0.0.1 // Install DocaLabs.Http.Client.with.NewtonSoft.Json.Serializer as a Cake Tool #tool nuget:?package=DocaLabs.Http.Client.with.NewtonSoft.Json.Serializer&version=2.0.0.1
Strong typed HTTP client with provider using. 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. |
-
- DocaLabs.Http.Client (>= 2.0.0.1)
- Newtonsoft.Json (>= 5.0.6)
NuGet packages (1)
Showing the top 1 NuGet packages that depend on DocaLabs.Http.Client.with.NewtonSoft.Json.Serializer:
Package | Downloads |
---|---|
My.Demo.Package2
Demo package |
GitHub repositories
This package is not used by any popular GitHub repositories.
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