Troubleshoot AVEVA or WPF apps that fail to import

There are two major factors that may stop an AVEVA or WPF app from successfully importing.

Expose controls and properties: Make sure that you have included an AppManifest.xml file with the app, and that all controls and properties that are needed in your app are explicitly exposed in it. For additional information about the AppManifest.xml file, see AVEVA app development guidelines and the AVEVA OMI SDK Online Help.

Block business logic from executing during design time: If you have business logic executing in the control constructor, or in static properties or static constructors, the import operation will not be successful. The control constructor is invoked when the control is instantiated. Therefore, do not include business logic within the control or static constructors, or in static properties.

• If you cannot remove business logic from a control or static constructor, or a static property, make sure the property is not invoked or that the property does not execute while in design mode.

• To block execution of logic within a constructor while in design time, add the following line to the constructor:

  !DesignerProperties.GetsInDesignMode