How does an ASP.NET MVC application depend heavily on a System.Web build?

Question

I read so many articles about OWIN and Katana, and one of the advantages of using OWIN in an ASP.NET application is that when I create an ASP.NET application, I am inherently attached to IIS because of the great dependency on System.Web build. In other words, System.Web builds by default for each request.

In fact, I did not understand how System.Web works on every request, thereby consuming resources and making ASP.NET applications in general much slower. And how do Middleware components solve this problem? Do they depend on the assembly of System.Web?

Answer 1

System.Web.dll .NET Framework, -, ASP.NET.

ASP.NET 5 , - System.Web.dll. :

http://weblogs.asp.net/scottgu/introducing-asp-net-5

http://docs.asp.net/en/latest/conceptual-overview/aspnet.html