Notes on Updating from Next Design V4.0 to V5.0

---

Table of Contents

• Update Method
• Project files
  • Migration from DB Format (iproj)
  • File Compatibility
• HTML Document Generation
• Extended Contents
• Extensions
  • V5.0 Support
  • IF YOU ARE USING AN API THAT CHANGES BEHAVIOR
  • If you are using the ExtensionPoints library
  • When referring to the library bundled with Next Design itself

Update Method

In V5.0, the application framework is updated to .NET 10. Due to this change, updating to V5.0 requires using the installer, and automatic updates from the menu are not available. Please use the installer to perform the update.

Starting with V5.0, the 32-bit version is discontinued and consolidated into the 64-bit version. Customers currently using the 32-bit version should uninstall it before performing a fresh installation of the 64-bit version. If you install the 64-bit version without uninstalling the 32-bit version, the installation destination folder will remain as the 32-bit version.

Project files

Migration from DB Format (iproj)

V5.0 discontinues support for the DB format (.iproj) and exclusively supports the JSON format (.nproj). Consequently, customers currently using the DB format must migrate their project files before applying the version upgrade in order to continue using them in V5.0.

Please refer to the following page and perform the migration from the DB format to the JSON format.

End of Support for DB Format (*.iproj) and Migration Procedure

File Compatibility

Opening a project file in JSON format created in an older version with V5.0 will automatically convert it to the latest schema version file format for continued use.

However, please note the following point:
While a V5.0 project file can be opened in V4.0, saving and overwriting it in V4.0 will result in the loss of data for property names added in V5.0.

HTML Document Generation

In V5.0, when generating HTML documents, the file names output within the pages folder are changed from {Model Name}.html to {Model ID}.html.

If the generated HTML files rely on user-defined processing or links tied to specific file names, please review the contents and update them as necessary.

Extended Contents

Extended content will also be updated in conjunction with the Next Design core update. Please update your pre-installed packages.

Please note the following points for this update.

• NDGit
  • Older versions of NDGit will not function correctly in Next Design V5.0.
    Be sure to update NDGit before opening any projects integrated with Git.
• MarkdownEditor
  • In Next Design V5.0, the MarkdownEditor from previous versions does not work properly.
    MarkdownEditor を使用しているプロジェクトを開く前に、必ず MarkdownEditor をアップデートしてください。
• ScriptEditor Extension Edition
  • In Next Design V5.0, functionality equivalent to the extension version of ScriptEditor is integrated as a standard feature.
    The extension version of ScriptEditor is no longer required, so please uninstall it if it is already installed.

Extensions

V5.0 Support

Next Design APIs are compatible between V4.0 and V5.0, with consideration given to compatibility for both .NET 8 and .NET 10, meaning that developed extensions will generally work as they are.
However, if you continue to use certain extensions in V5.0 under specific conditions, please verify their contents and take action as needed.

• IF YOU ARE USING AN API THAT CHANGES BEHAVIOR
• If you are using the ExtensionPoints library
• When referring to the library bundled with Next Design itself

To use APIs added in V5.0 and later, a development environment supporting .NET 10 is required. Visual Studio 2022 does not officially support .NET 10. Official support requires Visual Studio 2026 or later.

Please note that you can still develop extensions that work in V5.0 by continuing to use Visual Studio 2022 for V4.0-compatible extensions (.NET 8). In that case, you will not be able to use APIs added in V5.0 and later.

IF YOU ARE USING AN API THAT CHANGES BEHAVIOR

Due to the end of support for the DB format (.iproj), file formats that can be specified via the API are restricted. The affected APIs are listed below. If you are using these, please verify whether they affect the operation of your extensions and revise your processing as necessary.

• IWorkspace.OpenProject Method
• IWorkspace.SaveProjectAs method
• IProjectUnitManager.ExportModelUnit method
• IProjectUnitManager.ImportModelUnits method
• IProjectUnitManager.AddExternalUnits method
• IProductLineModel.ExportAppliedProject method

If you are using the ExtensionPoints library

If your extension development project uses the ExtensionPoints library, please update it to the V5.0-compatible version as follows.

Target Package	V5.0 Compatible Version
NextDesign.Desktop.ExtensionPoints	1.2.3.xxxxx (Tentative Release)

When referring to the library bundled with Next Design itself

If your extension development project does not reference any libraries bundled with Next Design other than the ExtensionPoints development package (*1), the following confirmation is not required.

If you are developing an advanced extension and referencing the same libraries bundled with Next Design in addition to the extension development package, the version of the library referenced at runtime may change due to version upgrades of the bundled libraries.

Please refer to the following manual to verify that your extensions operate correctly.

• Extension Development Manual > Reference > Extension Loading Mechanism > Notes on Extension Development and Maintenance

(*1) Extension development packages: NextDesign.Core, NextDesign.Desktop, NextDesign.Desktop.ExtensionPoints

(*2) For details on the libraries included with Next Design V5.0, please contact us via the "Technical Support" page.

That is all.