Anyone using Team Foundation Server?

[keyboardlover]

We are switching to it (for everything) starting today. I'm hoping it's going to go well.

If you've been using it for some time, I'd love to hear your thoughts.

I will miss Subversion. We'll still be using CruiseControl.NET for the time being for the automated builds.

[poxeclipse]

We are switching to it (for everything) starting today. I'm hoping it's going to go well.

If you've been using it for some time, I'd love to hear your thoughts.

I will miss Subversion. We'll still be using CruiseControl.NET for the time being for the automated builds.

We switched from VSS. It's ok, especially for managers.

[Soarer]

Been a user of it for a couple of years now. (Admin is SEP).
Definately not as nice as Subversion, but miles better than VSS.
If you work 'offline', watch out for it not finding all your changes when you go back online - it ain't clever :-(
If you work 'online', it automatically checks files out all the time, which I find annoying - it's uneccessary FFS! Especially since (in VS) it 'helpfully' tells you if the file has changed since you got your copy, which tabs away from a more interesting panel (find in files, for example).
The only purpose of checking-out files (without locking) seems to be to show others how busy you are ;-)
Get the power tools.

[keyboardlover]

Does shelving resolve that issue? My team plans to use shelving extensively.

[Soarer]

Well, I haven't used shelving much, but I don't think it addresses either of those issues. I've used it to dump changes up to the server so I can fetch them to another location and carry on working - in that sense it's sort of an alternative to making a branch. (I assume it's possible to share a shelveset, but it would be awkward compared to a true branch). And maybe I used it once to put some work to one side, then fix some other bug and commit, then continue with the shelved work - but TBH that's rare with the way I tend to code. I think other coders at my work make more use of it for that, but they also tend to break stuff when they eventually commit their 'big' changes to the trunk :-/

[keyboardlover]

Well, amazingly it was a non-issue event. Hopefully it will prove to be a good tool this year.

One annoyance is that selecting a workspace doesn't auto-switch your 'code perspective' to that workspace. You have to select the workspace and THEN remember what part of the code it's mapped to and THEN drill down to it. In subversion this was much simpler. Oh well.

[Soarer]

Yeah, just annoyances really. Of course it's not as groovy as git, but it seems to be pretty stable and reliable.