title: Using build with TFS2010 on projects that use moles assemblies fail with -1002 as cannot resolve reference
body: <p>After much playing i have managed to get TFS to be able to run builds on all of my projects except the test projects. These have a moles assembly in them.</p>
  <p>The errors i am getting are</p>
  <blockquote>
  <p>C:\Program Files\Microsoft Moles\bin\Microsoft.Moles.targets (79):<br />
  The command &quot;&quot;C:\Program Files\Microsoft Moles\bin\moles.exe&quot;<br />
  @&quot;C:\Builds\2\cv2\DevBranchBuild\Sources\CV.BL.Tests\obj\Release\Moles\moles.args&quot;&quot;<br />
  exited with code -1002.</p>
  </blockquote>
  <p>The warning is</p>
  <blockquote>
  <p>C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (1360):<br />
  Could not resolve this reference.<br />
  Could not locate the assembly &quot;CV.DAL.Moles, Version=1.0.0.0, Culture=neutral, processorArchitecture=MSIL&quot;.<br />
  Check to make sure the assembly exists on disk.<br />
  If this reference is required by your code, you may get compilation errors.</p>
  </blockquote>
  <p>CV.DAL is the assembly i am moling.</p>
  <p>I am using the latest version of pex and moles.</p>
  <p>I also have the <code>CV.DAL.moles</code> file checked into TFS (not the assembly).
  Everything builds perfectly fine on my local machine. The machine I am using to do the builds has exactly the same configuration. By exactly I mean that one is 32 bit and the other is 64 bit :o (serious oversight there).</p>
  <p>Any ideas?</p>
  <p>This makes pex and moles utterly useless as it is breaking gated checkins when merging branches which is a great shame as i invested a decent amount of time into them.</p>
  <h3>EDIT</h3>
  <p>Which molesAssemblies directories?<br />
  The install folder for moles or the directories under the project?<br />
  The installation folder has he same files and file sizes on both machines.</p>