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.
Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

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.
Read more

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more