Dialog System information and restrictions

The Compatibility AddPack for Enterprise Developer includes the Dialog System run-time components, Dialog System painter and a subset of the development components. This includes:

• Dialog System run-time system and run-time components.
• Panels V2.
• Dialog System painter.
• GUI class library and OLE class library. These libraries are needed if you migrate an existing Dialog System application that was extended using those libraries.

  Projects for building the GUI and OLE class libraries from source are also supplied. Additionally, a project file for the Base class library was added in Enterprise Developer 2.0.

• Visual Studio plug-in to associate screensets in Visual Studio with Dialog System. Double-clicking a screenset in Solution Explorer in Enterprise Developer starts the Dialog System painter.
• Sample applications demonstrating a range of modernization techniques.
• Supporting documentation in this Help explaining the significant elements of the sample code.

Prerequisites and Requirements

The Compatibility AddPack for Enterprise Developer requires the following software:

• Enterprise Developer for Visual Studio 2015. This provides full support for developing and running applications.

  Since the AddPack contains the Dialog System run-time components, you can run Dialog System applications (not develop them) if you have Enterprise Server installed.

• If you have an older version of this AddPack installed on the same machine, it must be uninstalled before you start the installation.

Restrictions and Limitations

The following restrictions apply to the Dialog System Runtime in the Compatibility AddPack for Enterprise Developer:

• Dialog System painter does not work with the Eclipse-based product.
• Several Dialog System extensions are not supported, such as DSGRAPH, DSDDE, DSPLAYER and DSONLINE.
• Screenset script animation is not supported.
• To make changes to a screenset, you use the Dialog System painter.
• Only x86 projects are supported, because there is no 64-bit support for Dialog System.
• Unlike in Net Express, debuggable versions of the class libraries are not installed automatically (and there is no debugger switch to enable use of the debug versions as there is in Net Express). Instead, you need to build the libraries yourself. See Debuggable OO Class Libraries in the topic Migrating a Dialog System Application to Enterprise Developer.
• The Dialog System painter generated incomplete code for ActiveX controls if the controls contained internal objects. No code was generated for finalizing these objects which can cause the application to crash upon exit. To ensure the application exits cleanly you need to add some code to finalize these objects as part of the finalization of the ActiveX control itself. Specifically, any objects created by invoking the ActiveX control’s domain object through the “GetDomainObject” method must be finalized prior to exiting the application.