Home/ Questions/Q 5999859
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-23T00:36:41+00:00

I have two assemblies, created through conditional compilation (dev and real). The public surface

  • 0

I have two assemblies, created through conditional compilation (dev and real).

The public surface of these assemblies is 100% identical: both are strongly named; both are signed with the same .snk and therefore have the same PublicKeyToken; both have the same culture and the same version. I cannot change this: making them appear identical is the whole point.

However, on my machine the real assembly is in the GAC. I have an ASP.NET 3.5 WebForms app that references the dev assembly. It absolutely must do that; the real assembly crashes the app.

Is there a way to force a specific ASP.NET application to use the dev one (which is in /bin), given that:

  • There is one in the GAC.
  • Both have the same Version and PublicKeyToken.
  • Both are strongly named/signed with the same key.
  • I can not change them, can’t change the version, and can’t remove the key.

I noticed that someone already asked this in #991293, but the accepted answer involved removing the signing, which isn’t an option here.

Am I out of luck?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    GAC is always tried first, when binding assemblies: How the Runtime Locates Assemblies

    So no, you can’t do this. However if you explain why you have such strange requirements there might be a different work around, you have not thought of.

    • 0