Classes

Functional Classes

Functional Classes from the original OpenText Team Developer application are all ported to public classes. The files are located either in the main application's directory or in the \Classes subdirectory, depending on the options set in Ice Porter.

The structure of the generated classes is simple and reflects the original structure. The description of the class is ported to the <summary> comments for the class. Variables and functions are grouped together and enclosed in regions.

If the class had a ObjectDestructor() method, the code is ported into a destructor in .NET. However, destructors in .NET are not called in a predictable manner because of the garbage collector. This difference in behavior may cause problems in the ported application and needs to be addressed by a developer.

The base class for Functional Classes is PPJ.Runtime.SalFunctionalClass.

Visual Classes

Visual classes are all ported to public classes derived from the corresponding control class in the PPJ Framework. The files are located either in the main application's directory or in the \Controls subdirectory, depending on the options set in Ice Porter.

The structure of visual classes is compatible with the Visual Studio Designer guidelines. All the visual properties are generated in the InitializeComponent() method. A call to InitializeComponent() is placed in the constructor. For .NET 2.0 and if the appropriate option in Ice Porter has been set, the designer's code is generated into a separate file called <class name>.Designer.cs.

Not all visual classes can be designed, however. Visual Studio can design only container classes, unlike SQLWindows/Team Developer that can design also single control classes. Nevertheless, Ice Porter generates designer-compatible code also for single control classes.