The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
I'm from such a bad year that I was not even invited to join the Dutch army, that was a big disappointment to me, but now I think it was probably for the best.
Played a lot of Battlefield1942 to compensate
Correct. We have a wonderful woman at work that took TFS training. Just yesterday, we asked her why one of our devs wasn't seeing my latest code commit. After some fussing, she suggested restarting Visual Studio and doing a "get latest" again. Yup, that solved the problem.
She actually is incredibly knowledgeable about TFS, this was one of those "tool flukes."
Compared to tools like SmartGitHg, the UI is incredibly klunky. OK, granted it integrates with the task management / work ID BS that the company uses, which is more incredibly klunky UI implementation, and nobody uses it anyways except to create work ID's and supposedly track amount of work done on a task, which nobody keeps up to date anyways.
So, yeah, there again, I'm complaining more about processes than the tool itself. But still, the UI and UX is so much more inferior than what I experience using SmartGitHg.
a, but ALL tools have some issues. I've used TFS before, and aside from it's hideous web UI, the source control portion VS integration seems to work OK.
Any concrete reasons to NOT use it?
No, there are no concrete reasons NOT to use the thing. TFS works fine. Like any complex system it requires some administration. You're going to get the same response from the development community that you'll get any time you ask them what the best text-editor or compiler is. The latest "fad" among developers for this kind of thing is GIT. You're probably in a shop that has TFS and all the cute answers telling you to switch to GIT are as productive as all the "switch to Linux" crap. All you asked for was books on the subject.
Go to APress.COM and search the titles there. You'll find several pertaining to TFS so you can learn what you need to know.
The fact that there's no stand-alone tool for checking in/out code, the VS UI's (I'm usually spending minutes fussing with the include/exclude trees) sucks, and, while not TFS's problem per se, our network and the server hosting TFS is so slow that it can literally take a couple minutes to add a file to a solution. And "Get Latest?" That's usually a couple walks around the facility and it might be done when you get back if you're lucky.
These are all issues with your setup. Where I work, a couple of minutes is how long it takes me to get the entirety of our main project -- a million lines of source code spread across a few hundred files.
And there is a standalone tool (Team Explorer Everywhere). I chased it down when I was doing Linux development on some of our C# code. It's not very friendly, but it's there. I ended up not using it.