>It comes from your FoxPro background, where the norm was "subclass everything". I've *never* seen that pushed in .NET, even with WinForms.
>
>>Ok, now I understand. I was having trouble comprehending this morning what it was that meant. I agree, on both counts. I have been doing MVVM as well and right now dealing with an application that has every control subclassed and because of this, no designer support on any visual view. Everytime something is broken we have to first determine if this is because of the subclassed controls. Even all the third party stuff has been subclassed. I am not thinking this was a great idea.
>>
>>Thanks for clarifying.
>>Timothy

Um well it didn't come from me at all as I didn't do it. I have been trying to undo it to regain designer support and reduce the time to track down bugs. However, I would agree in FoxPro but also in Windows Forms it is better to have your own base classes so you have a place to enhance controls already in place. In WPF, this just doesn't have the same meaning.

Timothy