108

I installed VS2013 (v12.0.21005.1) and added ReSharper 8 (v8.0.2000.2660) a day or two ago. That day it was fine. Now I'm lucky if I can get it to open one solution in a whole day. It opens OK by itself, but when I try and open a solution from within - via the menu - it hangs, badly. If I right-click a solution in Windows Explorer and 'open with VS 2013', it opens then hangs, in exactly the same way. Every now and again, for hours, I get a little notice that it's busy with something.

Anyone know what could be wrong, before I endure a reinstall that doesn't fix the problem?

ProfK
  • 49,207
  • 121
  • 399
  • 775
  • 2
    Have you tried removing ReSharpher in case there is a conflict? – Andrew Nov 21 '13 at 12:14
  • What happens when you open with VS2012? And how many and what project types/language does the solution contain? – RoelF Nov 21 '13 at 12:42
  • @Roel, VS2012 works perfectly. I have about twenty WPF apps and class libraries altogether, all in c# and xaml. – ProfK Nov 21 '13 at 13:17
  • Did you get any further with this? I am experiencing similar problems on my workstation (office). My private copy on a Core i7 notebook works perfectly fine in the same scenario: run a build on a large solution consisting mainly of native c++ projects... – Paul Michalik May 09 '14 at 06:54
  • I created an issue with Microsoft: https://connect.microsoft.com/VisualStudio/feedback/details/924779/visual-studio-is-busy – Ricardo Peres Aug 07 '14 at 13:56
  • I'm having the same issue except I don't use ReSharper. In my case I don't even have a v12.suo file. Don't know what else to do. I just downloaded the solution from a TFS online. – Nicolás Lope de Barrios Apr 08 '16 at 16:50

27 Answers27

244

Sometimes it's enough to simply delete the ".v12.suo" file and try to open the solution again. Helped me many times when VS2013 was freezing on loading a project.

Alex from Jitbit
  • 53,710
  • 19
  • 160
  • 149
  • 19
    Deleting .v12.suo files seem to work for me. Thanks. – ysrb Jul 08 '14 at 14:12
  • 4
    ...even though I'm getting sick&tired of this, VS freezes like once every 3-4 times I open a project... – Alex from Jitbit Nov 24 '14 at 12:29
  • 5
    Same is happening to me, it´s amazing how buggy the VS is becoming. – Fritjof Berggren Jan 14 '15 at 18:56
  • 1
    Helped me while trying to open a typescript project – parsh Mar 26 '15 at 22:27
  • 4
    helped me, but now I have to delete .v12.suo each time i open the solution. Obviously there is some issue with one of the projects in the solution, or with its packages, but this is frustrating. Anyone has any idea on how can I investigate more? – pomarc Jul 29 '15 at 14:38
  • 5
    Deleting the .suo file does indeed get it to load. But I shouldn't have to delete it *every single time*. And on one of my solutions, I literally have to delete the .suo file every single time. – John Rocha Aug 27 '15 at 17:35
  • This is the only solution that I was able to find for this issue. Thanks for posting it! – Bryan Oct 28 '15 at 15:42
  • 3
    For VS 2015 the file is .vs/{sln_name}/v14/.suo –  Jan 22 '16 at 15:53
  • 1
    I answered a similar question here http://stackoverflow.com/a/22838376/441729 with a little more detail and a script you can use to delete the .suo file in VS 2015 (easily adapted for VS 2013 and earlier). – grahamesd Mar 01 '16 at 19:28
  • This is so bad. It's only started happening recently for me after no having this issue since installing VS 2015 when it first came out. So over 3months it wasn't a problem. Has there been an update to Windows / VS? Can MS fix it? – Kind Contributor Mar 11 '16 at 04:12
  • 1
    this worked in visual studio 2015 enterprise too :) thanks just closed visual studio and deleted .vs folder and reopened project. my project code was hosted on tfs server. – Abhimanyu Apr 22 '16 at 01:27
  • For me almost the same problem appears after update of VS2015 to Update 2 version. When I clicked "Close Solution" menu item or tried to close whole application - Visual Struio just was freezing util I finally killed process. Have removed all my VS addons and have done setting reset, but helped only *.suo solution files removing – Volodymyr Jun 19 '16 at 12:30
  • There is better way instead of always deleting is to update Registry key. http://stackoverflow.com/a/39351114/1394331 – bdoshi Sep 20 '16 at 20:17
  • Worked for me - thanks - and luckily no need to delete the file each time I open the solution. I found that it was only one particular solution that was causing the problem - other were fine - but not what the root cause was. It just seemed to happen out of nowhere. – SteveCinq Dec 15 '16 at 18:42
  • Despite my comment above, this fix stopped working for me. Refer to suggested solution on this page. – SteveCinq Feb 22 '17 at 23:40
