Code coverage / testing errors in Team Build

I've been trying to get code coverage working from Team Build builds. I read about removing the path from the "binaryFile" tag in the testrunconfig, so I did that -- no dice. Next, I edited the team build file to add "/runconfig:$(SolutionRoot)\localtestrun.testrunconfig" to the TestingArgs element. After that, I got a complaint from the build log, that vsinstr.exe couldn't be found in the PrivateAssemblies folder. I copied from my machine to the server, but obviously that didn't work (so I removed it). The build now fails, with these errors in the testing section:

Run has the following issue(s):
Instrumentation tool VsInstr.exe cannot be found in C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies. Instrumentation cannot continue.
Code coverage in-place instrumentation: The binary e:\Dash911\builds\main\Dash911\Main Build\Binaries\Release\Dash911.Vui.dll was changed during the test run and won't be restored. It may be restored manually from this directory: e:\Dash911\builds\main\Dash911\Main Build\Binaries\Release\EQT_470f966e-d500-4d47-92b5-790fe6dafbe2.
Code coverage in-place instrumentation: One or more binaries in 'e:\Dash911\builds\main\Dash911\Main Build\Binaries\Release' were not restored.
They can be restored manually by running the file 'eqtrestore_470f966e-d500-4d47-92b5-790fe6dafbe2.bat' in this directory.

I didn't find any such .bat files.

Any ideas?

Thanks,
Michael

[1466 byte] By [MichaelGiagnocavo] at [2007-12-16]
# 1

Can you tell what VS SKU you have in your build machine? If you have only installed Team Build SKU then you need to install VSTD, VSTT or VSTS on your build machine to be able to run tests. To publish test results from build machine, your build machine has to have VSTT or VSTS SKUs installed.

Let me know if you are seeing your issues with above SKUs installed in your build machine.

Thanks,
Bata Chadraa

bchadraaMSFT at 2007-9-8 > top of Msdn Tech,Visual Studio Team System,Team Foundation Server - General...
# 2
Aha, that must be it. I just have TFS, Team Client, and Team Build. I'll throw on VSTS (default install I guess) and see what happens. I'm hoping this won't be required for RTM? :)
MichaelGiagnocavo at 2007-9-8 > top of Msdn Tech,Visual Studio Team System,Team Foundation Server - General...
# 3
Installation of VSTT, VSTS or VSTD is required in our current build if you plan to run tests in your build machine and I think it will stay as required install in RTM.

Thanks,
Bata Chadraa

bchadraaMSFT at 2007-9-8 > top of Msdn Tech,Visual Studio Team System,Team Foundation Server - General...
# 4
Will we need a separate license for VS on the server?
MichaelGiagnocavo at 2007-9-8 > top of Msdn Tech,Visual Studio Team System,Team Foundation Server - General...
# 5

Yea, that was the problem. Also, the needed steps: removing the path from the binaryfile tag of the testrunconfig -- that messes up my local machine from running the tests. However, the server needs that. So I ended up with two testrunconfigs.

MichaelGiagnocavo at 2007-9-8 > top of Msdn Tech,Visual Studio Team System,Team Foundation Server - General...

Visual Studio Team System

Site Classified