4

We are using moles 0.94 for some tests in our solution. However, every time it gets first compiled, the build server will raise a couple of warnings:

C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (1360): Could not resolve this reference. 
Could not locate the assembly "XXX.Moles, Version=1.0.0.0, Culture=neutral, processorArchitecture=MSIL". 
Check to make sure the assembly exists on disk. 
If this reference is required by your code, you may get compilation errors.

My understanding is that the build server will try to resolve all the references of the test project before starting to build, and if it cannot find the moles dll under the molesassembly folder (because in the first time, it's empty), it will generate a warning like the above.

But when msbuild starts to build this test project, the mole assemblies will be generated and copied into the moleassemblies folder, so it won't turn into an error.

In summary, for the first time, the build will partially succeed and the next time build will fully succeed.

We are trying not to have any warnings on the build server. Is there any way we can eliminate this warnning on the build server?

chrislewisdev
  • 556
  • 1
  • 7
  • 21
geekysteven
  • 113
  • 1
  • 6

1 Answers1

3

We have all 3rd party assemblies stored in the Assemblies folder in the project's root folder. All 3rd party assemblies used in any of our projects are referenced from this location. Assemblies folder is included in the TFS.

It seems like you are referencing XXX.Moles assemblies from the output folder instead of some common (Assemblies) folder. Try to update your references to use 3rd party libraries from Assemblies folder instead of output folder of your test project.

EDIT: Try to add check if XXX.Moles assembly exists into Reference tag e.g.:

<Reference Condition="Exists('..\molesassemblies\XXX.Moles.dll')" Include="XXX.Moles.dll">
  <SpecificVersion>False</SpecificVersion>
  <HintPath>..\molesassemblies\XXX.Moles.dll</HintPath>
</Reference>
Ludwo
  • 6,043
  • 4
  • 32
  • 48
  • I believe geekysteven is speaking about auto-generated Moles assemblies, which are created DURING the build process, but after the ResolveReferences target occurs in MSBuild, thus the Build Warning. – Nick Nieslanik Jan 06 '12 at 03:53
  • Nick is right, we don't want to check-in the dll. The moles assemblies are auto-generated on the build server. That's why the build server cannot detect the dll at the first time, so it drops warnings but not errors. – geekysteven Jan 06 '12 at 10:02