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?
Related
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.
Since a couple of weeks, MSBuild doesn't finish any builds anymore when I try to build a Visual C++ project in Visual Studio 2010.
In Process Explorer I can see that a subprocess MSBuild.exe is attached to devenv.exe, but no cl.exe is ever invoked. After 30 seconds another MSBuild.exe subprocess is attached and this continues for a while, until finally the build is aborted (or I kill Visual Studio).
I observed that after killing Visual Studio, the MSBuild processes are orphaned and if I restart Visual Studio and invoke another build, it suddenly works.
When every orphaned MSBuild process has exited, I cannot build anymore.
I tried to check, if there's anything wrong with the MSBuild installations, but at first sight it looks fine.
I reinstalled the SP1 of VS 2010 as well as Windows SDK 8.1, but nothing changed.
I also installed VS 2015 Express, which now ships with MSBuild (previously was shipped with .Net Framework), but same behavior.
The problem occurrs with different Visual C++ projects.
I could not google any solution, for slightly related problems there seemed to be issues with Avast antivirus. This is a corporate notebook, which is protected by Sophos, so I can't change any antivirus settings.
EDIT1
If I invoke MSBuild directly with
c:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe .\MyProj\MyProj.vcxproj
it just works.
Any hints or suggestions?
I have the problem that Visual Studio 2013 crashes when I lock the computer or start another instance of Visual Studio.
I use Visual Studio 2013 with latest patches applied. I always start Visual Studio as Admin.
This seems to only happen with a certain big solution. This problem did not occur to me with other solutions.
I tried to delete the solution and make a clean checkout from TFS, but Visual Studio still crashes.
I know this is not much information, but do you have any idea how to fix this or how to what else I could check?
Additional Information: This still happens even with Visual Studio 2015 on a fresh Windows 8.1 installation...
Here's the error:
Use the following steps to solve the issue:
Source: http://resharper-support.jetbrains.com/entries/24765142-Visual-Studio-with-ReSharper-is-freezing-and-or-crashing
I would copy the solution with quotation but as you can see, there is a lot of text to edit.
Start Visual Studio using the /log switch. Then check the created log file for warnings and errors:
%APPDATA%\Microsoft\VisualStudio\11.0\ActivityLog.xml
If you use a Web Browser to view the file, it will be nicely formatted, due to the accompanying xsl-sheet.
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.
My Visual Studio stopped recognizing external file changes.
I checked the respective options being enabled ('Environment/Documents/Detect when file is changed outside the environment' and 'Environment/Documents/Auto-load changes, if saved).
I restarted Visual Studio as well as my machine.
I tested other software that recognized changes, such as Notepad++, which works just fine.
I tested different Visual Studio projects to check if it has something to do with the project being screwed up somehow - same effect in all projects I tested.
What's going on here?
(There are some SO questions that appear to be related judging by the headline: VS2012 not detecting external changes, Visual Studio 2012 stopped applying changes to solution and Visual Studio 2012 not detecting file change, but all are about different issues.).
Happened to me as well this morning. Exiting VS and relaunching/opening the project seems to have it working again. Super strange!