Code Analysis or Check-In Policy for Warnings
I've been doing a bunch of Google searches today trying to figure out how I might be able to raise a violation if somebody tries to do a check-in when there are more than 100 warnings in the solution. Because (as far as I know, anyway) the only object available to you in a check-in policy is the PendingCheckin, I'm finding it difficult to implement this.
Does anyone know how I can approach this? I'm aware that Visual Studio will raise a violation when the number of warnings reaches a certain number, but this number is way too high for us.
I thought of doing it as a Code Analysis policy, but several questions came up with that approach as well. First, in order to write a custom code analysis policy, I have to use th FxCop SDK 1.35, don't I? There isn't a "CheckInPolicy" abstract base class that I can just subclass, is there?