Skip to main content
Newcomer
April 28, 2025
Question

Dependency error while using DocuSign.eSign.dll version 8.1.0 for eSignature API integration

  • April 28, 2025
  • 2 replies
  • 172 views

Received dependency version mismatch error while trying to import “DocuSign.eSign.dll” version 8.1.0.

While downloaded “DocuSign.eSign.dll” (version 8.1.0) using .NET NuGet Package Manager, the version of “System.Numerics.Vectors.dll” downloaded was “4.1.4.0”. But when tried to import that “DocuSign.eSign.dll” (version 8.1.0) to our product, got an error as “System.Numerics.Vectors.dll” version “4.1.3.0” is missing.

Unable to get any reference of the version 4.1.3.0 for “System.Numerics.Vectors.dll”.

Please help to this dependency version mismatch error for “DocuSign.eSign.dll”.

 

Error Message: “Could not load file or assembly ‘System.Numerics.Vectors, Version=4.1.3.0’ or one of its dependencies. The system cannot find the file specified.”

2 replies

Docusign Employee
April 29, 2025

@sumanm2025 Can you try using an Assembly Binding Redirect to resolve this issue? 
You can add a binding redirect to your application’s configuration file (App.config or Web.config) to direct the runtime to use version 4.1.4.0 when version 4.1.3.0 is requested. 
Searching online should show examples how this being implemented. 

Newcomer
April 30, 2025

@sumanm2025 Can you try using an Assembly Binding Redirect to resolve this issue? 
You can add a binding redirect to your application’s configuration file (App.config or Web.config) to direct the runtime to use version 4.1.4.0 when version 4.1.3.0 is requested. 
Searching online should show examples how this being implemented. 

Thanks for your response ​@Koll.Klienstuber.

For me the error is coming in a different scenario.

It is working fine in my Visual Studio project, but we have a product where we can write our own C# code. Only thing required there, is to add reference dll to run the C# code. Now when I am trying to add reference to “DocuSign.eSign.dll” then getting this error. There is not provision for runtime binding in our product.