What is the page life cycle of an asp.net page?

The ASP.NET Page Life Cycle:

1. PreInit : Create or re-create dynamic controls. Set a master page dynamically. Set the Theme property dynamically.
2. Init : Raised after all controls have been initialized and any skin settings have been applied. Use this event to read or initialize control properties.
3. InitComplete : Raised by the Page object. Use this event for processing tasks that require all initialization be complete.
4. PreLoad : Use this event if you need to perform processing on your page or control before the Load event. Before the Page instance raises this event, it loads view state for itself and all controls, and then processes any postback data included with the Request instance.
5. Load : The Page calls the OnLoad event method on the Page, then recursively does the same for each child control, which does the same for each of its child controls until the page and all controls are loaded. Use the OnLoad event method to set properties in controls and establish database connections.
6. Control events : Use these events to handle specific control events, such as a Button control’s Click event or a TextBox control’s TextChanged event.
7. LoadComplete : Use this event for tasks that require that all other controls on the page be loaded.
8. Page_PreRender : The PreRender event occurs for each control on the page. Use the event to make final changes to the contents of the page or its controls.
9. SaveStateComplete : Before this event occurs, ViewState has been saved for the page and for all controls. Any changes to the page or controls at this point will be ignored. Use this event perform tasks that require view state to be saved, but that do not make any changes to controls.
10. Render : This is not an event; instead, at this stage of processing, the Page object calls this method on each control. All ASP.NET Web server controls have a Render method that writes out the control’s markup that is sent to the browser. If you create a custom control, you typically override this method to output the control’s markup. However, if your custom control incorporates only standard ASP.NET Web server controls and no custom markup, you do not need to override the Render method. A user control (an .ascx file) automatically incorporates rendering, so you do not need to explicitly render the control in code.
11. Unload : This event occurs for each control and then for the page. In controls, use this event to do final cleanup for specific controls, such as closing control-specific database connections. For the page itself, use this event to do final cleanup work, such as closing open files and database connections, or finishing up logging or other request-specific tasks. During the unload stage, the page and its controls have been rendered, so you cannot make further changes to the response stream. If you attempt to call a method such as the Response.Write() method, the page will throw an exception.