ASP.NET MVC4 Killer Feature: Auto Conneg

There once was a project called the ASP.NET Web API but that is dead and gone. It’s features all merged into ASP.NET MVC4. For us that means that out of the box, building REST web services, just got a shit ton easier.

When creating RESTish services with MVC there are some things we need to handle and some places we don’t exactly have the right size legos to make it all look nice.

  • Routing
  • Content Negotiation
  • Verbs – attributes all over the damn place [HttpGet], etc

 

Content Negotiation!

If you ask for JSONyou get JSON, if you ask for xml you get xml! if you don’t specify you get XML…just kidding, you get JSON! The best part: You have a way to extend it build in! with the DelegatingHandler class.

Pedro Reys has an article that, while he does not like that it defaults to JSON, is a good overview of the feature.

http://pedroreys.com/2012/02/17/extending-asp-net-web-api-content-negotiation/#

Release Notes

http://www.asp.net/whitepapers/mvc4-release-notes#_Toc317096197

ASP.NET Web API

ASP.NET MVC 4 now includes ASP.NET Web API, a new framework for creating HTTP services that can reach a broad range of clients including browsers and mobile devices. ASP.NET Web API is also an ideal platform for building RESTful services.

ASP.NET Web API includes support for the following features:

  • Modern HTTP programming model: Directly access and manipulate HTTP requests and responses in your Web APIs using a new, strongly typed HTTP object model. The same programming model and HTTP pipeline is symmetrically available on the client through the new HttpClient type.
  • Full support for routes: Web APIs now support the full set of route capabilities that have always been a part of the Web stack, including route parameters and constraints. Additionally, mapping to actions has full support for conventions, so you no longer need to apply attributes such as [HttpPost] to your classes and methods.
  • Content negotiation: The client and server can work together to determine the right format for data being returned from an API. We provide default support for XML, JSON, and Form URL-encoded formats, and you can extend this support by adding your own formatters, or even replace the default content negotiation strategy.
  • Model binding and validation: Model binders provide an easy way to extract data from various parts of an HTTP request and convert those message parts into .NET objects which can be used by the Web API actions.
  • Filters: Web APIs now supports filters, including well-known filters such as the [Authorize] attribute. You can author and plug in your own filters for actions, authorization and exception handling.
  • Query composition: By simply returning IQueryable<T>, your Web API will support querying via the OData URL conventions.
  • Improved testability of HTTP details: Rather than setting HTTP details in static context objects, Web API actions can now work with instances of HttpRequestMessage and HttpResponseMessage. Generic versions of these objects also exist to let you work with your custom types in addition to the HTTP types.
  • Improved Inversion of Control (IoC) via DependencyResolver: Web API now uses the service locator pattern implemented by MVC’s dependency resolver to obtain instances for many different facilities.
  • Code-based configuration: Web API configuration is accomplished solely through code, leaving your config files clean.
  • Self-host: Web APIs can be hosted in your own process in addition to IIS while still using the full power of routes and other features of Web API.