title: Nuget creates app.config files in multiple projects
body: <p>I'm starting to use Nuget in my solution to install Owin and some other dependencies in certain projects. I'm reading about Nuget and app.config files here </p>
  
  <p><a href="https://stackoverflow.com/questions/22227675/why-nuget-adds-app-config-with-assemblybinding-to-library-projects-during-a-nuge">Why NuGet adds app.config with assemblyBinding to LIBRARY projects during a NuGet package update?</a></p>
  
  <p>and here </p>
  
  <p><a href="https://msdn.microsoft.com/en-us/library/7wd6ex19.aspx" rel="nofollow noreferrer">https://msdn.microsoft.com/en-us/library/7wd6ex19.aspx</a></p>
  
  <p>Now I know why are they used, binding specific versions and so on...</p>
  
  <p>The problem that I'm having is that i.e I have a big solution with 32 projects.</p>
  
  <p>If I install Owin in project C. An app.config file appears in projects A,B,D,F with the following information.</p>
  
  <pre class="lang-xml prettyprint-override"><code>&lt;runtime&gt;
      &lt;assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"&gt;
        &lt;dependentAssembly&gt;
            &lt;assemblyIdentity name="Microsoft.Owin" 
                publicKeyToken="31bf3856ad364e35" culture="neutral" /&gt;
            &lt;bindingRedirect oldVersion="0.0.0.0-3.0.1.0" newVersion="3.0.1.0" /&gt;
        &lt;/dependentAssembly&gt;
      &lt;/assemblyBinding&gt;
  &lt;/runtime&gt;
  </code></pre>
  
  <p>Why I'm getting this? These projects are not using OWIN. Is there any way to avoid this? Or maybe installing it manually without using nuget?</p>
  
  <p>Thank you.</p>
  
  <p>P.S: I'm using VS2015 enterprise</p>
  
  <p>EDIT:</p>
  
  <p>The architecture that we have it's as follow. I Have project WebApi with Owin installed. That project is referenced with the project Connector. That project Connector and all that reference it have the previous app.config file. Is that correct? Why it's necessary if they are not using OWIN?</p>
  
  <p>EDIT2:</p>
  
  <p>I uninstalled all nuget packages from my solution using nuget package manager inside VS2015 and these files with that dependencies are still there.</p>