My debugger stopped working as expected in Visual Studio Community 2015 (Update 1).
The solution I'm working on has the following architecture:
I run the Query project, it checks for session and redirect to Login. After the login is successful it makes another redirect back to the Query url. Until yesterday I had no issues debugging the whole solution from VS directly. Now the behavior is that the first time I run the "Query" project, my breakpoints get hit. After ing back from Login, no breakpoint is hit.
Both client-side projects are hosted using IIS Express.
Things I tried until now:
Also good to mention that I have set in web.config:
<pilation debug="true"></pilation>
Any hint or idea is highly appreciated.
My debugger stopped working as expected in Visual Studio Community 2015 (Update 1).
The solution I'm working on has the following architecture:
I run the Query project, it checks for session and redirect to Login. After the login is successful it makes another redirect back to the Query url. Until yesterday I had no issues debugging the whole solution from VS directly. Now the behavior is that the first time I run the "Query" project, my breakpoints get hit. After ing back from Login, no breakpoint is hit.
Both client-side projects are hosted using IIS Express.
Things I tried until now:
Also good to mention that I have set in web.config:
<pilation debug="true"></pilation>
Any hint or idea is highly appreciated.
After trying more different solutions, the only thing that worked in my case was to unload/reload the project. Also, now the breakpoints that I set before the application runs are no longer getting hit, but if I set them after the application started then they work fine.
I can suggest some Stack Overflow answers related to this issue, maybe it helps:
New project and just importing the files into it: Upgrade to Visual Sudio 2015 and now can't hit break points in debuging
Manual check of the Symbol Load Information: Fixing "The breakpoint will not currently be hit. No symbols have been loaded for this document."
Incorrect configuration selected in the debug menu: Visual Studio breakpoints not being hit
In my case (Vs2019) the Microsoft Symbol server was causing the issue.
It was not being able to attach Local IIS.
Enabling only the NuGet Symbol server and disabling the Microsoft worked for me