Partial (Visual Basic)


Indicates that a type declaration is a partial definition of the type.

You can divide the definition of a type among several declarations by using the Partial keyword. You can use as many partial declarations as you want, in as many different source files as you want. However, all the declarations must be in the same assembly and the same namespace.


Visual Basic supports partial methods, which are typically implemented in partial classes. For more information, see Partial Methods (Visual Basic) and Sub Statement (Visual Basic).

[ <attrlist> ] [ accessmodifier ] [ Shadows ] [ MustInherit | NotInheritable ] _
Partial { Class | Structure | Interface | Module } name [ (Of typelist) ]
    [ Inherits classname ]
    [ Implements interfacenames ]
    [ variabledeclarations ]
    [ proceduredeclarations ]
{ End Class | End Structure }




Optional. List of attributes that apply to this type. You must enclose the Attribute List (Visual Basic) in angle brackets (< >).


Optional. Specifies what code can access this type. See Access Levels in Visual Basic.


Optional. See Shadows (Visual Basic).


Optional. See MustInherit (Visual Basic).


Optional. See NotInheritable (Visual Basic).


Required. Name of this type. Must match the name defined in all other partial declarations of the same type.


Optional. Specifies that this is a generic type. See Generic Types in Visual Basic (Visual Basic).


Required if you use Of. See Type List (Visual Basic).


Optional. See Inherits Statement.


Required if you use Inherits. The name of the class or interface from which this class derives.


Optional. See Implements Statement.


Required if you use Implements. The names of the interfaces this type implements.


Optional. Statements which declare additional variables and events for the type.


Optional. Statements which declare and define additional procedures for the type.

End Class or End Structure

Ends this partial Class or Structure definition.

Visual Basic uses partial-class definitions to separate generated code from user-authored code in separate source files. For example, the Windows Form Designer defines partial classes for controls such as Form. You should not modify the generated code in these controls.

All the rules for class, structure, interface, and module creation, such as those for modifier usage and inheritance, apply when creating a partial type.

  • Under normal circumstances, you should not split the development of a single type across two or more declarations. Therefore, in most cases you do not need the Partial keyword.

  • For readability, every partial declaration of a type should include the Partial keyword. The compiler allows at most one partial declaration to omit the keyword; if two or more omit it the compiler signals an error.

  • Union of Declarations. The compiler treats the type as the union of all its partial declarations. Every modifier from every partial definition applies to the entire type, and every member from every partial definition is available to the entire type.

  • Type Promotion Not Allowed For Partial Types in Modules. If a partial definition is inside a module, type promotion of that type is automatically defeated. In such a case, a set of partial definitions can cause unexpected results and even compiler errors. For more information, see Type Promotion (Visual Basic).

    The compiler merges partial definitions only when their fully qualified paths are identical.

The Partial keyword can be used in these contexts:

Class Statement

Structure Statement

The following example splits the definition of class sampleClass into two declarations, each of which defines a different Sub procedure.

Partial Public Class sampleClass
    Public Sub sub1()
    End Sub
End Class
Partial Public Class sampleClass
    Public Sub sub2()
    End Sub
End Class

The two partial definitions in the preceding example could be in the same source file or in two different source files.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
© 2015 Microsoft