Rip,

I disagree ... if you decide you need to subclass a control, then you'd still have to go through everything and change that control to use the new subclass. Doesn't matter that it's usually trivial to do (compared to VFP), the fact is that you'd still have to do it.

I *still* think it's better to start off by sub-classing every control that you use.

Just my 2 cents ...
~~Bonnie


>One reason that is the rule in VFP is that if you use the class designer for your classes then it's really hard to change the baseclass of a class.
>
>In c# it's much easier to change the baseclass of a class than it was in VFP so I don't think subclassing if you don't need to is that beneficial.
>
>>That's always been the rule in VFP. Thanks!
>>
>>>Eric,
>>>
>>>I would subclass everything that you intend to use. Don't use the Framework classes directly on your forms, period. Today, you might not think you need to extend such-and-such a class ... but tomorrow you may realize that you needed to. Just go ahead and subclass all that you use now and you won't be kicking yourself in the butt later on.
>>>
>>>~~Bonnie
>>>
>>>
>>>>Is it general practice to subclass all your windows forms controls or just the ones you need to extend?