title: NetFramework app referencing NetFramework library in same solution referencing NetStandard library in another soln.: could not load file or assembly
body: <p>There are many similar questions about problems referencing a .NET Standard class library from a .NET Framework project where a NuGet package dependency in the netstandard library doesn't flow to the netframework app, and the <code>Could not load file or assembly</code> error occurs at runtime:</p>
  
  <p><a href="https://i.stack.imgur.com/lUGdX.png" rel="noreferrer"><img src="https://i.stack.imgur.com/lUGdX.png" alt="enter image description here"></a></p>
  
  <p>Many sources exist, like the one below, that indicate this can be resolved by adding the missing dependency on the netframework project:</p>
  
  <ul>
  <li><a href="https://stackoverflow.com/a/46015829/2704659">https://stackoverflow.com/a/46015829/2704659</a></li>
  </ul>
  
  <p>This is unfavorable, however, because I don't want to have projects have to carry around direct references that they shouldn't require; the dependencies should flow naturally so future added/removed dependencies just work.</p>
  
  <p>Other sources indicate that it can be resolved by adding <code>&lt;RestoreProjectStyle&gt;PackageReference&lt;/RestoreProjectStyle&gt;</code> and <code>&lt;AutoGenerateBindingRedirects&gt;true&lt;/AutoGenerateBindingRedirects&gt;</code> to the netframework project file:</p>
  
  <ul>
  <li><a href="https://stackoverflow.com/a/53654690/2704659">https://stackoverflow.com/a/53654690/2704659</a></li>
  <li><a href="https://stackoverflow.com/a/53732075/2704659">https://stackoverflow.com/a/53732075/2704659</a></li>
  <li><a href="https://www.hanselman.com/blog/ReferencingNETStandardAssembliesFromBothNETCoreAndNETFramework.aspx" rel="noreferrer">https://www.hanselman.com/blog/ReferencingNETStandardAssembliesFromBothNETCoreAndNETFramework.aspx</a></li>
  </ul>
  
  <p>I've tested both of the above fixes with projects <em>that reside within the same Visual Studio solution</em> and had success, but I prefer the second approach because it's a "set it and forget it" solution.  </p>
  
  <p>The problem I've found is when I try to reference a netstandard class library from a netframework project <em>in another VS solution</em> and I use the <code>&lt;RestoreProjectStyle&gt;PackageReference&lt;/RestoreProjectStyle&gt;</code> and <code>&lt;AutoGenerateBindingRedirects&gt;true&lt;/AutoGenerateBindingRedirects&gt;</code>approach in the latter project.  In my specific case, I have a .NET Framework executable project that references a .NET Framework class library in the same solution, and that class library references a .NET Standard class library in another solution.</p>
  
  <p>I've created <a href="https://github.com/roryap/Multi-Solution-NetStandard-from-NetFramework-Dependency-Issue" rel="noreferrer">an MCVE on GitHub that demonstrates this behavior</a>. I'm using VS 2017 v15.9.4.</p>
  
  <p>Other than always adding the packages directly on the netframework project, is there a way to get this working?</p>
  
  <hr>
  
  <p>(Note: it sounds similar to the problem here, but I'm not using "click once": <a href="https://stackoverflow.com/a/47839628/2704659">https://stackoverflow.com/a/47839628/2704659</a>)</p>