in the DesignHost why should the RootComponent be a Form even when the class
you may be designing is derived from a form?
Take for example a simple object graph of: (A form with 2 buttons and a user
control):

I am stuck in that, so I need your help. I designed a user control, which is
mainly a GroupBox (GB). When I drag a control in the GB, the new control (NC)
seems to be behind the GB. When I move my GB, the NC appears until I stop
moving the GB. At runtime, the NC does not show up. ...

If you place a textbox on a user control...then put that user control on a
form with a panel, then move the control to the panel, you then can activate
the textbox. In other words it no longer thinks it's in designMode. Anybody
know of this issue or a workaround?

I don't understand why my component appears gray in the toolbox. I added the
[ToolboxItemFilter("NETCF", ToolboxItemFilterType.Require)]
[ToolboxItemFilter("System.CF.Windows.Forms", ToolboxItemFilterType.Custom)]
attributes in my component.

[ Using C# in VS 2003 ]
I want to have a control with a constructor that accepts several parameters.
Unfortunately, the Visual Studio designers insist on parameterless constructors.
The problem is, exposing a parameterless constructor may create the object in an inconsistent state.

Is there a way to make the CollectionEditor readonly?
Looks like CollectionEditor uses CollectionForm, and CollectionForm
includes this field:
   internal virtual bool CollectionEditable { get; set; }

Is there a way for me to refresh the entire form to allow controls with
transparent backgrounds to refresh correctly and be superimposable?