Scripts and DLLs

Overview

There are two main ways to implement extensions.

• Script

  Implementation method by C# script

• .NET DLL

  Implementation method to compile from C# to .NET DLL

Differences depending on the implementation method

• The differences depending on how the extension is implemented are as follows.

  Items	Scripts	.NET DLLs
  Next Design Object Model Manipulation	Yes	Yes
  Event processing triggered by user operation	Impossible	Possible
  Advanced enhancements -Conditional formatting in diagram view Adding dynamic constraints during model editing operations Incorporating user-specific UI	Impossible	Possible
  Immediate execution in script editor	Yes	No
  Modification of distributed extensions	Possible	Not possible
  Visual Studio intellisense code completion	Impossible	Possible
  Debugging with Visual Studio	Impossible	Possible
  Compile wait time when calling the first process	Yes	None
  Processing performance	High	High

• The recommended implementation is to compile from C# to a .NET DLL. You can expect high productivity because you can take advantage of powerful development support functions such as intellisense and debugger that Visual Studio has. You can use the rich .NET library to realize various unique functions and develop from small to large extensions.

• The implementation method by C# script can open the processing contents. Extension users can also check the processing details before using it, and if necessary, the script can be directly modified and executed.

• Scripted C# scripts can also be run immediately in Next Design's Script Editor.

• The .NET DLL-based C# and script-based C# scripts share the same handler implementation code. Therefore, it is possible to debug using Visual Studio using the .NET DLL method, and then provide the implemented C# source code as a C# script with minor modifications.