Like a lot of changes in ASP.NET
lately, a lot of things in "vNext" remind me of things I liked in classic ASP & PHP. (All things old are new again.)
- "there’s no direct dependency on MsBuild to build/package a project."
vNext allows a welcome no-compilation workflow where you can make changes to source code and see the changes reflect as soon as you refresh your HTTP content."
- "The vNext project system also treats folders as a project—there’s no longer a file that holds references to each of the files in a project like your typical .csproj file, but rather a project is simply a folder and any file that is recognized is compiled."
- "The ASP.NET
Web Pages framework is also integrated into this combined MVC framework and uses the very same Razor View Engine implementation as MVC, so that the differences between MVC and standalone Web Pages go away. Web Pages is perhaps the most underused framework in ASP.NET
vNext is a major change that is as big as the step was from the original, classic Active Server Pages to ASP.NET