Hi all,
I have a solution that contains multiple webservices. I have code coverage turned on and everything works great when building local. When building with team build we get the following error.
The Code Coverage Analysis Service could not analyze the code coverage data for build IBS 1.1 Master Build_1.1.0.34 (Mixed Platforms/Debug). This is frequently caused by publishing different versions of the same binary to a particular build.
Processing of code coverage data from run tfsservice@CTSHELNT04 2007-01-05 10:59:47_Mixed Platforms_Debug caused the following exception to be thrown:
Error when creating coverage info: Module App_Code.dll version mismatch when aggregating coverage data. Check for out of date copies of this module
I see that the problem is with msbuild confusing the multiple App_Code.dll's that exist in the different webservice folders. When I turn off all code coverage except for one webservice, All works great!
Any ideas how to get past this....I would like to code coverage all webservices during the automated build.
Thanks
-Ken

Error when creating coverage info: Module App_Code.dll version mismatch
Tryin2Bgood
EnigMa_AnGeL
Ken,
Unfortunately, the technology we use in VS Code Coverage heavily relies on the binary names to determine the statistics and the merged results. The problem is that ASP.NET uses the same name AppCode.dll and this breaks our logic. I am afraid that the only way to work around that is to force the MSBuild/ASP.NET to use a separate output file name for each web site. I myself am not familiar with the ASP.NET web configuration properties, but I would assume that there is a way to control the output from there.
Regards,
Boris
Porko
Sorry for the delay Ken - we're still looking into it! I tried it out with the current version of all our bits, and a similar issue still repros...
One possibility for working around this problem would be to use the Web Application Project add-in, rather than the built in Website projects. You can find info on these projects here: http://msdn2.microsoft.com/en-us/asp.net/aa336618.aspx. The main advantage from your perspective is that all code files from the entire project are compiled into a single, named assembly (i.e. not App_Code.dll).
-Aaron
magicalclick
Any chance you are having the same issue discussed in this thread: http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=576361&SiteID=1
-Aaron
RajDas
I've asked somebody on the VSTS Test team to have a look at your post - hopefully we'll have some sort of answer for you in the near future.
-Aaron
MShetty
This is a real issue....Can anyone on Team Build can look into this
The scenario is that you have one solution containing multiple projects and multiple web services. All web services have tests. The testrunconfig code coverage is turned on and all assemblies (Not Test assemblies) are selected. I select one web service for coverage. It all works great!
I need to turn on coverage for ALL six web services in the solution and I can't. When I turn on code coverage for ANY of the other web services I get the following error:
The Code Coverage Analysis Service could not analyze the code coverage data for build IBS 1.1 Master Build_1.1.0.34 (Mixed Platforms/Debug). This is frequently caused by publishing different versions of the same binary to a particular build.
Processing of code coverage data from run tfsservice@CTSHELNT04 2007-01-05 10:59:47_Mixed Platforms_Debug caused the following exception to be thrown:
Error when creating coverage info: Module App_Code.dll version mismatch when aggregating coverage data. Check for out of date copies of this module
Code Coverage really seems to be broken when trying to test multiple Web Services in the same solution. Team Build can't differentiate between the DIFFERENT App_Code.dll's within the separate web service folders.
Thanks for any help (or confirmation that this is broken)
-Ken
seco
Sorry that isn't the problem at all....I know better then to select the Test Assemblies to run coverage on.
My problem happens when I select multiple Webservices to perform coverage on within the same testconfig. Code coverage won't work because of the multiple App_Code assemblies and their different time stamps.
Coverage thinks they should all be the same version when it really doesn't matter because they are separate projects within the master .sln.
I hope this explains the problem a little better
-Ken
Alex Yakhnin - MSFT
Thanks for responding guys....We are looking into how to solve the problem.
I will post back when we have it solved.
-Ken
simon_56387
Hi Aaron,
Any word from that group It really seems like a bug on Microsoft's end.
-Ken