Note that there are some explanatory texts on larger screens.

plurals
  1. POYet another issue about log4net 1.2.11 conflicts
    text
    copied!<p>I've spent the last 2 hours looking over these issues on SO, and nothing seems to be working.</p> <p>I have a solution that uses log4net 1.2.11, via NuGet. It works fine on my 32 bit development workstation running Windows 7. It does not run on my 64-bit Windows 2008 R2 test system. The error I get is:</p> <blockquote> <p>Unhandled Exception: System.IO.FileLoadException: Could not load file or assembly 'log4net, Version=1.2.11.0, Culture=neutral, PublicKeyToken=669e0ddf0bb1aa2a' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference.</p> </blockquote> <p>I am looking in the application directory on my test system. The <code>log4net.dll</code> file there is version 1.2.11. </p> <p>The version in the GAC was version 1.2.10. I have removed it. There was a version on my development server that was yet again something else; I removed that as well. I have rebuilt; I have redeployed. I have added </p> <pre><code>&lt;dependentAssembly&gt; &lt;assemblyIdentity name="log4net" publicKeyToken="669E0DDF0BB1AA2A" culture="neutral"/&gt; &lt;bindingRedirect oldVersion="0.0.0.0-1.2.10.0" newVersion="1.2.11.0"/&gt; &lt;/dependentAssembly&gt; </code></pre> <p>to my configuration file. Nothing seems to make a bit of difference. My deployment project shows the right version and signature of the log4net assembly that is being deployed.</p> <p>I do not know what else I can do, but I am getting quite frustrated that a logging library is preventing my application from running.</p> <p>What have I missed?</p>
 

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