Add a .NET assembly
You can add a .NET assembly from existing .NET assemblies or add a new assembly to the store (database).
When configuring .NET assemblies in TotalAgility running in On-premise multi-tenant and Azure environments, only existing local assemblies are available for use. You cannot add new local assemblies, but you can add Store assemblies.
TotalAgility supports both Local and Store .NET assemblies as process references for use in script activities.
Add a local .NET assembly
To add an assembly from existing .NET assemblies, perform the following steps.
-
Navigate to
.
The .Net assemblies page appears.
-
Select
.
The Add .Net assemblies (Local) dialog box is displayed.
- By default, your working category is selected. To change the category, on the Category list, select a category for the .NET assembly.
-
Enter the
Reference path of the .NET assembly.
If a .NET Core assembly is selected, its version number is displayed. For example, Version .Net 6.
-
Optional. In the
Description field, enter a description for the .NET assembly, such as
"Company .NET assemblies."
A description can include a maximum of 255 characters.
- Select Load assembly using full name if you want the system to load the assembly from GAC when you use this .NET reference in a process or form, at runtime. The full file path is still required in the Reference Path so that TotalAgility can retrieve the full name at design time. (Default: Clear)
-
Select
Save.
If you try to add an assembly created in .NET Core, and .NET 8 or higher is not installed, an error message is displayed.
Upload a .NET assembly to the store
You can upload .NET assemblies to the store as a single DLL file or as a ZIP package that includes the primary assembly along with its dependent assemblies. The ability to upload primary assembly along with multiple dependent assemblies in a single operation ensures that .NET actions, activities, and rules execute successfully without missing dependency errors.
You can upload both .NET Core and .NET Framework assemblies.
-
Navigate to
.
The .Net assemblies page appears.
-
Select
.
The Upload .Net assemblies (Store) dialog box is displayed.
- By default, your working category is selected. To change the category, on the Category list, select a category for the .NET assembly.
-
Select
Browse for
Reference path and select the required file (either a single .NET DLL or a
ZIP package).
The selected file path appears in the Reference path box.
- The ZIP must match the name of the primary assembly inside it. For example, MyLibrary.zip must contain MyLibrary.dll. If no matching DLL is found, an error message is displayed, and the ZIP cannot be uploaded.
-
The Package Zip Max Size (MB) and Package Max Files settings in the Streaming tab of the Configuration Utility control the ZIP size and the number of files allowed in the ZIP. Refer to the Tungsten TotalAgility Configuration Utility Guide for more information.
- To overwrite an existing assembly, select Overwrite existing files.
-
Optional. In the
Description box, enter a brief description for the .NET assembly, such as
"Company .NET assemblies."
A description can include a maximum of 255 characters.
-
Select
Save to upload the assembly.
The Upload .NET assemblies dialog box displays the progress of file upload.
If the upload fails for any reason, an error message is displayed.
-
Once the files are uploaded, select
Finish.
The .Net assemblies page lists the .NET assemblies created. You can filter the .NET assemblies by assembly type and category.