Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

Overview

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.

gmStudio Command Line Syntax

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 (gmstudio.cfg)

   /MIG = "migpath" sets path to a migration project file (.gmproj)
     
    or
   /MIG = a migration project specification string of the following form:

a string of one of more of the following semicolon delimited list of project creation parameters:

 

Parameter

Description

Status/Default

Name=name;

name is the name of new upgrade project

optional, default=NewUpgrade

Source=source;

source is the name of the folder containing the source codes

required

NetLang=lang;

lang is the target .NET language (csh|vbn)

optional, default=csh

SendTo=sendto;

sendto is the name of the folder to store the project workspace

required

SourceFilter=pattern;

pattern is *.vbp|*.asp|fully qualified path to a single file

optional=*.vbp

UseExtensions=yes|no;

'yes' indicates to use extension methods (aka. the lightweight object oriented coding style) and 'no' indicates to standard dialect

optional, default=yes

UseStubs=yes\no;

'yes' indicates to generate a stub framework for COM and 'no' indicates to use interop

optional, default=yes

VSVersion=VSnnnn;

VSnnnn is a VSversion name (e.g. VS2010, VS2010, VS2015)

optional, default=VS2013

OverWrite=yes|no;

'yes' means to replace a pre-existing gmProj silently and 'no' indicates to promot the user

optional, default="no"

 

/FILTER = "sourcelist" restricts processing to the source tasks listed.  Multiple tasks indicated using '+'.  Wildcard using '*'.

/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,
      Author Resx Files,
      Generate Visual Studio Solution,
      Update Project Metalang File 

 /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,
       Run Functional Test 
 /REPORTS = "report_list" specifies a comma-delimited list of reports (See Reports Article for more information)
      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

    • RunGmStudio.cmd: allows running gmStudio for a specific project from the command line 

  • No labels