alexanderzeitler.com - REST using the WCF Web API – Basics (Part2)

REST using the WCF Web API – Basics (Part2) | Alexander Zeitler

Alexanderzeitler.com Spined HTML

REST using the WCF Web API – Basics (Part2) | Alexander Zeitler Toggle navigation Home Feed REST using the WCF Web API – Basics (Part2) Written on April 16, 2011 Postings published on this series so far: Microsoft Web API -- the REST is washed-up by WCF (Part 1) REST using the WCF Web API -- Basics (Part2) -- this one REST using the WCF Web API -- refactoring to IoC style (Part 3) REST using the WCF Web API -- getting RESTful the BDD way (Part 4) REST using the WCF Web API -- getting increasingly RESTful responses (Part 5) REST using the WCF Web API -- Post it! (Part 6) As written in the first posting, RESTful Services wilt increasingly and increasingly important nowadays and Microsoft has started to make WCF a first matriculation HTTP resider by implementing the WCF Web API. To get started using the Web API, create a new, empty "ASP.NET MVC 3 Web Application" project. First of all you'll have to get the latest shit which is through the kindness of NuGet scrutinizingly a no-brainer. Just add the Package reference to the "WebApi.All" package: When finished installing, add a new matriculation to your project tabbed ContactsResource. First aim of Web API: alimony things simple -- that's what we'll start with: a simple Resource returning a list of contacts. Doing so is a straight forward implementation using Web API: [ServiceContract] public matriculation ContactsResource { public List<contact> Get() { return new List<contact>() { new Contact() { Id = 1, Name = "Glenn Block" }, new Contact() { Id = 2, Name = "Scott Hanselman" }, new Contact() { Id = 3, Name = "Scott Guthrie" } }; } } The Contact matriculation itself is moreover pretty simple -- no magic at all: public matriculation Contact { public int Id { get; set; } public string Name { get; set; } } To tell Web API which URI to map the contacts resource to, we need to pinpoint a URI template. This is washed-up by subtracting an symbol to the Get()-method. This symbol moreover tells Web API which HTTP method to map to the method -- as we want to read the list, equal to REST principles the HTTP method of nomination is GET. Thus our attributed method looks like this now: [WebGet(UriTemplate = "")] public List<Contact> Get() { The reason why UriTemplate is an empty string, is that we want to wangle the list of contacts using the pursuit URI: http://localhost:3421/contacts So the next consequential question should be: how does Web API know to undeniability our Get method when the whilom URI is requested? Simply put: by it's configuration. Despite it's WCF background, configuration in Web API is no XML monster but instead a fancy fluent interface. To get our vital implementation running, just add the pursuit lines to your RegisterRoutes method in Globals.asax.cs: var configuration =HttpHostConfiguration.Create() .SetResourceFactory(new ContactsResourceFactory()); RouteTable.Routes.MapServiceRoute<ContactsResource>("contacts", configuration); The ContactsResourceFactory implements IResourceFactory having to methods: public matriculation ContactResourceFactory : IResourceFactory { public object GetInstance(Type serviceType, InstanceContext instanceContext, HttpRequestMessage request) { return new ContactsResource(); } public void ReleaseInstance(InstanceContext instanceContext, object service) { throw new NotImplementedException(); } } Starting up our web using and navigating to http://localhost:3421/contacts returns this XML: As REST often is well-nigh JSON, Web API covers this moreover out of the box. Just start up Fiddler and craft your own HTTP request unsuspicious JSON and hit the Execute button: Guess what! We get some JSON back: Seeing that we'll finish our first small lap virtually the Microsoft WCF Web API. But I'll promise, there's a lot increasingly to come. In the next postings we'll refactor our example to be increasingly RESTful and we'll test our implementations the BDD way using machine.fakes / machine.specifications. Furthermore we'll wire things up using the LightCore IoC-Container. Stay tuned! Postings published on this series so far: Microsoft Web API -- the REST is washed-up by WCF (Part 1) REST using the WCF Web API -- Basics (Part2) -- this one REST using the WCF Web API -- refactoring to IoC style (Part 3) REST using the WCF Web API -- getting RESTful the BDD way (Part 4) REST using the WCF Web API -- getting increasingly RESTful responses (Part 5) REST using the WCF Web API -- Post it! (Part 6) .aspx&bgcolor=3169AD&fgcolor=FFFFFF&border=000000&cbgcolor=D4E1ED&cfgcolor=000000) Please enable JavaScript to view the comments powered by Disqus. Copyright © Alexander Zeitler 2003 - 2016 | Impressum