A few days ago Visual Studio 2015 started dying on me when compiling.
If the build is successful it takes forever to compile and Visual Studio hangs.
If the build fails Visual Studio kindly hangs and then I get a message saying the program has stopped:
This has never happened before and my work has been blocked for 3 days now.
I'm desperate. Any ideas?
Things I've tried:
Restart my computer (still dies)
Restart Visual Studio (still dies)
Build another project (still dies)
Deleting the .suo file in the solution (still dies)
Disabling ReSharper (still dies)
Removing ReSharper (still dies)
Resetting Visual Studio to its default settings (still dies)
Uninstalled and reinstalled Visual Studio 2015 (still dies)
Uninstalled and installed Visual Studio 2017 (still dies)
Run a memory check (Memory is OK. VS dies.)
Combining one or more of the above solutions (dies...)
Other teammates don't experience the problem. Same tools same projects.
Thanks in advance.
Edit 1:
Tried with a new, untouched, project as suggested by #Surreal.
Compiles successfully. I break the code on purpose and VS dies.
Tried manually running MSBuild on my solution from the command-line as suggested by #bsinky. Build fails with a strange error.
What is this "target go" thing? I looked it up on Google and can't seem to find anything related.
No idea how this was related but cleaning my Windows' temp folder along with the prefetch folder fixed the problem (I used CCleaner).
I did have to recompile and readd some broken references though.
But now I can compile both good code and bad code.
Related
I tried looking this up on the visual studio support site and apparently this should have been fixed. I am still experiencing periodic hanging while debugging.
I am running the most recent update of visual studio 2017: 15.2
I have tried disabling extensions (Resharper 2017 Ultimate, Developer Analytics, etc.) without any luck. Its very frustrating, because I end up having to end the Visual Studio task in task manager.
Has anyone else had similar issues with 15.2?
UPDATE
I found this on the MS site. I had looked up and down, but once I added a 15.2 search criteria it showed up.
I had issue with Visual Studio 2019 hangs while debugging. I have deleted .vs(hidden) folder. It works fine then.
The .vs directory can be found on the same directory where the solution file located. (It was hidden by default, we need to enable the visibility on file explorer setting at windows )
Updating to 15.2(26430.16) has solved this issue. I preformed the update almost 2 weeks ago and have not had an issue since.
I have a bunch of MSTests that can no longer be step into or debugged. I have breakpoints set but for some reason, Visual Studio ignores them while executing the tests.
I have cleaned the project and rebuilt, deleted the test results folder found under the solution root and also restarted Visual Studio all to no avail. Only thing I have not done yet is restart my machine.
Anyone know what the problem could be here?
Some time ago I started developing with Visual Studio 2013 Professional and everything worked well. But a few weeks ago I upgraded to the Ultimate version. But since then Visual Studio crashes when I load a project. VS just starts up normally, I can see the menu and log in and stuff like that. But when I open a project it crashes everytime. I tried to repair it VS in the control panel, but still the same problem... Then I reinstalled it but when loading a solution it crashed again. Now I downgraded to Professional again, but now even Professional crashes.
I have been searching on google for a long time to solve this problem. I tried to reconfigure the debugger, even reinstalled it, but no effect. A lot of forums say you have to delete the .suo file in the project, but even that doesn't work...
Is there a solution for this?
UPDATE
When Visual Studio crashes I get this error: https://i.imgur.com/VtaikJ5.png?1
My ActivityLog.xml is on OneDrive: https://onedrive.live.com/redir?resid=B3519F287A9CD3FC!2830&authkey=!AIUDHo1bCZan4Fk&ithint=file%2cxml
I already received the answer from the MSDN forum. And it was caused by the Web Essentials extension tool. And apparently with the Visual Studio Update 4 everything seems to be fixed. The extension tool was causing the error, and that error is fixed in the update.
Thanks for the support everyone!
When calling devenv.com from command line or FinalBuilder action within our automated build it sometimes hangs and never gets past compiling step.
It is called with this parameters from C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE:
devenv.com /build "Release|Any CPU" "D:\MyProject\MySolution.sln"
It hangs forever on this step. When I open it in VS 2013 and ReBuild the solution it works fine every time.
Any ideas? I've also tried it on other build machines and it does the same. So it is not machine dependent.
After a lot of troubleshooting and looking through various logs, solutions, googling, I figured out that this is caused by the Extension Manager in Visual Studio 2013.
You can find the extension manager in all Visual Studio version -> Tools -> Extensions and updates.
So by uninstalling the Nuget Package Manager from Visual Studio 2013, made it the solutions compile successfully every time.
Another fix we noticed and could reproduce every time is when our virtual machine in Hyper-V was given 2 CPUs, it would cause builds to hang every time. Reducing the VM to only have 1 CPU fixes the problem.
We have solved this by creating a new .sln and adding existing projects to it. NuGet info is now revomed from the .csproj files and we now use "nuget.exe restore" to update NuGet packages before a call to devenv.com. This has fixed it for some projects.
Recently I have faced a weird issue with Visual Studio. Every time I get the latest source from TFS, even though the source code gets updated but when I run my project, the old source code is executed!
No matter I clean and rebuild all the solution, I need to close the solution and re-open it to get it to work.
I am using Visual Studio 2012 Update 3 and TFS 2010.
Any idea about this issue?