title: how do I work around log4net keeping changing publickeytoken
body: <p>We have an asp.net 4.0 project which uses a couple of frameworks which is dependent on log4net version 1.2.10.0. Today I tried to include a new framework which is dependent on log4net version 1.2.11.0, I've been stuck ever since: </p>
  
  <p>log4net 1.2.10.0 has publickeytoken = 1b44e1d426115821</p>
  
  <p>log4net 1.2.11.0 has publickeytoken = 669e0ddf0bb1aa2a</p>
  
  <p>Since these are different i cannot use either assembly redirects (to make all frameworks use the same version of log4net) or codebase (to have just the new framework use version 1.2.11.0) through the runtime element in web.config. </p>
  
  <p>What are my options here ?</p>
  
  <p>(and why the bleep does log4net keep changing publickeytokens between versions, as I understand it a lost key was the reason for the switch between version 1.2.9.0 and 1.2.10.0, did they lose the key yet again? I'll volunteer my dropbox to keep it safe if they need it...)</p>
  
  <p>Edit: Ok, so the log4net guys apparently had the idea that releasing with two keys was a good idea, but that means that <em>every</em> framework you make use of needs to agree on <em>which</em> of the two flavors they prefer, or those frameworks cannot work side by side in the same appdomain. Am I the only one finding this a horrible idea? if everyone did this then everything would break down, right?</p>
  
  <p>Edit2: As I stated, I'm not using log4net in my business code, but I use several frameworks which depend on 1.2.10.0, and the problem arose when I tried to use a new framework which depended on 1.2.11.0 (new key), so Stefans answer doesn't apply, because the new framework will expect the new key, not the old one </p>