Changes in Next Design V2.0 Service Update 1
Changes to extension functions
Embedding libraries that contain WPF user controls
Libraries that cause problems when loaded in different areas for each extension, such as libraries that contain WPF user controls, can be loaded into the same area as the main Next Design and shared.
For details, see the following page.
Changes to behavior when an exception occurs in an extension command
The behavior when an exception occurs while executing an extension command has been changed as follows.
- If an exception occurs during command execution, the Post-Command Execution Event will not be notified.
Changes for each API
This section lists the API changes in Next Design V2.0 Service Update 1. For details on each API, see API Specifications.
Changed API
Lists the APIs changed in Next Design V2.0 Service Update 1.
For details on how to migrate to the new API, see the notes for the API in the API specifications.
NextDesign.Core
|API|Changes|
|:--|:--|
|IProject.ImportProfile method|Changed to stop importing a profile if a field with a different name than the profile to be imported is found|
NextDesign.Desktop
|API|Changes|
|:--|:--|
|IApplication.ExecuteCommand method|Changed to notify the caller of an exception if an exception occurs during command execution|
APIs to be consolidated
Lists APIs to be consolidated in the next update.
NextDesign.Desktop
- IApplication.CreateSearch method
- ICommonUI.MessageBox method
- IContext.Application property
- IEditorPage.ActiveInfoWindow property
- IEditorPage.CurrentOutputCategory property
- IEditorPage.CurrentInfoView property
- IWorkspace.CreateSearch method
- APIs scheduled for consolidation can still be used in V2.0, but a warning message will be displayed if you build them as DLL-type extensions.