Ported Application

Ice Porter generates a complete Visual Studio project that can be opened right after the conversion process. The new project is fundamentally different from the original OpenText Team Developer application and it's important to understand the structure and organization of the new .NET project to be able to find things quickly.

The biggest difference is that each single class or form template is in a separate file, while in the original application a SAL file may contain several classes and other objects. Also SAL has a number of items that do not belong to any class and are considered to be global, while in .NET (just like Java) everything must be in a class. Therefore Ice Porter also generates some "global" classes that contain the static members that have been ported from the original application global items.

The Visual Studio designer relies on resolvable types, resources, and design-time code. Inherited forms commonly require their base assemblies to be built first. A designer failure is not proof that the whole application must run successfully: inspect the reported missing assembly, constructor failure, or unsupported designer feature.

Start with Project Structure, then review Global Items, Forms, and Issues & Workarounds. Keep the conversion log with the generated baseline so each manual correction can be traced to its source.

For a web migration, review session state and integrations separately from the language translation. A file or database connection opened by server code belongs to the server environment, not the browser machine.