- INDEX VB TO NET
- VBUC QUICK START
- VBUC COMMAND LINE INTERFACE
6. Visual Basic Upgrade Companion - Command Line Interface
To create an upgrade solution and perform the upgrade process:
VBUM <sourcePath> <solutionName(without extension)> [options*]
To upgrade an existing solution file:
VBUM [options*]
Options detail:
Option | Description |
/? |
Show the usage of the VBUM |
/license |
Display the license information |
/out <outputPath> |
Specify the output directory (Default: <sourcePath>\UpgradeOutput) |
/target {vb|cs} |
Specify the target language (Default: vb) |
/upgradeoption <file> |
Upgrade Option file to use [Standard | MoreDotNet | MoreInterop] |
/vsversion <version> |
Choose Visual Studio Version for output.(2005-2008-2010) |
/folder <folder> |
Choose to preprocess/upgrade only one subfolder (it has to be relative to the solution source path) |
/includeNeeded |
Include all needed * projects in the preprocess phase |
/ignoreWarnings |
Don’t update warnings when loading a solution |
/phase <phaseId> |
Execute only the indicated phase (Default: Preprocess and upgrade) |
<phaseId> values:
|
|
Typing options (only one option can be used): |
|
/typer |
Use full typing for object and variant members |
/noTyper |
Don’t use typing for object and variant members |
/localTyper |
Use local typing for object and variant members |
* The needed projects are those that reference or are referenced by one of the projects included in the upgrade. If the needed project is not in the upgrade solution, it will not be included. |
Examples:
- Upgrade all the VB6 projects that are contained in
“C:\Source Code\” vbum “C:\Source Code\” MySolutionFilename /out ./OutputPath /target cs
- Perform upgrade on all the projects specified in an upgrade solution file.
vbum SolutionFilename.VBCSln
See also:
5. Start the Automated Upgrade6. Visual Basic Upgrade Companion - Command Line Interface
7. Shortcuts
Visual Basic Upgrade Companion Quick Start