0

I recently inherited a large solution containing a lot of suppressed messages in its code base.

Waiting to simply run across each of these messages one by one as I happen to touch parts of the code is a terrible way of handling all of these suppressed analysis errors.

While there is a small amount of suppressions that are considered valid (such as in auto-generated code files) most are needing to be fixed.

Is there some sort of plug-in or process through TFS that anyone can recommend as far as managing these code analysis issues in an efficient manner?

obizues
  • 1,473
  • 5
  • 16
  • 30
  • Which version of Visual Studio are you using? – Nicole Calinoiu Oct 19 '15 at 15:26
  • Visual Studio Enterprise 2015, Version 14.0.2107.0 D14REL – obizues Oct 19 '15 at 17:09
  • Unfortunately, there's nothing out of the box in that case. However, there are a few approaches you could potentially take. It would be easier to suggest something if you could elaborate a bit with regards to what you mean by "managing" the suppressions... – Nicole Calinoiu Oct 20 '15 at 01:32

1 Answers1

0

You can use the /property:WarningLevel=0 MSBuild argument to suppress all build warnings. Open build definition, go to Process -> 2.Build -> 5.Advanced -> MSBuild argument. Check my reply in this link: MSBuild Defintion - Suppress Warning Messages for Specific Solutions

Community
  • 1
  • 1
Vicky - MSFT
  • 4,970
  • 1
  • 14
  • 22