S
Seth Petry-Johnson
Is there a way to compile a user control into a redistributable
assembly [i.e. server control], but still have access to its child
controls using the .Controls property?
Here's what I mean:
I have a user control that contains some child controls, mostly custom
text boxes and such. If I load this control declaratively or using
LoadControl(), I can access those child controls using the .Controls
property.
However, I need this control to be redistributable, ideally as a .dll.
I found a blog post [http://blogs.msdn.com/davidebb/archive/
2005/10/30/487160.aspx] that explains how the user control can be
compiled into an assembly that can then be used just like a server
control.
That technique works fine, except that when I load the control I can
no longer iterate those child controls; the .Controls property returns
an empty collection.
Anyone have any suggestions?
Thanks so much in advance,
Seth Petry-Johnson
assembly [i.e. server control], but still have access to its child
controls using the .Controls property?
Here's what I mean:
I have a user control that contains some child controls, mostly custom
text boxes and such. If I load this control declaratively or using
LoadControl(), I can access those child controls using the .Controls
property.
However, I need this control to be redistributable, ideally as a .dll.
I found a blog post [http://blogs.msdn.com/davidebb/archive/
2005/10/30/487160.aspx] that explains how the user control can be
compiled into an assembly that can then be used just like a server
control.
That technique works fine, except that when I load the control I can
no longer iterate those child controls; the .Controls property returns
an empty collection.
Anyone have any suggestions?
Thanks so much in advance,
Seth Petry-Johnson