Issues with Dialog System Support
- It is not possible to edit screensets in
Enterprise Developer. To make changes to a screenset, you use the Dialog System painter which is installed with
Enterprise Developer.
- Several Dialog System extensions are not supported, such as DSGRAPH, DSDDE, DSPLAYER and DSONLINE.
- 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
Migrating a Dialog System Application to
Enterprise Developer in
Related Information at the end of this topic.
- 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.
- Applying the Windows visual styles to existing Dialog System applications might result in changing the size and positioning of controls and in UI inconsistency of your applications between different versions of Windows. For more information about some of the UI inconsistences that can occur, see ....
