Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

gmStudio Reporting Overview

gmStudio can produce a variety of useful reports to help you plan, execute, and measure the progress of your migration effort. There are four classes of reports:

  • Code Scan Reports 
  • Project Information Reports  
  • Semantic Model Reports  
  • Utility Reports

The gmStudio report titles and output file names are listed below:

TitleOutput File
Code Scan Reports 
Source Structure[MigName]
Source References[MigName]
Source Members[MigName]
Source GUI Scan[MigName]
Source Code Scan[MigName]
Project Reports 
Project Summary[MigName]-MigStat.txt
Metrics Summary[MigName]-Metrics.htm
Migration Set[MigName]
Code Bundles[MigName]
.NET Build Logs[MigName]
Translation Logs[MigName]
All Logs[MigName]-AllLog.txt
Interface File Headers[MigName]
Interface File ProgIds[MigName]
Semantic Model Reports 
Semantic References[MigName]
Semantic Definitions[MigName]
Semantic Symbols[MigName]
Semantic Audit[MigName]-Audit.txt
Utility Reports 
Migration Project
Multi-Unit Scripttran.[MigName]_MultiJob.xml
Target Code Scan[MigName]
Target Code Chanfges[MigName]-BndChanges.txt


Most reports are driven off selected tasks in the Migration Project. You indicate which migration tasks to include in a report by selecting them in the migration panel.

Most reports are authored as tab-delimited text files with the first record containing the column names of the report. These reports are written to files with a .tab extension. A handful of reports aggregate various log files and other data as free-form text files. These reports are written to files with a .txt extension.

Most reports are written to the report folder in your migration workspace. 

Running Reports

There are three ways to run gmStudio reports:

  1. To run a single report for a set of one of more migration tasks, highlight the desired tasks in the migration panel then select the desired report from the [Reports] menu. The report will only include data for the highlighted migration tasks. The resulting report will be displayed in the associated application (e.g., excel for .tab files, or a text editor for .txt files).
  2. To run a set of reports in batch, use the Reports Panel. This Panel allows you to perform a variety of reporting-related operations such as selecting a set of reports and running them in batch or viewing all the report files in the report folder. Click the [Reports] tab on the task details panel at the bottom of the main form.
  3. To run a set of reports from one or more migration projects in batch use the command line scripts supplied with the gmStudio Samples. See [INSTALLDIR]\samples\batch\run1set.cmd for details.

.NET Assessment Tools

Once you have your code into .NET, Visual Studio offers several useful reports. See Code Analysis and Code Metrics in the Visual Studio documentation.

titleAutomated .NET Code Review

Note that the Build Log report will tabulate code analysis results if they are in the MSBuild log. This can be a convenient way to run an automated code review of your new .NET codebase. See MSDN for additional details on using MSBuild for code reviews.