44

Deleting all ".suo" files worked for me. There were several copies due to opening the solution in multiple versions of Visual Studio.

Edit:

Possible path could be:

PathToSolution\.vs\ProjectName\v14\

.vs may be a hidden folder.

.suo is filename.

John M
  • 14,338
  • 29
  • 91
  • 143
GER
  • 1,870
  • 3
  • 23
  • 30
34

Basically it could be anything, but you can try a few things:

  1. Turning it off and on again.
  2. Clear the ReSharper cache, it's in %LOCALAPPDATA%\JetBrains\ReSharper\<CurrentVersion>\SolutionCaches, where you should find a folder matching the solution you are trying to open. Just close all instances of VS2013, delete the folder and try again.
  3. turn off ReSharper: Tools > Options > ReSharper > General > Suspend
  4. uninstall ReSharper completely and see if problems persists.
  5. Repair Visual Studio through Programs and Features.
RoelF
  • 7,483
  • 5
  • 44
  • 67
  • Haha, been turning it off and on again for a few days. Even the whole machine. Wow, that solution cache was quite fat. – ProfK Nov 21 '13 at 13:21
  • 2
    Worked for me to go through step 2. Path is slightly different now with Resharper 8.1 %LOCALAPPDATA%\JetBrains\ReSharper\v8.1\SolutionCaches – KevM Feb 10 '14 at 22:39
  • Uninstalling & ReInstalling ReSharper seemed to do it for me! – Tim Jul 16 '14 at 02:40
  • 3
    As of ReSharper version 9, the path to the cache folders seem to be `%LOCALAPPDATA%\JetBrains\Transient\ReSharperPlatformVs12`. – Asbjørn Ulsberg Jul 13 '15 at 14:03
  • Thanks. When I used option 3 the solution opened correctly, so the issue was indeed with ReSharper. Turning it on again after the solution was loaded didn't worked and steps 1 and 2 also didn't work. Now I have uninstalled ReSharper (v7.1.*) and installed the latest version (9.2.*) Trial, and everything works now. Visual Studio isn't freezing anymore. Now I just need to contact my supervisor for a ReSharper 9 licence. – Kevin Cruijssen Nov 02 '15 at 10:24
  • My cache was here JetBrains\Transient\ReSharperPlatformVs14\v04\SolutionCaches – Steve Greene Feb 11 '17 at 17:04
11

I found the following to be the better approach to debugging VS based on MS Connect instructions

Please help to confirm if your captured dump file is a 32-bit dump file. If it is a 64-bit dump file, please use the following step to capture a new dump file.

  1. Start Visual Studio.
  2. Start another instance of VS.
  3. In the second instance click Tools | Attach to Process...
  4. In the list of processes locate devenv.exe.
  5. Click Select... and explicitly choose 'Native' and 'Managed' code.
  6. Click OK and OK to close Select dialog and Attach to Process dialog.
  7. Go back to the first instance of VS and repro the hang.
  8. Upon the hang, control should go to the second instance of VS. If not please go back to the second instance of VS manually, and hit "Break All".
  9. In the second instance click Debug | Save Dump As Minidump with heap.

