ASP.NET Web API replaces WCF Web API

The new MVC 4 beta was released last Thursday / Friday.  One of the big changes is the moving of the WCF Web API into the ASP.NET MVC code stream.

Get the bits and the initial documentation on the ASP.NET Web API page at http://www.asp.net/web-api

The team has provided some initial guidance on migrating from the WCF Web API to ASP.NET Web API on the WCF CodePlex site.

ScottGu has an overview on his blog along with a video of a presentation that he gave at the Belgium and Dutch TechReady events.

Jon Galloway interviewed Brad Wilson about the ASP.NET MVC 4 release.  Brad Wilson on ASP.NET 4 Beta and ASP.NET Web API

Henrik Nielsen the Principal Architect on the WCF Team has a post on the new HttpClient for ASP.NET Web API that has been back ported from .NET 4.5.

I plan on migrating my current project using the WCF Web API and ASP.NET MVC 3 to the new ASP.NET Web API and ASP.NET MVC 4 API this week.  After spending a lot of time last week getting Ninject work work with the WCF Web API, it looks like the ASP.NET Web API makes it trivial.  But it was still a good learning experience right?

I am also contemplating moving to the new .NET 4.5 beta when it is released.  It looks like the asynchronous support on C# 5 will be very useful with the new ASP.NET Web API.