ASP.Net Page Life Cycle (Cheat Sheet)
Today i am looking for articles about ASP.Net Page Life cycle and after Googling i found this incredible diagram explaining the detailed Page Life Cycle.
All credit goes to “Andrianarivony Leon”
| Page Event | Typical Use |
|---|---|
| PreInit | Use this event for the following:
|
| Init | Raised after all controls have been initialized and any skin settings have been applied. Use this event to read or initialize control properties. |
| InitComplete | Raised by the Page object. Use this event for processing tasks that require all initialization be complete. |
| 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. |
| 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. |
| 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. |
| LoadComplete | Use this event for tasks that require that all other controls on the page be loaded. |
| PreRender | Before this event occurs:
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. |
| 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. |
| 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. For more information, see Developing Custom ASP.NET Server Controls. A user control (an .ascx file) automatically incorporates rendering, so you do not need to explicitly render the control in code. |
| 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. Note: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.
|

Related posts:
- A Quick Reference Guide to Microsoft Technologies (Cheat Sheets) While working as a developer we all face some syntax...
- Health Check of your ASP.NET 2.0 Web Application One of the best, yet often overlooked, features of ASP.NET...
- What is the Difference Between <%# j %> and <%= j %>? These are the two types constructs to access page-level variables...
- Forcing a Download Dialog to Display If your browser is capable of rendering the content type...
- HttpWebRequest, HttpWebResponse and send POST request to another web server Some times we do have a requirement to call external...

Note:
what about LoadViewState and LoadPostbackdata ?
See further reference on codeproject : http://www.codeproject.com/KB/aspnet/aspnetviewstatepagecycle.aspx
@titeoe
Thanks for providing this link for further reference.
Both of these LoadViewState and LoadPostbackdata are shown in the first diagram, Later one are the ASP.Net page life cycle overview only, Refer first Diagram for detailed analysis,
More here: http://john-sheehan.com/blog/net-cheat-sheets/
@John Sheehan
Thanks John, For providing more information.
Look at this post .
It is inspired by your post:
http://www.soliddotnet.com/index.php/2009/09/08/a-quick-reference-guide-to-microsoft-technologies-cheat-sheets/
Great articles & Nice a site
Super-Duper site! I am loving it!! Will come back again – taking you feeds also, Thanks.
A SUPPORTED BY THE DEVELOPER TOOLS? It was interesting. You seem very knowledgeable in ypour field.