...
- Select [Run Translation] from the task context menu.
- Select [Snapshot a Baseline] from the task context menu Choosing [Snapshot a Baseline] makes a copy of the last translation bundle file and stores it for safe keeping in the [workspace]\log\sav folder.
- Alter the migration inputs (e.g., translation script, refactor libraries)
- Select [Run Translation] from the task context menu
- Click the [Compare] button on the Toolbar to see the effects of the changes.
- Repeat the process to incrementally and iteratively refine the configuration to produce better .NET codes.
| Info | ||
|---|---|---|
| ||
The Snapshot process copies the latest actual translation script, translation log, code bundle, and generated IDF if applicable, from the working directory (workspace\log) to the snapshot folder (workspace\log\sav). |
Comparing Two Migration Tasks
...
- Add two migration tasks to your migration project that both reference the same source code but have different translation scripts and different TaskTag values. Note that the TaskTag value will be included in the names of all output files and folders produced for the migration task.
- Select both tasks and select [Run Translation] from the task context menu
- Select both tasks and click the [Compare] button on the Toolbar to compare the two translations.
- Repeat the process to incrementally and iteratively refine the configuration to produce better .NET codes.
Comparing Snapshots in Batch
If you are doing translation tuning on a large codebase with many VBPs or ASP pages, a question that will come up again and again is "what was the impact of my last configuration change?" In order to answer this question efficiently, gmStudio provides an operation that reports which code bundles have changed. This operations can be invoked in several ways:
- Select migration tasks and click \[Compare Snapshot] on the task context menu. This operation will set the LastMsg field to the summarized results of the comparison.
- Select \[Reports|Utilities|Target Code Changes] from the main menu.
| Info | ||
|---|---|---|
| ||
By default, the batch comparison process is done by running windows file comparison utility (fc.exe ) on each task then analyzing and recording the result. |
Compare Snapshot Folder
The batch comparison process only reports differences in the code bundle file. The snapshot comparison process compares composite snapshot files which, by default, include the actual translation script, the translation log, the bundle, and the associated IDF if applicable. Sometimes you want to inspect changes in these snapshot files independently. This can be done by clicking \[Tools|Compare Snapshot Folder]. This operation will open the file comparision tool in folder comparison mode with the snapshot folder on the left and the working directory on the right. This technique allows you to produce a detailed report of all changes using your preferred file comparison tool.
Comparing Tool-generated and Hand-fixed Code
You will typically research translation refinement ideas by fixing and refactoring codes in a .NET IDE. After you make and verify a few changes in the IDE, you can compare the hand-fixed code to the code that was generated automatically and then incorporate the refinements into the translation configuration.
...
- Select [Run Translation] from the task context menu.
- Select [Deploy Translation] from the task context menu
- Click the [New IDE] button on the Toolbar to open the .NET code in the .NET IDE.
- Modify the .NET code as desired and save the files
- Select [Rebundle Translation] from the task context menu. This will produce a "new" bundle file and compare it to the last one generated by the tool.
- Incorporate the changes into the migration process by modifying the Translation Script (e.g. Target Edits) and RefactorLibraries as needed.
- Repeat the process to incrementally and iteratively refine the configuration to produce better .NET codes.
Comparing Snapshots in batch – TODO
...