Find below the steps that solved my problem:
- Delete ASP.NET temporary files from
C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files - Change build configuration to debug from project properties.
- Delete bin folder from your project.
- Check if compilation debug is set to true in the web.config
- iisreset
- Rebuild the project.
Top answer 1 of 16
27
Find below the steps that solved my problem:
- Delete ASP.NET temporary files from
C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files - Change build configuration to debug from project properties.
- Delete bin folder from your project.
- Check if compilation debug is set to true in the web.config
- iisreset
- Rebuild the project.
2 of 16
11
There are a couple of things that could be wrong:
- Your source code and assembly could be out of sync - rebuild the application and try again.
- You could be attached to the wrong process - check to see what process you are attached to.
- There could be a logical error in your code that is causing your breakpoint to not be hit (i.e. the method you are in is not actually called, logical branching is routing control around the breakpoint, etc.)
Visual Studio debugging not working
You can not debug it because you have build errors. It did not create the executable. First solve the build errors. More on reddit.com
8
1
May 31, 2024Visual studio debugging not working
Hi guys, I did a clean install ... with working on a plugin. I feel like it’s just a simple setting or something I need to change but cannot figure it out. I cannot seem to debug at a breakpoint and noticed this in visual studio: I don’t know how come but the plugin doesn’t want to update if I make changes, nor go into debugging mode using ... More on discourse.mcneel.com
15
0
April 14, 2023Newest 'visual-studio-debugging' Questions - Stack Overflow
Bring the best of human thought ... at your work. Explore Stack Internal ... In Visual Studio 2022, C# project, I need to keep an eye on an expression that's valid only in a specific method, but I need to keep an eye on it even when I'm stepping through called methods, and ... ... I am debugging a solution ... More on stackoverflow.com
.net - Debugger is not working on Visual Studio 2022 - Stack Overflow
I am using Visual studio 2022 with .NET Framework 6.0 while i am trying to debug application not hit the breakpoint at the starting point. try to apply debugger on program.cs class I have applied all More on stackoverflow.com
Videos
02:29
Debugger Not Working Issue in visual studio | Breakpoint not getting ...
02:13
[Simple] How to fix debugger not working in visual studio ? - YouTube
02:15
Debugger not working issue in Visual studio - YouTube
20:00
How to Debug in Visual Studio: A Beginner's Guide - YouTube
14:13
Inspect Variables Like a Pro in Visual Studio Debugger - YouTube
05:57
Debugging Tips and Tricks in Visual Studio 2022 - YouTube
Developer Community
developercommunity.visualstudio.com › content › problem › 100383 › visual-studio-community-2017-debugger-not-working.html
Visual Studio Community 2017 Debugger not working ...
August 23, 2017 - Skip to main content · Microsoft · Visual Studio
Microsoft Learn
learn.microsoft.com › en-us › troubleshoot › developer › visualstudio › debuggers › troubleshooting-breakpoints
Troubleshoot breakpoints in the debugger - Visual Studio | Microsoft Learn
If a source file has changed and ... a source file is changed, but the source code wasn't rebuilt. To fix this issue, rebuild the project....
Reddit
reddit.com › r/visualstudio › visual studio debugging not working
r/VisualStudio on Reddit: Visual Studio debugging not working
May 31, 2024 -
Good morning,
I am new to VS as I just started using it yesterday, and I have done some work on it, but my build keeps failing, and I have been trying to debug it yesterday, but its been no use so far. It keeps telling me that my Service folder is not a valid Win32 application.
Quora
quora.com › Why-is-Visual-Studio-not-hitting-the-breakpoint
Why is Visual Studio not hitting the breakpoint? - Quora
Answer (1 of 2): Please make sure you are running your project with Debug as solution configuration instead of release. it is an option on the top bar on visual studio.
Microsoft Learn
learn.microsoft.com › en-us › visualstudio › debugger › debug-using-the-just-in-time-debugger
Debug using the Just-In-Time Debugger - Visual Studio (Windows) | Microsoft Learn
March 9, 2026 - The specified program is not a Windows or MS-DOS program. The debugger tried to attach to a process running under another user. To work around this problem, in Visual Studio, open Debug > Attach to Process (or press Ctrl + Alt + P), and find ...
Microsoft Learn
learn.microsoft.com › en-us › visualstudio › debugger › unable-to-connect-to-the-microsoft-visual-studio-remote-debugging-monitor
Unable to Connect to the Microsoft Visual Studio Remote Debugging Monitor | Microsoft Learn
March 19, 2024 - In the Attach to Process dialog box or in the project properties, make sure that the remote computer name and the port number matches the name and port number shown in the remote debugger window.
Visual Studio Code
code.visualstudio.com › docs › debugtest › debugging
Debug code with Visual Studio Code
November 3, 2021 - For debugging other languages and runtimes (including PHP, Ruby, Go, C#, Python, C++, PowerShell and many others), look for Debuggers extensions in the Visual Studio Marketplace, or select Install Additional Debuggers in the top-level Run menu.
C# Corner
c-sharpcorner.com › UploadFile › 7078b8 › breakpoints-are-not-working-in-visual-studio
BreakPoints Are Not Working in Visual Studio
May 15, 2015 - Solution: Browse to C:\Users\<YOUR USER>\AppData\Local\Temp\Temporary ASP.NET Files\vs Delete everything in this directory! Solution: Be sure your are in Debug Mode. Solution: Reinstal Visual Studio (Backup everything).
Microsoft Learn
learn.microsoft.com › en-us › visualstudio › debugger › debugger-feature-tour
Overview of the debugger - Visual Studio (Windows) | Microsoft Learn
1 month ago - You might not yet have any breakpoints set to use for examining your app code. After you set breakpoints, you're ready to start debugging. Breakpoints are the most basic and essential feature of reliable debugging. A breakpoint indicates where Visual Studio should suspend your running code so you can take a look at the values of variables, or the behavior of memory, or whether or not a branch of code is getting run.
Blakepell
blakepell.com › blog › debugging-not-working-in-visual-studio-2015
Debugging not working in Visual Studio 2015
November 30, 2015 - The setting in question is a Visual Studio setting and not one that is project or solution specific. The "Enable Just My Code" setting needed to be unchecked. It is located at: Tools->Options->Debugging->General->Enable Just My Code · After unchecking this setting my breakpoints began working again.
Top answer 1 of 15
1
that seems strange; I guess I would double check that all have copy local set to false, save the solution, close visual studio, delete the ./obj and ./bin dirs, and the hidden .vs directory, and then try again
also check what may be in post-build for all projects & confgurations
2 of 15
0
Hard to tell. You cannot attach to a process and jump through the code, if sources do not match to the binaries loaded. Are you sure you reference the correct dll/gha in Rhino? You can also use DNSpy for debugging any desired dll. You can use that to see if your gha equal to your sources.
Microsoft Learn
learn.microsoft.com › en-us › visualstudio › debugger › remote-debugging-errors-and-troubleshooting
Remote Debugging Errors and Troubleshooting - Visual Studio (Windows) | Microsoft Learn
March 19, 2024 - Error: The Microsoft Visual Studio Remote Debugging Monitor (MSVSMON.EXE) does not appear to be running on the remote computer.
Microsoft Learn
learn.microsoft.com › en-us › troubleshoot › developer › visualstudio › debuggers › troubleshooting-remote-debugging
Troubleshoot remote debugging - Visual Studio | Microsoft Learn
March 20, 2023 - The debugger only loads symbols (.pdb files) that exactly match the .pdb files created when an app was built (that is, the original .pdb files or copies). For remote Windows debugging, by default PDB files are read on the Visual Studio machine and not from the server.
Stack Overflow
stackoverflow.com › questions › tagged › visual-studio-debugging
Newest 'visual-studio-debugging' Questions - Stack Overflow
We are having a "main" application that starts one child "compute" worker processes one after the other. The "main" application creates a complex job that is handed over ... ... Since last Friday, I have been unable to create projects with Docker support or start them for debugging in Docker via Visual Studio Pro 2022.
Top answer 1 of 8
26
That happens to me ~ once per week. To resolve it, I can shut down Visual Studio and delete the hidden .vs folder. After that it's fine again.
Microsoft is probably debugging this already, except they can't, because their breakpoints are not working.
2 of 8
3
Just disable the "Enable JavaScript debugging....." from TOOLS->Options->Debugging->Genera window.
Developer Community
developercommunity.visualstudio.com › t › cannot-run-in-debug-mode › 281320
Developer Community
Visual Studio IDE Visual Studio Code Azure DevOps Team Foundation Server Accounts and Subscriptions Subscriber Access
Microsoft Learn
learn.microsoft.com › en-us › answers › questions › 1846022 › how-to-fix-the-debugger-in-visual-studio-code
how to fix the debugger in visual studio code - Microsoft Q&A
My debugger is not working. I guess there is some problem with the configuration but it is not working. Everytime i try to debug it show 'Configuration 'C/C++: gcc.exe build and debug active file' is missing in 'launch.json'. Please help me configure the…
Visual Studio Magazine
visualstudiomagazine.com › articles › 2025 › 09 › 04 › microsoft-supercharges-visual-studio-debugging-profiling-with-ai-powered-copilot-features.aspx
Microsoft Supercharges Visual Studio Debugging/Profiling with Copilot -- Visual Studio Magazine
September 4, 2025 - By integrating GitHub Copilot directly into Visual Studio's diagnostic workflow, the new Copilot Diagnostics toolset promises to transform how developers identify, understand, and resolve performance issues and bugs.