Alan,

I think it's overkill for the simple controls ... those like TextBox, ComboBox, etc. There's no real reason, IMHO, to be able to visually sub-class these types of controls.

Others, however, are good candidates for this. ToolBar being an excellent example. Our ToolBarControl is a UserControl with a ToolBar on it.

So, there's nothing wrong with creating controls this way, in fact it's definitely good practice ... I just wouldn't go overboard and do it for each and every control.

I have no idea if there's a list of controls that are able to be sub-classed visually ... I've never searched for one.

~~Bonnie



>I am currently building a project of base-classes which I can reference from other projects/solutions. I already have a set of base-controls which are subclassed in a single .cs file, and now I am embarking on subclassing the classes which can be done visually. Apart from forms and usercontrols, what other controls and/or containers can be subclassed visually? Is there a list anywhere?
>
>For controls which cannot be subclassed visually (eg. a textbox), is there any reason why I can't place each one within its own user-control (eg. called UserTextBox) so that the subclass becomes visual and properties can be accessed/changed via. the property sheet? I can see this method being useful eg. for toolbar classes which could be designed visually instead of in code.
>Would this be regarded as bad C#/VS/.NET practice? Apart from the extra overhead of having each control contained within a user-control, are there any other good reasons why it should not be done?
>
>
>TIA
>
>Alan