Merging .Net assemblies for Tungsten TotalAgility

Professional Services
|
June 1, 2020
2 min read

In general, external .Net assemblies are used to implement additional customisation in the applications developed using Tungsten TotalAgility . However, there are challenges in Tungsten TotalAgility with uploading references of the .Net assemblies to Tungsten TotalAgility store. The challenge involves copying references of a .net assembly in the bin directory of TotalAgility, CoreWorker Service folders, etc.

For instance, “acmo.acore.businessrules.dll” is a reference in acmo.apay.tungsten .Net project. When the “acmo.apay.tungsten.dll” is uploaded to Tungsten TotalAgility .Net assemblies store, “acmo.acore.businessrules.dll” must be copied to bin directory of KTA manually.

The problem of copying, maintaining the references can be solved and the answer is “ILMerge“!.

ILMerge is a utility that merges multiple .NET assemblies into a single assembly. It is freely available for use and is available as a NuGet package. The merged single assembly can be uploaded into Tungsten TotalAgility store and we need not to worry about the reference dll’s

Firstly, ILMerge must be included in the .Net project and the simplest way is import as a NuGet package. Using following commands to install the pacakge to your project.

Once the package is installed successfully, right-click the reference dll and select “Properties” as shown below.

Set “Copy Local” property value to “true”. This will ensure that the reference dll is copied to the output directory. By default ILMerge considers only dll’s part of the output directory.

If there are multiple reference dll’s, Copy Local property should be set to true for each dll. This property is not required to be set for system .Net assemblies such as “System.Data”, “System.Core”,etc.

Once the project is built successfully, the ILMerge utility will create a folder named “ILMerge” in the \bin\(Debug or Release) directory based of build type.

“ILMerge” folder will contain the single merged dll and it can be uploaded to KTA .Net Assemblies store.

Additional configuration can be done using a config file – https://github.com/emerbrito/ILMerge-MSBuild-Task/wiki/Config-File

For further reading and reference – https://github.com/dotnet/ILMerge

Merging .Net assemblies for Tungsten TotalAgility

Professional Services
|
June 1, 2020
2 min read

In general, external .Net assemblies are used to implement additional customisation in the applications developed using Tungsten TotalAgility . However, there are challenges in Tungsten TotalAgility with uploading references of the .Net assemblies to Tungsten TotalAgility store. The challenge involves copying references of a .net assembly in the bin directory of TotalAgility, CoreWorker Service folders, etc.

For instance, “acmo.acore.businessrules.dll” is a reference in acmo.apay.tungsten .Net project. When the “acmo.apay.tungsten.dll” is uploaded to Tungsten TotalAgility .Net assemblies store, “acmo.acore.businessrules.dll” must be copied to bin directory of KTA manually.

The problem of copying, maintaining the references can be solved and the answer is “ILMerge“!.

ILMerge is a utility that merges multiple .NET assemblies into a single assembly. It is freely available for use and is available as a NuGet package. The merged single assembly can be uploaded into Tungsten TotalAgility store and we need not to worry about the reference dll’s

Firstly, ILMerge must be included in the .Net project and the simplest way is import as a NuGet package. Using following commands to install the pacakge to your project.

Once the package is installed successfully, right-click the reference dll and select “Properties” as shown below.

Set “Copy Local” property value to “true”. This will ensure that the reference dll is copied to the output directory. By default ILMerge considers only dll’s part of the output directory.

If there are multiple reference dll’s, Copy Local property should be set to true for each dll. This property is not required to be set for system .Net assemblies such as “System.Data”, “System.Core”,etc.

Once the project is built successfully, the ILMerge utility will create a folder named “ILMerge” in the \bin\(Debug or Release) directory based of build type.

“ILMerge” folder will contain the single merged dll and it can be uploaded to KTA .Net Assemblies store.

Additional configuration can be done using a config file – https://github.com/emerbrito/ILMerge-MSBuild-Task/wiki/Config-File

For further reading and reference – https://github.com/dotnet/ILMerge

Here is our comparison chart of the top 6 eSignature software solutions in 2022

