Skip to main content

Farewell WCF Web API… Welcome ASP.NET Web API

***Important remark: this is all unofficial information I have found while browsing through the WCF Web API discussion board. So feel free to leave a comment if some of the things I’ve found are not correct.***
WCF Web API will die soon. But in it’s ashes a new API is born, this time based on ASP.NET instead of WCF.
I found the following information about this:
  • Web API will be coming late February as part of the ASP.NET MVC 4 beta.
  • RTM in Q3 2012
  • Will support ASP.NET 4.0, including a HttpClient implementation
  • ASP.NET Web API is not limited to only MVC4, possible to host in WebForms for example.
  • ASP.NET Web API is a separate assembly with no dependency on system.web.mvc.dll
  • Deep integration with MVC routing to identify resources, including default values and constraints
  • Web API uses MapHttpRoute() with a routeTemplate ("api/{controller}/{id}"), very similar to the MVC .MapRoute.
    • UriTemplates not attributes on methods anymore.
    • Discovers actions based on method name (Get, Post etc), but possible to override with attributes.
  • HttpOperationHandler replaced by MVC ActionFilters.
  • Authorization filter attributes, just like MVC
  • Exception filters
  • All stack is async Task based.
  • Web API classes inherit from ApiController base class
    • Instantiated per request, stateless
  • HTTP methods are now like MVC actions
  • Official site will probably be (not working at the moment): http://asp.net/web-api
  • HttpResponseException and HttpResponseMessage/Request still there
  • MVC-like model binding to input parameters
  • Model binding validation using filters and data annotations!
  • Message body bound to types using MediaTypeFormatters
  • Content negotiation supported based on Accept header
  • No static context objects
  • HttpRequestMessage.Properties is still the way to keep request context
  • Out-of-the box IOC integration through DependencyResolver
  • OData supported simply by returning IQueryable<T> from actions, the rest is automatic.
  • Web API/MVC ships with dynamic JsonObject types
  • Supports hosting in IIS or self-hosting.
  • Only a tiny bit of WCF left in there(in the self-host client).
  • Supports JSON.NET out of the box.

Popular posts from this blog

DevToys–A swiss army knife for developers

As a developer there are a lot of small tasks you need to do as part of your coding, debugging and testing activities.  DevToys is an offline windows app that tries to help you with these tasks. Instead of using different websites you get a fully offline experience offering help for a large list of tasks. Many tools are available. Here is the current list: Converters JSON <> YAML Timestamp Number Base Cron Parser Encoders / Decoders HTML URL Base64 Text & Image GZip JWT Decoder Formatters JSON SQL XML Generators Hash (MD5, SHA1, SHA256, SHA512) UUID 1 and 4 Lorem Ipsum Checksum Text Escape / Unescape Inspector & Case Converter Regex Tester Text Comparer XML Validator Markdown Preview Graphic Color B

Help! I accidently enabled HSTS–on localhost

I ran into an issue after accidently enabling HSTS for a website on localhost. This was not an issue for the original website that was running in IIS and had a certificate configured. But when I tried to run an Angular app a little bit later on http://localhost:4200 the browser redirected me immediately to https://localhost . Whoops! That was not what I wanted in this case. To fix it, you need to go the network settings of your browser, there are available at: chrome://net-internals/#hsts edge://net-internals/#hsts brave://net-internals/#hsts Enter ‘localhost’ in the domain textbox under the Delete domain security policies section and hit Delete . That should do the trick…

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.