Skip to main content

Execution and Debugging

Preparation for Execution​

  • Create a subfolder for each extension directly under the extension's destination folder (hereinafter referred to as the storage folder).

For details on the extension's destination folder, please refer to Extension Distribution.

  • Copy and place the following set of files into the storage folder.
{NextDesignAppFolder}\extensions\helloworld\
manifest.json ... Manifest
main.cs ... Script file specified as the entry point (for C#)
main.py ... Script file specified as the entry point (for Python)
locale.en.json ... English locale file (for multilingual support)
locale.ja.json ... Japanese locale file (for multilingual support)
resources\
button.png ... Image file for the UI button specified in the extension point of the manifest

Debugging​

  • When Next Design is launched, the manifests of all extensions placed in the designated folder are loaded, and the ribbon tabs and buttons defined in the extension points are added according to the extension lifecycle.

  • When a handler implemented in an extension is called for the first time, the script is loaded, compiled, and then executed.

  • If there are errors during the compilation of the C# script, the error message will be displayed in the System category of the [Output] tab in the error list window.

  • In the case of Python scripts, syntax errors and runtime errors will also display error messages in the output area.

Script execution debugging

note
  • Debuggers cannot be used with the script-based implementation method, so breakpoints cannot be set.
  • Development using the .NET DLL method with Visual Studio allows you to use the debugger included in Visual Studio.
caution

Changes made to extensions or scripts while Next Design is running will not be reflected. All extensions are loaded when Next Design is launched and are not reloaded while Next Design is running. Similarly, extension scripts are loaded at the time of the first processing call and are not reloaded while Next Design is running.

important

  • If there is an error in the manifest definition, the extension will not work.

  • If there is an error in the manifest definition, the manifest will be ignored, and the ribbon element defined as an extension point will not be displayed.

  • Rarely, Next Design may fail to start due to an error in the manifest. In such cases, temporarily change the manifest file name to something other than manifest.json and then restart Next Design to check.

  • Next Design will not start if a C# script is missing a using statement.

  • Classes used in C# scripts must be referenced by including a using statement at the beginning of the script. If an application lifecycle extension is missing a using statement, Next Design will fail to start. In such cases, change the lifecycle in manifest.json to switch to the project lifecycle, restart Next Design, and check the system output messages displayed when you open any project.

Last updated on