|Important||This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here.|
VBControlExtender Object for Visual Basic 6.0 Users
The Visual Basic 6.0 VBControlExtender object has no equivalent in Visual Basic 2005, and it is no longer necessary to use a control extender to host an ActiveX control.
In Visual Basic 6.0, the VBControlExtender object is used to provide access to properties of a host form to an ActiveX control. The VBControlExtender object is primarily used when dynamically adding a control to the Controls collection using the Add method. The VBControlExtender object is particularly useful for this purpose because it provides a generic set of properties, events, and methods to the developer.
In Visual Basic 2005, ActiveX controls can be hosted directly on a Windows form; they no longer require an extender object to access the properties of the host form. When an ActiveX control is added to a project, a COM interop wrapper is created, allowing you to use the ActiveX control as you would any other control.
When a Visual Basic 6.0 project is upgraded to Visual Basic 2005, any instances of the VBControlExtender object are ignored. A COM interop wrapper is created for each ActiveX control; property, method, and events are mapped to their equivalents. Where there are no equivalents, upgrade warnings are added to the code.