Distribution of extensions
Overview
There are two ways to distribute extensions for others to use:
- Distribute using the package function
- Distribute a set of extension files directly
memo
At the time of personal use or debugging, it is simple to distribute the extension file set directly, but it is recommended to use the Use Package Function, which is easy to update, for distribution to multiple users. increase.
Distribute using the package function
Build and deploy extensions as packages to Next Design Extensions It will be possible to publish at. It has the following advantages.
- Easy to install and update
- Can manage multiple versions
- Can be used for profile distribution as well as extensions
Packages can be published in folders, so you can use your corporate network or distribute them using GitHub or Subversion. See Deployment by Package Function for the package function.
Distribute a set of extension files directly
It can be distributed directly at the time of extension development or for simple extension sharing. Distribute the created extension file set by sharing it in a network folder or zip-compressing it. After that, each user copies and places it in the specified folder of his Next Design execution environment. The following describes where to place the extension and shows an example of the folder structure.
Extension folder
To make extensions available, copy the extension storage folder directly under one of the following extensions
folders:
When only a specific user uses the extension
{User's home path}\AppData\Local\DENSO CREATE\Next Design\extensions\
Example user home path:
C:\Users\user-name
If all users of Next Design on that computer will use the extension
C:\ProgramData\DENSO CREATE\Next Design\extensions\
memo
The following folders are hidden folders.
{User's home path}\AppData\
C:\ProgramData\
To access from Explorer, type directly in the address bar or select the View> Show/Hide> Hidden Files check box from the Explorer ribbon.
Attention
When distributing an extension developed by the .NET DLL method, the extension may not work properly if the following DLL versions do not match.
NextDesign.Core.dll
andNextDesign.Desktop.dll
referenced in the extension development project- The same DLL stored in the Next Design installation folder to which the extension is distributed.
Extension folder configuration example
If 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