After referencing the Asp.net master page, the page event execution sequence of the master page and Content Page

The following steps are taken:

Step 2: page_preinit of the Content Page
Step 2. page_init of the master page
Step 2: page_init of the Content Page
Step 2: page_initcomplete on the Content Page
Step 2: page_preload of the Content Page
Step 2: page_load of the Content Page
Step 2: page_load of the master page
Send back events such as Button clicking on step 2, master page or content page (Button events of Master or content will not be triggered at the same time)
Step 2: page_loadcomplete on the Content Page
Step 2: page_prerender of the Content Page
Step 2: page_prerender on the master page
Step 2: page_prerendercomplete on the Content Page
Step 2: page_savestatecomplete on the Content Page
Step 2: page_unload on the master page
Step 2: page_unload of the Content Page

In addition, repost an article:Asp.net page event execution sequenceHttp://www.cnblogs.com/oletan/archive/2008/11/04/1326587.html#1549248)

Note: For ease of understanding, you can think that the onpreinit method is equivalent to the page_preinit method, and the onload method is equivalent to the page_load method.

In fact, the rewritten onpreinit method internally calls the page_preinit method above, and so on, the rewritten onload method calls the page_load method above.

If the base. onload (e) statement is not written in the override onload method, the page_load method will not be executed.

 

View plaincopy to clipboardprint?

2. UsingSystem;
4. UsingSystem. Data;
6. UsingSystem. configuration;
8. UsingSystem. Web;
10. UsingSystem. Web. Security;
12. UsingSystem. Web. UI;
14. UsingSystem. Web. UI. webcontrols;
16. UsingSystem. Web. UI. webcontrols. webparts;
18. UsingSystem. Web. UI. htmlcontrols;
22. PublicPartialClass_ Default: Page
24. { 
26. # Region onpreinit Step 1
28. Protected Override VoidOnpreinit (eventargs E)
30. {
32. // Check the ispostback attribute to determine whether the page is processed for the first time.
36. // Create or recreate a dynamic control.
40. // Dynamically set the master page.
44. // Set the theme attribute dynamically.
48. // Read or set the configuration file property value.
52. // Note
54. // If the request is a send-back request, the value of the control has not been restored from the view State. If the control property is set in this phase, its value may be overwritten in the next event.
60. Base. Onpreinit (E );
62. } 
64. # Endregion 
66.  
68. # Region oninit Step 2
70. Protected Override VoidOninit (eventargs E)
72. {
74. // Triggered after all controls have been initialized and all appearance settings have been applied. Use this event to read or initialize control properties.
76. Base. Oninit (E );
78. } 
80. # Endregion 
82.  
84. # Region oninitcomplete step 3
86. Protected Override VoidOninitcomplete (eventargs E)
88. {
90. // Triggered by the Page Object. This event is used to handle all tasks that require initialization to be completed first.
94. Base. Oninitcomplete (E );
96. } 
98. # Endregion 
100.  
102. # Region preload Step 4
104. Protected Override VoidOnpreload (eventargs E)
106. {
108. // Use this event if you need to process pages or controls before loading events.
112. // After a page event is triggered, it loads the view status for itself and all controls, and then processes any sending data included in the request instance.
116. Base. Onpreload (E );
118. } 
120. # Endregion 
122.  
124. # Region onload Step 5
126. Protected Override VoidOnload (eventargs E)
128. {
130. // Page calls the onload event Method on the page, and then performs the same operation on each sub-control recursively. This repeats until the current page and all controls are loaded.
132. // Use the onload event method to set properties in the control and establish a database connection.
136. Base. Onload (E );
138. } 
140. # Endregion 
142.  
144. # Step 6 of region control events
146. Protected VoidButton#click (ObjectSender, eventargs E)
148. {
150. // Use these events to process specific control events, such as click events of the button control or textchanged events of the Textbox Control.
154. // Note
156. // In the send-back request, if the page contains VerificationProgramCheck the isvalid attribute of the page and each validation control before performing any processing.
162. } 
164. # Endregion 
166.  
168. # Region onloadcomplete Step 7
170. Protected Override VoidOnloadcomplete (eventargs E)
172. {
174. // Use this event for tasks of all other controls on the page to be loaded.
178. Base. Onloadcomplete (E );
180. } 
182. # Endregion 
184.  
186. # Region onprerender Step 8
188. Protected Override VoidOnprerender (eventargs E)
190. {
192. // Before the event:
196. // The Page Object calls ensurechildcontrols for each control and page.
200. // The databind method is called for each data binding control with the performanceid attribute set. For more information, see the data binding event of the data binding control below.
204. // A prerender event occurs for each control on the page. Use this event to make the final changes to the page or its control content.
208. Base. Onprerender (E );
210. } 
212. # Endregion 
214.  
216. # Region savestatecomplete Step 9
218. Protected Override VoidOnsavestatecomplete (eventargs E)
220. {
222. // Viewstate is saved for the page and all controls before this event occurs. Any changes made to the page or control at this time will be ignored.
226. // Use this event to execute tasks that meet the following conditions: the view status is saved, but no changes are made to the control.
230. Base. Onsavestatecomplete (E );
232. } 
234. # Endregion 
236.  
238. # Region render step 10
240. // Render
242. // This is not an event. At this stage of processing, the page object calls this method on each control. All ASP. NET web server controls have a render method used to write the control flag sent to the browser.
246. // If you create a custom control, you usually need to override this method to output the control tag. However, if the custom control only merges the standard ASP. NET web server control and does not merge the custom tag, the render method is not required. For more information, see develop custom ASP. NET Server controls.
250. // The user control (. ascx file) is automatically merged and rendered, so you do not needCodeExplicitly present the control. 
252.  
254. # Endregion 
256.  
258. # Region onUnload Step 1
260. Protected Override VoidOnUnload (eventargs E)
262. {
264. // This event first occurs for each control and then for this page. In the control, use this event to perform final cleaning on the specific control, for example, closing the connection to the specific database of the control.
268. // For the page itself, use this event to perform the final cleaning, for example, closing the opened file and database connection, or completing logging or other request-specific tasks.
272. // Note
274. // When the page and its control are displayed, no further changes can be made to the response stream. If you try to call a method (such as the response. Write method), this page will cause an exception.
280. Base. OnUnload (E );
282. } 
284. # Endregion
286. }

 

From: http://blog.csdn.net/youbl/archive/2009/08/28/4492747.aspx