I have a web project (DNN module) that I am developing and I recently updated to Visual Studio Professional 2015 Update 3.
I am using IIS 10 on a windows 10 PC
When I try to F5 / Debug my app I get the following warning on any breakpoints:
the breakpoint will not currently be hit. no symbols have been loaded for this document
I am at a total loss and really need help. I can not figure out why my breakpoints are not being hit, when I debug the site no errors are thrown and the site runs fine.
From this SO thread I tried:
From This SO Thread I tried:
From User suggestions:
Can someone help me figure out why my break points are not being hit when debugging from visual studio.
Not sure what I did. I have been fighting with this all day and afer restarting the computer and visual studio numerous times I can now attach to process w3wp.exe and the breakpoints are hit.
However hitting F5 still does not work. The site loads but no breakpoints are hit and I can see that my projects .dll is not added to the debug modules list (but it is when I attach to process).
I feel like I am closer but still can not figure out why my project .dll is not loaded in the debug modules when hitting f5.
When you debug ASP.NET applications in Visual Studio .NET, the debugger might not stop on breakpoints. This problem occurs because ASP.NET debugging isn't enabled on the application. To resolve this problem, follow these steps in Visual Studio .NET: Right-click your project from the Solution Explorer, and then click Properties.
Breakpoint Warnings. When debugging, a breakpoint has two possible visual states: a solid red circle and a hollow (white filled) circle. If the debugger is able to successfully set a breakpoint in the target process, it will stay a solid red circle.
To modify this setting for all breakpoints, go to Debug > Options and Settings. On the Debugging/General page, clear the Require source files that exactly match the original version option. Make sure to reenable this option when you're finished debugging.
You set a breakpoint in the project. You start debugging the project. In this scenario, the breakpoint that you set is not hit. Note This problem does not occur when you use the release version of Microsoft Visual Studio 2010. This problem occurs because Visual Studio treats the add-in as a .NET Framework 2.0-based application.
Are you able to attach directly to the w3wp.exe process, and if so are your breakpoints hit then?
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With