Click here to Skip to main content
15,881,742 members
Please Sign up or sign in to vote.
1.00/5 (5 votes)
See more:
I want to know that about ASP.NET page Life cycle
Posted
Comments
Dave Kreskowiak 25-Jan-16 8:14am    
Why all the one votes? because you could have EASILY found this yourself just by Googling for "ASP.NET page life cycle" and start reading.

Following are the general ASp.NET Page life cycle
1. Page request : The page request occurs before the page life cycle begins
2. Start : In the start stage, page properties such as Request and Response are set
3. Initialization : During page initialization, controls on the page are available and each control's UniqueID property is set
4. Load : During load, if the current request is a postback, control properties are loaded with information recovered from view state and control state.
5. PostBack : If the request is a postback, control event handlers are called
6. Rendering : Before rendering, view state is saved for the page and all controls.
7. Unload : The Unload event is raised after the page has been fully rendered.
 
Share this answer
 
C#
Following are the page life cycle events:

PreInit - PreInit is the first event in page life cycle. It checks the IsPostBack property and determines whether the page is a postback. It sets the themes and master pages, creates dynamic controls, and gets and sets profile property values. This event can be handled by overloading the OnPreInit method or creating a Page_PreInit handler.

Init - Init event initializes the control property and the control tree is built. This event can be handled by overloading the OnInit method or creating a Page_Init handler.

InitComplete - InitComplete event allows tracking of view state. All the controls turn on view-state tracking.

LoadViewState - LoadViewState event allows loading view state information into the controls.

LoadPostData - During this phase, the contents of all the input fields are defined with the <form> tag are processed.

PreLoad - PreLoad occurs before the post back data is loaded in the controls. This event can be handled by overloading the OnPreLoad method or creating a Page_PreLoad handler.

Load - The Load event is raised for the page first and then recursively for all child controls. The controls in the control tree are created. This event can be handled by overloading the OnLoad method or creating a Page_Load handler.

LoadComplete - The loading process is completed, control event handlers are run, and page validation takes place. This event can be handled by overloading the OnLoadComplete method or creating a Page_LoadComplete handler

PreRender - The PreRender event occurs just before the output is rendered. By handling this event, pages and controls can perform any updates before the output is rendered.

PreRenderComplete - As the PreRender event is recursively fired for all child controls, this event ensures the completion of the pre-rendering phase.

SaveStateComplete - State of control on the page is saved. Personalization, control state and view state information is saved. The HTML markup is generated. This stage can be handled by overriding the Render method or creating a Page_Render handler.

UnLoad - The UnLoad phase is the last phase of the page life cycle. It raises the UnLoad event for all controls recursively and lastly for the page itself. Final cleanup is done and all resources and references, such as database connections, are freed. This event can be handled by modifying the OnUnLoad method or creating a Page_UnLoad handler.
 
Share this answer
 

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900