Cannot eliminate warning VSP2013 when Code Coverage is enabled in TeamBuild builds

Cannot eliminate warning VSP2013 when Code Coverage is enabled in TeamBuild builds by NathanB

Closed

as Won't Fix Help for as Won't Fix

Type:	Bug
ID:	428678
Opened:	3/31/2009 2:42:40 PM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

We would really like to have warning-free builds, as it is very difficult to remember "how many warnings are good".

Our last remaining warnings are VSP2013 when running TeamBuild (either on the build machine or DesktopBuilds using msbuild) builds that have tests with Code Coverage enabled. There doesn't appear to be a reasonable way to get rid of this warning.

What I'd like is a way to pass arguments to vsinstr.exe (in this case "-nowarn:2013"), but there doesn't seem to be a way to do that in TeamBuild.

Details (expand)

English

Visual Studio 2008 SP1

Windows Vista

English

Create a TeamBuild build

Include tests (we use the <TestContainer> mechanism if that matters).

Enable Code Coverage.

For each DLL listed in the <TestContainer> ItemGroup, we get the following warning:

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.

No warnings.

0 attachments

Posted by Microsoft on 6/16/2009 at 3:05 PM

Hi Nathan,

At the moment there is no plan to fix it in the current release. This may be addressed in future products.

Thanks
Visual Studio Product Team

Posted by Microsoft on 3/31/2009 at 10:32 PM

Thanks for your feedback.

We are escalating this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Thank you,
Visual Studio Product Team

Posted by djellison on 10/4/2009 at 7:24 AM

I encountered this problem as well. My workaround is as follows:

1) Open the project properties of the assembly you are instrumenting.

2) Go to the Build tab.

3) Make sure the combo configuration selection is set to the Debug (or equivalent) configuration.

4) Set the "Platform target" to x86.
Note: This sets the assembly to be compiled specifically as 32 bit but only the debug assembly so you do not alter the output of your production, deployment assembly.

This will remove the warning when you are performing code coverage on the debug version of your assembly.

I hope this helps you or anyone else out even if the issue is a bit old (and closed my Microsoft).

Dave Jellison
http://djproduct.blogspot.com/

Posted by Ewald Hofman - TFS Product Team on 1/25/2011 at 11:08 PM

http://blogs.msdn.com/b/haniatassi/archive/2009/02/04/getting-rid-of-warning-vsp2013-in-msbuild.aspx