After I install Visual Studio 2013 update 2, I notice that right click on any kind of project file (aspx, cshtml) causes about 45 seconds of hang in Visual Studio. It eventually opens context menu, but every single time this happens.
If I right click on Solution Explorer, Class View etc.. there is no issue at all, just in files editor.
I am using intel i7 processor and 16gb ram (hardware is not an issue) and Windows 8.1 Pro.
I also cannot connect tfs online for last 2 days so I am using my solution with disconnect from tfs. This causes hangs on start up because it tries to connect remote server. But I am not sure it will cause issue on right click of the files.
What I did up to this moment;
1- Installed last update again 2- Restarted Visual Studio several times 3- Restarted PC 4- Cleared TFS cache files
Is there any idea what is causing this issue?
Update: I created an empty MVC project without TFS binding and there is not issue. Looks like it is totally related to TFS dis-connectivity, I will investigate more and will post answer if find out.
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.
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.
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.
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.
ReSharper can cause this problem. You can suspend it (temporarily) to see if the problem is solved. If it is indeed solved, you should clear ReSharper's cache before you enable it again. Go to %LOCALAPPDATA%\JetBrains\ReSharper
and delete the SolutionCaches
folder for whatever version of ReSharper you are using.
I just had the same issue and in my case wasn't Resharper the culprit. What worked for me was, inside VS, right clicking the SOLUTION, open Nuget Package Manager and at the top was a message telling "There are missing packages". I clicked to restore them and immediately after that the problem was solved.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With