UPGRADE_ISSUE: (2064) Line property Line1.Y2 was not upgraded. UPGRADE_ISSUE: (2064) Line property Line1.Y1 was not upgraded. UPGRADE_ISSUE: (2064) Line property Line1.X2 was not upgraded. UPGRADE_ISSUE: (2064) Line property Line1.X1 was not upgraded. Those lines will cause a compilation error unless they get manually corrected by an equivalent. NET, and the VBUC generates a warning message indicating that. This might cause a number of compilation errors that might hide other issues that need to be resolved manually.įor instance, the sample below shows properties of a VB6 Line Control that don’t have an equivalent in. When there is no equivalent, the default behavior is to add a comment in the source code indicating that the following expression/statement was not converted and requires manual correction. The VBUC converts library elements to their equivalent where possible. The converted code still requires that library via COM Interop, and the library is properly installed/registered in the current development machine.Įvery reference marked as not found by Visual Studio must be recreated manually by adding again the reference to the component. The screenshot below shows the Visual Studio Solution Explorer for a VB6 migrated application using MSWinsock library. NET projects are correct and exists in current machine. Make sure all references required by migrated. NET application (or Functional Equivalence application).

Getting green code compiling is the first stage to complete when trying to achieveĪ workable. Once the above list is checked, then, the Compilation, Visual Equivalence and Functional Equivalence phases should be executed. Any other component not included in the VBUC will be be used via COM Interop by the converted. Note: VBUC may convert some of the COM/OCX/ActiveX components used by the VB6 application to. Remember that any resource file (*.ini files, images, icons, custom string resource files) used by the VB6 application at runtime will be required by the. NET application must be installed/registered in the development machine (the machine where developers will stabilize the migrated application). NET application (code generated by the VBUC tool)Īny component used via COM Interop by the new.

This list details what you need to start the manual stabilization:

Manual changes may be needed to stabilize portions of the application that will require human intervention. Using automatic tools to convert code from a source language (VB6) to a modern language like ( VB.NET or C# ) is just the first step before getting a workable converted application. NET using the Visual Basic Upgrade Companion Tool.īefore reading this post, please read What not to do in a VBUC migration process article. This post offers a quick summary of steps to be executed to achieve a successful migration project from Visual Basic 6 to.

Vbuc visual basic