Thanks Keven - great little article. Based on the following statements in
the article...
"a control is unable to invoke its parent until the tree of controls on a
page has been populated"
and
"CreateChildControls can be invoked when loading a page, during data
binding, or during rendering"
.... I'm concluding that the scenario I have created (as described in the OP)
is just fine - if not what must happen. If I'm totally wrong about that,
then please let me know - otherwise have a great day!
-Frankie
"Kevin Spencer" <ke***@DIESPAMMERSDIEtakempis.com> wrote in message
news:ei***************@TK2MSFTNGP12.phx.gbl...
Hi Frankie,
The following >Net SDK article on Control Execution Lifecycle should clear
everything up for you. I keep a print-out of it on my office wall!
http://msdn.microsoft.com/library/de...nLifecycle.asp
--
HTH,
Kevin Spencer
Microsoft MVP
.Net Developer
Ambiguity has a certain quality to it.
"Frankie" <A@B.COM> wrote in message
news:%2****************@TK2MSFTNGP10.phx.gbl...I have a user control into which I insert a bunch of controls dynamically.
I have it all working just fine - Everything is there on Postback, etc.
I load this user control into a hosting ASPX page at runtime during the
Page_Load event procedure of the hosting ASPX page.
Question: Would it be better to load the user control from the hosting
page's OnInit event rather than Page_Load? Does it matter or not?
I ask because I understand that for dynamic controls to be properly
inserted - it must be done during the OnInit event - which is happening -
but only in the ASCX lifecycle (which gets kicked off from the hosting
aspx page_load).
Thanks.