ASP.NET vNext

Ryan Hayes
ryanhayes.net
@RyannosaurusRex
Tri-Cities .NET User Group
6/17/2014


So What's the Problem?


ASP.Net's a Changin'. Why Is This Important?

(...more than any other update)



(Really Big)

Breaking Changes!



Today, ASP.NET Uses The Same Framework Everything Else Does, even Desktop Apps!!


(While productive, it's really big)



ASP.NET vNext is a Reimagining of what ASP.NET could be like without the history of .NET and with everything we've learned from Ruby on Rails and Node.JS

ASP.NET vNext is:

  • Based SOLELY on NuGet packages w/side-by-side deploy
  • Deploy the entire framework with your app
  • Mac/Linux have first-class citizen support from MS
  • Hosted in IIS or "self-hosted" via the command line
  • Project files based on NuGet
  • Roslyn live-compile
  • Use VS, Sublime, MonoDevelop, Notepad, whatever
  • All compilation done in-memory
  • MVC/WebAPI are unified and the same
  • and more... (or less)




No More System.Web!

System.Web consumes 30K of memory per request.  vNext consumes just 2K per request.



But...System.Web had...

  • IIS Integration (Native module)
  • aspnet_regiis
  • web.config <system.web> section
  • HttpRuntime.Cache
  • Routing
  • HttpContext and friends
  • HttpUtility

And System.Web had...

  • Session
  • Health Monitoring
  • Profile/Membership
  • MS Ajax
  • JavascriptSerializer
  • WCF/IIS Integration
  • MachineKey
  • OutputCache

ASP.NET vNext

By Ryan Hayes