Asp DotNet 5 New fetures
ASP.NET 5 includes frameworks for building Web apps and services such as MVC, Web API, Web Pages (coming in a future release), SignalR and Identity. Each of these frameworks has been ported to work on the new HTTP request pipeline and has been built to support running on the .NET Framework, .NET Core or cross-platform.
Today, the existing implementations of MVC, Web API and Web Pages share many concepts and duplicate abstractions, but share very little in the way of actual implementation. As part of porting these frameworks to ASP.NET 5, Microsoft decided to take a fresh look at combining these frameworks into a single unified Web stack. ASP.NET MVC 6 takes the best of MVC, Web API and Web Pages and combines it into a single framework for building Web UI and Web APIs. This means from a single controller you can just as easily render a view as return formatted data based on content negotiation.
In addition to unification, ASP.NET MVC 6 introduces a host of new features:
- Built-in DI support
- Ability to create controllers from any class—no base class required
- Action-based request dispatching
- View Components—a simple replacement for child actions
- Routing improvements, including simplified attribute routing
- Async views with flush points
- Ability to inject servers and helpers into views using @inject
- ViewStart inheritance
- Tag helpers
You can find more information and samples at github.com/aspnet/mvc.
Web Forms isn’t available on ASP.NET 5, but is still fully supported on the .NET Framework. There are a number of important new features coming to Web Forms in the upcoming version of the .NET Framework, including support for HTTP 2.0, async model binding and a Roslyn-based CodeDom provider. We’re also working on various features reminiscent of Web Forms in MVC 6, such as tag helpers and other Razor improvements.
0 comments: