Notes on upgrading from Next Design V2.0 to V3.0

project file

PROJECT FILES CREATED WITH THE PREVIOUS VERSION WILL BE CONVERTED TO THE LATEST SCHEMA VERSION FILE FORMAT WHEN OPENED IN V3.0 AND CAN CONTINUE TO BE USED.

However, please note the following

Extensions

The extensions you are using are basically compatible and can be used without modification in most cases.

However, please check to see if your extensions are affected by the following two changes, and if so, please take action.

  1. Change in extension activation/deactivation timing
  2. SPECIFICATION CHANGES IN SOME APIS

Change extension activation/deactivation timing

Extensions are now activated/deactivated when project files are reloaded.

If the extension is an application lifecycle, it is not affected.

WHEN AN EXTENSION IS A PROJECT LIFECYCLE, THE EXTENSION WAS PREVIOUSLY ACTIVATED AND DEACTIVATED WHEN THE PROJECT FILE WAS OPENED AND CLOSED, BUT WHEN THE PROJECT FILE WAS RELOADED*, THE EXTENSION REMAINED ACTIVE. IN V3.0, HOWEVER, EXTENSIONS ARE NOW DEACTIVATED AND THEN REACTIVATED WHEN THE PROJECT FILE IS RELOADED, JUST AS THEY ARE WHEN THE PROJECT FILE IS CLOSED AND REOPENED.

Therefore, the process upon activation of the extension (Activatemethod) and processing upon deactivation (Deactivatemethod), please make sure that reactivating the extension after deactivating it does not affect its behavior.

(*) Example: When a project file is updated in conjunction with a configuration management system and reloading is executed according to the message that prompts reloading.

2. SOME API SPECIFICATION CHANGES

SOME APIS HAVE BEEN CHANGED. IF YOU DO NOT USE THESE APIS, NO ACTION IS REQUIRED. IF YOU ARE USING THE RELEVANT API AND ARE AFFECTED BY THE CHANGES, YOU WILL NEED TO CHANGE YOUR EXTENSION PROGRAM.

PLEASE REFER TO THE FOLLOWING MANUAL FOR THE CHANGED APIS AND THEIR CHANGES.

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

That is all.