Team City failed build - NAnt and MSBuild pass the exact same build

I have just started to get to grips with Team City and am very excited so far, after using for the last 6 months.

Hi, I have an issue where a build of a .sln file works fine over the msbuild command line and also using NAnt over the command line.

Running the exact same build through TeamCity causes it to fail with:

Namespace or type specified in the Imports 'MbUnit.Framework.Reflection' doesn't contain any public member or cannot be found. Make sure the namespace or the type is defined and contains at least one public member. Make sure the imported element name doesn't use any aliases.

The reference is located at C:\ProgramFiles\MbUnit\MbUnit.Framework.2.0.dll and exists fine when I open the solution file.

I had previous been using the NAnt.contrib task but switched to the TC preferred mark up with no joy.

I'm sure this will be an easy one to pick up, but at the moment I just can't figure out where the differences may lie in the build.

Thanks in advance,

1 comment
Comment actions Permalink

Could you please check the user account for TeamCity build agent service. That should not be SYSTEM.

Do you use GAC for MSUnit assemblies, if so, please make sure MBUnit is installed on the build agent machine.

Please make sure there is no assembly binding redirect or version missmatches somewhere near MBUnit assemblies.



Please sign in to leave a comment.