This page introduces gmStudio reporting features.
In addition to a number of batch reporting features, gmStudio has a powerful search-based reporting feature that allows. See the Search Panel
Most reports written as tab-delimited files with a .tab extension. When a report file is generated from the Reports menu, gmStudio attempts to display it by launching the application associated with .tab files. Typically the associated application is Microsoft Office Excel.
Sample report data in an Excel Pivot Table
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:
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. 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:
|Code Scan Reports|
|Source GUI Scan||[MigName]-SrcGUI.tab|
|Source Code Scan||[MigName]-SrcScan.tab|
|.NET Build Logs||[MigName]-BldLog.tab|
|Interface File Headers||[MigName]-LibHeaders.tab|
|Interface File ProgIds||[MigName]-LibProgIds.tab|
|Semantic Model Reports|
|Migration Project List||gmProjects.tab|
|Target Code Scan||[MigName]-BndScan.tab|
|Target Code Chanfges||[MigName]-BndChanges.txt|
There are three ways to run gmStudio reports: