title: Efficient development workflow with Nuget?
body: <p>Nuget is a great tool but it seems to complicate the common process of iteratively modifying libraries and the hosting application at the same time.  </p>
  
  <p>For example, in the application if we have the app itself and 5 Nuget packages and we want to start changing three of the Nuget packages.  There seems to be limited efficient options.</p>
  
  <p>Scenario 1:
  Load up 4 copies of Visual Studio (one for the app and one for each of the packages), modify the packages, wait for packages to be built, update, modify host, build, rinse and repeat.</p>
  
  <p>Scenario 2:
  In the main app, rip out Nuget dependencies and add in proj files and iterate efficiently.  However, then once you are happy with the packages, the solution/proj files need to be repaired (Nuget restored, etc).</p>
  
  <p>What are we missing here?  In the open source world, this is a snap.</p>