Edit

Share via


DriveListBoxArray Constructors

Definition

Initializes a new instance of the DriveListBoxArray class.

Overloads

DriveListBoxArray()

Initializes a new instance of the DriveListBoxArray class.

DriveListBoxArray(IContainer)

Initializes a new instance of the DriveListBoxArray class, specifying its container.

DriveListBoxArray()

Initializes a new instance of the DriveListBoxArray class.

public:
 DriveListBoxArray();
public DriveListBoxArray ();
Public Sub New ()

Remarks

When you instantiate a DriveListBoxArray, you must also call the SetIndex method to create the initial element in the array.

Note

Functions and objects in the Microsoft.VisualBasic.Compatibility.VB6 namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.

Applies to

DriveListBoxArray(IContainer)

Initializes a new instance of the DriveListBoxArray class, specifying its container.

public:
 DriveListBoxArray(System::ComponentModel::IContainer ^ Container);
public DriveListBoxArray (System.ComponentModel.IContainer Container);
new Microsoft.VisualBasic.Compatibility.VB6.DriveListBoxArray : System.ComponentModel.IContainer -> Microsoft.VisualBasic.Compatibility.VB6.DriveListBoxArray
Public Sub New (Container As IContainer)

Parameters

Container
IContainer

The IContainer where the control array will be hosted.

Remarks

When you instantiate a DriveListBoxArray, you must also call the SetIndex method to create the initial element in the array.

Note

Functions and objects in the Microsoft.VisualBasic.Compatibility.VB6 namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.

Applies to