>That could be. I've never looked at WF frameworks. But I *have* attended *lots* of .NET conferences and several MVP Summits at Microsoft and never heard anyone say you should subclass everything. In fact, I rarely heard that you should subclass. (Note: Interfaces are a different story)

In the early days of .NET (1.0 and 1.1), there were some WinForm controls that didn't work quite right and sub-classing them was the only way to get around their quirkiness (ComboBoxes come to mind, I think ... it was a long time ago <g>). Plus, it seemed at the time, that I was always needing to add some functionality to a control (TextBox or whatever), that was needed throughout my application. So, we sub-classed everything. Now, granted, I had just jumped from VFP to .NET, so perhaps it was out of habit. But, at the time, it seemed the only way to solve the issues we were having.

Not sure what point you're trying to make about interfaces ...

~~Bonnie