| Using the Visual Basic Upgrade Wizard |
The most attractive method for converting a Visual Basic 6 project to .NET, though we do not recommend it, is to use the Visual Basic Upgrade Wizard. It can be used for standalone applications and partly for class library types of projects. Converting an existing Visual Basic 6 project will result in a new VB.NET project with new source code.
To convert an existing Visual Basic 6 project:
- In Visual Studio or Visual Basic 2008, open an existing Visual Basic 6 .vbp file. The Visual Basic Upgrade Wizard appears.
- Follow the instructions in the wizard.
The code that is generated will include many automatically-generated comments that indicate incompatibilities between Visual Basic 6 and VB.NET, similar to the following examples:
'UPGRADE_NOTE: Object v may not be destroyed until it is garbage collected.Click for more: 'ms-elp://MS.VSCC.v90/dv_commoner/local/redirect.htm?keyword="6E35BFF6-CD74-4B09-9689-3E1A43DF8969"'
'UPGRADE_WARNING: Couldn't resolve default property of object v()(). Click formore: 'ms-help://MS.VSCC.v90/dv_commoner/local/redirect.htm?keyword="6A50421D-15FE-4896-8A1B-2EC21E9037B2"'
'UPGRADE_WARNING: IsEmpty was upgraded to IsNothing and has a new behavior.Click for more: 'ms-elp://MS.VSCC.v90/dv_commoner/local/redirect.htm?keyword="9B7D5ADD-D8FE-4819-A36C-6DEDAF088CC7"'
'UPGRADE_WARNING: App property App.EXEName has a new behavior. Click for more: 'ms-help://MS.VSCC.v90/dv_commoner/local/redirect.htm?keyword="6BA9B8D2-2A32-4B6E-8D36-44949974A5B4"'
All of the incompatibilities must be resolved before the project can be run. But that should be done later. First, you must replace references to the Meridian Enterprise COM libraries. The conversion wizard will preserve the COM library references and create interop assemblies for them. You must remove each reference and replace it with the correct interop library provided with the BlueCielo .NET SDK. For example, in the project’s References page, remove references to Meridian Enterprise COM type components such as AM-Meridian EDM Server 5.0, InnoCielo EDM Client Components 1.0, and so on. After removing the references, add a reference to BlueCieloECM.InnoCielo.Meridian.dll.
Every Visual Basic .NET source code file that will operate on Meridian Enterprise objects should contain statements similar to the following examples depending on the objects that it will work with.
Imports BlueCieloECM.InnoCielo.Meridian.Client Imports BlueCieloECM.InnoCielo.Meridian.Server
Only after replacing references to the Meridian Enterprise COM libraries with references to the .NET interop assemblies are you ready to manually resolve the incompatibility comments in the converted files.
See Also