TFS Check In Policies, Code to Police Code

James Manning's blog : check-in policy to disallow certain patterns (for instance, particular extensions).

"A request that's come up a couple of times is to have a checkin policy help guide developers about certain file extensions that they shouldn't check in to version control. While making a policy with "forbidden extensions" is certainly possible, it's basically the same amount of work to make "forbidden regular expressions" and give more power to the user - extensions are just a subset, like "\.tmp$" for "don't check in any files end in .tmp".

…"

I think it’s pretty cool that TFS Check In policies can be created by writing code. Allows for a good bit of flexibility doesn’t it?

It just seems ironic, yet appropriate, in some way (code to police checking in of code).

BTW, James’ blog has a number of cool TFS check in policy examples as well as general good poop on TFS.