After that, the Validate method of all validator controls is called, which sets the IsValid property of individual validator controls and of the page. If the request is a postback, control event handlers are called. 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.ĭuring load, if the current request is a postback, control properties are loaded with information recovered from view state and control state. A master page and themes are also applied to the page if applicable. The page also sets the UICulture property.ĭuring page initialization, controls on the page are available and each control's UniqueID property is set. At this stage, the page also determines whether the request is a postback or a new request and sets the IsPostBack property. In the start stage, page properties such as Request and Response are set. 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. The page request occurs before the page life cycle begins. For postbacks, the page life cycle is the same during a partial-page postback (as when you use an UpdatePanel control) as it is during a full-page postback. Some parts of the life cycle occur only when a page is processed as a postback. For more information, see Introduction to the ASP.NET Application Life Cycle and ASP.NET Application Life Cycle Overview for IIS 7.0. In addition to the page life-cycle stages, there are application stages that occur before and after a request but are not specific to a page. In general terms, the page goes through the stages outlined in the following table. This topic contains the following sections:Īdditional Page Life Cycle Considerationsĭata Binding Events for Data-Bound Controls The life cycle of a control is based on the page life cycle, and the page raises many of the events that you need to handle in a custom control. If you develop custom controls, you must be familiar with the page life cycle in order to correctly initialize controls, populate control properties with view-state data, and run control behavior code.
APS.NET PDFWRITER DOCUMENT CODE
It is important for you to understand the page life cycle so that you can write code at the appropriate life-cycle stage for the effect you intend. These include initialization, instantiating controls, restoring and maintaining state, running event handler code, and rendering.
APS.NET PDFWRITER DOCUMENT SERIES
When an ASP.NET page runs, the page goes through a life cycle in which it performs a series of processing steps.
0 kommentar(er)
