You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Overview

Script References in FrameworkX refer to external DLLs (Dynamic Link Libraries) that are incorporated for compiling scripts or display codes in solution. 

 These references allow users to extend the capabilities of their scripts by leveraging additional functionalities provided by external libraries.

On this page:

Configuring References

To add a DLL reference to your solution in FrameworkX, follow these steps:

Accessing References: Navigate to Scripts → References in your project.

Adding the DLL: Click on the 'More' button. This action will open a file manager.

Selecting the Library File: Browse and select the DLL file of your library that you wish to reference in your solution.

Configuring the Reference: After selecting the file, you can:

Assign a name to the reference.
Decide whether the reference is for client-side or server-side use.
Add a description.
Review in References Table: Once added, a new row will appear in the References table corresponding to the DLL file you selected.

TargetDomainSpecifies the domain where the DLL will be used (client or server).
NetAssemblyNameSpecifies the domain where the DLL will be used (client or server).
DefaultNamespaceThe default namespace used by the DLL.
ResolvedIndicates whether the reference has been successfully resolved. A checkmark symbol (?) signifies that the DLL import compiled without errors, whereas an 'X' indicates that there were compilation errors. If you encounter an 'X', hover over the line of your Script Reference to view the error code and a description of the problem.
PortableShows if the DLL is portable across different platforms.
AssemblyPathLocalThe local path of the assembly file.
AssemblyPathRuntimeThe runtime path of the assembly file used during execution.

To see more information about Managing External DLLs, please the the Manage External DLLs page.


In this section...

The root page @parent could not be found in space v10.

  • No labels