The life cycle of an ASP.NET application starts with a request sent by a browser to the Web server IIS than goto ASPNET_ISAPI.dll than Appication Manager. It will read web.config and create App domain. Than it will create Request, Response, Session and Context. Than call Http Application

The life cycle of an ASP.NET application starts with a request sent by a browser to the Web server IIS than goto ASPNET_ISAPI.dll than Appication Manager. It will read web.config and create App domain. Than it will create Request, Response, Session and Context. Than call Http Application

The life cycle of an ASP.NET application starts with a request sent by a browser to the Web server (for ASP.NET applications, typically IIS). ASP.NET is an ISAPI extension under the Web server. When a Web server receives a request, it examines the file name extension of the requested file, determines which ISAPI extension should handle the request, and then passes the request to the appropriate ISAPI extension. ASP.NET handles file name extensions that have been mapped to it, such as .aspx, .ascx, .ashx, and .asmx.

If a file name extension has not been mapped to ASP.NET, then ASP.NET will not receive the request. This is important to understand for applications that use ASP.NET authentication. For example, because .htm files are typically not mapped to ASP.NET, ASP.NET will not perform authentication or authorization checks on requests for .htm files. Therefore, even if a file contains only static content, if you want ASP.NET to check authentication, create the file using a file name extension mapped to ASP.NET, such as .aspx.If you create a custom handler to service a particular file name extension, you must map the extension to ASP.NET in IIS and also register the handler in your application's Web.config file.