Web api migration

[ardalis]

A simple article on migrating a Web API 2 project to ASP.NET 5. Includes new /samples/ folder in aspnet/docs root.

[danroth27]

For RC we will be renaming the ASP.NET 5 Class Library and ASP.NET 5 Console Application templates to something more generic that fits their purpose. We will need to track updating the screen shots accordingly.

ASP.NET 5 Class Library will be renamed to Class Library (Package).
ASP.NET 5 Console Application will be renamed to either Console Application (Package) or Command Library (Package), it's still being debated.

[danroth27]

Also, the ASP.NET dialog is getting some cleanup. The template names will just be Empty, Website and Web API.

[danroth27]

From ASP.NET Web API 2 to MVC 6

[danroth27]

There are a bunch of subtle changes to attribute routing in MVC 6 that need to be addressed somewhere. @rynowak is probably the best person to detail the main differences

[danroth27]

There are a number of topics related to migrating Web API 2 code that are not addressed by this article:

• Migrating HttpConfiguration logic to the MvcOptions pattern
• Migrating message handlers to middleware
• Migrating formatters to the new formatter model (less common)
• Using the Microsoft.AspNet.Mvc.WebApiCompatShim package if you are porting a lot of Web API 2 code and you want to use the Web API 2 patterns (method overloading, HTTP verb convention based on method name, HttpRequestMessage/HttpResponseMessage programming model, etc).

[danroth27]

As mentioned previously, we recommend using attribute routing instead of trying to make things work with global routes.

It would be interesting to discuss this with you more and get your thoughts on this guidance.