- INDEX VB TO NET
- VBUC FEATURES
- OPTIONAL THIRD-PARTY LIBRARY MAPPINGS
Optional Third Party Library Mappings
By default any third-party library is upgraded to .NET using a “COM-Interop” wrapper around the original VB6 library. This process generates a .NET library with an equivalent behavior to the original one as well as a quick and smooth conversion process, but using a legacy component in the back of the managed code wrapper.
In some cases, a more elaborate process is desirable to convert a COM third-party library to a similar .NET library. While many of the third-party libraries don't have a fully equivalent library in .NET, it's common to find similar libraries implementing part of the functionality. In some cases it is possible to automatically convert almost all of the functionality, especially when the same vendor has versions of its components in both VB6 and .NET.
The VBUC includes a set of mapping plug-in dlls designed to automatically convert functionality from legacy ActiveX libraries to .NET libraries, saving thus an important amount of time in code analysis and manual modifications. Each plug-in dll contains the transformation specifications for a third-party library.
Turning mapping plug-ins on/off
All the included mappings and features can be enabled/disabled from the Graphical User Interface in the Profile Manager. This tool is used to save all the upgrade preferences into a profile, which can be modeled to fit specific upgrade requirements. Please read the section “Upgrade Manager” for more details.
The Visual Basic Upgrade Companion Developer Edition has a fixed migration profile which can’t be modified. The mappings included on this profile are:
- MSComCtlLib
- MSComCtl2
- MSACAL
- MSComDlg
- MsMask
- RichTextBox
- PrinterObject
Download VBUC Free Trial
It's time to eradicate VB6
8 Proven Tips for
Planning a Successful Migration