2

I've got a VS/TFS2010 project in which we use a generated file. Here's how it works:

  1. There's a pre-build event that creates the file (foo.cs)
  2. The file is included in the project.
  3. The file is NEVER added to TFS version control.

It works great, except... People have an unfortunate habit of accidentally checking in the file. This, of course, breaks the system.

Are there any good ways to prevent this from happening? Can I at least set up some kind of watch mechanism to alert me if it does happen?

dbc
  • 104,963
  • 20
  • 228
  • 340
Stephen Gross
  • 5,274
  • 12
  • 41
  • 59
  • If the file is never added (pended add?) to TFS Version Control, how can someone accidentally check it in? – Duat Le Jan 19 '12 at 18:37

2 Answers2

3

You'll need to install the Team Foundation Server Power Tools, which will include the "Forbidden Patterns" check-in policy. This will allow you to prohibit a file from being checked in based on regular expression applied to the server path.

This will allow you to simply add the full server path of the file you wish to ensure does not get added. For example:

^\$/TeamProject/Folder/foo\.cs$
Edward Thomson
  • 74,857
  • 14
  • 158
  • 187
1

I was researching this exact issue today and found this, which may be of some help: How to ignore files/directories in TFS for avoiding them to go to central source repository?

Not sure if 2010 has made this easier or not.

(Apologies, this should probably be a comment, but I don't think I have enough rep to comment.)

Community
  • 1
  • 1
pamphlet
  • 2,054
  • 1
  • 17
  • 27