ASP.NET System.Web.UI.Page lifecycle

Question posted in Computer Software on 11 2009
Rate question difficulty level 0 Votes
From constructor to destructor (taking into consideration Dispose() and the concept of non-deterministic finalization), what the are events fired as part of the ASP.NET Page lifecycle. Why are they important? What interesting things can you do at each?
 
 
1 Answer
 





























 


 


Page request


The page request occurs before the page life cycle begins. When the page is requested by a user, ASP.NET determines whether the page needs to be parsed and compiled (therefore beginning the life of a page), or whether a cached version of the page can be sent in response without running the page.


Start


In the start step, page properties such as Request and Response are set. At this stage, the page also determines whether the request is a postback or a new request and sets the IsPostBack property. Additionally, during the start step, the page's UICulture property is set.


Page initialization


During page initialization, controls on the page are available and each control's UniqueID property is set. Any themes are also applied to the page. If the current request is a postback, the postback data has not yet been loaded and control property values have not been restored to the values from view state.


Load


During load, if the current request is a postback, control properties are loaded with information recovered from view state and control state.


Validation


During validation, the Validate method of all validator controls is called, which sets the IsValid property of individual validator controls and of the page.


Postback event handling


If the request is a postback, any event handlers are called.


Rendering


Before rendering, view state is saved for the page and all controls. During the rendering phase, the page calls the Render method for each control, providing a text writer that writes its output to the OutputStream of the page's Response property.


Unload


Unload is called after the page has been fully rendered, sent to the client, and is ready to be discarded. At this point, page properties such as Response and Request are unloaded and any cleanup is performed.


Credits and more informaition at  http://msdn.microsoft.com/en-us/library/ms178472.aspx , you can read


11/08/2009
 
 
Add an answer*
 
Email
Location: United States
c# .net
Now hiring!
Intuit 
---------------------------
---------------------------
---------------------------
---------------------------
---------------------------
---------------------------
---------------------------