Page tree

Versions Compared

Key

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

...

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 or html. These reports are written to files with a .txt or .htm extension respectively.

Most reports are written to the report folder in your migration workspace.  When the report file is ready, gmStudio will open the file with the associated application.

The gmStudio report titles and output file names are listed below ([MigName] is the Migration Project Name):

TitleOutput File
Code Scan Reports 
Source Structure[MigName]-SrcStruct.tab
Source References[MigName]-SrcRef.tab
Source Members[MigName]-SrcMember.tab
Source GUI Scan[MigName]-SrcGUI.tab
Source Code Scan[MigName]-SrcScan.tab
Iceberg[MigName]-Iceberg.tab
Project Reports 
Project Summary[MigName]-MigStat.txt
Metrics Summary[MigName]-Metrics.htm
Migration Set[MigName]-MigSet.tab
Code Bundles[MigName]-Bundle.tab
.NET Build Logs[MigName]-BldLog.tab
Translation Logs[MigName]-TranLog.tab
All Logs[MigName]-AllLog.txt
Interface File Headers[MigName]-LibHeaders.tab
Interface File ProgIds[MigName]-LibProgIds.tab
Semantic Model Reports 
Semantic References[MigName]-AnaRef.tab
Semantic Definitions[MigName]-AnaDef.tab
Semantic Symbols[MigName]-AnaSym.tab
Semantic Audit[MigName]-Audit.txt
Utility Reports 
Migration Project ListgmProjects.tab
Multi-Unit Scripttran.[MigName]_MultiJob.xml
Target Code Scan[MigName]-BndScan.tab
Target Code Chanfges[MigName]-BndChanges.txt
Generate Visual Studio Solutiondeploy\[MigName].sln
Generate Project Signature File[MigName]-ProjectSignature.txt

 

Running Reports

There are three ways to run gmStudio reports:

...