Microsoft recently released ASP.NET MVC 5.2, Web API 2.2 and Web Pages 3.2 with new features, bug fixes and improvements. The product team has also provided solutions to certain key issues surfaced in the previous version.
Part of the ASP.NET vNext initiative, ASP.NET MVC 6 represents a fundamental change to how Microsoft constructs and deploys web frameworks. The goal is to create a host agnostic framework that eliminates the dependencies on the legacy System.Web infrastructure.
ASP.NET Web API 2.2 for OData v4.0 are now available as nightly builds. The team also released OData core libraries version 6.1 on nuget with several bug fixes and new features, especially increased support for OData v4 spec. However, the MS team suggested that WCF will not get OData v4 specific features.
The team behind the website FeedbackHound has taken ownership of the Unity.Mvc and Unity.WebAPI. These open source libraries allow for integration between ASP.NET MVC & Web API and Microsoft’s IoC framework, Unity.
ASP.NET MVC 5 introduces the same attribute based routing used by Web API 2. This optional syntax allows routes to be registered declaratively instead of by manipulating a RouteCollection.
One of the new features in VS 2013 is OData Scaffolding. Like MVC Scaffolding, this feature is designed as both a training aid and to speed development. However, it requires a bit more setup than the MVC version.
In ASP.NET Web API OData, it is important to enable validation in Queryable API if you make use of queries outside the organization and this article examines the various scenarios where you can enable validation.
Microsoft has released ASP.NET and Web Tools 2012.2 with enhancements for ASP.NET WEb, MVC, Windows Azure authentication including support for SignalR.
Microsoft has been working on some interesting features after shipping ASP.NET 4.5. Some of these are available in the Fall 2012 Build preview. Scott Hanselman and Jon Galloway demoed a few of them, at a //build/ session "Bleeding Edge ASP.NET".
IApiExplorer is a new abstraction layer that allows you to obtain a description of the structure of your ASP.NET Web APIs. This interface also comes with a default implementation - APIExplorer.
Technically speaking, ASP.NET MVC has been open source all along. But as with most Microsoft projects it wasn’t “open development”, all work was done internally with occasionally drops. As of yesterday, that all changed. Everyone in the community is now able to contribute code and tests to ASP.NET MVC, Web Pages, and Web API.
Web API is the first real alternative to WCF that .NET developers have seen in the last six years. Until now emerging trends such as JSON were merely exposed as WCF extensions. With Web API, developers can leave the WCF abstraction and start working with the underlying HTTP stack.