If you are running the VB profile you will not see the Save Dump As menu item. To add this menu item:

  1. Select Tools -> Customize
  2. Select the Commands tab
  3. Select Debug from the Menu bar dropdown
  4. Click Add Command...
  5. Select Debug from the Categories list.
  6. Find the Save Dump As entry in the Commands window.
  7. Click OK (the Save Dump As... command is added to the top of the Debug menu).
  8. Click Close

You can get detailed steps about how to get the dump file and call stack at http://blogs.msdn.com/debugger/archive/2009/12/30/what-is-a-dump-and-how-do-i-create-one.aspx

If you find the problem is with Resharper Addin you can then report the issue via - http://youtrack.jetbrains.com/issues/RSRP

Jamie Clayton
  • 1,007
  • 11
  • 24
  • That worked for me. In my case, I had a build target pointing to a file that doesn't exist - debugging let me know what was going on. – Arnaud Oct 07 '15 at 04:26
  • My .dmp file is 708 mb...why is it so large? Is this normal? – James Wierzba Nov 30 '16 at 21:27
  • @JamesWierzba, unfortunately, I've seen large dump files. If you have resharper open, it regularly uses 500-800MB, so it's possible that VS may also be including Add-in + some of the project code details to help them issolate the issue. If you are running re-sharper you can turn on the memory usage by that product, it's an interesting value to watch on big projects. – Jamie Clayton Dec 06 '16 at 11:54
  • 9. Open the dump file in VS 10. Make sure your load the required debugging symbols (do a search for this) 11. Run the dump from the "Action/Debug with ..." in the top right of the dump file window. Personally, I had trouble locating an issue but I agree that this is probably the best approach to solving the problem. – SteveCinq Feb 21 '17 at 19:58
8

Suspending Resharper Worked for me. Goto

Tools -> Options -> ReSharper -> General -> Suspend Now

Now your solution will load very fast. After your solution fully loaded, you can change the Resharper settings to Resume Now.

Rashad Valliyengal
  • 3,132
  • 1
  • 25
  • 39
8

Are you using any node modules in your project? Or can you identify that it is a ReSharper specific issue?

If you've got NPM modules (eg. for Grunt), mark your 'node_modules' folder as 'hidden' (no need to make child folders hidden though), and try again.

Visual Studio was hanging on open for me, turned out it was trying to scan deeply nested node modules with file paths longer than the Windows maximum (260 characters), and this was preventing me from opening the solution in VS, but marking the folder as hidden solved the problem.

Matty J
  • 3,116
  • 32
  • 31
4

I had this issue recently as well, and found that disconnecting my computer from the internet when loading the project fixed it. With this, I managed to cut loading times from several hours down to seconds. Since my network cable is not particularly accessible, I simply disabled my network adapter before loading the project (in Control Panel).

This soon became frustrating, however, and I recently looked into the problem again. It seems that logging on to my Microsoft account in Visual Studio ultimately fixed the problem, and I now have no more issues loading projects.

This may work for you as well (if you haven't yet fixed it - but since there is no accepted answer here, I assume that the problem is persisting), so I suggest that you at least try disconnecting from the internet, even if you would rather not enter your Microsoft credentials.

Mmarss
  • 178
  • 1
  • 5
4

I went into the %LOCALAPPDATA%\JetBrains\ReSharper\ and opened all the directories looking for the SolutionCaches, and emptied all of them. Problem solved. The application was quite large, so this helped.

csnyder
  • 41
  • 1
  • This is what fixed it for me - mine got stuck on "processing assemblies" seemingly for random, different assemblies every time. I searched for "SolutionCaches" in that folder and deleted the contents of each result. Seems to be fixed now. – Isaac Lyman Jun 22 '16 at 18:56
3

Check for Windows updates

I had this problem too. Furthermore, I couldn't open my Windows firewall settings (trying to block VS's internet connection).

