The following are general considerations to the migration of customisations to AVEVA E3D 3.1.
AVEVA E3D and AVEVA PDMS and Hull & Outfitting rely on the use of environment variables for various aspects of configuration. AVEVA E3D has a different set of Environment Variables to PDMS. Most notably for PML developers, PMLLIB is unchanged but PDMSUI has been replaced by PMLUI. There is a compatibility mode so most applications will work using PDMS environment variable names.
Where AVEVA PDMS and Hull & Outfitting environment variables are used in PML code, these should be changed to the equivalent AVEVA E3D environment variable name.
The following table shows equivalent AVEVA PDMS / Hull & Outfitting and AVEVA E3D environment variables.
|PDMS Environment Variable
|AVEVA E3D™ Environment Variable
It is recommended that PMLLIB and PMLUI paths are used to add customised PML functions to AVEVA E3D. This is the same approach as used in AVEVA PDMS and Hull & Outfitting with PMLLIB and PDMSUI paths. A variable (CAF_UIC_PATH) is used in AVEVA E3D to specify where the system will find customised User Interface Configuration files.
At AVEVA E3D 3.1 support has been added for an environment variable that is read and transformed in the customization.xml files.
The name of many of the AVEVA assemblies (DLLs) differ at AVEVA E3D. In most cases the word CORE has been used to replace the former PDMS notation, for example the assembly Aveva.Pdms.Database has been renamed to Aveva.Core.Database.
This change is to align naming with the core codebase that AVEVA E3D 3.1 utilises. Core functionality and supporting code has now been separated to support a number of AVEVA products.
As a consequence, customised C# Visual Studio projects will need to be refactored for the new references.
The USING & NAMESPACE commands used in PML and associated with C# controls will also need to be updated (such as the PMLFILEBROWSER, NETGRIDCONTROL, etc.).