Important Notes When Updating from Next Design V4.0 to V5.0

Table of Contents

How to Update

In Version 5.0, the application framework will be updated to .NET 10. As a result, you must use the installer to update to Version 5.0; automatic updates via the menu are not available. Please use the installer to update.

Starting with Version 5.0, the 32-bit version will be discontinued, and we will transition exclusively to the 64-bit version. If you are currently using the 32-bit version, please uninstall it before installing the 64-bit version. If you install the 64-bit version without first uninstalling the 32-bit version, the installation folder will remain set to the 32-bit version.

project file

Migration from the DB format (iproj)

In Version 5.0, support for the DB format (.iproj) will be discontinued, and only the JSON format (.nproj) will be supported. Consequently, customers currently using the DB format must migrate their project files before upgrading to Version 5.0 in order to continue using the software.

Please refer to the next page and proceed with the migration from the DB format to the JSON format.

DB format (*.iproj) support termination and migration procedure

File compatibility

When you open a JSON project file created in an earlier version in V5.0, it will be converted to the file format based on the latest schema version, allowing you to continue using it.

However, please note the following:
Although you can open V5.0 project files in V4.0, saving them in V4.0 will result in the loss of data associated with attribute names added in V5.0.

HTML Document Generation

In V5.0, when generating HTML documents, the filenames output to the `pages` folder will change from `{Model Name}.html` to `{Model ID}.html`.

If the generated files contain any user-specific processing or links that rely on the filename, please review the contents and make any necessary adjustments.

Extended Contents

Extended content will be updated along with the update of Next Design itself. Please update your installed packages.

Please note the following regarding this update.

Extensions

Compatible with V5.0

The Next Design API is compatible between versions 4.0 and 5.0, and since .NET 8 and .NET 10 have been designed with compatibility in mind, extensions developed for these versions will generally work as-is.
However, if you plan to continue using extensions that meet the following conditions with version 5.0, please review their contents and make any necessary adjustments.

To use the APIs added in version 5.0 or later, you need a development environment that supports .NET 10. Visual Studio 2022 does not officially support .NET 10. Visual Studio 2026 or later is required for official support.

Note that you can still develop extensions that work with V5.0 by continuing to use Visual Studio 2022 and creating extensions for V4.0 (which supports .NET 8). However, in that case, you will not be able to use the APIs added in V5.0 and later.

IF YOU ARE USING AN API THAT CHANGES BEHAVIOR

In V5.0, the behavior of the following APIs will change. If you are using any of these, please verify that there are no impacts on your extension's operation and review your code as necessary.

API terms Before change After change
IModel.SetRichTextField Method
IModel.SetRichTextFieldValues Method		 Set by specifying a text value You can change the text value. The specified text value will be ignored.
IWorkspace.OpenProject method
IWorkspace.SaveProjectAs method
IProjectUnitManager.ExportModelUnit method
IProjectUnitManager.ImportModelUnits method
IProjectUnitManager.AddExternalUnits method
IProductLineModel.ExportAppliedProject method		 Specify a database file You can specify a file in DB format. An exception occurs.
IWorkspace.CleanUpProject Method There are model files registered as references This operation is performed on editable units within the project's managed units. This operation is performed on loaded units within the project's managed units that are editable and not marked as read-only.
IApplication.ExecuteScript Method
IApplication.ExecuteScriptCode Method		 Processing failed A system error occurs. A defined exception occurs.

If you are using the ExtensionPoints library

If you are using the ExtensionPoints library in your extension development project, please update to the V5.0-compatible version as follows.

Applicable Packages Compatible with Version 5.0
NextDesign.Desktop.ExtensionPoints 1.2.3.10306

When referring to the library bundled with Next Design itself

If your extension development project does not reference any libraries (Note 2) bundled with Next Design itself other than the extension development package (Note 1), the following checks are not required.

If you refer to the same libraries as those bundled with Next Design in addition to the extension development package to develop advanced extensions, the version of the libraries referred to when executing extensions may change with version upgrades of the libraries bundled with the main unit. The version of the library referenced when executing the extension may change as the version of the library bundled with the main unit is upgraded.

Please refer to the following manual to verify that the extension is functioning properly.

(Note 1) Packages for extension development: NextDesign.Core, NextDesign.Desktop, NextDesign.Desktop.ExtensionPoints

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

That is all.