The Porting Process
Phase 3. Translation
Enter Ice Porter™ - the translation engine that makes it possible for an organisation to port to .NET without ditching its original investments.
This screenshot illustrates Ice Porter in action. The outcome from the previous phase is used to configure the project space in Ice Porter.
Each SAL intermediate file corresponds to one .NET project in Visual Studio. Each project must compile without errors. Starting from the bottom-up, all the projects are ported and compiled. Ice Porter takes care of incrementally removing all the SAL code that has already been ported in shared modules. The result is a set of Visual Studio projects with virtually no duplicated code, clear and fully qualified references among the modules, and a new clean and well organized project tree. All the projects can be loaded at once in a single Visual Studio solution and further code reorganization can be accomplished by simply dragging & dropping classes from one project to another. Dataline’s engineers ensure that the code generated by Ice Porter is fully compilable and runnable, and that every problem issue is isolated and tagged for further processing.
The outcome of this phase is a complete Visual Studio .NET solution that completely compiles. This is the input to the next phase, which is about smoothing things out.
