Distributing extensions
Overview
There are two ways to distribute an extension so that other users can use it.
- Distribute using the package function
- Distribute the entire set of extension files directly
For personal use or debugging, directly distributing the entire set of extension files is simple, but for distribution to multiple users, we recommend using the package function, which is easy to update.
Distributing using the package function
By building and deploying an extension as a package, it becomes possible to publish it in Next Design extensions. This has the following advantages:
- Easy to install and update
- Multiple versions can be managed
- Can be used to distribute profiles in addition to extensions
Packages can be published using folders, so they can be distributed using an internal network or GitHub or Subversion. For information on the package function, see Distribution using the package function.
Distributing the extension file set directly
Direct distribution is possible when developing an extension or for simple extension sharing. Distribute the created extension file set by sharing it in a network folder or compressing it into a zip file. After that, each user copies and deploys it in a specified folder in the Next Design execution environment. The following explains where to deploy the extension and shows an example of the folder structure.
Folder where extension is deployed
To make the extension available, copy the extension storage folder directly under one of the following extensions
folders.
- If only a specific user uses the extension
{user home path}\AppData\Local\DENSO CREATE\Next Design\extensions\
Example of user home path: C:\Users\user-name
- If all users who use Next Design on that computer use the extension
C:\ProgramData\DENSO CREATE\Next Design\extensions\
-
The following folders are hidden folders.
-
{user home path}\AppData\
-
C:\ProgramData\
-
To access from Explorer, enter it directly in the address bar or turn on the [View] > [Show/Hide] > [Hidden Files] check box in the Explorer ribbon.
-
When distributing an extension developed using the .NET DLL implementation method, the extension may not work correctly if the following DLL versions do not match.
-
NextDesign.Core.dll
andNextDesign.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 placed in the execution environment by direct distribution, the folder structure will be as follows.
{NextDesignAppFolder}\extensions\
myCsExtension\
manifest.json
main.cs
locale.en.json
locale.ja.json
resources\
image.png
myDllExtension\
manifest.json
myDllExtension.dll
resources\
image.png