What’s the advantage of using .NET intrinsic controls?
Many controls in Visual Basic 6.0 that enhanced the GUI of an application were available by means of importing ActiveX libraries. Many of these components are automatically migrated to .NET by the Visual Basic Upgrade Wizard, but not to their intrinsic counterparts in Visual Basic .NET. Instead, they are converted to ActiveX components. Note: there’s an enhanced enterprise version of this migration tool, called the Visual Basic Upgrade Companion, that converts additional commonly used ActiveX controls to Windows Forms controls that offer similar functionality, and promotes the use of .NET native libraries when possible, instead of VB Compatibility libraries. Even though most of the ActiveX controls upgraded from VB 6.0 will work fine when upgraded to VB .NET, you might be better off substituting them for native Windows Forms controls. You can make your project easier to maintain by removing references to ActiveX controls that are not imperative to use. Furthermore, by removing the refe
