I'm evaluating TeamCity for my company, and I'm also new to MSBuild (i.e. I've got about one day's experience :)).
In my MSBuild file I've got the following:
<TestAssemblies Include="$(TestsDir)\*\.Tests.exe" />
Is it possible to specify the .nunit file that has a list of the test assemblies, rather than specifying them as an item group? If that's the case, I can get rid of the TestAssemblies ItemGroup.
Currently my build is failing (silently) because the NUnit launcher seems to die. I get the following message in my log file:
Using "NUnit" task from assembly "C:\TeamCity\buildAgent\plugins\dotnetPlugin\bin\JetBrains.BuildServer.MSBuildLoggers.dll".
C:\TeamCity\buildAgent\plugins\dotnetPlugin\bin\JetBrains.BuildServer.NUnitLauncher.exe "@@" C:\TeamCity\buildAgent\temp\buildTmp\tmp42D.tmp
The "NUnit" task is using "C:\TeamCity\buildAgent\plugins\dotnetPlugin\bin\JetBrains.BuildServer.NUnitLauncher.exe" from "C:\TeamCity\buildAgent\plugins\dotnetPlugin\bin\JetBrains.BuildServer.NUnitLauncher.exe".
Failed to initialize log4net Process performance counter is disabled, so the requested operation cannot be performed.
at System.Diagnostics.NtProcessManager.GetProcessInfos(PerformanceCounterLib library)
at System.Diagnostics.NtProcessManager.GetProcessInfos(String machineName, Boolean isRemoteMachine)
at System.Diagnostics.ProcessManager.GetProcessInfos(String machineName)
at System.Diagnostics.Process.EnsureState(State state)
Process exit code: 0
Does anyone know what's going wrong here? Also, why doesn't the build fail when this happens (i.e. why is the exit code 0)? I can run nunit using an exec statement fine, but obviously that's a pain because it doesn't integrate with TeamCity.