The PPJ Framework is the collection of libraries that are needed by ported applications to support features that are not available, or are too different, in .NET.
Additionally, the PPJ Framework provides a very convenient layer in between the newly generated code and the .NET system. Thanks to this layer we can provide fixes for bugs that are present in .NET itself and we can debug applications putting breakpoints into key places in the core libraries.
The PPJ Framework is composed of several separate libraries (see tables below) compiled into .NET assemblies. Its architecture is very thin, most of the low level work is left to the .NET Framework and the PPJ Framework simply provides plumbing code, or adapts parameters and checks for errors.
PPJ Framework assemblies are organized into several namespaces. The table below lists the public namespaces that are imported by the Ice Porter conversion tool when generating the new .NET code.
There is no difference in the namespaces in the PPJ.Runtime (Desktop) and PPJ.Web (Wisej.NET) assemblies.
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.
Ported applications reference only the PPJ libraries that are actually needed. If your application doesn't use DDE functionality, you will not need to reference or deploy PPJ.Runtime.DDE.#.dll.
The PPJ Framework references some additional libraries:
- Wisej.Framework (Web)
- FlexGrid.NET (WinForms)
- Oracle ODP
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.