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:
The gmStudio report titles and output file names are listed below:
Title | Output 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 List | gmProjects.tab |
Multi-Unit Script | tran.[MigName]_MultiJob.xml |
Target Code Scan | [MigName]-BndScan.tab |
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.
There are three ways to run gmStudio reports:
Once you have your code into .NET, Visual Studio offers several useful reports. See Code Analysis and Code Metrics in the Visual Studio documentation.
Tip | ||
---|---|---|
| ||
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. |