Distribution of Extensions

Overview

There are two ways to distribute extensions so that other users can use them:

• Distributing using the package function
• Directly distributing the extension files

Memo

While directly distributing the extension files is simpler for personal use and debugging, for distribution to multiple users, we recommend using the package function as it makes updates easier.

Distributing using the Package Function

By building and deploying the extension as a package, it becomes possible to publish it using Next Design Extensions. This offers the following advantages:

• Easy installation and updates
• Manage multiple versions
• Can be used for distributing profiles in addition to extensions

Packages can be published as folders, allowing distribution via internal networks, GitHub, or Subversion. For details on package functionality, please refer to Distribution via Package Functionality.

Direct Distribution of Extension Files

Direct distribution is possible during extension development or for simple extension sharing. The complete set of extension files is distributed via network folder sharing or zip compression. Each user then copies and places the files in their designated folder within their Next Design execution environment. The following describes the extension placement location and provides an example folder structure.

Extension Placement Folder

To make the extension usable, copy the extension's storage folder directly under one of the following extensions folders.

• If only specific users can use the extension:

{User's Home Path}\AppData\Local\DENSO CREATE\Next Design\extensions\

Example of User's Home Path: C:\Users\user-name

• If all users of Next Design on that computer can use the extension:

C:\ProgramData\DENSO CREATE\Next Design\extensions\

note

• The following folders are hidden folders:

• {User's Home Path}\AppData\

• C:\ProgramData\

• To access them from Explorer, either type them directly into the address bar, or enable the [View] > [Show/Hide] > [Hidden Files] checkbox in the Explorer ribbon.

caution

• When distributing extensions developed using the .NET DLL implementation method, the extension may not function correctly if the following DLL versions do not match.

• NextDesign.Core.dll and NextDesign.Desktop.dll referenced in the extension development project

• The same DLLs stored in the Next Design installation folder where the extension is distributed

Example of Extension Folder Structure

When multiple extensions are deployed to the execution environment via direct distribution, the folder structure will be as follows:

C# Script

{NextDesignAppFolder}\extensions\
    myCsExtension\
        manifest.json
        main.cs
        locale.en.json
        locale.ja.json
        resources\
            image.png
    myDllExtension\
        manifest.json
        myDllExtension.dll
        resources\
            image.png

Python script

{NextDesignAppFolder}\extensions\
    myPyExtension\
        manifest.json
        main.py
        locale.en.json
        locale.ja.json
        resources\
            image.png