Visual Studio 2013 Crashing When Opening Team Explorer

2
votes

After opening Visual Studio 2013 successfully, I switch to the Team Explorer tab and consistently get a popup error dialog saying that, "Microsoft Visual Studio 2013 has stopped working" and "Windows is checking for a solution to the problem".

This seems to be directly related to TFS (2013 Update 4) since other tools that access TFS (like Source Control Explorer > Workspaces...) also cause the crash.

Edit: I have already tried a VS 2013 Repair. This took all morning with no different results.

This is frustrating because I cannot use TFS outside of the command-line tools. Any help would be greatly appreciated. Thank you.

3
visual-studio-2013tfs
Possible duplicate question, please check these submissions: 1) stackoverflow.com/questions/23587666/… 2) stackoverflow.com/questions/13883371/… - Boris
I have found a solution to this. This is similar to the issue stackoverflow.com/questions/23587666/…. Credit to stackoverflow.com/users/2121065/tu%c4%9frul-emre-atalay. - Richard Ruge

3 Answers

4
votes

Credit to Tuğrul Emre Atalay for the post: Visual Studio Crashing When Checking In.

His issue was checking in changes and having Visual Studio crash. In my case, just using the TFS tools was consistently causing a crash.

The fix for me was to only clear out the local cache and not both the server and local caches.

Clean the Cache folder on client computer. The folder path is: C:\Users\username\AppData\Local\Microsoft\Team Foundation\5.0\Cache.

I cleared this folder and I was able to use all of the TFS tools without any further issues.

I then realized that this happened since migrating to a new user name. I had copied many of my settings over from my old account folder and it must have corrupted the cache area.

2
votes

I had the same issue with Visual Studio 2015 Enterprises. When i open it, VS wasn't able to connect to TFS and it crashed when i clicked on "manage connections"

The issue was not about the cache (I cleared the cache, made a repair of VS and nothing changed) but about the fact that we are currently migrating our projects from perforce to Git with Team Foundation Server.

When Visual Studio starts, it seems VS is trying to connect to TFS with linked Git repositories, but since the plugin currently used is perforce, it causes an exception somehow.

The solution is to set your source control plugin to Microsoft Git Provider (or Visual Studio Team Foundation Server if you are using it)

Here's two screen shots I took. Right after I selected the Microsoft Git Provider, the Team Explorer tab automatically refreshed and I am now able to connect to my projects.

git perforce

0
votes

Go to Tools -> Extensions and Updates
Look for Github Extension for Visual Studio and Uninstall it
Never Mind as you can still work with Github
Now Restart Visual Studio.
Enjoy working on Team Explorer.