title: Found conflicts between different versions of the same dependent assembly - app.config different from packages.config
body: <p>I have a solution with over 40 projects.
  In most of these projects I'm using System.Net.Http which I have installed via NuGet. At the time of writing we have installed v4.3.3 from Nuget. That is also what is written into packages.config</p>
  
  <pre><code>&lt;package id="System.Net.Http" version="4.3.3" targetFramework="net47" /&gt;
  </code></pre>
  
  <p>When I look into my app.config , I'm using different versions here. In some of my configs the version is listed as 4.1.1.2, in others its listed as 4.2.0.0. I Guess these are the internal versions, but what I find wired is that installing the same NuGet on two different projects gives me two different internal versions.</p>
  
  <p>One app.config:</p>
  
  <pre><code>&lt;dependentAssembly&gt;
    &lt;assemblyIdentity name="System.Net.Http" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" /&gt;
    &lt;bindingRedirect oldVersion="0.0.0.0-4.1.1.2" newVersion="4.1.1.2" /&gt;
  &lt;/dependentAssembly&gt;
  </code></pre>
  
  <p>Another app.config:</p>
  
  <pre><code>&lt;dependentAssembly&gt;
   &lt;assemblyIdentity name="System.Net.Http" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" /&gt;
    &lt;bindingRedirect oldVersion="0.0.0.0-4.2.0.0" newVersion="4.2.0.0" /&gt;
  &lt;/dependentAssembly&gt;
  </code></pre>
  
  <p>I have tried downgrading and then upgrading again in Nuget in order to get both the packages.config &amp; app.config updated. And the files are updated.
  But in some app.config I get another version than I get in other. With the excat same NuGet version, installed at the same time.</p>
  
  <p>What gives?</p>
  
  <p>I have read quite a bunch of topics here on SO, but none of them quite has the same problem. Most of the time, people fix their problem by upgrading to the latest version, that doesn't help here.</p>
  
  <p>I'm guessing that I might have other references that force the version of System.Net.Http to an older version for that project, but is there any way I can confirm this thesis? Also, if that is actually the case, is it then possible to enforce all project to run the highest common version instead of different versions?</p>