title: Handling .dll not in GAC moving between DEBUG and Release
body: <p>Ok, I have had a good look and found nothing useful on this problem.
  I have a solution in VS (Visual Studio). It has two projects say ProjectA and ProjectB. </p>
  
  <p>ProjectA creates <code>A.dll</code>. 
  ProjectB creates <code>B.EXE</code> which references <code>A.dll</code>.</p>
  
  <p>In DEBUG mode everything works correctly as you would expect. However, in release mode the files are moved to where they will be located when installed. The <code>A.dll</code> will not be installed in the GAC. Because the <code>A.dll</code> is not where it is expected to be in relation to <code>B.EXE</code> the exes fail. Reasonable enough.</p>
  
  <p>In the After Build Event I copy the .exes to <code>c:\los\</code> and <code>A.dll</code> gets moved to <code>c:\los\libs\</code> </p>
  
  <p>Currently I have to de-reference the <code>A.dll</code> and then re-reference it now pointing it to it's new location, rebuild and then the release version works. The real solution has a lot of projects and a great number of .dlls which means I can easily (and do) forget to re-reference new .dlls regularly.</p>
  
  <p><strong>Is there a way to automate this tiresome process?</strong> </p>