title: Using NuGet when developing several dependent projects locally
body: <p>The problem I want to solve is how to work with NuGet on several local projects  that depend on each other without having to copy files around manually and have all sorts of dll issues as a result.</p>
  
  <p>Today my projects (c#) are not using NuGet (working to move them to NuGet), and the way it works is that when working locally all projects build outputs to a "shared bin folder" and all reference from there, so that you alway see the right binaries you are building locally.
  On the build server, through some games in the csproj files, projects reference a non-shared bin and get the dependencies there.</p>
  
  <p>How can I achieve the same effect with NuGet? What is the right way to work locally without having to copy dll around manually? (And of course keep the ability to build in the server by getting everything using NuGet normally)
  Is there a way to get packages to one bin folder with NuGet or at least folders without version numbers so I can just build and reference from there? And is this even wise?</p>
  
  <p>Assume the latest NuGet, VS versions as required.</p>
  
  <p>Thanks a lot for your help,
  Roy.</p>