This section describes the types of steps gmStudio performs for you when it processes a migration project.

Default Processing

When you first create a Migration Project, gmStudio assigns it a full complement of automated preparation and translation steps. The set of steps depends on the external handling strategy.

Default Prototype Migration Steps

The default batch steps for a Prototype (aka. Stub) migration are as follows:

Apply Task Filter (select all migration tasks)
Set Build Order
Author Interface Descriptions
Author Resx Files
Run the translation with BuildFile="Local"
Deploy Translation
Build Translation

Default Interop Migration Steps

The steps for an Interop migration are as follows:

Apply Task Filter (select all migration tasks)
Set Build Order
Author Interface Descriptions
Author Interop Assemblies
Author Resx Files
Run Translation with BuildFile="Off"
Deploy Translation
Build Translation

Optimizing Batch Processing

The default processing for a new migration includes a number of steps that you will typically only have to run during the initial preparation phase of your migration work or when the source codebase changes in a significant way.

For example:

Apply Task Filter -- you should only select this when you want the subsequent batch steps to apply to all migration tasks in your project. This makes sense for the initial preparation, but once you start doing iterative translation tuning, you will typically focus you efforts on a select set of migration units. See the discussion of the Task Filter Form in the FAQ for more details.
Set Build Order -- you should only select this during initial preparation or when you want to recompute the order because the dependencies between migration units has changed.
Author Interface Descriptions -- you should only select this during initial preparation or when you want to update IDFs because external dependencies of your migration project have changed.
Author Interop Assemblies -- you should only select this during initial preparation or when you want to update interop assemblies because external dependencies of your migration project have changed. Note this is not needed for pure Prototype migrations.
Author Resx Files -- you should only select this during initial preparation or when the source code of your user interface files (forms, controls) have changed.

In summary, if your source codebase is stable and you have successfully completed the preparation work, then the set of processing steps you will typically run is:

Run Translation
Deploy Translation
Build Translation

To change batch processing steps:

Select [Tools/Batch Control] from the menu to display the Batch Control Form.
Check or Clear the check box for each step you want to turn on or off respectively.
Click Start to Save your preferences and run the batch process.

Your selections are saved to your migration project file.

Deploy = Replace

By default, the deployment step will replace files in the deploy folder. If you have made hand changes to the code in that folder and have not captured those changes in the tool configuration, they will be lost.

The rationale behind this is that the translation tuning process is iterative. We expect you to translate and retranslate your code each time improving the translation configuration to improve the quality of the generated codes. Your fixes should be implemented in your migration configuration so that they can be applied systematically and repeatedly in future iterations.

Browser not supported