...
If your license allows it, gmStudio can be operated in a batch mode. You will typically do this using the sample batch files we provide. This section describes the gmStudio command line.
| Table of Contents | ||
|---|---|---|
|
gmStudio Command Line Syntax
...
/TOOLS = "tool_list" specifies a comma delimited list of the following tools (iterate over all migration units for each tool)
Apply Task Filter, Author Interop Assemblies, Author Interface Descriptions, Set Build Order, Create Buildset, Author Resx Files,
/TASKS = "task_list" specifies a comma-delimited list of the following tasks (iterate over list of all tasks for each migration unit)
Validate Source,
Build VB6,
Snapshot a Baseline,
Reset Task Status,
Run Translation,
Deploy Translation,
Build Translation
/REPORTS = "report_list" specifies a comma-delimited list of reports Source Structure,
Source References,
Source Members,
Source GUI Scan,
Source Code Scan,
Iceberg,
Project Summary,
Metrics Summary,
Migration Set,
Interface File Headers,
Interface File ProgIds,
Code Bundles,
.NET Build Logs,
Translation Logs,
All Logs,
Semantic References,
Semantic Definitions,
Semantic Symbols,
Semantic Audit,
Migration Project List,
Target Code Scan,
Note that tools are processed before tasks.
Sample Command Scripts
For examples of using gmStudio as a console application, contact Great Migrations.
- runall.cmd: is a driver script that initialized the environment then calls run1set.cmd for a collection of migration projects.
- run1set.cmd: specifies the tasks, tools, and reports to perform for each migration project.
- gather_reports.cmd: is used to consolidate reports from multiple project workspaces. It assumes all of the workspaces are under a common root folder.
...
- RunGmStudio.cmd: allows running gmStudio for a specific project from the command line