Note that there are some explanatory texts on larger screens.

plurals
  1. POAssembly reference error on web site with same signature
    text
    copied!<p>I've more than one ASP.NET 2.0 web site on IIS 6 and Windows Server 2003. Each site reference some DLLs: design, logic and so on. Each site is on a different ApplicationPool with default configuration about recycling techniques.</p> <p>Every DLL is strong named (not delayed) and has a version that never changes (2.0.0.0), all DLLs are placed in GAC.</p> <p>After I update a DLL in GAC (ie. MyLibrary.dll) that has changed in something (method, classes..) for the use in web-site "A", and after recycling only the "A" application pool, when I try to access to web-site "B" that reference the same DLL I get the common error about that DLL:</p> <blockquote> <p>The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)</p> </blockquote> <p>Of course nothing is changed in DLL rather than code, same strongkey, same version, culture. The error disappear over recycling "B" application pool, of course.</p> <p>What can generate a strange, <strong>RANDOM</strong> (I've to say!), behavior? There's something more, like hashing, that it's used to compare assemblies?</p> <h2>Addendum</h2> <ul> <li><a href="https://stackoverflow.com/users/37494/perpetualcoder">Perpetualcoder</a> asked me how DLLs are referenced, if with full qualified name, I think it is, here a line of web.config:</li> </ul> <blockquote> <p>assembly="MyNamespace.MyComponent, Version=2.0.0.0, Culture=neutral, PublicKeyToken=1234567890ASDFGH"</p> </blockquote>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload