title: Creating one NuGet package from multiple projects in one solution
body: <p>I have a solution that I'm working on that contains 4 class library projects (<code>A</code>, <code>B</code>, <code>C</code>, <code>D</code>). <code>A</code> and <code>B</code> could be considered the top level projects in the solution. Both <code>A</code> and <code>B</code> reference <code>C</code>, and <code>D</code> stands alone.</p>
  
  <p>These four projects represent a group of services that I have made that handle an automated workflow. They are all closely related, and will only be used in one location (the service manager) so I don't want to split them into different solutions.</p>
  
  <p>My problem is that I want to create a single NuGet package that will contain all 4 libraries, without having to build them all and gather up their DLLs manually. I know that I could technically achieve this by having either <code>A</code> or <code>B</code> reference the remaining projects, but that's not a true relationship and I feel it should be avoided.</p>
  
  <p>I've done a lot of searching on this problem and I can't find a solution other than manually collecting the DLLs and building the package myself. Is there a way to achieve the result that I want using NuGet's features/abilities?</p>
  
  <p><strong>NOTE</strong>: In case the tags don't make it clear I'm currently using VS2010 with a TeamCity build server. In case it's relevant I'm also using Git through a Stash server.</p>
  
  <p><strong>EDIT</strong>: I just realized this might be important enough to mention. These projects do reference other NuGet packages that I will need to mark as dependencies.</p>