Friend and Protected Friend in VB.NET
Friday May 15, 2009
In addition to the three access modifiers we have always had - Public, Private and Friend - VB.NET adds one and a half more - Protected and Protected Friend. The last only counts for half because it's really just the union of two of the others. Why do we need these? ... This Quick Tip tells you.
Dan, I’ve been programming for many years in various language, but have only played around in true Object Oriented languages like Java. It’s quite a learning curve for an old-time programmer.
I’ve been programming in VB for many years. I can’t say that I’ve ever had a need for inheritance! It’s a cool idea and I understand the press about not re-inventing the wheel, but I’ve never banged my head against the wall saying “if only I had inheritance!”
Now that I am in a position where I MUST learn VB.Net, I’m wondering if I’ll get religion on this!
It would be to your best interest to get religion on this!
On a basic level, you don’t create inherited classes yourself a lot, but you have a heck of a time using some of the technology available to you when you don’t ‘get’ the concepts.