Page History

Configuring References

To add a Script Reference, follow the steps below:

1. Access Scripts → References.
2. Click on the plus icon.
3. Browse and select the DLL file that you wish to reference in your solution.
4. Input a name, description, and a choose the domain target for the reference.
5. Click OK.

Once added, a new row will appear in the References table corresponding to the DLL file you selected. 

Script References Configuration Table

The following is a table describing each available property field for script classesScript References:

AssemblyPath Macros

When defining the AssemblyPath, the following macros are available:

Loading and Placing

the External DLL

It's necessary to understand the best location to put the external DLLs, and when they are loaded by the platform. 

Location of Referenced DLLs

You should avoid using absolute paths, as when you need to move your Solution to other computercomputers, that path may be invalid. 

For Server server-side DLLs, the best location to put the external DLL is the ThirdParty folder created by the platform in your Documents folder after the installation. For Client side DLLs, the best location is WpfControls folder in the product installation folders.

ThirdParty Folder

This folder is to store external server side ThirdParty DLLs. Use the macro _ThirdParty_ at ScriptsReferences to add a reference to those DLLs in your solution.

To add custom C# using statements (or VB Import), use the Namespaces Declarations toolbar icon at the Script CodeEditor. Those DLL can be used on ScriptsTasks and ScriptsClasses of domain Server.

The subfolder SNMP is to add additional MIB files for SNMP communication driver.

WpfControls Folder

This folder is to store external client side WPF Controls DLLs. Use the macro _WpfControls_ at ScriptsReferences to add a reference to those DLLs in your solution

If necessary to add custom C# using statements (or VB Import), use the NamespacesDeclaration toolbar icon at the Script CodeEditor. Those DLLs can be used on Displays and CodeBehind in WPF Displays. Those controls won't be available automatically for SmartClients, for that type Client, it is necessary to create a new manifesto. 

if the DLL was created using T.Portable specification, it can also run on Web Pages.

When the DLLs are Loaded Loaded

When

in

Runtime

The DLL is loaded when the Script Module is started. So if If you need to update the DLL file, you need to must stop the Script module Module and close the Designer (Solution engineeringEngineering) , so , you can replace the DLL file in the folder. After that, and after you can run the Script Module again, and the DLL will be updated.

Just

Using the Designer

The DLL file is loaded when the Edit>Scripts Edit > Scripts page is open opened for the first time. If you open the project, open access the Scripts, and add for the first time a new DLL in the references for the referencefirst time, you can back return to Scripts and you will be able to use the DLL. ButHowever, if you add a DLL in the referencereferences, open the Scripts, and only after, you afterward replace or update the DLL file, and when you open Scripts again, the script will not be able to find the new modifications of the DLL. You need to close the Designer and open it again, and when you join in Edit>Scripts return to Edit > Scripts, the DLL will be updated.

C#

Using or VB.NET Import

Statements

When using external DLLs it is common to have to add the namespaces of the DLL on your code. 

In C#, we refer to that is the as using keyword, which is equivalent to the VB.NET Import.

Due some optimizations in our Code Editor, you can't add those namespaces directly in the code, ; you need to use the Add Namespaces button on the top toolbar.Image Added

Image Removed Use this Toolbar command to open the "Namespace Declarations" where you can your namespaces references, whatever you using C# or VB.NET language. 

In this section: