title: Process for Creating and Consuming Nuget Packages
body: <p>I am currently in a situation where our team is creating a nuget package <code>DLL A</code> and consuming that package in an application <code>Application B</code>.  <code>A</code> and <code>B</code> are maintained as separate Git repositories.</p>
  
  <p>Right now my process is:</p>
  
  <ol>
  <li>Make changes to <code>A</code></li>
  <li>Commit and push to prerelease branch(CI is run which generates pre-release package on our Artifactory instance)</li>
  <li>Nuget update <code>B</code></li>
  <li>Consume Changes in <code>B</code></li>
  </ol>
  
  <p>While nothing in this process takes terribly long, it does add up over time.  Previously <code>A</code> was part of the solution of <code>B</code> and we could just use project references to quickly iterate.</p>
  
  <p>My question is, is there a better way to approach this process for creating and consuming Nuget packages?  I would like this to work for multiple team members who each have their development folder structure setup the way they like it. We have considered using local nuget packages, but I am unsure how to set that up so it works for everyone on the team consistently (and that still requires manually updating <code>B</code>'s nuget packages).</p>
  
  <p>I am using Visual Studio 2015 Update 3 with projects that all target .net 4.6.1. Mainly I am working with Class Libraries and WPF Applications that use nuget package.config to manage nuget references.</p>