title: Reproducing Newtonsoft.Json assembly version conflict
body: <p>I've set out to consistently reproduce the assembly version conflict in Newtonsoft.Json (related to my previous question <a href="https://stackoverflow.com/questions/44650761/why-is-newtonsoft-json-so-prone-to-assembly-version-conflicts">Why is Newtonsoft.Json so prone to assembly version conflicts?</a>) in order to better understand it, but I can't trigger it.</p>
  
  <p>From the top answer there, it should happen if I have project A which references one version of Json.NET, then it references a project B which itself references a different version (and they don't have assembly redirects to handle the issue).</p>
  
  <p>I've made a solution with a Class Library project and a Command Line project, both of which reference Newtonsoft.Json which I installed with Nuget Package Manager for both projects, and then I edited the Class Library packages.config to use an older version:</p>
  
  <pre><code>&lt;package id="Newtonsoft.Json" version="6.0.1" targetFramework="net452" /&gt;
  </code></pre>
  
  <p>While the Command Line project references the most recent version:</p>
  
  <pre><code>&lt;package id="Newtonsoft.Json" version="10.0.2" targetFramework="net452" /&gt;
  </code></pre>
  
  <p>This does not trigger the problem, however, the project still builds successfully and executes (I just serialize a string and print it from both projects, and I call the DLL from the EXE to ensure it tries to load both versions of Newtonsoft.Json.</p>
  
  <p>I've uploaded the test project at <a href="https://github.com/sashoalm/ReproduceNewtonsoftJsonBug" rel="noreferrer">https://github.com/sashoalm/ReproduceNewtonsoftJsonBug</a> if needed.</p>
  
  <p>Why isn't the bug getting triggered?</p>