WebBrowserArray Constructors

Definition

Namespace:

Microsoft.VisualBasic.Compatibility.VB6

Assembly:

Microsoft.VisualBasic.Compatibility.dll

Initializes a new instance of the WebBrowserArray class.

Overloads

WebBrowserArray()	Initializes a new instance of the WebBrowserArray class.
WebBrowserArray(IContainer)	Initializes a new instance of the WebBrowserArray class, specifying its container.

WebBrowserArray()

Initializes a new instance of the WebBrowserArray class.

public:
 WebBrowserArray();

public WebBrowserArray ();

Public Sub New ()

Remarks

When you instantiate a WebBrowserArray, 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.

WebBrowserArray(IContainer)

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

public:
 WebBrowserArray(System::ComponentModel::IContainer ^ Container);

public WebBrowserArray (System.ComponentModel.IContainer Container);

new Microsoft.VisualBasic.Compatibility.VB6.WebBrowserArray : System.ComponentModel.IContainer -> Microsoft.VisualBasic.Compatibility.VB6.WebBrowserArray

Public Sub New (Container As IContainer)

Parameters

Container

IContainer

The IContainer where the control array will be hosted.

Remarks

When you instantiate a WebBrowserArray, 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.