Extracted from: [ASP. NET development Q & A 200 Q & A] book ..
① Page initialization ---------- after receiving a request from the client, the Page Object of the corresponding page is generated, and the page object and its control are initialized through the page_init event.
② Load view status ------- viewstate is a set of attributes and values of the Page Server Control. The client uploads the control through a hidden control _ viewstate to the server (the server also has such a variable, this step is to use the viewstate on the server side. Compared with the _ viewstate passed by the client, it is an old version.) ________ this is not necessarily true and is purely a personal understanding.
= The machine is poisoned...
Qq tail virus ...... continue
③ Return data processing ------- locate _ viewstate from the customer request in step 1, extract the data, and assign values to the page control.
④ Page loading ------------ execute the load () event. It feels like page_load (), objects are all instantiated, (controls are assigned values. Here the instantiation refers *. class in CS, as if)
⑤ Raisepostbackchanged event --------- the control is assigned a bool value to identify whether it has been updated.
6. Handle the return event ------- it is the events triggered by the client and starts to execute. For example, if you press a button or something, the specific process to be executed.
7. Page pre-return stage-the last opportunity to modify the property value of the control and the control tree structure.
Secrets save viewstate ------- store the properties and values of the server control in viewstate (server side) for the next page request. therefore, compared to the next request for this page, the viewstate is an old version.
Response page return stage ------- send the generated page to the client.
Destroy destroy object ------------ call the dispose event to destroy the webpage and release all resources it occupies.
The processing of a client request on the server is completed .!!!!!