title: Use source control history with nDepend to create trend
body: <p><em><strong>We would like to pick points in time in our source control (git) to generate trend metrics.</strong></em></p>
  <p>We are working through a trial of nDepend to determine its value for our large, 15+ -year-old code base.</p>
  <p>The steps taken so far are:</p>
  <ol>
  <li>Checkout a given changeset</li>
  <li>Build/analyze</li>
  <li>Go to 1 until all selected changesets have been analyzed</li>
  </ol>
  <p>The problem that we're seeing is that each time the code is checked out, it is a fresh start, including the nDepend configuration. As a result, we have a series of analytics sets that are completely independent, no trend across them.</p>
  <p>Is this something that can (easily) be done?</p>