title: Visual Studio "project" reference synchronization problem
body: <p>I'm not really sure how to phrase my issue, so I hope this isn't a repeat.</p>
  
  <p>The problem I'm seeing is with Visual Studio 2008.   When I directly reference a project within my solution, I notice that the dependent reference occassionally gets out of synch, and my top-level project ends up holding on to an old build of the DLL  (most obvious in the fact that my break-points are no longer being hit).   I would expect behavior like this if my reference was DLL-based, but I thought reference the project directly was supposed to avoid these synchronization issues since the projects are built in tandem as part of the solution.</p>
  
  <p>If I manually change the version number of the dependent project, that seems to force a reference update and correct things, or of I rebuiild the dependent project, then "clean", and rebuild the entry point project, the references seem to synch up, so I do have a workaround.  In the past, though, I never really noticed this problem; a full rebuild of the solution usually kept everything synchronized in one easy step.</p>
  
  <p>It took me a little while (and a good deal of frustration) to determine the nature of the problem, and since it's been sporadic, it's taken me even longer to realize that it's more than just a fluke.  all that to say, I can't quite pin point what's changed between the time things worked well, and now.</p>
  
  <p>I have done the following fairly recently, so I was hoping to pick y'alls brains to see if there were any known issues (and/or a simple fix) related to any of these things.</p>
  
  <ul>
  <li>Upgraded (debatable adjective? :) ) my OS from XP to Windows 7</li>
  <li>Upgraded from 32-bit to 64-bit processor (my OS change reflected this as well...32bit XP -> 64bit Win7) </li>
  <li>Installed Visial Studio 2010 Express alongside my 2008 version.</li>
  </ul>
  
  <p>I'm running Visual Studio 2008 w/ SP1 (v 9.0.30729.1)</p>