ASP.NET VNEXTANURAJ P

WWW.DOTNETTHOUGHTS.NET

@ANURAJ

WHAT IS ASP.NET VNEXT?

ASP .NET vNext is the next version of ASP .NET Framework. As part of ASP.NET vNext, the MVC, Web API, and Web Pages frameworks are being merged into one framework, called MVC 6. The new framework removes a lot of overlap between the existing MVC and Web API frameworks.

ASP.NET VNEXT FEATURES.

• Side by side support – ASP.NET vNext will support true side by side support, developers can deploy ASP.Net vNext along with web applications, each app can run different versions of .NET vNext side-by-side and upgrade separately, all on the same machine.

• Lean and Faster – ASP.NET MVC 6 has no dependency on System.Web.dll. ASP.NET vNext is a subset of .Net Framework, which is around 11 MB in size, and it is composed of a collection of NuGet packages

• Single Programming model – MVC, Web API, and Web Pages are merged into one framework, called ASP.NET MVC 6. The new framework uses a common set of abstractions for routing, action selection, filters, model binding etc. Dependency injection is built into the framework.

ASP.NET VNEXT FEATURES.

• Enhanced Developer Experience – vNext uses the Roslyn compiler to compile code dynamically, so developer can edit a code file, refresh the browser, and see the changes without rebuilding the project.

• Open Source – Microsoft has released entire source code open source via the .NET Foundation. You can see the source at https://github.com/aspnet and follow progress on vNext in real time.

ASP.NET VNEXT COMPATIBILITY

ASP.NET vNext is not backwards compatible with existing ASP.NET applications. However, the current frameworks (Web Forms 5, MVC 5, Web API 2, Web Pages 3, SignalR 2, and Entity Framework 6) will continue to ship in Visual Studio, and will be fully supported in ASP.NET vNext.

HELLO WORLD APPLICATION IN ASP.NET VNEXT

Global.json – file helps to support project-to-project references. It also makes it easy to separate test code under a different folder, but still be able to reference application projects from your test projects. This is the Global.json file for empty vNext web application. The “sources” element, indicating the “src” folder is the parent folder for finding project references.

Project.json – The project.json file contains a list of dependencies for the project and a list of build output configurations. It can also include a list of commands.

HELLO WORLD APPLICATION IN ASP.NET VNEXT

• Startup.cs – By default, the vNext hosting environment expects to find a startup class named Startup. This class must contain a Configure method that takes an IBuilder parameter, and you configure the HTTP pipeline inside this Configure method. The empty project creates the class with nothing in the Configure method. If you were worked in Owin / Katana project, Startup.cs is similar to Owin Startup file.

To enable MVC in the HTTP pipeline you’ll add a NuGet package and configure the Startup class.

DEMO - HELLO WORLD MVC APPLICATION IN ASP.NET VNEXT WITH K RUNTIME