Wednesday, September 08, 2010
 

Search
Latest entries in the Euricom Team blog
Apr 15

Written by: Euricom
4/15/2009 7:21 PM 

When a CI build or full build has code coverage enabled, you could get some build warnings in the build log. These warnings won't break the build, but they do make life harder when someone would want to review the buildlog.

One of these build warnings is this one:

TESTTOOLSTASK : warning VSP2013: Instrumenting this image requires it to run as a 32-bit process. The CLR header flags have been updated to reflect this.

This warning is caused because of the target platform specified in the project build properties. By default the target platform is AnyCPU. Because code coverage data can only be obtained for 32-bit assemblies, the build also generates the above warning. This warning means that the assembly has been recompiled with the x86 property applied for the purpose of obtaining code coverage data during this test run. To avoid this warning, compile any assembly for which you want code coverage data with the x86 setting.

If your application is meant to run on both 32-bit and 64-bit computers, remember to recompile it using the AnyCPU setting after testing has completed.

For more information see:
Troubleshooting Test Execution
http://msdn.microsoft.com/en-us/library/ms182478.aspx

How to: Set Build Properties
http://msdn.microsoft.com/en-us/library/027febhz.aspx
 
By Kurt Torfs, .Net Solutions Architect

Tags:

Your name:
Your email:
(Optional) Email used only to show Gravatar.
Your website:
Title:
Comment:
Add Comment   Cancel 
Copyright (c) 2010 Euricom ::Terms Of Use::Privacy Statement