>>Indeed it does mean that. I guess I need to move that up on my priority list. When I started out, I was feeling a bit overwhelmed and that was just one less thing to deal with. I'll be paying for that decision for a while.
>
>One less thing to deal with perhaps, but a pretty important one to dismiss, unfortunately. And, to make you feel even worse about it ... ;-) ... here's how easy it is to do:
>
>Basically, you'll want a class library that contains your sub-classed UI controls, like textbox, button, etc. Something like this:
>

>using System;
>using System.Drawing;
>using System.Collections;
>using System.ComponentModel;
>using System.Windows.Forms;
>using System.Data;
>
>namespace MyCompany.MyFramework.WinUI.MyClasses
>{
>	public class MyComboBox : System.Windows.Forms.ComboBox
>	{
>		// code here
>	}
>
>	public class MyTextBox : System.Windows.Forms.TextBox
>	{
>		// code here
>	}
>
>	public class MyButton : System.Windows.Forms.Button
>	{
>		// code here
>	}
>}
>

>That's it. And you could have started off with no code in them at all, and added as needed. These controls can't be sub-classed visually, but as you can see, it's easy enough to do it in code. I have all the basic controls sub-classed in one class library file. Once they're added to the ToolBox, then can be dragged onto any design surface in the IDE.
>
>~~Bonnie

Thanks, Bonnie. I'll move that up on my priority list. I think it was not having a visual way to do it that kept me from starting out with that. I'm feeling a lot more at ease with the .NET way of doing things now.