ImageListArray Constructors
Definition
Important
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
Initializes a new instance of the ImageListArray class.
Overloads
| ImageListArray() |
Initializes a new instance of the ImageListArray class. |
| ImageListArray(IContainer) |
Initializes a new instance of the ImageListArray class, specifying its container. |
ImageListArray()
Initializes a new instance of the ImageListArray class.
public:
ImageListArray();public ImageListArray ();Public Sub New ()Remarks
When you instantiate an ImageListArray, 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
ImageListArray(IContainer)
Initializes a new instance of the ImageListArray class, specifying its container.
public:
ImageListArray(System::ComponentModel::IContainer ^ Container);public ImageListArray (System.ComponentModel.IContainer Container);new Microsoft.VisualBasic.Compatibility.VB6.ImageListArray : System.ComponentModel.IContainer -> Microsoft.VisualBasic.Compatibility.VB6.ImageListArrayPublic Sub New (Container As IContainer)Parameters
- Container
- IContainer
The IContainer where the control array will be hosted.
Remarks
When you instantiate an ImageListArray, 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.
