Profile Manager

The Visual Basic Upgrade Companion sports several optional features to include particular transformations techniques during the upgrade stage. All the switchable options are displayed in the Profile Manager Window accessible from different parts of the main window. Each set of selected features is called an Upgrade Profile.

Upgrade Profiles

The Visual Basic Upgrade Companion has different upgrade profiles depending on the Edition and Mode being currently used. The included profiles are described as follows:

  • Visual Basic Upgrade Companion Enterprise Edition
    • Default: default profile to upgrade to VB.NET or C#.NET depending on the current license. This profile relies on COM Interop and additional support code to automatically bridge the functionality gap between VB6 and .NET.
    • .NET Native: This profile takes advantage of native .NET features in the migrated code by replacing all supported controls and language structures by their .NET equivalents, including visual components and replacing the database access layer with ADO.NET. May require additional manual intervention to bridge the gap between Visual Basic 6 and the .NET Framework
  • Visual Basic Upgrade Companion Developer Edition
    • Fixed Profile: this profile is not able to be modified. Is based in the Enterprise Edition default profile.
  • Assessment Mode
    • Fixed Profile: This mode is not able to start the upgrade process.

In the VBUC Enterprise Edition, the user can customize the current profile by clicking over the “Edit” button in the “General Settings” container from the main window, or, by clicking over the file menu and then over “Manage Upgrade Profiles”.

At this point, the Profile Manager window will be displayed. This window is equipped with a menu and a toolbar with options for creating, saving and deleting custom Upgrade Profiles. There’s as well a combo box called “Available Profiles” which allows alternating between the already existing profiles.

All the user profiles are saved in to the installation path on the folder “\profiles” as [profilename].pro. The default profiles are embedded in the application and can’t be edited or deleted.

Optional Features

All the items contained in the Profile Manager are arranged into two different categories:

  • Component Maps: These optional features are used to port 3rd party components to different versions of their respective .NET counterparts. The full list of Component Maps is described in section 3rd Party Library Support.
  • Code Conversion Rules: These settings are able to change the shape and behavior of the resulting source code. For detailed information about the actual benefits of turning these options on or off please read Appendix A.
Skip Navigation Links.