1.Page_PreInit
|
This event is the beginning of the page life
cycle. Every page controls are initialized and the properties are set
according to aspx source code.
- Possible
to Change or set Master page, Themes
- Creates
or re-creates dynamic controls.
- Reads
or sets Profile property values.
|
2.Page_Init
|
First,
the Init event for the Page object occurs, and then Init event occurs for
each control on the Page. Viewstate information is not available at this
stage.
- Controls have been
initialized
- Theme skins applied if any.
- Initialize control
properties.
|
3.Page_InitComplete
|
This event is used to processing tasks
that require all initialization be complete
|
4.Page_PreLoad
|
This event is used
before Perform any processing that should occur before Load. 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.
|
5.Page_Load
|
Allows actions that are common to every
request to be
placed here. Note that the
control is stable at this time; it has been
initialized and its state has been reconstructed.
|
6.Control Events
|
These are control
specific events such as – Button Click, DropDownIndexChanged etc.
|
7.Page_LoadComplete
|
This event is used for performing those
tasks which require load has been completed.
|
8.Page_PreRender
|
In this event page
insures that all child controls are created. Page calls EnsureChildControls
for all controls, including itself. Every controls whose datasource/databind
property is set calls for its databind method.
|
9.SaveViewState
|
This event occurs after viewstate encoded
and saved for the page and for all controls.
|
10.Page_Render
|
Every ASP.NET control
has render method and the page instance calls this method to output the
control’s markup, after this event any changes to the page or controls are
ignored
|
11.Page_Unload
|
Unload event used to do cleanup task like
closing the database connections, closing of the open files, completing
logging or other requested tasks. Unload events occurs for each control on
page control tree first and after that page. |