Import AVEVA apps and client controls

You can import AVEVA apps developed with Windows Presentation Foundation (WPF), or Winforms/.NET controls through the IDE. Once you import the app or control, you can configure its properties and deploy it in runtime.

An AVEVA App is collection of one or more controls primarily developed with Windows Presentation Foundation (WPF) for use in AVEVA OMI ViewApps. Other technologies such as Windows Forms (WinForms) and HTML5, can also be used. You can create your own AVEVA Apps, which can be imported via WPF interoperability. For more information about creating your own AVEVA Apps, see the AVEVA OMI SDK Help. The AVEVA OMI SDK is installed automatically when you install the IDE.

You can enhance a Galaxy's functionality by adding an embedded control from an AVEVA App to a pane in a layout for inclusion in a ViewApp.

A control developed with Winform or .NET can be imported in much the same way, and like an AVEVA app, you can configure the control within a layout for inclusion in a ViewApp.

Note: Libraries, Client Controls, and OMI Apps compiled with any version of .NET Core, including .NET 5, 6, 7, or 8) are not supported in System Platform. While the system may indicate a successful import, these components will not appear in the IDE or be usable in design time or at runtime.

Some .NET Standard libraries may work, but compatibility is not assured. For the best results, we recommend only using libraries compiled with .NET Framework 4.8.1.

In order to qualify for import as an AVEVA App, the App should contain at least one WPF FrameworkElement Class control (System.Windows.FrameworkElement).

AVEVA Apps should be organized in a single folder which can optionally include subfolders. These subfolders typically contain locale files.

To import an AVEVA App

1. Assemble the App, together with all required dependencies and related files, into a folder.

2. From the ribbon, select Galaxy, then Import.

3. Select Visualization, then OMI Apps.

4. Select the folder that contains the App to be imported.

   The contained App, along with all dependent files, including dependent files contained in subfolders, are imported when you select OK.

   If the App does not import successfully, see Troubleshoot AVEVA or WPF apps that fail to import.

After the import process completes successfully, a new object appears in the Visualization folder named DisplayModule_00n, where n is 1 or the next available integer. The new object can be renamed, deleted, or exported as an .aaPKG file for use in another Galaxy. See Export objects for additional information.