Professional Documents
Culture Documents
ASP NetPageLifeCycle
ASP NetPageLifeCycle
com/
Table of Content
Introduction Application Life Cycle IIS Request Process Application Pool Worker Process HTTP Handler/Module ASP.NET Page Life Cycle Page Life Cycle Steps Page Life Cycle Events Life Cycle for Master Page and User Control QA
Introduction
When Clients request for an aspx page from browser
and lot of stuffs happens in background to produce the output or sending response to client. This evolves ASP.NET Page Lifecycle. ASP.NET Page Life Cycle is very much important to know for each and every developer to developed an ASP.NET Web Application. All events, data processing, dynamic control creation, view state, postback, rendering etc. are depends with Page Life Cycle.
http://blogs.thesitedoctor.co.uk/tim/2006/06/30/Complete+Lifecycle+Of+A n+ASPNet+Page+And+Controls.aspx
S R
I E
L V
http://msdn.microsoft.com/en-us/library/ms178472.aspx
This is the first event which raised in asp.net page lifecycle Check for Request is for Post Back or not. All dynamic control need to be created Theme Change, Master Page Set at runtime Raised after all controls have been initialized Build up a tree of controls from the ASPX file Turn on view state monitoring any changes in control will be tracked by View State for future.
Init()
Load view state data for page and controls Load Postback data if needed We can process any kind operation that need to perform before page load OnLoad methods control called for each and every control We can create the connection initialization for any kind of external source like database connection We can also set the control properties
Load()
If this is an postback request , Corresponding events will triggered. Like, if the post back is happing for button click, then Button_Click Event will fired. Each control of the page has a PreRender event which is being invoked. EnsureChildControls is also being called during this events DataBind method for all control has also been called If we want to change any thing to any control this is the last event where we can do because after the pageRender starts
PreRender
ViewState Monitoring is turned off as here all the ViewState Data need to be saved. View State data saved in hidden filed called _VIEWSTATE Pages calls the Render method for each and every control. Text writer that writes the output to the as output stream Output steam set to the page's Response property.
Render
This is the last event of asp.net page life cycle This ensure the Request and Response has been set to null. This is called only after the content of the page fully rendered and response sent to client
of page. The content of Masterpage gets loaded side by side as the page gets loaded. User control will be initialized and added to the page and before page gets initialized After page Onload, MasterPage_OnLoad gets called and UserControl_Onload gets called sequentially. Followed by each of Page events, masterPage events gets called and next Usercontrol events are called. During the unload phaze, Usercontrol gets unloaded first and then masterpage and Page in sequence. For further reference refer to : http://blogs.thesitedoctor.co.uk/tim/2006/06/30/Complete+Life cycle+Of+An+ASPNet+Page+And+Controls.aspx
Q/A
Thank you