Asp. NET's life cycle

I mainly refer to this article for ASP. NET application and page life cycle

1. The user sends a request from the browser to the Web server, and the server checks the requested extension to determine which ISAPI extension handles the request.

The. aspx,. ascx,. ashx, and. asmx classes are mapped to them and can be processed by ASP.

2.ASP. NET receives the first request for any resource, the Applicationmanager class creates an application domain. Then in the application domain, an instance is created for the Hostingenvironment class.

Application domains provide application isolation for global variables and allow each application to be uninstalled separately.

This instance provides access to information about the application, such as the name of the folder where the application is stored.

After the 3.HostingEnvironment class creates an instance, ASP. NET creates and initializes core objects, such as Httpcontext,httprequest,httpresponse.

4. After initializing the core, launch the application through an instance of the HttpApplication class.

  httpapplication class and uses the derived class to represent the application. "Data-guid=" 303b1a8fce57c312b0dfa728c7b3d00d "> If the application has Global.asax files, ASP. NET creates An instance of the Global.asax class (derived from the HttpApplication class) and uses that derived class to represent the application .

httpapplication class and uses the derived class to represent the application. "Data-guid=" 303b1a8fce57c312b0dfa728c7b3d00d "> above 4 steps such as

httpapplication class and uses the derived class to represent the application. "Data-guid=" 303b1a8fce57c312b0dfa728c7b3d00d ">5. Request MHPM by HttpApplication pipeline (module, Handler, page and Module event) /span>

httpapplication class and uses the derived class to represent the application. "Data-guid=" 303b1a8fce57c312b0dfa728c7b3d00d "> as

Asp. NET's life cycle