Support.SetItemData(Control, Int32, Int32) Method
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.
Caution
Microsoft.VisualBasic.Compatibility.* classes are obsolete and supported within 32 bit processes only. http://go.microsoft.com/fwlink/?linkid=160862
Sets the ItemData property for a ListBoxItem.
public:
static void SetItemData(System::Windows::Forms::Control ^ Control, int Index, int ItemData);
public static void SetItemData (System.Windows.Forms.Control Control, int Index, int ItemData);
[System.Obsolete("Microsoft.VisualBasic.Compatibility.* classes are obsolete and supported within 32 bit processes only. http://go.microsoft.com/fwlink/?linkid=160862")]
public static void SetItemData (System.Windows.Forms.Control Control, int Index, int ItemData);
static member SetItemData : System.Windows.Forms.Control * int * int -> unit
[<System.Obsolete("Microsoft.VisualBasic.Compatibility.* classes are obsolete and supported within 32 bit processes only. http://go.microsoft.com/fwlink/?linkid=160862")>]
static member SetItemData : System.Windows.Forms.Control * int * int -> unit
Public Sub SetItemData (Control As Control, Index As Integer, ItemData As Integer)
Parameters
- Index
- Int32
The Index
of the ListBoxItem.
- Attributes
Remarks
In Visual Basic 6.0, the ItemData
property for a ListBox
or ComboBox
control could be set at design time in the Properties window to associate an Integer
with a ListBox
or ComboBox
item. In Visual Basic, the ItemData
property no longer exists; the GetItemData and SetItemData
methods can be used to emulate the behavior of ItemData
.
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 2008. 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.