How is an ASP.NET MVC application heavily dependent on System.Web assembly?

Question

I've read so many articles about OWIN and Katana, and one of the benefits of using OWIN in ASP.NET application is that when building ASP.NET application, i'm inherently bound to IIS due to the heavy dependency on System.Web assembly. In other words, the System.Web assembly by the default run on every request.

Actually, i didn't get how does the System.Web runs on every request, thus consuming the resources and making ASP.NET applications in general lot slower. And how does the Middleware components solve this problem? does they don't depend on System.Web Assembly?

Answer 1

System.Web.dll is more related to the .NET Framework and not with the web server, so you will have it and use it in your ASP.NET application.

However, the newest version of ASP.NET 5 has a lot of architectural changes and one of these is to get rid of the System.Web.dll dependency. Check more about it on this links:

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

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