Since there are hundreds of controls and vendors in the VB6 market, many migration customers are looking to automatically convert their references to legacy 3rd party components to revamped .NET versions.

The Visual Basic Upgrade Companion’s core functionality can be customized to satisfy your specific VB6 to .NET migration needs in terms of control/library automated conversion ratio.

The VBUC’s extensibility approach allows you to automatically upgrade your specific programming patterns, to add some new functionality on the migrated .NET application, and also to convert the ActiveX controls that you have in the original application to .NET Framework components or newer versions of those specific third-party controls, saving manual efforts, time and money on your VB to .NET migration projects.

Below you can find a list with the ActiveX controls that are currently supported by default by the Visual Basic Upgrade Companion:

The Visual Basic Upgrade Companion features a user-customizable mapping engine called the Custom Maps extensibility. This means the user can specify particular transformations for element occurrences in the original VB6 code, so that they can be converted (mapped) into specific library elements, intrinsic or 3rd party. As a result, the overall VB to .NET migration process’ precision can be enhanced by creating personalized mappings to handle conflictive or particular elements.