I'm wondering if I should be subclassing some very basic .NET classes to protect against Microsoft changing or discontinuing a class in future versions.

This occurred to me with File IO but it obviously applies to others. Right now Streams are used for reading and writing - if I use new StreamWriter() or new StreamReader() all over my code and Microsoft decides in .NET 5.0 to alter or discontinue the functionality - wow, I'd be in for some work!

I guess if I hadn't had to deal with Microsoft's discontinuation of VFP, I wouldn't be asking this question: what do you guys do or think about the above?

Thanks in advance.