Page_PreInit

[rn5a]

In the article titled "ASP.NET Page Life Cycle Overview" at
http://msdn2.microsoft.com/en-us/library/ms178472.aspx, under the
topic "Life-cycle Events", for the Page Event named PreInit, it is
stated that

-------------------------------------
If the request is a postback, the values of the controls have not yet
been restored from view state. If you set a control property at this
stage, its value might be overwritten in the next event.
-------------------------------------

Can someone please explain me the first sentence with a small code
sample (maybe using just a TextBox & a Button)?

Also if a control property is set during PreInit, then upon postback,
its value will ALWAYS be overwritten in the next event rather than
MIGHT be overwritten in the next event (as stated in the second
sentence), isn't it?

Thanks

 

[George Ter-Saakov]

If page has controls then first Init of all those controls is called before
Init of the page is called.
sometimes you need to execute some lines first, before anything even
started.
Like in my case each page is checking if user has been properly logged in
and recreated the Context (like permissions, first, last names..) of the
user. (get's it from cache)

Then all controls are simply relying on that context being there.

for that method PreInit was created. PreInit is the one that called first.
Obviously if you try to manipulate controls at that stage they might
override it in the Init process.
Example is textbox. If you try to set it's value in PreInit then that value
will be overridden when controls read it's own value from PostBack stream..
(the one that browser sent responding you clicking button submit).




George.

 

[Lloyd Sheen]

If page has controls then first Init of all those controls is called
before Init of the page is called.
sometimes you need to execute some lines first, before anything even
started.
Like in my case each page is checking if user has been properly logged in
and recreated the Context (like permissions, first, last names..) of the
user. (get's it from cache)

Then all controls are simply relying on that context being there.

for that method PreInit was created. PreInit is the one that called first.
Obviously if you try to manipulate controls at that stage they might
override it in the Init process.
Example is textbox. If you try to set it's value in PreInit then that
value will be overridden when controls read it's own value from PostBack
stream.. (the one that browser sent responding you clicking button
submit).




George.

Just to add another use. Lets say you create a dynamic control. Now you
postback causing the page to try to restore the properties of the dynamic
control if it has viewstate. If you do not create the control in the
pre_init your page will fail.

LS