Click or drag to resize
PPJ Assemblies
Namespaces

PPJ Framework assemblies are organized into several namespaces. Table 2 below lists the public namespaces that are imported by Ice Porter when generating .NET code.

Namespace

Functional areas grouped by the namespace

PPJ.Runtime

All core data types and functionality, SAL functions, system constants.

PPJ.Runtime.Com

COM server and client support, COM classes (Variant, SafeArray, etc.).

PPJ.Runtime.Sql

SQL support, SQL Types and functions, binding, error management.

PPJ.Runtime.Reports

Implementation of reporting functionality based on CR.NET.

PPJ.Runtime.Reports.??

Implementation of reporting functionality using alternative reporting engines (LL, RS, ST).

PPJ.Runtime.Windows

All visual classes, messaging system, and visual implementation.

PPJ.Runtime.Windows.QO

Supported QuickObjects.

PPJ.Runtime.DDE

SalDDE functions and DDE implementation.

PPJ.Runtime.Vis

Visual Toolchest functions and classes.

PPJ.Runtime.XSal

XSal2 functions and classes.

Deployment

The deployment of the PPJ Framework is very easy. You can simply copy the assemblies to the same directory (or the working directory) of the application or anywhere in the PATH. In alternative you can register the assemblies with the GAC using GACUTIL.EXE. We also provide MSI installers that you can use as part of your deployment procedure.

References

The PPJ Framework references 3 additional libraries: FlexGrid.NET, Oracle ODP, and SharpZipLib. However, because of the .NET architecture, the referenced libraries are needed only if they are actually used by the application. If your application doesn't use the Oracle driver to connect to Oracle (or if it doesn't use Oracle at all) you don't need to reference the Oracle ODP assembly. Similarly, if your ported application doesn't use XSalZip functions you don't need the SharpZipLib library.

Additional ADO.NET libraries maybe needed depending on the configuration of sql.config for accessing databases using ADO.NET drivers.