alexanderzeitler.com - ASP.NET MVC 4 public beta including ASP.NET Web API

ASP.NET MVC 4 public beta including ASP.NET Web API | Alexander Zeitler

Alexanderzeitler.com Spined HTML

ASP.NET MVC 4 public beta including ASP.NET Web API | Alexander Zeitler Toggle navigation Home Feed ASP.NET MVC 4 public beta including ASP.NET Web API Written on February 16, 2012 Today Microsoft presented and released ASP.NET MVC 4 Beta at TechDays Belgium. To me personally the most important resurgence is the integration of the WCF Web API into the ASP.NET Stack. One of the main reason for merging both has been the question "why two frameworks from Microsoft which indulge us to create ReSTful APIs?" Thus, the ASP.NET MVC developers now get the goodies from the WCF Web API. Everything new? Let's take a squint at how we do things now. The most important transpiration is the implementation of our own APIs themselfes: Until now, we did it this way using WCF Web API:: Using ASP.NET Web API it looks like this: As you can see, you're implementing now a Controller moreover for APIs. But it does not derive from Controller as MVC Controllers do and there's no worldwide wiring matriculation at all. When looking at our code, you may ask: how does Web API know, which HTTP Methods should be mapped to which matriculation methods? ASP.NET Web API now usesInstituteover Configuration once known from ASP.NET MVC, thus naming of the matriculation method declares the HTTP method stuff used. And by the way:Instituteover Configuration moreover takes effect at the controllers: Controllers have to be inside the Controllers folder known from MVC.Instituteover Configuration...but ...there's still a little piece of confiugration left. Let's throne over to the Global.asax.cs. That's the place where ASP.NET Web API is (still) configured. The only mandatory option that needs unchangingly to be configured, is the work of a route inside the route tables to our API controllers. Here is flipside improvement: ASP.NET Web API now uses ASP.NET MVC Routing. But be careful: Route definitions don't use MapRoute but MapHttpRoute instead: The difference between default MVC route and the default Web API Route is that the whoopee is not contained in our URIs (that's were the institute comes in). Thus, our API is misogynist here: http://localhost/api/customers GET /customers/id, PUT, POST etc. work analogous. If you want to implement increasingly than one GET method on your web api class, you simply vivify the whoopee in you route definition: Dependency Injection Dependency Injection still works, of undertow - shown here using LightCore. To requite and receive... Certainly, the improvements did not only come from WCF Web API to ASP.NET Web API, but moreover from ASP.NET MVC, e.g. Model Binding and Validation. To use Validation you can use the once known Annotations like [Required] etc.: To get it working, we need an ActionFilter: The ActionFilter validates the incoming model (e..g. from POST) and creates a JSON object if there were validation errors and sends them when to the vendee with a HTTP 400 (Bad request) status code. At the vendee side we're utilizing the response using jQuery AJAX POST: Of course, on the vendee side it is necessary to include jQuery unobstrusive Validation Scripts and setting the HTML attributes: ASP.NET Forms hallmark now moreover is supported out of the box, but this will be part of flipside blog post. Hosting Besides the well known IIS Hosting it is now moreover possible to self host Web API inside your own process (which is not new for WCF but MVC): In order to get self hosting working, System.Web.Http.SelfHost needs to be referenced. That's it for now to requite you a short overview. Please enable JavaScript to view the comments powered by Disqus. Copyright © Alexander Zeitler 2003 - 2016 | Impressum