…alue == string.Empty instead of just checking if value == null.

Another fix for ExecuteAsync

Added CONTRIBUTING.markdown to repository

XmlAttributeDeserializer crashes if value == ""

When adding an Accepts header to the request, this shouldn't be put into
DefaultParameters.  Repeated requests through the same RestClient instance
were adding the Accepts header every time, resulting in a large memory
leak because DefaultParameters was growing without bound.

Instead, only add the header for this particular request.

Implement the ability for the body of a PUT or POST to be specified using
a byte array, rather than a string.  This avoids the roundtrip through
UTF-8 and back again if the caller already has a byte array.

…ostParameters.

Added ConfigureProxy(http) to the end of ConfigureHttp(request, http).
Removed call to ConfigureProxy(http) in Execute().

…364

Added support for token type in OAuth2Authenticator. fixes #364

…ET and POST specific usage and added overloads without CancellationToken

…tSharp

…T> from regular request.

- Modified Deserialize<T> so that the deserialization is only preformed when the request returned successfully. This because the current implementation threw an useless error when for example the request timed out and no correct header was present to be processed. This error was not cought and even if it was it would override the source error already stored in the request object.

In addition to this, a bare object was returned even when there was nothing to deserialize (invalid request, ex. 404). The returned object should of been null.

For anyone copying and pasting your example (like me) - you can get started a little bit quicker :)

…d just after starting.

…Aborted"

VS seems to be out of sync an doing strange things hence the odd commits

Implemented multipart/form-data POSTS with only parameters and without
files.

MSBuildBinPath was replaced with MSBuildToolsPath after VS2005.
MSBuildBinPath was kept around for back-compat, but is no longer
needed. The extra import causes unnecessary build warnings.

See http://msdn.microsoft.com/en-us/library/bb397428.aspx for
a full discussion.

This fixes #346

Since SimpleJson.cs is a linked file, only one project should have a
packages.config entry for it, the one with the actual file. The others
will fail trying to update a linked file.

I removed the SimpleJson packages.config entry for all the other
projects. I left it in RestSharp\packages.config

Remove redundant MSBuildBinPath import

Upgraded SimpleJson to 0.25

Remove JSON.NET from unit test project

IRestResponse instead of RestResponse

Fixed System.Net.ProtocolViolationException issue cause of missed the ContentLength property

This fixes a mistake in my previous commits.

In mono there is no setter for the ClientCertificates property on the WebRequest
class, and therefore it throws a NotSupportedException. However, if the collection
is empty upon access a new instance is added and returned, thus, one can simply
add the current certificates to the request's certificate collection.

…esponse method.

…8 and RFC2396