What is the purpose of CreateChildControls()?

[Michael]

Hi,

I'm coding a custom server control, and CreateChildControls() is giving me
some pain. I'm just wondering why we have CreateChildControls(), and why
this methods seems to be called at different times in the page lifecycle. I
mean the order it is called is not deterministic. Example if not post back,
then my CreateChildControls() is being executed before my Load event. But
for post back, my Load event executes before my CreateChildControls().

I suppose calling EnsureChildControls() will call CreateChildControls() if
it has not already been called. But why all this complication? I'm even
thinking about creating my controls in the constructor instead of inside
CreateChildControls(); at least this way I know that my controls will have
been created when I need to use them.

[Kevin Spencer]

Hi Michael,

Here's a good reference for this:

http://msdn.microsoft.com/library/de...nLifecycle.asp

At the bottom, there is a note:

"The CreateChildControls method is not listed in the table because it is
called whenever the ASP.NET page framework needs to create the controls tree
and this method call is not limited to a specific phase in a control's
lifecycle. For example, CreateChildControls can be invoked when loading a
page, during data binding, or during rendering."

--
HTH,

Kevin Spencer
Microsoft MVP
Professional Chicken Salad Alchemist

A lifetime is made up of
Lots of short moments.

"Michael" <mi*****@somewhere.com> wrote in message
news:Ou**************@TK2MSFTNGP05.phx.gbl...

Hi,

I'm coding a custom server control, and CreateChildControls() is giving me
some pain. I'm just wondering why we have CreateChildControls(), and why
this methods seems to be called at different times in the page lifecycle.
I mean the order it is called is not deterministic. Example if not post
back, then my CreateChildControls() is being executed before my Load
event. But for post back, my Load event executes before my
CreateChildControls().

I suppose calling EnsureChildControls() will call CreateChildControls() if
it has not already been called. But why all this complication? I'm even
thinking about creating my controls in the constructor instead of inside
CreateChildControls(); at least this way I know that my controls will have
been created when I need to use them.