1 / 9

ASP.NET vNext

ASP.NET vNext. By Rob Richardson July 24, 2014 http://robrich.org @ rob_rich. ASP.NET vNext. What if we invented ASP.NET today? Why do we have what we have? What can we do about it?. Warning: Microsoft Content. These slides shamelessly pulled from: Introduction:

yvonne
Download Presentation

ASP.NET vNext

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ASP.NET vNext By Rob Richardson July 24, 2014 http://robrich.org @rob_rich

  2. ASP.NET vNext • What if we invented ASP.NET today? • Why do we have what we have? • What can we do about it?

  3. Warning: Microsoft Content These slides shamelessly pulled from: Introduction: http://channel9.msdn.com/Events/TechEd/NorthAmerica/2014/DEV-B385 Deep Dive: http://channel9.msdn.com/Events/TechEd/NorthAmerica/2014/DEV-B411

  4. ASP.NET vNext and the Modern Web Totally Modular Faster Development Cycle Seamless transition from on-premises to cloud Choose your Editors and Tools Open Source with Contributions Cross-Platform OSS Fast

  5. Future of .NET .NETvNext Openness Client apps Web and services • ASP.NET vNext: Web Forms, MVC, Web Pages, Web API, SignalR • WCF • Windows Store, WPF, Windows Forms, • Console apps and related libraries. Multi-purpose • Device optimized • Native compilation • Small footprint, side-by-side • Cross-device enabled • Cloud optimized • High throughput • Small footprint, side-by-side • Cross-platform enabled Specialized Common • Runtime • Compilers • Libraries • Next gen JIT (“RyuJIT”) • SIMD (Data Parallelization) • .NET Compiler Platform (“Roslyn”) • Languages innovation • BCL and PCL • Entity Framework

  6. Future of .NET Providing the best end-to-end development experience… …on your terms Platform Framework Tools …or bring your own …or bring your own …or bring your own

  7. ASP.NET vNext - Summary MVC, Web API, Web Pages 6, SignalR 3, EF 7

  8. ASP.NET vNext - Compatibility • Web Forms, MVC 5, Web API 2, Web Pages 3, SignalR 2, EF 6 • Fully supported on .NET vNext • MVC, Web API, Web Pages 6, SignalR 3, EF 7 • Breaking changes: • New project system • New configuration system • MVC / Web API / Web Pages merge • No System.Web, new lightweight HttpContext (not System.Net.Http) • .NET vNext (Cloud Optimized) • Subset of the .NET vNext Framework • Things you depend on might not be available yet (images, etc)

  9. Demos • ASP.NET vNext101 • Project System, Packages, & NuGet • WebAPI and MVC Convergence • No build step • Cloud-optimized .NET Framework • Referencing a class library • DI Built-in • EF7: “Diet Entity Framework Zero with Lime”

More Related