I just upgraded from Visual Studio 2013 to 2015 and now I am having trouble with breakpoints.
It\'s a hit or a miss where break points will actually work and if I se
In my case, there was a new web.config file created after I use Profiler
. Restoring web.config to the previous version, resolved this issue. It was a VS2015 C# web application.
VS breakpoints cannot bind on async methods.
I had an App Dynamics agent installed that caused this. Remove that and you are good to go.
While this is a much later build (VS2017) I had this issue with C# projects. Tried cleaning, rebuilding, restarting visual studio, etc.
What fixed it was closing Visual Studio and deleting the .vs folder, which is a hidden folder located in the solution directory. Deleting the .vs folder should not cause you any problems, although you will need to reset your startup project.
This may seem trivial, but after a lot of headscratching with the same issues as you mention, I found out that my build was set to "release" instead of "debug" when I tried debugging.. re-building the solution for "debug" fixed it, and I could set breakpoints as normal
I didn't change the 'optimize' setting, but based on other answers here, I
So far this has fixed it for me. Seems like updating to VS2015 Update 2 has borked a few things on my system.
In case you are publishing your web-application check that Configuration
is set to Debug
(by default in debug configuration is set such that code not is optimized and symbol table is fully created).