The page will be activated in the following sequence:

Execution sequence of page events in ASP. NET 2.0

The page will be activated in the following order: Page. preinit Page. init Page. initcomplite Page. Preload Page. Load Page. loadcomplete Page. prerender Page. prerendercomplete If a page is inherited from a page, such as basepage: system. web. UI. page, some extensions are made in the basepage, such as permission check. When other pages inherit from the basepage, the order of activation of the events of the basepage and the final page is: Ui. preinit Page. preinit Ui. init Page. init Ui. initcomplite Page. initcomplite Ui. Preload Page. Preload Ui. Load Page. Load Ui. loadcomplete Page. loadcomplete Ui. prerender Page. prerender Ui. prerendercomplete Page. prerendercomplete If masterpage is used, the events in masterpage and those in contentpage are activated in the following order: Contentpage. preinit Master. init Contentpage. init Contentpage. initcomplite Contentpage. Preload Contentpage. Load Master. Load Contentpage. loadcomplete Contentpage. prerender Master. prerender Contentpage. prerendercomplete Furthermore, if contentpage inherits the basepage, the execution sequence of each event is changed: Ui. preinit Contentpage. preinit Master. init Ui. init Contentpage. init Ui. initcomplite Contentpage. initcomplite Ui. Preload Contentpage. Preload Ui. Load Contentpage. Load Master. Load Ui. loadcomplete Contentpage. loadcomplete Ui. prerender Contentpage. prerender Master. prerender Ui. prerendercomplete Contentpage. prerendercomplete