All geek questions in one place

How does ASP.NET vNext compare with WinRT?

The ASP.NET vNext description on this blog describes it as a “skinny and sophisticated .NET stack for building modern cloud applications. Does this mean a similar limited subset of .NET, such as WinRT?

WinRT had serious limitations and violations. This made it impossible to port popular libraries because there was n’t enough support for dynamically creating code . There have also been many changes to BCL (from my own experience). I think this was reasonable for many reasons, but it has left the .NET environment a lot.

I do not think ASP.NET vNext will have these limitations, but it offers much more, claiming to be cross-platform. This is really great, but I'm curious if such an experience, for example, WinRT, will turn out. Can I assume that we will work on the same BCL (corresponding parts for ASP.NET vNext applications)?

There is also another statement that says nothing about supporting the old BCL:

ASP.NET vNext will be based on .NET vNext..NET vNext - the next major release of the .NET Framework..NET vNext will be a cloud-optimized mode that will have a smaller size compared to full .NET. Framework

I am wondering if we can update our current applications and libraries.

+4
source share
1

, " " CLR. ASP.NET vNext CLR ( ), Core CLR ( 8 ​​ 2012 ), ( , , )

, ASP.NET vNext MVC, WebAPI, SignalR . System.Web, CLR System.Web WebForms "R Runtime". , ASP.NET vNext WebForms, MVC 6 ( MVC WebAPI)

0

Source: https://habr.com/ru/post/1546027/

More articles:


All Articles