Ask a questionAsk a question
 

AnswerRestricting Code Analysis Errors Suppression

  • Tuesday, November 03, 2009 9:48 AMPavan Kulkarni Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi All,

    We do Code Analysis for our solution in VSTS. And of course, we suppress few errors as applicable. However, at this point anybody from my team (senior or junior) can suppress errors. Is there any way that I can restrict as to who can suppress?

    Thanks in advance,
    Pavan

Answers

  • Tuesday, November 03, 2009 12:51 PMNicole Calinoiu Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Not without restricting who can commit source files within your project/solution.  Rather than attempting to restrict creation of suppressions, you may want to consider reviewing them on a regular basis.  While you could use Visual Studio's "find all references" functionality for this, the stand-alone version of FxCop offers a somewhat more convenient presentation of the suppression list, as well as detecting which suppressions are not required any more.

All Replies

  • Tuesday, November 03, 2009 12:51 PMNicole Calinoiu Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Not without restricting who can commit source files within your project/solution.  Rather than attempting to restrict creation of suppressions, you may want to consider reviewing them on a regular basis.  While you could use Visual Studio's "find all references" functionality for this, the stand-alone version of FxCop offers a somewhat more convenient presentation of the suppression list, as well as detecting which suppressions are not required any more.