Nothing gets my blood boiling faster than any product which automatically tries to make a remote connection without you asking it to.
Team Explorer is integrated into Visual Studio and will try to make a connection to Team Foundation whenever the tab (if you have docked it so) gets focus.
If you *know* you can’t connect to TFS (i.e. you connect via VPN for example) you must wait while the connection times out – and there’s no way to stop it.
It will hang Visual Studio while it attempts to connect and it seriously ticks me off.
When will Microsoft learn that:
a) We’re not always connected!!!!,
b) Things shouldn’t auto connect by default, or at the minimum, give me an option to stop it, and,
c) Loading the Team Explorer tab should be an asynchronous operation – why can’t I do anything else in Visual Studio while it is loading?
Whilst waiting for Team Explorer to time out recently (just now), I came across this little gem:
"You too may have missed this and it’s very handy especially when you are on the move or can’t always connect to your Team Foundation Server.
add a DWORD value called AutoLoadServer under HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\8.0\TeamFoundation and set the value to 0."
Thanks to this article here for the heads up.
By the way, stay tuned for my notes on SQL Data Services (SDS) – coming shortly.
I’ve been evaluating the new service offering and I’ll have something to say about it.
One thought on “Team Explorer #@%$#%”
I know this is an old post, and about an old VS version, but I’m still ticked off by TFS with VS2010 Team Explorer integration.
Since I’ve only been using VS2010, and developing on the MS platform for under a month, I still look at something like TFS and “shake my head”.
The reason? Distributed Version Control Systems. EVERYTHING is local. It’s gets around the “We are not always connected” point.
Read why it’s good having everything local: http://whygitisbetterthanx.com/#everything-is-local