Comments on: Using RestSharp to consume RESTful Web Services

By: mstum

mstum — Wed, 11 Jan 2012 04:38:35 +0000

Seems to work again, possibly a temporary outage.

By: Enrique

Enrique — Mon, 09 Jan 2012 22:11:47 +0000

request.BaseUrl = "http://carma.org"; <---- Unavailable!!!

By: The Morning Brew - Chris Alcock » The Morning Brew #504

The Morning Brew - Chris Alcock » The Morning Brew #504 — Wed, 23 Dec 2009 08:29:36 +0000

[...] Using RestSharp to consume RESTful Web Services - Michael Stum shows how the RestSharp library helps make consuming RESTful web services easier from C# illustrating with a simple example consuming a search serivce [...]

By: uberVU - social comments

uberVU - social comments — Tue, 22 Dec 2009 23:54:33 +0000

Social comments and analytics for this post...

This post was mentioned on Twitter by mstum: blogged: Using RestSharp to consume RESTful Web Services - http://www.stum.de/2009/12/22/using-restsharp-to-consume-restful-web-services/...

By: mstum

mstum — Tue, 22 Dec 2009 22:02:57 +0000

Thanks for the notice, I've changed it. I'll have a look at the Automatic-Name-Matching. In my own fork on GitHub I've added an Attribute to arbitrarily Map, but I'm not sure if more attribute-spam is the better solution. Well, maybe having 'ugly' classes is also a good way to encourage writing Business Classes I'll have a look soon to see if two things can be improved: List requires the Class Name to match the XML Element, so I had to name the Class "item" instead of "PowerPlantDTO". And I wonder if Execute could take a type converter (I think there is a Converter interface or similar in the CLR) to convert the "Model Class" into a "Business Class" directly. I'm not sure about this though (separation of concerns...). The big reason to use RestSharp is still to avoid having to parse 4-layers-nested-XML manually

By: John Sheehan

John Sheehan — Tue, 22 Dec 2009 21:30:03 +0000

One more note (again, there needs to be docs for this) that you can name your model class properties using pascal casing and RestSharp will match them up when deserializing the XML. If your property name is MetroArea it would first look for an XML element named 'MetroArea' and if it can't find one, it then looks for 'metroarea' and failing that it looks for 'metro_area'. You can see the code that does that here: http://github.com/johnsheehan/RestSharp/blob/master/RestSharp/Deserializers/XmlDeserializer.cs#L147

By: John Sheehan

John Sheehan — Tue, 22 Dec 2009 21:23:16 +0000

Great post Michael! Thanks for taking the time to write this up. My only suggestion is to use request.AddParameter(name, value) or request.AddParameter(Parameter) instead of request.Parameters.Add(); since it's a little more terse and there's a chance that collection might not be so exposed in the future. A minor nit from an overall excellent article. If there were docs it might be more obvious....I wonder who's fault that is

Thanks again. It will be really nice to have another intro article to point people to.

By: Tweets die Not Rocket Science » Using RestSharp to consume RESTful Web Services erwähnt -- Topsy.com

Tue, 22 Dec 2009 21:14:45 +0000

[...] Dieser Eintrag wurde auf Twitter von John Sheehan und Michael Stum, RestSharp erwähnt. RestSharp sagte: RT @mstum: blogged: Using RestSharp to consume RESTful Web Services - http://www.stum.de/2009/12/22/using-restsharp-to-consume-restful-w ... [...]