Member Avatar for akraj

Hi !

anyone tell me the link or explain abt ASP.NET Page Life Cycle.

thanks in advance.:-|

  • 5 Contributors
  • 5 Replies
  • 254 Views
  • 1 Year Discussion Span
  • Latest Post Latest Post by kedar_challa

Dani AI

Generated

As ’s link covered the HTTP pipeline (and correctly called that out) and pointed to page-level docs, this note summarizes the ASP.NET Web Forms Page lifecycle (System.Web.UI.Page) and gives practical rules that often solve the common problems raised in this thread. This applies to Web Forms; ASP.NET MVC / Core follow different flows.

Key Web Forms page events (typical order) and their purpose:

  • PreInit — earliest page event: choose master page/theme and create dynamic controls before viewstate is restored.
  • Init — controls are initialized; markup-based properties exist but viewstate is not yet applied.
  • InitComplete — initialization finished (prepares for state restoration).
  • PreLoad — runs after viewstate/post data restores and before Load (rarely needed).
  • Load — page and controls are “loaded”; use IsPostBack here to avoid re-binding data on postbacks.
  • Control events — postback event handlers (Button.Click, etc.) are executed after Load.
  • LoadComplete — finalization of load stage.
  • PreRender / PreRenderComplete — last chance to change controls before viewstate is saved.
  • SaveViewState — framework persists control state.
  • Render — HTML is emitted.
  • Unload — cleanup; do not access Response or control state here.

Practical rule (dynamic controls): recreate server-side dynamic controls at Init (or PreInit if master/themes matter) so viewstate can be restored and events will wire. Example:

protected void Page_Init(object sender, EventArgs e)
{
    Button dyn = new Button();
    dyn.ID = "dynBtn";
    dyn.Text = "Click";
    dyn.Click += new EventHandler(Dyn_Click);
    PlaceHolder1.Controls.Add(dyn);
}

protected void Dyn_Click(object sender, EventArgs e)
{
    // handle postback
}

Troubleshooting tips: missing viewstate or no event firing usually means controls were created too late or IDs change; large viewstate hurts performance—disable EnableViewState where not needed; use tracing or logging (for example add <%@ Page Trace="true" %> during debugging) or put Trace.Write/Debug.WriteLine calls inside lifecycle overrides to observe order. This complements the earlier posts by separating the global HTTP pipeline (modules, HttpApplication events) from per-page lifecycle events.

Recommended Answers

All 5 Replies

Member Avatar for Paladine

Hi !

anyone tell me the link or explain abt ASP.NET Page Life Cycle.

thanks in advance.:-|

Here you are:

Hope this helps :)

Member Avatar for akraj

Hi Paladine!

Its really worth. Thanks a lot!

Kombaraj.

Member Avatar for stewy68

one life cycle coming up

commented: Excellent Site Post +4
Member Avatar for red1980

Here you are: ASP.Net Web Page Processing

That's actually not the life cycle, that's the asp .net pipeline.

Member Avatar for kedar_challa

Here you are: ASP.Net Web Page Processing

That's actually not the life cycle, that's the asp .net pipeline.

Hi Red,

You are right. It is HTTP request processing pipeline explains how the request is manipulated by different objects.

But Page Event Life Cycle contains all the events and methods that executed at the page level when the request comes to the Page object.

Please go through the follwong link, if u want to know about Page Life cycle.
http://www.aspfree.com/c/a/ASP.NET/ASP.NET-Life-Cycle-and-Best-Practices/2/

Thanks,
Kedar

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.