Is there a more visual way to differentiate what process you are busy debugging when hitting a break point and then switching between the processes using the process drop down?
Something in the line of different background windows colors per process?
Possibly a add on or plugin?
At present, I haven’t found any plug-in that could highlight the process that is currently debugging in Visual Studio.
But the tools those Visual Studio offers could help us to differentiate them while multi-process debugging:
You can see there are two places where we could find out the current process under debugging:
In the process window (Debug -> Windows -> Processes), it gives the golden arrow.
In the right hand, at the top of Diagnostic Tools, there is also a pop-up which indicates the process with PID that is under debugging.
I also found thread talking about the similar issue which also might help:
How can I tell which process I am debugging (attached to multiple processes)?
Related
In an older version of Visual Studio (Like the one at home, guess 2013), I am able to edit my code while the system is running but I can't continue (and I don't want to continue). While step-ping through my code, I just want to start typing and once I finish editing then to recompile.
The advantage is that while typing I can hoover my mouse and watch values/structures of the variables and edit according. It's a nice guide sometimes, like a reminder or notes.
Why my Visual Studio 2015 prevents me from editing my code? saying:
Changes are not allowed when unmanaged debugging is enabled
P.S my Edit and Continue option is enabled as suggested everywhere on the internet. And there is no Enable Unmanaged debugging option for 2015 like suggested here for 2010 How to: Enable Debugging of Unmanaged Code
Edit: It's a C#/C++ application. I didn't start the project from scratch and it's a huge one. I start it as Debugger and sometimes Release. Doesn't work on both (I don't care about the Release)
How my settings under Tools -> Options -> Debugging -> General look like:
You're in the completely wrong place; that's the system-wide debug options.
As explained in the post you linked to, you need to go to the Debug tab in Project Properties.
use native compatibility mode when you want to break ok C++ code. Also right click on the project and check "enable native debugging" in the project properties. Those two things should allow you to debug c++ (not edit and continue, just normal debugging)
For Visual Studio 2022, you need to add
<EnableUnmanagedDebugging>true</EnableUnmanagedDebugging>
in your vcxproj files (under PropertyGroup Condition subset)
I have updated Visual Studio 2015 to the first update. Since then I cannot debug my code twice in a row. It goes like this:
I start VS and try to debug. So far OK
Change code, build and debug.
Try to reach a web but it never loads.
If I close the VS and load the solution again it works or If I do not change code in step 2.
Other thing I noticed is the IIS Express Worker process is consuming most of CPU time.
And apparently the symbols are not loaded (I do not see the messages of DLL loading in the status bar).
This is making my development process very slow and tedious.
The solution is a MVC project under 4.6.1 framework.
Any ideas? Thank you very much!!
You should boot Visual Studio into Safe Mode. To enter safe mode do the following:
Open Command Prompt, as Administrator.
Enter: cd C:\Program Files (x86)\Microsoft Visual Studio 14.0
Enter devenv.exe /safemode
If Visual Studio does load and debug, then more than likely an extension or an update is the culprit. This will allow you to also see which updates may have occurred. The other potential issue would be if your Internet Information System had an issue.
Otherwise if your Internet Information System is stuck 'on'.
CTRL + ALT + DELETE
Go to processes, end W3P process.
Try to launch and debug inside Visual Studio.
Otherwise, simply try restarting your computer. We would need more information, as this can occur for an assortment of reasons.
#Julen - I have the same issue as you and I have found a work-around.
Add the "Terminate all" button to your toolbar and use it instead of just stopping the debugging. This command kills the IIS Express process.
See how to add it here:
Automatically Kill IIS Express Process After Debugging (VS Express 2013 Web)
If your IIS doesn't shut down after stopping the debugger, you could do one of the tricks written in this blog post - but the opposite way because the article focuses on keeping the debugger on.
Here is the proposed solution 2 - to check "Enable Edit and Continue":
Similar to VS 2013, if you disable Edit and Continue IIS Express will continue to run when you stop your debug sessions.
Open the menu item Tools/Options, look for the Debugging/General option. Scroll down and uncheck “Enable Edit and Continue”
It might be hanging when trying to load external symbols. I had a problem with that before.
To test this theory:
Open the Tools menu.
Click 'Options'.
Find and expand 'Debugging' on the left.
In the 'Symbol file (.pdb) locations' list, uncheck everything.
Click OK and see if the problem reappears.
I'm running a web application with models defined in C# and views being in HTML5, client-side business logic is JavaScript/jQuery. I've noticed something odd recently. Whenever both Visual Studio and my web application are running simultaneously, the browser memory usage starts to climb. It is worse in IE and Chrome, but likewise substantial in Firefox (all the latest versions of these browsers). Also, the memory usage of Visual Studio starts to climb. The CPU usage for the browser hovers in the teens, normally hovering around 0 otherwise.
Once I close down either the web application, or Visual Studio, the memory stops growing, and indeed, closing Visual Studio often allows the browser to run its garbage collection and clean up the mess. I suspect this has something to do with some sort of background debugging going on. I'm surprised that googling this hasn't turned up a similar issue for somebody somewhere in the world, and I suspect it's some kind of configuration setting in my IDE. Visual Studio 2013 Premium. I've reset my settings (Tools -> Import and Export Settings -> Reset all settings, with no effect. Building in Release mode likewise seems to have no effect. I'll keep hunting this one down, but has anyone here seen anything like this and resolved it?
edit: I have recently been debugging some dynamic code using the debugger keyword. I've commented that out, and am still seeing the same results. But I wonder if there isn't some lingering effect from using this in the first place?
edit: Updating Resharper from 8.2 to 9.2 didn't help either.
edit: Apparently this issue has been seen before and reported, if you just know what to google for.
Visual Studio has a browser link feature that causes the web app to poll Visual Studio in case you have changed a file.
In VS there is a small refresh icon in the debug menu with a drop down. In there you can disable this feature.
Did you trying running the application without debugging? (Ctrl+F5)
To enable VS debug the browser more info is needed specifically things like scripts and eval code are needed even after use. So, running the browser with debugging enabled will use more memory and cause memory to grow with time.
I have a relatively large C#/WPF Visual Studio 2008 solution that I am trying to test and synchronize across 2 developer's computers. On my computer, I am able to build and debug (run) the project successfully without errors.
On the second computer, I am able to build the solution without any errors. When I attempt to run the solution, Visual Studio starts the process but about 3 seconds later the entire development platform exits. Before it exits I briefly see one of our .xaml files opened by visual studio with a yellow 'unhandled exception' box pop-up on a certain line number. I'm currently contacting the part of my company who is responsible for implementing the functionality of that xaml file.
This raised a bigger issue in my mind: How can you troubleshoot an issue when Visual Studio is immediately exiting after attempting to run a program?
The Visual Studio 2008 crashes when starting to debug post may also be helpful. I'm trying those solutions now.
We found that executing the three following commands helped to fix our problem:
devenv.exe /ResetSettings
devenv.exe /ResetSkipPkgs
devenv.exe /Setup
This was suggested in another stackoverflow post here helped us to determine that it was a plugin, AccuRev's Visual Studio plugin, that was causing the issue.
The issue also appears to be a "known issue" with a hotfix from Microsoft, documented here.
VS2008 SP1: In Visual Studio 2008 SP1, having windows in non-default locations, for example after docking and undocking windows, when switching between debugging and designing or switching to/from full screen, can result in a crash of the Visual Studio IDE.
Thanks for your help!
Run devenv/debugexe to debug your exe. When an unhandled exception occurs, in the debug menu, select "save as dump", then visit http://connect.microsoft.com/visualstudio to open a bug report and attach the dump file after creating the report.
I try to debug several applications that communicates with each other - and want to have ability to step over without switching to another process/thread.
So Visual Studio has command "Step Over Current Process (Ctrl-Alt-F10)" - which looks like what I want but it's disabled, why?
I've found the same question but for C++:
"Step over" when debugging multithreaded programs in Visual Studio
So write macros is only way for .net too?
My understanding is there is no real way to do this in visual studio. Unlike Eclipse :D. The best you can do is use the Threads debug window to freeze all threads other than the one you want to debug.
As stated in the comments you can also use a conditional break point and set a filter like "ThreadNameToStopOn" == Thread.CurrentThread.Name