to day we will complete the Request trip:
The request and the application pool:
the request is forwarded to the application pool; each application pool is managed by an instance of the worker process “w3wp.exe”. The “w3wp.exe” runs by default under the “NetworkService” account.
This can be changed as follows: Right click on the application pool hosting your application--Properties--Identity Tab. Recall that the application pool is running by the worker – the “w3wp.exe”. So now the worker process takes over.
The worker process loads the ASP.NET ISAPI:
1-The worker process “w3wp.exe” looks up the URL of the request in order to load the correct ISAPI extension.
2-The requested resource in the URL is “Arenypage.aspx”. ISAPI extensions are IIS way to handle requests for different resources.
3-“.aspx” extension is mapped to the aspnet_isapi.dll extension.
4-The worker process passes the request to the aspnet_isapi extension.
5-The aspnet_isapi extension in turn loads the HTTP Runtime and processing of the request starts.
Note1:“Once ASP.NET is installed it installs its own ISAPI extension (aspnet_isapi.dll) and adds the mapping into IIS. IIS maps various extensions to its ISAPI extension.”
Note2: You can see the mappings in the IIS as follows: Right click on the Web Site-Properties-Home Directory Tab-Configuration Button-Mappings Tab. The figure below shows the mappings.
Thx Hope lesson 1 be useful for U ... tomorrow will Complete with
how the worker process loads the web application.
References
http://www.codeproject.com/KB/aspnet/aspnetrequestarchitecture.aspx
http://www.codeproject.com/KB/aspnet/aspnetviewstatepagecycle.aspx
http://www.codeproject.com/KB/aspnet/PageLifeCycle.aspx