Private (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 declaration context, including from within any contained types.
If a programming element represents proprietary functionality, or contains confidential data, you usually want to limit access to it as strictly as possible. You achieve the maximum limitation by allowing only the module, class, or structure that defines it to access it. To limit access to an element in this way, you can declare it with
- Declaration Context. You can use
Privateonly at module level. This means the declaration context for a
Privateelement must be a module, class, or structure, and cannot be a source file, namespace, interface, or procedure.
Access Level. All code within a declaration context can access its
Privateelements. This includes code within a contained type, such as a nested class or an assignment expression in an enumeration. No code outside of the declaration context can access its
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.
Private modifier can be used in these contexts: