If you license allows it, gmStudio can be operated in a batch mode. You will typically do this using the sample batch files distributed with gmStudio. This section describes the gmStudio command line.
The form of the gmStudio command line is as shown below:
gmStudio /AUTOBATCH = ["YES"|"NO"] /CFG = "cfgpath" /MIG = "migpath" /TOOLS = "tool_list" /TASKS = "task_list" /REPORTS = "report_list" where: /AUTOBATCH = "YES|NO" If AutoBatch=YES then the command list specified in the migration project file (.gmproj) will be performed. Otherwise, the set of task/tools specified on the command line will be performed. /CFG = "cfgpath" sets the path to an application config file /MIG = "migpath" sets path to a migration project file /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.
For examples of using gmStudio as a console application command line, see the sample scripts in the [INSTALLDIR]\batch folder: