>I thought I wasn't going to ask you any more questions today but I really need to clarify one more thing (sorry for messing up your Sunday afternoon <g>).

Nah, you didn't mess it up. I've been doing a little catch-up work today anyway (in between goofing-off).

>When you create a library of your own classes (subclasses) of basic controls, do you sub-divide them into groups/tabs like VS does: Common Controls, Menus and Toolbars, Data, etc; creating a separate DLL for each one? Like:
>MyComp.WinUi.CommonControls.dll
>MyComp.WinUI.MenusToolbars.dll
>MyComp.WinUI.Data.dll
>
>or
>
>You put them all in the same DLL (e.g. MyComp.WinUi.BasicClasses.dll)?

I have one project ... MyComp.WinUI.BasicClasses.DLL ... all of the simple controls, like TextBox, ComboBox, etc., are all contained in one file (one .cs file). This file basically contains the controls that can't be sub-classed visually. Then there are other, more complex controls (those that *can* be sub-classed visually), forms, menus, ToolBars, etc. in the project too, but they each have their own separate .cs file.

Also, you mentioned MyComp.WinUI.Data.DLL above ... I have a separate namespace for Data. IMHO, it shouldn't be in with the WinUI stuff, since we use it as a data transfer mechanism ... IOW, it's used in all layers, so it needs to be separate. So, it would be something like MyComp.DataSets.BasicClasses.DLL.

~~Bonnie