Annual Cost per user $AU
Number of users allowed
Signing packages/year
In-person eSignature
Reusable Templates/drag and drop editor
Collect Payments
Automatic reminders & notifcations
Bulk Send
On-premise deployment
Cloud deployment
Hybrid deployment
Signature biometrics
Multiple input fields
Guided Signing
Delegate Signing
Stage Signing
Fully Customizable Signing Workflows
100% Personalised Branding
Custom Settings/ user rolls
Multifactor authentication
Mobile app
Enterprise-grade security
Free Trial available
API integrations
Audit trail
Supported Languages
US ESIGN, HIPAA
GDPR, eIDAS compliant
Upload documents as part of signing (photos)
Personal
Standard
Business Pro
Advanced
$168
$408
$660
Custom Quote
1
5
5
Custom Quote
60 (5/month)
100
100
Custom Quote
X
V
V
V
Y
Y
Y
Y
N
N
100
Y
Y
Y
Y
Y
N
N
Y
Y
N
N
N
N
Y
Y
Y
Y
N
N
N
N
Info N/A
Info N/A
Info N/A
Validate signer fields
in real-time
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
N
N
N
N
N
Y
Y
Y
N
N
N
N
N
N
Y
Y
Y
Y
Y
Y
SOC 2Type II
Y
Y
Y
Y
N
N
N
N
Y
Y
Y
Y
44
44
44
44
Y
Y
Y
Y
Y
Y
Y
Y
N
N
Y
Y
Professional
Enterprise
$336
Custom Quote
Unlimited
Unlimited
250
Custom Quote
Y
Y
Y
Y
N
N
Y
Y
Y
Y
Y
Y
Y
Y
N
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
N
Y
N
Y
N
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
43
43
Y
Y
Y
Y
Y
Y
Essentials
Standard
Premium
$291
$970
Custom Quote
1
2 or more
5 or custom
Unlimited
Unlimited
Unlimited
N
Y
Y
5 templates
15 templates
Y
N
N
N
Y
Y
Y
N
Y
Y
N
N
N
Y
Y
Y
N
N
N
N
N
N
Y
Y
Y
Y
Y
Y
N
Y
Y
N
Y
Y
N
N
Y
N
Y
Y
N
Y
Y
Y
Y
Y
Y
Y
Y
SOC 2 Type II ISO 27001
SOC 2 Type II ISO 27001
SOC 2 Type II ISO 27001
Y
Y
Y
Y
Y
Y
Y
Y
Y
22
22
22
N
Y
Y
Y
Y
Y
N
Y
Y
Free
Essentials
Business
Enterprise
Free
$335
$864
Custom Quote
Unlimited
Unlimited
Unlimited
Unlimited
Unlimited
Unlimited
Unlimited
Unlimited
N
N
N
N
N
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
N
N
Y
Y
N
N
N
N
Y
Y
Y
Y
N
N
N
N
N
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
N
N
Y
Y
N
N
Y
Y
N
N
N
Y
N
N
N
N
Y
Y
Y
Y
SOC 2 Type II
SOC 2 Type II
SOC 2 Type II
SOC 2 Type II
Free
Y
Y
Y
N
N
N
Y
N
Y
Y
Y
Info N/A
Info N/A
Info N/A
Info N/A
Info N/A
Info N/A
Info N/A
Info N/A
Y
Y
Y
Y
Info N/A
Info N/A
Info N/A
Info N/A
Business
Premium
Enterprise
Cloud
$141
$264
$529
$894
10
10
10
10
Unlimited
Unlimited
Unlimited
Unlimited
1
2+
2+
2+
Y
Y
Y
Y
N
N
Info N/A
Info N/A
N
Y
Y
Y
N
Y
Y
Y
N
N
N
N
Y
Y
Y
Y
N
N
N
N
N
N
N
N
Y
Y
Y
Y
Y
Y
Y
Y
N
N
Y
Y
N
N
Y
Y
N
N
Y
Y
N
N
Y
Y
N
N
Y
Y
N
N
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
N
N
N
N
Y
Y
Y
Y
Info N/A
Info N/A
Info N/A
Info N/A
Y
Y
Y
Y
Y
Y
Y
Y
N
N
Y
Y
Standard
Pro
Acrobat Sign
$264
$418
Custom Quote
Unlimited
Unlimited
Unlimited
Unlimited
Unlimited
Unlimited
Y
Y
Y
Y
Y
Y
N
Y
Y
Y
Y
Y
N
Y
Y
N
N
N
Y
Y
Y
N
N
N
N
N
India Only (Aadhar)
Y
Y
Y
Y
Y
Y
Y
Y
Y
N
Y
Y
Y
Y
Y
N
Y
Y
N
Y
Y
N
N
Y
Y
Y
Y
N
N
Y
Y
Y
Y
N
N
Y
Y
Y
Y
34
34
34
Y
Y
Y
Y
Y
Y
N
N
N

Try before you buy

Using our handy comparison chat you can now see the cost-to-feature breakdown of the top 6 e-Signature providers. All these providers offer a free trial of their software, so it’s worth doing some personal investigation and trying out the software yourself. ACMO offer a free 7-day trial of Kofax SignDoc via our Signmore solution.

Understand How is ACMO helping businesses accomplish more with intelligent automation

Related Posts