Check Only Projects X, Y, Z


The code comment checking policy currently checks all source code files that are being checked in based on a rather simple logic inside method CCCPTfsPolicy::IsVerifyableFileType.
However, it would be desirable to exclude certain projects from checking. The reasoning is that class libraries are a good candidates for checking proper code commenting, whereas eg a quick-and-dirty VB Winforms frontend checked into the same team project doesn't need code comments at all.
Things to be evaluated: is there a way in the checkin policy to find out which file belongs to which project? Or would we need to track this based on directories and mapped workspaces?
Closed Jul 19, 2007 at 3:00 PM by ChristophWille
Implemented as "Included Paths" feature in v2.1


RyanHaney wrote Feb 2, 2007 at 2:56 AM

This is a GREAT idea. We currently get warnings from FX-Cop but this doesn't preclude us from checking items into TFS, which should be a policy. Our commenting goal is only aligned with custom framework related libraries, as multiple programming groups within our organization use it. 10 votes from me!

wrote Jul 19, 2007 at 3:00 PM

wrote Feb 14, 2013 at 12:43 AM

wrote May 16, 2013 at 4:55 AM