title: Could not load file or assembly 'AssemblyName PublicKeyToken=null' or one of its dependencies
body: <blockquote>
    <p>{"Could not load file or assembly 'AssemblyName, PublicKeyToken=null' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)":"AssemblyName, PublicKeyToken=null"}</p>
  </blockquote>
  
  <p>I'm getting the message in question as an <code>InnerException.Message</code> while trying to debug my application after signing the unsigned third-party assemblies it is using. 
  The weird thing is that I have already signed the assembly shown in the message, the one that can't be loaded. </p>
  
  <p>What could the problem be here? How can I resolve this?</p>
  
  <p><strong>EDIT</strong></p>
  
  <p>Editing to give more information on what I did:</p>
  
  <ul>
  <li>Signed all the unsigned third-party assemblies my project is referencing.</li>
  <li>Disassembled those assemblies to see if they internally reference any external unsigned assemblies (they didn't)</li>
  <li>Deleted the old unsigned assemblies from the project's reference list, and re-added the newly signed ones.</li>
  <li>Unloaded the project and edited the reference of the assembly that can't be loaded in the .sln XML-styled file by adding the PublicKeyToken that was missing from the assembly reference.</li>
  </ul>
  
  <p>The assembly that throws the exception, btw the project builds fine it's a runtime exception I'm getting on <code>InitializeComponent()</code> of that assembly, is an open source component with WPF controls (<a href="http://mahapps.com/MahApps.Metro/" rel="noreferrer">MahApps.Metro</a>). I've found a similar question but none of the answers there fixed the issue.</p>
  
  <p><a href="https://stackoverflow.com/questions/1453107/how-to-force-wpf-to-use-resource-uris-that-use-assembly-strong-name-argh/6341678#6341678">How to force WPF to use resource URIs that use assembly strong name? Argh!</a></p>