Skip to main content
arrow-left Back to Docusign.com

Using methods of DocuSign.eSign.dll in a Window Service , developed with C# and targeted to .NET framework 4.7.2 you got a seemingly endless number  of runtime exceptions like ‘Could not load file or assembly 'System.Memory, Version=4.0.1.1, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies.’

When you fix the the dependency exception e.g. for Microsoft.IdentityModel.Tokens.dll a new problem with Microsoft.IdentityModel.Logging.dll shows up and then with Microsoft.IdentityModel.JsonWebTokens.dll an so on.

Even the latest version of DocuSign.eSign.dll (8.1.0.0) seems to depend on older or deprecated versions of system dlls.

Has anyone already had to deal with this problem ?

 

Hi,

The list of dependencies are located here: https://github.com/docusign/docusign-esign-csharp-client?tab=readme-ov-file#dependencies

This client has the following external dependencies:

.NET Standard v2 and .NET Core:

  • Newtonsoft.Json v13.0.3
  • BouncyCastle.Cryptography v2.3.1
  • System.ComponentModel.Annotations v5.0.0
  • Microsoft.IdentityModel.JsonWebTokens v7.5.2

.NET Framework, version 4.6.2:

  • Newtonsoft.Json v13.0.3
  • BouncyCastle.Cryptography v2.3.1
  • System.ComponentModel.Annotations v5.0.0
  • Microsoft.IdentityModel.JsonWebTokens v7.5.2

It sounds like your project may have some conflicting dependencies that you will need to resolve based on your project references.

Code of ConductAccessibility statement

Docusign Community

Code of Conduct