I've heard Microsoft Visual Basic 6.0 developers say things like "Well, I don't really need inheritance in my object designs." They wonder why getting inheritance in Microsoft Visual Basic .NET is such a big deal. I think many of these developers have really needed inheritance all alongthey just didn't realize it.
To see why, let's look at how collections are managed in Visual Basic 6.0, and then how things change in Visual Basic. NET. I should first point out that if you don't use collections in your object designs, then you are not really using object orientation in depth. It's probably appropriate for you to invest some more time in object-oriented philosophy, because that understanding is central to using .NET most effectively. For the rest of this article, I'll assume you are proficient with collections in Visual Basic 6.0, and talk about differences in working with them in Visual Basic .NET. In particular, I'll talk about how you use inheritance in conjunction with collection classes.