Scripts and DLLs

Overview

There are two main ways to implement extensions:

Differences depending on how the extension is implemented are as follows.

Item	Script	.NET DLL
Next Design Object Model Manipulation	Yes	Yes
Event processing triggered by user operation	No	Yes
Advanced functional enhancements ・Conditional formatting changes in diagram view Addition of dynamic constraints during model editing operations Incorporation of user-specific UI	No	Yes
Immediate execution in Script Editor	Yes	No
Modification of distributed extensions	Yes	No
Visual Studio intellisense code completion	No	Yes
Debug execution with Visual Studio	No	Yes
Compile wait time at the time of the first process call	Yes	None
Processing Performance	High	High

The recommended implementation is to compile from C# to .NET DLL. You can expect high productivity because you can use powerful development support functions such as intellisense and debugger that Visual Studio has. Various unique functions can be realized by using abundant .NET libraries, and you can develop small to large-scale extensions.
In the C# script implementation method, the processing contents can be made open. The users of the extension can also use it after confirming the processing details, and if they need to change it, they can change the script directly and execute it.
Script-driven C# scripts can also be run immediately in Next Design's Script Editor.
.NET DLL-style C# and script-style C# scripts share the same handler implementation code. Therefore, after debugging using Visual Studio in the .NET DLL method, it is also possible to make small modifications to the implemented C# source code and provide it as a C# script.