Notes on upgrading from Next Design V1.1 to V2.0

install

• NET Core, please uninstall the previous version of Next Design V2.0 before installing Next Design V2.0. NET Core, please uninstall the previous version and re-install Next Design V2.0.

project file

• PROJECT FILES CREATED WITH V1.1 WILL BE CONVERTED TO THE LATEST DATA FORMAT WHEN THE FILE IS OPENED AND CAN CONTINUE TO BE USED.

• NOTE, HOWEVER, THAT IF YOU OVERWRITE THE FILE WITH V2.0, YOU WILL NOT BE ABLE TO OPEN THE FILE WITH THE PREVIOUS VERSION.

• In addition to the Xaml format of V1.1, V2.0 supports HTML format for rich text type fields. Rich text data created with V1.1 can be used as is in Xaml format, but when editing rich text data with V2.0, the edited parts will be converted to HTML format and saved.
  If you are using an API that manipulates rich text data with an extension, you need to be careful about this behavior. If you are not using the relevant extensions, there is no effect.

• Sample Project: The BasicSamples package has been updated. Please uninstall the old BasicSamples package and reinstall one of the following packages

  • BasicSamples.Professional (Package for Professional Edition)
  • BasicSamples.Enterprise (package for Enterprise Edition)

  For more information, please click here.

Extensions

IF YOU WISH TO CONTINUE TO USE V1.1 EXTENSIONS WITH V2.0, PLEASE TAKE THE FOLLOWING ACTIONS

1. Porting extensions to .NET Core
2. SUPPORT FOR API SPECIFICATION CHANGES

EVEN FOR SCRIPT-BASED EXTENSIONS, "2. SUPPORT FOR API SPECIFICATION CHANGES" IS NECESSARY TO SUPPORT THE ABOVE, SO PLEASE TAKE THE NECESSARY ACTIONS.

1. porting extensions to .NET Core

• With the change in the platform of Next Design itself from .NET Framework to .NET Core, extensions must also be ported to .NET Core. Please refer to the following manual for details.

  EXTENSION DEVELOPMENT MANUAL > MIGRATION GUIDE > MIGRATION OF EXTENSIONS FROM V1.1 TO V2.0

• There are also changes to the way extensions are built and the file structure in which they are distributed. Please refer to the following manual for details

  EXTENSION DEVELOPMENT MANUAL > MIGRATION GUIDE > MIGRATING EXTENSIONS FROM V1.1 TO V2.0 > BUILDING AND DISTRIBUTING V2 EXTENSIONS

2. SUPPORT FOR API SPECIFICATION CHANGES

• SOME APIS HAVE BEEN CHANGED OR REMOVED. IF YOU ARE USING THESE APIS, YOU WILL NEED TO CHANGE YOUR PROGRAM. IF YOU DO NOT USE THE RELEVANT API, NO ACTION IS REQUIRED.

• PLEASE REFER TO THE FOLLOWING MANUAL FOR A LIST OF APIS THAT HAVE BEEN CHANGED OR DELETED.

  Extension Development Manual > Changes by Version > Changes in Next Design V2.0 > Changes by API

That is all.

Revision History

• 2022/1/20
  • A note on handling rich text data has been added to the Project File section.
  • BasicSamples package updates have been added to the project file section.