Locks based on file types (extensions) and shelving

Developing MSBee - Part 8

Geek Runs Through My Veins — Thu, 01 Jun 2006 23:10:43 GMT

I hit another TFS snafu on Tuesday which I thought I'd share. MSBee has a unit tests project which currently...

re: Locks based on file types (extensions) and shelving

Tommy — Fri, 25 Jul 2008 16:52:39 GMT

I just ran into the same thing. Although locking a file could be a good thing in some situations, its usually bad. Plus, why can't I unlock my own 'locks'. I have to get on that certain workspace and unlock it. That seems simple enough, until you find out that the workspace is limited to the computer it was created on, so if you have a workspace on a home machine and your at work, well, your outta luck!

For as much as TFS costs, I think its pretty terrible. I would much rather use SVN and an issue tracking system like Trac then this piece of garbage that cost mucho dinero.

re: Locks based on file types (extensions) and shelving

buckh — Thu, 31 Jul 2008 05:05:57 GMT

You can unlock files you've locked on a remote machine using the lock command, unless the lock is due to being in the file extension list.

I'm curious to know what has brought you to the conclusion that TFS is terrible.

Buck

re: Locks based on file types (extensions) and shelving

Tom — Thu, 26 Nov 2009 12:05:15 GMT

I agree with Tommy. Specific points:

Why can't TFS tell me what files I've changed without contacting the server? Every other source control system on earth can do this.

Why does TFS tell me 'All files are up to date' when I say 'Get Latest' even if I've changed files locally? I understand that editing without checking out does not really fit into the TFS model, but the message is just plain wrong. Which brings me to my next point...

Why doesn't TFS support edit-merge-commit? Every other source control system supports this. Even sourcesafe had a workaround to make it work.

Why does TFS complain about merge conflicts when merging a branch back to the trunk when only one of them has changed? Just plain wrong.

Why can't someone else unshelve a shelfset that contains binary files unless I undo the changes in my workspace first? Providing shelfsets and thinking that people are not going to use them for reviews is delusional; requiring that I stop working on something before someone reviews it is just wrong.

If my workspace has one TFS path checked out inside another TFS path, why can't TFS figure out that I don't want the subsidiary path to show up in comparison results? Or, even more usefully, compare the subsidiary path to its server location?

Why doesn't the "tree compare" tool present the comparison results as a... erm.. tree? Like, so I can collapse parts of it I'm not interested in? Only a UI thing, I know, but easily the most annoying thing about working with TFS.

Why do the commit notification emails include hyperlinks to completely useless pages that won't show me the changes in the changeset?

Some of these are alleviated by binding a VS Solution to the TFS server, but then why does it take VS over a minute to figure out that I'm not connected to the network any more when I take my laptop home?

Why can't I move multiple files? Why do I have to select each one individually, right-click, select Move, put the new path in? Drag-and-drop is far too new a concept for TFS, apparently.

The list goes on, rather, I'm afraid. These are the ones that have annoyed me in the last day or so.