ASP.NET vNext: the future of .NET on the Server
At TechEd we announced our plans and vision for ASP.NET vNext. ASP.NET vNext is being designed from the bottom up to be a lean and composable .NET stack for building web and cloud based applications. You can find an overview of ASP.NET vNext and walkthroughs of the current experience at http://www.asp.net/vnext.
- MVC, Web API, and Web Pages will be merged into one framework, called MVC 6. MVC 6 has no dependency on System.Web.
- ASP.NET vNext includes new cloud-optimized versions of MVC 6, SignalR 3, and Entity Framework 7.
- ASP.NET vNext will support true side-by-side deployment for all dependencies, including .NET for cloud. Nothing will be in the GAC.
- ASP.NET vNext is host agnostic. You can host your app in IIS, or self-host in a custom process.
- Dependency injection is built into the framework.
- Web Forms, MVC 5, Web API 2, Web Pages 3, SignalR 2, EF 6 will be fully supported on ASP.NET vNext
- .NET vNext (Cloud Optimized) will be a subset of the .NET vNext Framework, optimized for cloud and server workloads.
- MVC 6, SignalR 3, EF 7 will have some breaking changes:
- New project system
- New configuration system
- MVC / Web API / Web Pages merge, using a common set of abstractions for HTTP, routing, action selection, filters, model binding, and so on
- No System.Web, new lightweight HttpContext
To learn more about the ASP.NET vNext announcements, see the TechEd sessions:
ASP.NET vNext is an open source project released under Apache License Version 2.0 by Microsoft Open Technologies, Inc. You can follow its progress and find instructions on how to contribute on https://github.com/aspnet .
We’d love to hear your feedback. Please provide it in Github, comments on this blog, or the ASP.NET vNext forum. If you ask question in Stack Overflow, use asp.net-vnext tag. Thanks for being with us in this exciting time.