I regularly experience lockups in VS2022.
When I try to close the program I get a message
Microsoft Visual Studio 2022 is not responding.
With a dialog asking whether to
Restart the program.
Close the program
Wait for the program to respond.
For some reason I am unable to capture a screen shot of the message.
Today when running my program in the IDE, I saw that whilst the UI was responsive the code screen was behaving this way.
I had some break points in controls. Could that be the cause?
I also often get this message when Microsoft Visual Studio (Not Responding) is in the designer caption.
Related
When trying to open an older C++ project in Visual Studio 2019 Professional, I keep getting this "Review Solution Actions" dialog that hangs Visual Studio.
I've tried starting in safe mode and resetting my user settings but neither of those have done anything.
Once this dialog shows up it just hangs here and I cannot focus on this dialog or Visual Studio. It's as functional as the image of it posted in this question.
I can successfully "End Task" in Task Manager (as opposed to killing the process) so it's still doing something in the Windows message loop (and redrawing)-- but strangely won't obtain focus or allow drags. Haven't seen that before.
Is there a way to retarget this project via the command line? Is there something else I can do?
Version: VisualStudio.16.Release/16.4.5+29806.167
Updating to 16.5.2 resolved this, thankfully.
I have noticed a frustrating problem during which a standard Winform control will not enter a drag-drop operation during a debug session as it should after calling the control's DoDragDrop method. The source control (from which the drag-drop operation is initiated) acts as if it doesn't support drag-and-drop.
In my case, it turns out that I was running a debug session in a second instance of Visual Studio 2017. When I stopped running that second debug-session instance of Visual Studio (I was able to keep Visual Studio open, I just had to stop my debug session), the drag operation in the first debug-session instance of Visual Studio began working as expected.
Clearly, drag-and-drop should work in two debug sessions open at the same time in two different Visual Studio instances--and sometimes it does on my system. But occasionally something happens (I'm not yet sure what) to "corrupt" the VS IDE or the .NET subsystem that causes a Winform drag operation from no longer functioning.
This behavior occurs even after rebooting and happens in the latest VS Enterprise 2017 IDE (Ver 15.5.6) with .NET 4.7.02556.
I realize that this problem and its solution is rather nebulous but I felt it was enough to be useful here (and I invested a lot of time figuring out what was going on!).
I have a WPF solution in Visual Studio 2013 update 2 with over 100 projects, mostly C#. I have a small C# exe as the start-up project which does some basic initialisation and displays a file open dialog which appears within a few seconds.
I have recently encountered an intermittent problem that occurs a few seconds after launching the debugger, usually before the file open dialog is displayed. Visual Studio starts loading dependencies (visible in the status bar at the foot of the window), then suddenly goes unresponsive and fails to recover.
Crucially, it is impossible to launch new processes or close windows/terminate existing processes. It is still possible to interact superficially with programs that were already running, i.e. menus in user interfaces are still clickable but have no effect. Running any command in an open cmd prompt causes the window to stop responding; Ctrl+Alt+Del/Ctrl+Shift+Esc have no effect. The only option is a hard reset.
I have tried deleting PDBs and performing a full clean/rebuild, to no avail. There is also nothing of interest in the system or application event logs.
This issue started happening a few days ago and has become more regular, but remains intermittent.
I deleted the solution's SDF file, and the issue has not occurred since.
For the past couple of days, Visual Studio 2012 and 2013 have been hanging during debug mode. Most of the time, i dont get this issue until further into my project. When i press the Start Button, everything continues as normal, but then hangs with this message at the bottom of visual Studio statusBar.
Inside Task Manager, when i try to force taskkill, or end process/process tree, this continues to stay present in my running processes.
Even after a reinstall, nothing seems to help it. I did see somewhere on the Microsoft Developer forums where a person was told it was something to do with the windows sybmol server?. What do i need to do to fix this issue i am having?
After this occurs once, i am forced to reboot my computer. Even if i open Visual Studio after this happens, it still has the same issue.
I feel pretty ridiculous having to ask this, but is there an easy way to close Visual Studio while it's debugging?
I'm debugging my application, and when switching to full screen it crashes. I am unable to alt-tab to visual studio to stop the debugger, and I'm unable to pull any other windows on top of the full screen application.
I can, however, see the start bar. I can right click on visual studio and click close, but it does nothing (same goes for the debugging application).
I'm unable to get the task manager to show in front of the full screen application.. However, I'm on Windows 8 and I've noticed the Metro interface still works (and all metro apps). If I could find a little command prompt metro app I'm sure I could get around this, but I'm unable to.
Is there an easier way to resolve the issue without having to restart my pc each time I crash?
Almost forgot to mention, I'm on Visual Studio 2013
Edit: Forgot to mention, I'm programming on-the-go on a laptop; I only have the one monitor for this situation
I found a solution:
I can toggle focus to Visual Studio via Windows' Alt-Tab hotkey. This won't bring up Visual Studio, though.
Usually the problem is an unhandled exception, which requires me to hit "break." Since I gave Visual Studio focus, I can hit enter to select break.
I then use the Shift+F5 hotkey to stop the debugger
You might be able to use Developer Command Prompt - see MDbg.exe (.NET Framework Command-Line Debugger) to debug and kill your process