Strong named assembly alongside unsigned assembly

Question

I have a situation where Docusign API is referencing the RestSharp signed assembly with a public key token of 598062e77f915f75. In the same project I am using the Twilio API which also references the unsigned Restsharp assembly, obviously with a null public key token.

I can make one or the other work but not both at the same time since I can't add both the signed and unsigned RestSharp references since they both have the same name.

When I have a reference to the signed assembly, the Docusign part works but the Twilio code errors with this:

Could not load file or assembly 'RestSharp, Version=105.2.3.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

When I reference the unsigned assembly, Docusign errors with this:

Could not load file or assembly 'RestSharp, Version=100.0.0.0, Culture=neutral, PublicKeyToken=598062e77f915f75' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

Is there any way around this?

I have tried binding redirects in every combination I can think of:

  <dependentAssembly>
    <assemblyIdentity name="RestSharp" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-100.0.0.0" newVersion="105.2.3.0" />
  </dependentAssembly>
  <dependentAssembly>
    <assemblyIdentity name="RestSharp" publicKeyToken="598062e77f915f75" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-100.0.0.0" newVersion="105.2.3.0" />
  </dependentAssembly>

With different publicKeyToken the assemblyRedirect configuration is a bit more complicated. Try use the answer on this question http://stackoverflow.com/questions/3158928/referencing-2-different-versions-of-log4net-in-the-same-solution/3163050#3163050 — Vince, Jun 16 '16 at 00:32

score 0 · Answer 1 · edited May 23 '17 at 12:32

I can think of few possible ways to solve this issue:

Binding redirect. Works if assemblies have same public key, otherwise you need to specify code base. See SO answer: Referencing 2 different versions of log4net in the same solution
Using GAC. Not sure if it would work with unsigned assembly.
Making use of AppDomain.AssemblyResolve event (see How to use Assembly Binding Redirection to ignore revision and build numbers)
Signing / unsigning assembly with one key using ildasm.

I once had similar issue with different log4net versions being referenced by our project and 3rd party library. Here is a blog post.

score 0 · Answer 2 · answered Jul 27 '17 at 14:54

0

I was facing the same issue. I have used the Nuget package of RestSharpSigned. This resolved my issue.

answered Jul 27 '17 at 14:54

Abhay Dhar

131
11

score -1 · Answer 3 · answered Jul 22 '16 at 10:54

Try to redirect every version up to the current to the latest installed version:

  <dependentAssembly>
    <assemblyIdentity name="RestSharp" publicKeyToken="598062e77f915f75" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-105.2.3.0" newVersion="105.2.3.0" />
  </dependentAssembly>

Strong named assembly alongside unsigned assembly

3 Answers3