Aug 04

Since starting the project in Jan 2015 one of the most asked for features has been full static support (you have always been able to cast responses via duck typing). Inspired by libraries written in dynamic languages like JavaScript and Python – the idea behind RestClient was to reduce the fiction and ceremony when working with Rest API’s, and later on HTTP in general.

I’ve always wanted to add static typing to be more inline with what is expected from a C# library, but wanted to do it in such way that the original concept remained, and that all code is backwards compatible. I’ve now spent the time required to change the package, and this is the result:

DalSoft Rest Client https://github.com/DalSoft/DalSoft.RestClient

Continue reading »

Tagged with:
Feb 22

CodeMaze have written a great post with real world examples of using C# and DalSoft.RestClient to consume any REST API. It includes everything you need to know head over there now if you find yourself writing a lots of boilerplate code to consume REST API’s.

Tagged with:
Jul 21

During this series of posts I’m going to share with you how I work with WebApi. I’m going to share the steps with you so you understand exactly what is going on and the choices made. There of course is a GitHub repo you can folk and use in your own projects.

Being a consultant I have to create REST API’s (or as I like to say ‘RESTish API’s’*) a lot, I’m going to show you how I do it. When you create your WebApi project your first instinct might be to select the WebApi project template, I would resist doing it like that.

Not because there is anything wrong with using the templates, because there ins’t I’ve used both the WebApi and MVC templates as learning tools as well as for quick hacks. That said that’s what you should use them for – here are my reasons for saying that:

  • So much of the config is done for you that it can be difficult to understand what’s going on, what if you need to change the config or had a deployment issue would you be confident in making changes?
  • So many extra packages are added that you probably don’t need.
  • It’s not Owin backed.

Continue reading »

Tagged with:
May 14

Earlier this year I posted about a pet project I’ve been working on DalSoft.RestClient which is a dynamic C# rest client.

I’ve now used it on a number of projects, and it works really for fluently accessing rest api’s (if I do say so myself). So I thought I’d do a quick post on a real life scenario. For a client of mine I’ve recently needed to integrate PushWoosh, so I thought I’d share some code to show how easy it would be to create a PushWoosh SDK with DalSoft.RestClient.

Continue reading »

Tagged with:
Jan 26

Whenever I’ve wanted to create a SDK for my WebApi’s I’m surprised by the amount of bolierplate code you end up with. HttpClient made things easier for us, but you still end up wrapping HttpClient and passing generics around.

I wanted something between Simple.Data and angular’s $http service, the main driver was to make my tests as readable as possible. I’ve messed around with .NET 4 dynamic objects before, so I set about creating a dynamic wrapper around HttpClient and a fluent API I could re-use. It’s passed the rule of 3 as I’ve used it for multiple clients. A side note is that it should be trivial to generate DalSoft.RestClient code examples in your WebApi docs.

Continue reading »

Tagged with:
preload preload preload