‘Get latest’ cannot be trusted, ever. It just does not work, which is pretty bad for a source control product. ‘Get specific version’ is fine though.

Performance can be crappy, both on check-in and check-out, with no clear reason why.

Any other problems are really just due to the way it is integrated into studio (single source provider, usual ‘add to source control’ issues).

Oh, and one time I totally lost all changes to a project for the last 3 months..dunno why!

“One option could be just to always keep everything checked out, and use the multiple check-out option.”

With this model in TFS, are you still forced to checkin files which you never changed despite their being checked out under TFS? This would create a lot of churn under the version history wouldn’t it?

I’m hoping to find a way around this, but at the moment this seems like a huge flaw in the TFS model. Although it’s a remarkable improvement over VSS, I don’t consider that a very high bar to have bested.

If you have ideas here I’d welcome the feedback!

My team has struggled with files not checked in, files not getting out, and changes done outside of vs not detected at all.

And please note that TFS to me is as seen from inside of Visual Studio.