ASP.NET vNext: the future of .NET on the Server

ASP.NET vNext: the future of .NET on the Server

Rate This
  • Comments 27

At TechEd we announced our plans and vision for ASP.NET vNext. ASP.NET vNext is being designed from the bottom up to be a lean and composable .NET stack for building web and cloud based applications. You can find an overview of ASP.NET vNext and walkthroughs of the current experience at http://www.asp.net/vnext.

  • MVC, Web API, and Web Pages will be merged into one framework, called MVC 6. MVC 6 has no dependency on System.Web.
  • ASP.NET vNext includes new cloud-optimized versions of MVC 6, SignalR 3, and Entity Framework 7.
  • ASP.NET vNext will support true side-by-side deployment for all dependencies, including .NET for cloud. Nothing will be in the GAC.
  • ASP.NET vNext is host agnostic. You can host your app in IIS, or self-host in a custom process.
  • Dependency injection is built into the framework.
  • Web Forms, MVC 5, Web API 2, Web Pages 3, SignalR 2, EF 6 will be fully supported on ASP.NET vNext
  • .NET vNext (Cloud Optimized) will be a subset of the .NET vNext Framework, optimized for cloud and server workloads.
  • MVC 6, SignalR 3, EF 7 will have some breaking changes:
    • New project system
    • New configuration system
    • MVC / Web API / Web Pages merge, using a common set of abstractions for HTTP, routing, action selection, filters, model binding, and so on
    • No System.Web, new lightweight HttpContext

To learn more about the ASP.NET vNext announcements, see the TechEd sessions:

ASP.NET vNext is an open source project released under Apache License Version 2.0 by Microsoft Open Technologies, Inc. You can follow its progress and find instructions on how to contribute on https://github.com/aspnet .

We’d love to hear your feedback. Please provide it in Github, comments on this blog, or the ASP.NET vNext forum. If you ask question in Stack Overflow, use asp.net-vnext tag.  Thanks for being with us in this exciting time.

Leave a Comment
  • Please add 5 and 3 and type the answer here:
  • Post
  • So basically no support for Web Forms in the cloud optimized .NET because it depends heavily on System.Web? Fair enough as long as you don't decide a couple of years from now that new features will only come on the cloud optimized version.

    BTW does the new edit/save/refresh work with (non Web Sites) Web Forms?

  • Congrats! I'm really excited for what vnext brings to the table.

  • I could be wrong but I think you could add System.web and that gets added to the deploy. So you get Cloud Optimized Plus your additional stuff. So maybe out of the box Web Forms isn't there but I don't think it means it can't be.

  • @Stilgar there is no Web Forms here for the reason you mention: System.Web can be used only with the full .NET Framework and has dependencies that are outside the scope of ASP.NET vNext. However, we did just post earlier today many new features and enhancements specifically for Web Forms: blogs.msdn.com/.../improvements-to-asp-net-web-forms.aspx

    @Ryan if running on the full .NET Framework (and not the Cloud Optimized flavor) you can call certain APIs in System.Web, such as for HTML encoding, or other utilities, but that ASP.NET pipeline will not be compatible (e.g. HTTP Modules and HTTP Handlers). Instead we use middleware based on Katana.

  • @Eilon I would grade the enhancements for Web Forms as barely acceptable. Half of them are just project templates. You can do better.

    Can you confirm if the edit/save/refresh developer experience is coming to Web Forms or not. I can't quite understand this from the announcements.

  • Friends don't let friends do postback

  • Friends don't let friends do postback

  • Will there be support for Virtual Path Providers, or additional middleware that can take advantage of them?

  • Hi, what is needed to open the new projects (.kproj)?

    VS2013 + Update 2 RTM seems unable to handle it

  • @Max, we don't have the tooling released yet.  Please wait for a few weeks for us to release the tooling.

  • Make some revolution with WebForms, and implement new Synchronous Mode. with this mode control's graph will be preserved between postback. This way you can provide huge benefits

    - no view state

    - no canvoluted caching

    - smaller generated html

    - less coding

    - much higher performance (no serialization/deserialization and no creating control's graph on every postback)

    Currently WebForms are broken by design. There is necessity to provide enormous and tricky code, to avoid huge viewstate and cache some data, to avoid lenghty recreation.

  • The only statement that seems strange is:

    "ASP.NET vNext includes new cloud-optimized versions of [...] Entity Framework 7"

    Would that mean that there will be an EF version optimized ONLY for.. ASP.NET web applications? (and not for desktop, Windows Services or Azure Worker roles etc..)

  • Really great post.Thanks for this valuable posting.

  • @Tudor - Entity Framework (EF) can be used outside of ASP.NET - definitely! EF6 can be used anywhere the full .NET Framework can be used. The new EF on GitHub will also be usable in Windows Store apps and other places where there is .NET.

  • What .NET improvements are being made for non-cloud based web solutions?  Cloud is not applicable for our financial web solutions since they must be entirely hosted in-house.

Page 1 of 2 (27 items) 12