Code Coverage for website causing team build to stop

Question

Hi,

I'm having problems when I enable code coverage for a web application that is part of a tfs build. The web application has references to other assemblies (eg. ClassLibrary1.dll, ClassLibrary2.dll etc). When I enable code coverage for any assembly other than my web application (eg. ClassLibrary1.dll), everything works fine. But if I also enable code coverage for my web application, the build hangs for a while before eventually stopping and displaying the following message in the last build step: "The build was stopped due to the Visual Studio Team Foundation Build service being stopped."

After examination of the BuildLog.txt, I noticed there were no entires after all tests were executed. I assume this is the point at which it hangs before eventually stopping. I also could not see any exceptions in the BuildLog.txt. So I tried to see if there was anything reported in the event logs on the build server itself and I found several errors similar to the following:

Event Type:    Error
Event Source:    VSPERF
Event Category:    None
Event ID:    1406
Date:        20/08/2008
Time:        10:39:21 AM
User:        N/A
Computer:    VICVMTST44
Description:
There was an error connecting to the Logger Engine while registering D:\WorkingDirectory\TestProject\TestBuild\Binaries\Release\_PublishedWebsites\TestWebsite\bin\ClassLibrary1.dll for coverage.


Event Type:    Error
Event Source:    VSPERF
Event Category:    None
Event ID:    1406
Date:        20/08/2008
Time:        10:39:21 AM
User:        N/A
Computer:    VICVMTST44
Description:
There was an error connecting to the Logger Engine while registering D:\WorkingDirectory\TestProject\TestBuild\Binaries\Release\_PublishedWebsites\TestWebsite\bin\ClassLibrary2.dll for coverage.

...

I also noticed that the build service had stopped and that the 'Default Website' in IIS6 had also stopped (which were both running fine until I ran the build).

Note: The account under which the tfs build service runs has local administrative access.

I'm totally confused as to why this only happens for web application projects. Any help will be greatly appreciated.

Thanks.

Answer 1

This is a known issue and side effect of enabling code coverage on an IIS website in team build. Disabling Code coverage on the website will 'resolve' the issue. You will need to run the test outside of TeamBuild. There might be something logged on Connect regarding this... I'll take a look.

Answer 2

Hello Mike,

I'm having the same issue right now.  Do you know if I can have a fix for VS.NET 2008 ?  Do you know if this issue have been reported to Microsoft ?  Last question do you know if this issue will be resolved in VS.NET 2010 ?

Thanks
Annie

---

bizbiz