TFS Destroy – friend or foe?

While everyone else is blogging about VS 2010 Beta 2, I thought it still may be worth publishing this post that talks about VS 2008 behavior (yes, the old release ;). One of the features missing in VS 2005 and added in VS 2008 was destroy command; people wanted to get rid of the source…

0

Disposing of checkin policy

Recently while I was fixing up StyleCop checkin policy, I came across one small not-so-obvious snippet of knowledge worthwhile to share. Any custom checkin policy inherits from PolicyBase, which in turn implements IDisposable. Meaning – if you need to clean up after yourself in your custom policy, Dispose method is the place for that. So…

0

New check-in policy for VSS fans: keywords expanded

One of the much-talked-about missing features of TFS is the keyword expansion feature. You know, the ability to place the template in the beginning of every single file and then have every revision tracked in the body of the file (in addition to tracking in source control history, that is). Personally, I am not a…

0

Every developer must read on PDB files

Usually I try not to repost the links, but in this case just could not; I must recommend absolutely awesome super concise and informative post on benefits of PDBs from John Robbins (author of debugging Necronomicon if you don’t know). And to add what John says in his post, here is the how to source…

1

Work Item customization tidbits: custom controls (part 14 of X)

In one of my previous posts I mentioned that I consider custom controls in WI one of the most complex types of customization to implement. Since I got asked related question let me expand on the topic. Custom work item controls provide a way to implement truly specialized behavior for WI, by writing managed class…

1

Work Item customization tidbits: limits of complexity (part 13 of X)

Today I’d like to talk about WIT customization recommendations that will mostly become applicable as your custom Work Item types increase in complexity. Keep the number of custom fields limited (per TFS server) One can have a maximum of 1024 fields defined per Team Foundation Server (as every field is represented by a column in…

2

MSBuild UsingTask gotchas

One significant drawback of MSBuild UsingTask element is that you must specify exactly the task name you are importing. That is if the assembly you are importing contains 200 tasks, you will have to import them explicitly one by one. And since you probably do not want to do that in every project you author,…

1

Branching off renamed trunk

Recently I got asked a small but unobvious branching question. Suppose you have a folder named FolderName, and for some reason you have renamed it to NewFolderName. All is well, but now you decided you want to create a branch from that folder, and to branch from the version prior to renaming. Due to the…

1

Work Item customization tidbits: (part 12 of X)

In my previous posts I have discussed various bits that are important know before taking on Work Item types customization. Today I’d like to talk more about approaching the whole process. I would like to advocate a conservative approach, since in most organizations (at least in my experience) there are limited resources dedicated to customization,…

3

TFS Administrator chores – space offender strikes again!

In my previous post I talked about management of large files in TFS version control database. Today I’d like to talk about what you can do to optimize space management in work item tracking database. As you know, it is possible to add file attachments to Work Item, with the maximum attachment size of 2Mb…

0