Team Foundation Server (TFS) continues the long Microsoft tradition of horrible source control. It’s getting more annoying every day working with proprietary tools where some corporation decided how I should get my work done. Or in this case, not get my work done. TFS works, for the most part (which is more than you can say for Visual SourceSafe, its predecessor). But if you have a large number of shared projects under one directory, don’t even think about grabbing just one of them. Awesome. Here’s why…
If you try to map the top-level TFS folder to a local folder, you can either grab everything (to make it happy), or uncheck the recursive box. But once you do that, subdirectories are “cloaked”, meaning you can’t do anything with them. Stupid.
You can set the top-level TFS folder to recursive, and then avoid doing a subsequent get. But you’ll have to be careful NEVER to do a get from that folder, or you’ll end up hearing a huge sucking noise as it pulls down everything.
But I ended up grabbing everything in the top level folder. It was the least painful way to proceed.
But that gave me more headaches, running into the <256 character limit on path name. You must be kidding - I HAVE to grab a huge source tree, and it CAN'T have more than 256 characters total in the path. Nice job M$. So I had to remap the base folder to an extremely short name. This leads many of my coworkers to use a common shared directory under [c:\] for code - the opposite of what you want when using source control. Joy. Man it's nice to use open-source software that's actually controlled by the people that use it.

Leave a Reply