ASP.Net Page Life Cycle Events:
At each stage of the page life cycle, the page raises some
events, which could be coded. An event handler is basically a function or
subroutine, bound to the event, using declarative attributes like Onclick or
handle.
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 defined with the
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.
No comments:
Post a Comment
Comments Welcome