aspnet_wp.exe and w3wp.exe

ASP.NET与IIS6.0进程解析

最新推荐文章于 2017-02-24 15:23:24 发布

转载最新推荐文章于 2017-02-24 15:23:24 发布 · 1.2k 阅读

文章标签：

#asp.net #iis #extension #processing #dll

开发技术专栏收录该内容

44 篇文章

订阅专栏

本文解析了ASP.NET在IIS5.0和IIS6.0中的工作流程，阐述了aspnet_wp.exe与w3wp.exe两个关键进程的作用与区别。在IIS5.0中，请求由aspnet_isapi处理并交由aspnet_wp.exe执行；而在IIS6.0中，http.sys接收请求，并启动w3wp.exe加载aspnet_isapi。

aspnet_wp.exe and w3wp.exe [Article From:http://geekswithblogs.net/vivek/archive/2006/10/18/94436.aspx]

when compared with 5.0. In 5.0, the ASP.NET worker process is handed off control by the aspnet_isapi extension in IIS. The aspnet_isapi dll runs in the inetinfo.exe process in IIS and functions what is known as the CLR host (a CLR host is the piece of unmanaged code which is responsible for loading the CLR into the memory). So aspnet_isapi “hands over” the processing to the worker process named aspnet_wp.exe, where the request passes through a series of HttpModules and an HttpHandler.

But in IIS 6.0, there is a driver named http.sys which listens to all the incoming requests (aspnet_isapi.dll is not in the picture at this point). The moment an ASP.NET specific request comes in, this driver starts an IIS 6.0 worker process (which is not related to ASP.NET at all) named w3wp.exe. This process now loads the aspnet_isapi.dll (CLR host) and the request follows through a similar sequence of HttpModules and HttpHandlers.

So the important thing to note here is that w3wp.exe is not an ASP.NET worker process (unlike aspnet_wp.exe) but instead specific to IIS 6.0.