title: All solution packages copied to output for single project
body: <p>I have a solution that contains a primary .NET project (WPF desktop application) and several library projects (i.e. plugins). Each of these projects contains (non-overlapping) references to NuGet packages (installed using the PackageReference mechanic). For example:</p>
  
  <ul>
  <li><code>WpfApplication</code> References:
  
  <ul>
  <li><code>MaterialDesignThemes</code></li>
  <li><code>MvvmValidation</code></li>
  <li><code>System.Threading.Tasks.Dataflow</code></li>
  </ul></li>
  <li><code>Plugin1</code> References:
  
  <ul>
  <li><code>Newtonsoft.Json</code></li>
  <li><code>WpfApplication</code> (copy local=False)</li>
  </ul></li>
  <li><code>Plugin2</code> References:
  
  <ul>
  <li><code>Accord.Video.FFMPEG</code></li>
  <li><code>WpfApplication</code> (copy local=False)</li>
  </ul></li>
  </ul>
  
  <p>But when I build <code>Plugin1</code>, the build directory (a subdirectory of the <code>WpfApplication</code> build directory) contains the union of the packages referenced in <code>WpfApplication</code> and <code>Plugin1</code> (but not packages defined in <code>Plugin2</code>).</p>
  
  <p>Similarly, when I build <code>Plugin2</code>, the build directory (again, a subdirectory of the <code>WpfApplication</code> build directory) contains the union of the packages referenced in <code>WpfApplication</code> and <code>Plugin2</code> (but not packages defined in <code>Plugin1</code>).</p>
  
  <p>I did not have this problem with older style <code>packages.config</code>.</p>
  
  <p>These extra packages amount to >100 files and ~15MB of disk space per plugin! How can I stop this from happening? </p>