This section describes the types of steps gmStudio performs for you when it processes a migration project.
| Table of Contents |
|---|
...
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 migration Prototype (aka. Stub) migration are as follows:
- Apply Task Filter (select all migration tasks)
- Set Build Order
- Author Interface Descriptions
- Author Resx Files
Create - BuildSet. The "Create BuildSet" step includes the following sub-steps:
- a) Run Translation and aggregate list of external dependencies,
- b) Deploy .NET project(s) for each migration unit,
- c) Generate/Deploy/Build External prototype assemblies, and
- d) Build .NET migration unit project(s)
- 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.
...
- 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.
Create BuildSet -- you should only select this during initial preparation or when you want to update prototype assemblies because external dependencies of your migration project have changed. Note that you may eventually implement your prototype assemblies by hand.
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:
...