[karsten samaschke]

I always recommend the use of Denis Bauer's DynamicControlsPlaceholder for this, it basically lets you forget about recreating the controls - you have to re-hookup the events but it makes things a less painful see: http://www.denisbauer.com/ASPNETControls/DynamicControlsPlaceholder.aspx

Why not create them in CreateChildControls like everything else? Page_Init is definately not good, because you are adding an additional event to your page. Always prefer overrides to events when subclassing (if you must use init, use OnInit).

You don't really have to create the controls every time either, but you should always assign IDs to them so that your events will work properly. Otherwise, you have random IDs which will change if the number of controls on the page changes for some reason (which may not be because of anything your code is doing).

However, regardless of all this, you shouldn't add controls dynamically to a page, because it leads to nasty error messages. Not only can you get the invalid viewstate one if you are not careful, but you can't insert <%= "value" %> blocks and other nice things in your pages. Use user controls or composite controls, that is what they are there for.

Ditto Scott's recommendation for DynamicControlsPlaceholder. I've used it in a pretty large application that I developed recently and found it to be excellent!

Ive seen may examples of Dynamic Loading of webcontorls and handling events etc.. But I have a little different problem to deal with. In most provided solutions on websites the classname of the control that needs to be loaded is know at design time. Lets say I have a n number of usercontrols whose classnames and paths are stored in the database. On a page home.aspx, I want these controls to appear and behave normally as a control would.
Key point to note is that I do not have any infomation about the control at design time. How can i do this?

ff