>Is that so different than any other software development platform?

No, not at all. That's why I've been sub-classing "name-your-language" base classes for many, many, *many* years! <g>

~~Bonnie



>I haven't been around the software development game that long, but my expectations would be that if I am using VB 2.0 then I should have no problems with functionality changes even if I apply service packs. However, if I am using VB 2.0 and upgrade to 3.0, I should probably expect a few things to change. Is that so different than any other software development platform?
>
>>Derek,
>>
>>I sub-class from all kinds of .NET base classes, but *not* because I'm worried that the functionality might change with newer versions, but because the existing functionality is typically not good enough for me.
>>
>>~~Bonnie
>>
>>
>>>>>> How would sub-classing help in such a case?
>>>
>>>Simple example: If you use "new StreamWriter()" all over the code as opposed to one place in your own subclass - if/when the functionality (of StreamWriter) gets changed or discontinued, you either have hundreds of places to modify or one place--in your class code.
>>>
>>>So you don't subclass anything?
>>>
>>>Do you believe base classes in .NET version 2.0 will work the same in .NET 5.0 or 7.0?