restsharp/RestSharp — pull request #477 by mbp (2013-12-02 12:48:48+00:00)
Title: Remember to map ErrorException along with other properties

This change is quite simple, When using the generic Execute overload, ErrorException was not set (even though ErrorMessage) was.

The following code gives me the ability to handle any exception occured - for example "Connection refused":

var restClient = new RestClient(url);
var response = restClient.Execute(new RestRequest());
// response.ErrorException is set

However using the overload of Execute which takes a Dto to deserialize into, works differently:

var restClient = new RestClient(url);
var response = restClient.Execute(new RestRequest());
// response.ErrorException is not set