CODEWITHSUNDEEP
visual-studiovisual-studio-2015tfstfs-2015team-explorer
Nicolas C
Nicolas C

Reputation: 754

Visual Studio loses connection to TFS

I use Visual Studio 2015 and connect throught a VPN to a TFS 2015. It happens that the VPN disconnects, when it happens VS loses the connection to TFS. When the VPN reconnect, I can't connect back to TFS, I get an error: "The remote name could not be resolved". The only way to reconnect is to close VS and relaunch it.

I guess it's not that bad since it does not happens often.

But recently, the error started to happen regularly, even when there is no drop in the connection. I get the same error as before and I can't "just" reconnect to TFS, I need to restart VS.

Following advices from this question, I cleared my cache in this directory:

%LOCALAPPDATA%\Microsoft\Team Foundation\6.0\Cache

I also tried to install Power Tools for TFS 2015 to launch the "Best Practices Analyzer Tool" only to find out it was no longer supported in this version.

I would continue to blame the VPN or some other network micro cuts, but my colleagues on the same network don't have these issues.

Any idea of the cause of this issue or a way to make VS more resilient ?

What I don't get is why the reconnect fails, and why it works only when I restart VS. If I could just reconnect to TFS without restarting, it would already be a major plus.

Upvotes: 3

Views: 4611

Answers (1)

PatrickLu-MSFT
PatrickLu-MSFT

Reputation: 51073

If this issue only occurs on your machine, but your colleagues on the same network works perfect. Most likely related to your VS. To narrow down if the issue related to your personal account, try to use your account on colleagues' computer for test.

%LOCALAPPDATA%\Microsoft\Team Foundation\6.0\Cache will only clear the TFS cache , you need to also clear VS cache typical location for 64 bit: C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE Source Link: If you have problems with TFS or Visual Studio flush the user cache … or not? Also clear IE cache on your dev machine.

If you don't mind, you could also try to reinstall your VS.

Upvotes: 1

Related Questions