Protected (Visual Basic)
Updated: July 20, 2015
For the latest documentation on Visual Studio 2017, see Visual Studio 2017 Documentation.
Specifies that one or more declared programming elements are accessible only from within their own class or from a derived class.
Sometimes a programming element declared in a class contains sensitive data or restricted code, and you want to limit access to the element. However, if the class is inheritable and you expect a hierarchy of derived classes, it might be necessary for these derived classes to access the data or code. In such a case, you want the element to be accessible both from the base class and from all derived classes. To limit access to an element in this manner, you can declare it with
Declaration Context. You can use
Protectedonly at class level. This means the declaration context for a
Protectedelement must be a class, and cannot be a source file, namespace, interface, module, structure, or procedure.
Combined Modifiers. You can use the
Protectedmodifier together with the Friend modifier in the same declaration. This combination makes the declared elements accessible from anywhere in the same assembly, from their own class, and from derived classes. You can specify
Protected Friendonly on members of classes.
Access Level. All code in a class can access its elements. Code in any class that derives from a base class can access all the
Protectedelements of the base class. This is true for all generations of derivation. This means that a class can access
Protectedelements of the base class of the base class, and so on.
Protected access is not a superset or subset of friend access.
Access Modifiers. The keywords that specify access level are called access modifiers. For a comparison of the access modifiers, see Access Levels in Visual Basic.
Protected modifier can be used in these contexts: