{"id":113,"date":"2014-05-12T00:35:51","date_gmt":"2014-05-12T00:35:51","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/cesardelatorre\/2014\/05\/12\/the-future-of-net-in-the-server-asp-net-vnext-optimized-for-cloud-and-server-workloads\/"},"modified":"2014-05-12T00:35:51","modified_gmt":"2014-05-12T00:35:51","slug":"the-future-of-net-in-the-server-asp-net-vnext-optimized-for-cloud-and-server-workloads","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/cesardelatorre\/the-future-of-net-in-the-server-asp-net-vnext-optimized-for-cloud-and-server-workloads\/","title":{"rendered":"The Future of .NET in the Server: ASP.NET vNext optimized for Cloud and Server workloads"},"content":{"rendered":"

Before getting into \u201cThe future of .NET in the server\u201d, I want to highlight how the ASP.NET and Web Tools teams just released great RTM ASP.NET stuff (final version). Specifically, Improvements to ASP.NET Web Forms<\/a> and many other new features for ASP.NET in general<\/a>, all of that final\/RTM as part of Visual Studio 2013 UPDATE 2 RTM, released during this week in TechEd NA 2014.<\/p>\n

But, in this blog post I want to focus on the \u201cFuture of .NET and ASP.NET\u201d<\/strong>. A sneak peak or preview of ASP.NET vNext and .NET vNext in the Server. <\/p>\n

The ASP.NET and .NET teams joined forces for this effort, and are taking advantage of the great innovation at the .NET core, like the .NET Compiler Platform (\u201cRoslyn\u201d), and impressive improvements in the runtime\/CLR and framework especially made for server workloads.<\/p>\n

So, this week, at TechEd NA North America (May 12-15 2014), we\u2019re announcing the next generation of .NET on the Server, a new wave of ASP.NET vNext and .NET vNext in the server<\/strong>. These news are about early previews (ALPHA) and it will be evolving during the upcoming months (therefore, many things could also change). But, this is the first public disclosure about \u201cthe future of .NET in the server\u201d, like I said. <\/p>\n

ASP.NET vNext is an evolution of ASP.NET. Everything you know today about ASP.NET will apply to ASP.NET vNext. You can use the existing libraries or the new versions for those libraries in .NET vNext and get immediate benefits. <\/p>\n

However, modern web development demands a simple, lean development experience built on top of a composable framework. <\/p>\n

Below I show a diagram that I made for the TechEd announcement, summarizing the future of .NET, where ASP.NET vNext focuses especially on the \u201cCloud optimized\u201d area (right-below), with pillars like high throughput, small foot-print, side by side execution and \u201ccross-platform enabled\u201d<\/strong>. I\u2019ll drill down on those topics in this post.<\/p>\n

\"image\"<\/a> <\/p>\n<\/p>\n

Then, focusing just on ASP.NET vNext, you can see below a simplified ASP.NET vNext stack diagram. <\/p>\n

\"image\"<\/a> <\/p>\n

A very important news to highlight is that MVC, Web API and Web Pages now share a unified core, they are merged, in fact. For instance, there\u2019s now a single type of controller. This will allow a much better and unified developer experience. This includes:<\/p>\n