Visual Studio Professional 2013 Crashes When Opening Solutions/Files

Question

I\'ve been trying to open some of the webpage/database solutions I made while working for my previous employer, to get a refresher on what they were, but for some reason Vis

Answer 1

For VS2013: I've hit a similar problem every now and then and my fix is to delete the *.suo file and then open the solution.

The only time that has not worked was when an extension was playing up, in which case I opened VS in Safemode using the /safemode switch.

devenv.exe /safemode

Using the /log switch as noted in another answer is also a good idea if it turns out to be a misbehaving extension because that can help you track it down. The default location of the ActivityLog.xml file on my computer is "c:\Users\\AppData\Roaming\Microsoft\VisualStudio\\ActivityLog.xml" but you can also specify where you want the file to be:

Devenv /log Path\NameOfLogFile

See the documentation for VS2013 (with links to other versions) at: /Log (devenv.exe)

I hope that helps.

For VS2015: Same solution, just the suo file is in a different place. VS2015 adds a ".vs" folder. Within that folder are other folders, one of which is named the same as your solution, within that folder is another folder named "v14" and within that one (finally) is a file called ".suo". Delete that file.

Example: your solution is called "Whatever". Starting from your "Whatever" folder the path to the suo is:

.vs\SolutionName\v14\.suo

If you can't see the ".suo" file, remember that it is a hidden file.

I've been using this PowerShell script for a few days to get rid of the .suo files after switching between git branches:

get-childitem -Include .suo -Recurse -force | Remove-Item -Force –Recurse

I've not had any problems with it so far, but no promises that it won't incinerate your laptop :) so use it carefully.

For VS2017: The path to the .suo is:

.vs\SolutionName\v15\.suo

My guess is the "v15" will keep incrementing in future releases.

I found another SO answer that covers some other solutions to VS issues, such as flushing the ReSharper cache if you are using that tool: Visual Studio displaying errors even if projects build.

... And VS2019 The path to the .suo is:

.vs\SolutionName\v16\.suo

When I started using VS2019 I got a lot of "errors" reported after a successful build of an existing project. The editor didn't like namespaces from other projects within the solution. Closing VS, deleting the .vs folder and restarting VS fixed it.