Top posts
Latest articles
Searching in TFS history, made easy by Microsoft
(No Ratings Yet)
Loading ...One of the greatest things about version control systems is the ability to keep track of changes. Or is it? Well Microsoft certainly has a unique look on this. Team Foundation Server (TFS), also known as the Team Failure Server, has a very unique way of keeping track of changes.
To be honest the tracking of changes works fine, for the most part. But what happens when you made a change sometime in the past, you know roughly what you did but not which files were affected or which branch was used. Yes I sometimes don’t know what version (branch) of the software a fix was made in. In any normal version control system you would open up the history log and start searching for a comment you entered. That would result in some result popping up, and with any luck the change-set you were looking for.
Alas Microsoft in all its wisdom decided that searching is overrated and not needed for a version control system. After all you can read through the entire history log to find the change-set can’t you. Ah you can’t, silly you!
Here is a quick work around for this ‘missing’ feature:
- Open up the History view on the ROOT of the TFS server
- Scroll all the way down, in most systems that will be just a few thousand change-sets
- Select all and copy
- Open Excel and paste
Voila now you can search. At least Excel offers a way to search your Team Foundation Server history.
Why Team Foundation Server is useless for Java
In the company I’m currently working for we are using the Team Foundation Server as a version control system. No for developers of C# or any other Microsoft related programming language this is probably fine. However being a Java developer TFS is less then perfect. In fact it is a near nightmare.
We are using various IDE’s for editing our Java projects, meanly because different developers like different IDE’s. Personally I’m using Netbeans, which has perfect Subversion, Git, CVS and Perforce support. Some other developers use IntelliJ from Netbrains. Which is sorta expensive and the version we are using has no support for TFS at all.
So when I want to edit a simple file I first locate it in my IDE, which takes me about 5 seconds. Then I need to look up its location on disk, followed by opening the completely useless Team Exporer. Then I again need to look up the file in TE, followed by a check-out. The whole process to the point that the file is checked out and ready to go takes probably about 1 minute, each and every time.
On an average day I probably waste up to an hour checking out files, and commiting them back into the version control system.
To ease the burden a bit I’ve tried the SvnBridge tool to link my IDE’s Subversion system with TFS, but this tool has many flaws. Just a few of which are:
- No longer appears to be developed
- A merge in TE causes all updates to fail, you need to do a clean checkout again
- Random update failures due to commits of other developers
So for now I’m stuck. Really, really, really stuck.
