title: Merge code changes without true source control
body: <p>We have a few developers working on the same VS2005 solution, but our source control is very bad.  (Our company uses Harvest, which we give a vote of no confidence).</p>
  
  <p>Right now, we're all just working off of the files on a shared lan drive.  Obviously, this causes some problems. But we think it's better than working locally, and tracking the files we touched in a spreadsheet and merging everything manually.  Does anybody have a strategy for merging our changes?</p>
  
  <p>Some of the problems exist because of corporate beaurocracy (like mandating Harvest).  Those same policies prevent introducing new tools into our environment.  So, strategies that avoid buying/downloading new software would work best for us.</p>