>>In VFP when we got a new install, or a new release or started a new app etc., the first thing we'd do is sub-class the base classes to insulate us from changes, and give us flexibility to add higher level functionality etc. Does the same apply in .Net ?
Definitely!!!
>>From my hours of reading, perhaps the wrong books, I haven't seen this mentioned...
Yep. Wrong books. <g> Actually, I don't know if I've seen it mentioned in any of the older books, but I haven't read any newer ones lately ... As far as sub-classing Mere Mortals, I'll have to leave that answer up to someone who uses it. I guess it couldn't hurt though. <g>
>>If it is needed, then surely a useful enhancement to .Net in the future would be to provide a tool that does this automatically (I'll now be told it exists...).
AFAIK, there isn't a tool to do this automatically, but I don't know everything. I hope someone will correct me if I'm wrong. <s>
~~Bonnie
You'll have to take it on a case by case basis. There are some classes don't make sense to subclass such as utility classes ans what not. Other classes make an absolute sense to sub-class because of the specialized functionality that you'll need to add - such as forms, business classes and application class.
Others you might want to sub-class but most don't until they have to are the managers.
