Home/ Questions/Q 7707095
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-01T00:16:27+00:00

I have a problem with .NET assembly redirection. 3rd party assembly A references another

  • 0

I have a problem with .NET assembly redirection. 3rd party assembly A references another 3rd party assembly B. B is not signed so it doesn’t have public key token. Manifest of A:

....
.assembly extern B
{
  .ver 1:0:0:0
}
....

How can I make binding redirection to the next version of B that became signed?
If I don’t specify publicKeyToken in assemblyBinding/dependentAssembly/assemblyIdentity, runtime can’t find assembly “B, Version=2.0.0.0, Culture=neutral, PublicKeyToken=null”. If I specify than redirection rule doesn’t match dependent assembly reference in metadata.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I’ve found no ways make binding redirection to signed assembly from unsigned. Just one not very good solution I’ve found is to remove signature from signed assembly. To do it ildasm can be used to disassembly, after public key should be removed from .il file and using ilasm changed .il can be compiled.

    • 0