ASP.NET 5

Editor's Notes

• #4: Talking points 1.8 Billions of active installs of .NET .NET is everywhere (from embedded systems up to the cloud) 6 million of .NET professional developers .NET has 1.8 Billions of active installs of .NET, but that is just the number coming from Windows Update. That’s just computers that are actively using .NET and staying current with the latest patches and updates across all versions. If you add to that embedded systems and phones, the number grows even more!. Not only that, focusing on PROFESSIONAL DEVELOPERS, there are around 6 million .NET Pro devs, that means around 60% of pro developers building business applications. TBD: Add another line with VS 2013 downloads or as a talking point… Aditional data: Xamarin – 8 million C# developers, but that includes non-pro developers, moonlighters, etc. -- Source: Microsoft figures for total world wide Windows Update installs.
• #6: Talking points You know that nowadays, “every company is a software company”. If your business wants to stay relevant, you need software that can push your core-business to the limits. In addition to the business applications, the number of web and mobile apps are growing exponentially, so, that’s why the developer role is more important than ever before. But these new trends related to apps and agile development for the business require us to deliver much faster in a much shorter cadence or even in a continuous motion. We also hear from you that you need to develop apps for different platforms but you’d like to have a cross-device development strategy so you can share the development investments between the different device platforms. Finally, you also say, hey!, I know there are new device and cloud trends but I have existing business applications to run and evolve, what is the right way? Because this feedback and many others, we are changing our approach to building .NET… (go to next slide)
• #7: This slide would be just about Talking points for the “Future of .NET” slide WHAT – WHY – HOW (*) You want .NET innovation and Microsoft investment on .NET. We’ve invested on .NET innovation from end-to-end, as I’ll show you in a minute. That innovation will benefit future application development but also your existing applications and your existing development experience. (*) You want flexibility and agile delivery so your applications can have an agile evolution up to date to the latest versions of frameworks and components. That can be achieved by using NuGet packages and Microsoft is betting on NuGet as the mainstream channel for most of the .NET libraries. NuGet is key for .NET vNext and ASP.NET vNext. (*) You want Openness . Microsoft is heading strongly towards OPEN SOURCE because it is key for a vibrant community and evolving ecosystem. This mainstream in .NET will promote community involvement and will provide the ability to influence and contribute to the .NET roadmap.
• #8: The slides that follow address each of the points
• #9: Flexible and cross-platform CLR hosting .NET - Maximum compatibility Cloud Optimized – Be fully self-contained and support true side-by-side versioning! Mono – Run on Mac/Linux! Better dependency management Assembly references → NuGet package dependencies Native support for building and consuming NuGet packages and symbol packages Reference NuGet package directly and leverage NuGet semantics for dependency resolution Integrated runtime compilation with Roslyn Build everything up front or deploy source and compile in memory at runtime Easily replace binary dependencies with code for debugging or for modification Simple JSON format for managing dependencies and compilation settings
• #10: Slimmed down to just the “Core” (a.k.a. CoreCLR) No WinForms, WebForms, WCF, WIF, WF, etc. Modernized API surface area Cleaned up for better factoring Continuation of Windows Store .NET API contracts, extended for the server Existing binaries will probably need to be updated – use ApiPort tool to find out what’s different Still lots of API gaps, but more stuff being added with every NuGet release Factored as NuGet packages New features ship as new independent packages on NuGet Better versioning for simplified deployment Bin deploy the pieces of the .NET framework you need with your app – including the CLR! Completely self-contained apps that support true side-by-side versioning
• #11: Modular Get high productivity with built-in or community contributed middleware and frameworks Use a stripped down pipeline for bare metal performance Fast and lean Light weight HttpContext Highly optimized IIS integration and WebListener for maximum throughput Flexible hosting Run both in IIS and hosted in your own process Supports OWIN But doesn’t force you to code against the raw OWIN abstractions Easily migrated Katana middleware to this new model
• #12: New environment based config system Pick up the appropriate config values for the environment you are running (dev, staging, prod) Read name/value pairs from a variety of sources (JSON, XML, INI, environment variables, etc) No more complicated web.config and config transforms Integrated DI Use common DI abstraction in inject services appropriate for the environment Replace the built-in container with your favorite IoC (Ninject, Autofac, Unity, StructureMap, etc) Reduce COGS Run on the Cloud Optimized runtime for higher runtime density and better resource utilization Integrated tracing and diagnostics ETW, App Insights
• #13: Premier developer experience in Visual Studio 2015 The agility of a dynamic environment with the power of .NET Fully integrated with new runtime artifacts – project.json, config.json, global.json Easily visualize, manage and manipulate dependencies Cross-platform command-line support K Version Manager (kvm): Manage runtime versions K Package Manager (kpm): Create and install NuGet packages K <cmd>: Run apps and commands New command-line scaffolding Leverage online or third party editors Deploy as source and edit your app on the server (ex. Visual Studio Online) Code in your editor of choice
• #15: Visual of different features, to be merged in next slide
• #16: WebForms are not part of MVC 6
• #18: For step-by-step walkthrough: http://palermo4.com/post/Creating-an-ASPNET-5-Empty-Application.aspx