What are the MAIN differences (things I should be concerned about) between WepApi and WepApi2 that now ships with Visual Studio 2013?
In its simplest form, a Web API is an API over the web (HTTP). ASP.NET Web API is a framework that allows you to build Web API's, i.e. HTTP-based services on top of the . NET Framework using a convention based and similar programming model, as that of ASP.NET MVC.
In ASP.NET Core, there's no longer any distinction between MVC and Web APIs. There's only ASP.NET MVC, which includes support for view-based scenarios, API endpoints, and Razor Pages (and other variations like health checks and SignalR). In addition to being consistent and unified within ASP.NET Core, APIs built in .
KEY DIFFERENCEWCF is used for developing SOAP-based services whereas Web API is used for both SOAP-based and RESTful services. WCF does not offer any support for MVC features whereas Web API supports MVC features. WCF supports HTTP, UDP, and custom transport protocol whereas Web API supports only HTTP protocol.
The latest ASP.NET Web API 2.2 package has the following version: "5.2. 0". You can install or update these packages through NuGet. The release also includes corresponding localized packages on NuGet.
Major new features are,
- AttributeRouting
- OWIN self host
- IHttpActionResult
- CORS
- HttpRequestContext
I had the same question and found simple article about this, here.
In addition to the features mentioned by iJay
Testability
ODATA Improvements
Filter Overrides
ByteRangeStreamContent
We can differentiate web api and web api2 by using above features.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With