When opening update settings (Windows 8), I saw there was a pending update ("found today"), so I rebooted my computer, letting Windows update. After that, VS and the firewall worked fine again.

Check your hardware

I've had the problem a second time; even Windows 8's update page would keep loading forever. It was an issue with my (non-OS) hard drive: https://superuser.com/questions/756261/various-parts-of-windows-8-and-visual-studio-2013-get-blocked-by-possibly-comm?noredirect=1#comment978074_756261

Community
  • 1
  • 1
Cedric Reichenbach
  • 8,970
  • 6
  • 54
  • 89
3

I get this issue now and again - VS 2013 Update 2, Win 8.1, IE 11.

Try this - Open task manger, kill the VS app hanging, and then close any IE sessions that are running in the Background Process list - there may be one or more hanging around.

Restart VS

Seems to clear it for me, without a reboot.

Richo
  • 31
  • 1
3

The problem I had was the Perforce connection.

When opening the solution, it would ask if I wanted it to connect to Perforce. Allowing it to try would make it hang and allocate 1.5 GB of RAM.

Not allowing the P4 connection let it load properly (allocating 1 GB RAM). Then I could tell it to connect to P4 after, and it is now fine.

Almo
  • 15,538
  • 13
  • 67
  • 95
3

For me , whether computer crashes with power outage, or sometimes with mandatory reboots in the middle of the night. What does WORK for me

DELETE ALL FILES IN THIS DIRECTORY:

C:\Users\yourusername\AppData\Local\Microsoft\WebsiteCache\

Tom Stickel
  • 19,633
  • 6
  • 111
  • 113
  • 1
    Same scenario: Power failure, total crash, windows reboots, I can load the sln, but all the settings from the csproj files are ignored. Deleted suo and the above mentioned fodler (which was fuuuL :-) ) ans so far everything seems fine again. – Xan-Kun Clark-Davis Jul 09 '16 at 20:08
3

For anyone still referring this helped me:

I had to always delete .vs12.suo file to load the project.

I came across this thread from Microsoft and following that I created registry entry which fixed my issue with Solution load.

https://connect.microsoft.com/VisualStudio/feedback/details/860685/visual-studio-hangs-after-10s-when-loading-solution-corrupt-suo

bdoshi
  • 1,051
  • 12
  • 19
2

I had similar issue, when i checked the solution file it was created by VS.Net 2012. To resolve the issue, I created dummy solution file and reloaded the projects from vs.net 2012.

Also observed when nuget package update got screwed up, while you reload the solution, Visual Studio might get hang.

The Visual Studio might go hang, when there was a problem in loading the nuget packages.

Sivalingaamorthy
  • 983
  • 2
  • 9
  • 26
2

In my case, VS 2013 Professional was hanging on every startup, even without opening a solution because the license was no longer valid.

Last item in the log file:

<entry>
    <record>367</record>
    <time>2015/07/13 20:11:05.051</time>
    <type>Information</type>
    <source>UserConnection</source>
    <description>myemailaddrs@gmail.com signed in for IDE user</description>
</entry>

And on the msdn.microsoft.com subscription page: "Your subscription is no longer active, contact your administrator."

I had to get an updated subscription from my employer.

Kerry Randolph
  • 591
  • 6
  • 15
2

Deleting Test Results from my TestResults folder actually did the trick for me. Just another thing to try.

V B
  • 121
  • 7
2

VS2012 hangs on me e.g. when opening a csproj file on a network share (in fact on a share that was on the VirtualBox host, connected as a smb share using a VirtualBox feature).

Copying the project over to a local drive fixed it for me. Not sure if assigning a drive letter would do the trick.

Also not sure why it does not work via network share, if it is a VS limitation or perhaps some plugin (I use resharper, of course).

Evgeniy Berezovsky
  • 18,571
  • 13
  • 82
  • 156
2

