Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Visual Studio 2012 hangs when closing a solution

Using Visual Studio Ult 2012 v. 11.0.50727.1.

When I close a solution or Visual Studio, the program doesn't not respond for several minutes.

I've tried the solutions proposed in http://connect.microsoft.com/VisualStudio/feedback/details/748339/vs2012rc-hangs-on-close (turning of auto-recover and installing hotfix http://support.microsoft.com/kb/2493869)

Visual Studio 2010 is installed next to 2012. Here we don't see the problem.

Any ideas?

like image 701
Thomsen Avatar asked Sep 20 '12 06:09

Thomsen


People also ask

Why does Visual Studio 2013 hang on startup?

The Visual Studio might go hang, when there was a problem in loading the nuget packages. Show activity on this post. In my case, VS 2013 Professional was hanging on every startup, even without opening a solution because the license was no longer valid.

Why does Visual Studio get hang when reloading the solution?

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. Show activity on this post.

How do I fix Visual Studio 2007 that won't open?

Re-start VS and open the solution. Save the solution. (Possibly again do the open file, clean, build/re-build, etc.) Close the solution and exit VS. Restart VS and re-open the solution and all should be well.

How to repro a hang in Visual Studio Code?

Start Visual Studio. Start another instance of VS. In the second instance click Tools | Attach to Process... In the list of processes locate devenv.exe. Click Select... and explicitly choose 'Native' and 'Managed' code. Click OK and OK to close Select dialog and Attach to Process dialog. Go back to the first instance of VS and repro the hang.


1 Answers

This particular problem was caused by Visual Studio projects referencing dlls on a (mapped) network drive. The file-server runs Windows Server 2008 and the client (where VS is running) runs Windows 7. Hence SMB 2.0 is used between the two. SMB is the protocol used for network file transfer.

Disabling SMB 2.0, reverting back to SMB 1.0, on the client fixes the problem. http://www.petri.co.il/how-to-disable-smb-2-on-windows-vista-or-server-2008.htm

like image 113
Thomsen Avatar answered Sep 30 '22 06:09

Thomsen