Introducing ASP.NET vNext


The next version of ASP.NET (“ASP.NET vNext”) has been re-designed from the ground up. The goal is to create a lean and composable .NET stack for building modern cloud-based apps.

ASP .Net vNext

Below are Key Statements from Blog ^-^

ASP.NET vNext will let you deploy your own version of the .NET Framework on an app-by-app-basis. One app with new libraries can’t break an app next door with a different version. Different apps can even have their own cloud-optimized CLR of their own version. The CLR and cloud-optimized libraries are NuGet packages!

vNext is open source and cross platform.

NuGet packages and class libraries are treated the same. You get full intellisense in the project.json file and NuGet packages come down automatically and transparently. Even better, let’s say NuGet package Foo.Bar has a bug but you’ve only got the NuGet package. You can make a folder called Foo.Bar in our local project and put the source via “git clone” in that folder. This is great for open source projects. That local version overrides the NuGet, allowing you to easily patch bugs locally in libraries while you wait for a new release. When a new fixed NuGet-distributed version shows up, update the version and delete the local source.

One of the great aspects of environments like node or rails is that they are “no compile.” Just change some code and hit refresh. With the next version of ASP.NET you get the power and throughput of the .NET runtime plus the “Roslyn” compiler-as-a-service for a “no-compile compile.” That means means during development time you can just change your C# classes and hit Refresh in the browser. It’s the power of .NET with the dynamism of a refresh-and-go development experience

ASP.NET vNext is modular and all about choice; your choice of framework, your choice of runtime, your choice of operating system, your choice of text editor.

SUMMARY OF ASP.NET VNEXT IS:

  • Cloud and server-optimized.
  • ASP.NET MVC, Web API, and Web Pages will be merged into one framework, called MVC 6.
  • MVC 6 has no dependency on System.Web. The result is a leaner framework, with faster startup time and lower memory consumption.
  • No-compile developer experience.
  • Dependency injection out of the box.
  • Side by side – deploy the runtime and framework with your application.
  • NuGet everything – even the runtime itself.
  • All Open Source via the .NET Foundation and takes contributions.

Oh, and by the way

  • ASP.NET vNext (and Rosyln) runs on Mono, on both Mac and Linux today. While Mono isn’t a project from Microsoft, we’ll collaborate with the Mono team, plus Mono will be added to our test matrix. It’s our aspiration that it “just work.”
ASP.NET on a Mac

ASP.NET VNEXT VIDEOS AT TECHED

OTHER ASP.NET VIDEOS FROM TECHED

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s