For me this appears to have something to do with the project having the MVC 4 project type guid (E3E379DF-F4C6-4180-9B81-6769533ABE47). Removing this guid from the .csproj resolved the hanging for me. (An additional wiping of the .vs folder was required after removing the guid.)

lbergnehr
  • 1,578
  • 11
  • 15
2

I just removed "packages" folder from root of solution and it helped for me (Visual Studio Express 2015)

2

Sorry for having to create a new post instead of commenting on the selected answer .. I do not have enough rep to comment at this time.

My issue was was temporarily resolved by the "...delete the .suo file ..." solution, and as other folks pointed out, I had to delete the file every single time.

Since it (apparently) is impossible to stop the creation of the file I started to dig a little more into what the file did. In addition to saving user settings, I believe it is also saving session settings, like which files you have open when VS is closed. I suspected that my project is attempting to open a file that no longer exists and that is what is causing the hang. What fixed things on my end was to delete the .suo, open VS, open a file within my solution, build and close the solution. After doing this I have had no hangs.

tl:dr

In my case, a user setting file(.suo) was attempting to open a file in my solution that no longer existed. I resolved the issue by performing the following steps.

  1. Delete the .suo file (for me this was in /[projectfolder]/.vs/[projectname]/v14
  2. Open Visual Studio
  3. Open your project
  4. Open a file (I simply opened a random .cs file)
  5. Build and save your solution (Simply saving may do the trick, I built by habit)
  6. Close Visual Studio

Hope this helps someone ... we spent way too many hours on this issue :)

Jeramy D.
  • 53
  • 7
1

Lots of suggestions here and elsewhere but the only thing that permanently worked for me had to do with the start-up project I'd set. This is what I did:

  1. Delete the .suo file as suggested elsewhere.
  2. Start VS and open the solution. All should be well at this point.
  3. Leave the start-up project as-is, even if it's not what you want.
  4. Save the solution. (Possibly do as someone else suggests and open a file, clean, build/re-build, etc, but I didn't have to do any of that.)
  5. Close the solution and exit VS.
  6. Re-start VS and open the solution.
  7. Change the start-up project to whatever it should be
  8. Save the solution. (Possibly again do the open file, clean, build/re-build, etc.)
  9. Close the solution and exit VS.
  10. Restart VS and re-open the solution and all should be well.

This might or might not work for you but I'd tried everything I could find - registry changes, debugging VS from a second VS session, you name it - but nothing else worked for more than a single start/open.

SteveCinq
  • 1,920
  • 1
  • 17
  • 22
0

Try to uninstall extensions with "Control Panel" or disable any add-in in [Tools]=>[Add-in Manager] then try to reopen the solution.

My problem was fixed by uninstall "Visual Localizer".

firemaples
  • 1,521
  • 13
  • 18
0

In my case the Fusion log has been enabled. Log files has been growing for months as I forgot to turn it off after investigation. This way the antivirus software started to check these big log files several times during opening the solution, and "Preparing solution..." message is visible for long-long time. When I noticed this, I turned off the fusion log, and problem solved. Solution loads in 10 seconds instead of 20 minutes.

DJackson
  • 1
  • 1
0

I've had this issue multiple times, in pretty much all versions of VS. The one solution that seems to work most of the times is to delete the .vs folder located in the solution folder. Sometimes it's enough to delete the .sou file located in .vs///

The folder is hidden by the way, so you will have to enable "Show hidden files and folders"

Jonas Lindau
  • 73
  • 1
  • 8
0

For me the solution was to disable source control (Set plugin to None in Tools->Source Countrol). I think it was trying to sync some huge Git repo for some reason (have a couple of massive repos, but not in the tree I was trying to open).

griffin2000
  • 709
  • 9
  • 26
0

I have fixed the issue by uninstalling these two plugins:

  1. Productivity Power Tool
  2. Web Essentials
-1

I restored a previous version of the .vbproj file and it solved it.

I don't know what was in the newer version but the problem was something inside the .bvproj file itself.

Doron Saar
  • 446
  • 5
  • 7