title: NuGet Assembly outside lib folder
body: <p>I'm going to bang out a couple of questions here...first, with NuGet is it possible to create a package from a few DLLs? There is no visual studio project, just the command line and a couple of pre-compiled DLL files. </p>
  
  <p>Second, assuming that is possible, why do I continuously get the "Assembly outside of the lib folder" warning? I've tried everything I can think of to get associated assemblies to add themselves as references inside of the NuGet package. </p>
  
  <p>My file structure looks like this</p>
  
  <pre><code> Root
     - File1.dll
     - lib
       - File2.dll
       - File3.dll
  </code></pre>
  
  <p>When I tell NuGet to pack it using a .nuspec like this</p>
  
  <pre><code>&lt;?xml version="1.0"?&gt;
  &lt;package &gt;
    &lt;metadata&gt;
      &lt;id&gt;File1.dll&lt;/id&gt;
      &lt;version&gt;1.0.0&lt;/version&gt;
      &lt;authors&gt;thisguy&lt;/authors&gt;
      &lt;owners&gt;thisguysmom&lt;/owners&gt;
      &lt;requireLicenseAcceptance&gt;false&lt;/requireLicenseAcceptance&gt;
      &lt;description&gt;This is some library&lt;/description&gt;
      &lt;releaseNotes&gt;Porting to NuGet&lt;/releaseNotes&gt;
      &lt;copyright&gt;Copyright 2012&lt;/copyright&gt;
      &lt;references&gt;
        &lt;reference file="File2.dll" /&gt;      
        &lt;reference file="File3.dll" /&gt;
      &lt;/references&gt;
    &lt;/metadata&gt;
  &lt;/package&gt;
  </code></pre>
  
  <p>I receive that warning. From what I'm reading, I shouldn't even have to define the references node in any of my projects, as the lib folder items should automatically be added as references?</p>
  
  <p>Does anyone out there understand this NuGet mess?</p>