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

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 428678 Comments
Status Closed Workarounds
Type Bug Repros 7
Opened 3/31/2009 2:42:40 PM
Access Restriction Public


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.
Sign in to post a comment.
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.

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