RestSharp has recently released a major new version with a lot of breaking changes. One of the things to change was custom authenticators which now seem to be less obvious to use. The documentation suggests creating a custom authenticator by inheriting from IAuthenticator but this doesn’t seem to work and Read more…
When serializing object to JSON using Newtonsoft it’s possible to change the naming of the properties by updating the serializer naming conventions as detailed here. It’s also possible to create your own custom naming strategy if none of the inbuild ones do the dop. This can be done by inheriting Read more…
I’m currently using RestSharp as a client for downloading product details, however it appears that the response from the server (which I have no control over) is encoded in a differerent character set (ISO-8859-1) than RestSharp is expecting (UTF-8). This means that although most characters are converted as expected, some Read more…
I’ve been needing to access the AWS S3 API recently as part of a project and although there’s a pretty good client already available it didn’t quite meet my needs so I decided I needed to build my own client based on RestSharp. Unfortunatly although the API is pretty simple Read more…
There are various ways of authenticating against Azure Functions but the default method is by providing a code value as a URL parameter in the call to the endpoint. If you’re using RestSharp to call your function there’s no specific authenticator to manage handling this parameter but it is pretty Read more…