I've got an ASP.NET website that I deployed to Azure. I'm using VS2013, .NET 4.5.1 and Azure SDK 2.2. I turned on remote debugging for VS2013 in the management portal. I can successfully right click the website under the "Azure" node in servers, and select "Attach debugger." It says that it is downloading debugging settings, and then the web browser comes up. But breakpoints are never hit despite them being in code that I know is executed. One clue: the breakpoint has an open circle and states: "The breakpoint will not currently be hit. No symbols have been loaded for this document." But the breakpoint works fine when testing locally. Does anyone have any thoughts on how to address this?
Thanks...
-Ben
Update: I dropped from .NET 4.5.1 to 4.5; problem persists.
Make sure you publish a debug build to a specific deployment slot. I had this same problem and when I attached the remote debugger to my staging slot that had a debug build deployed there, it worked. Trying to debug a release build doesn't work because the requisite debug symbols are not present. Like @Lars explains above, I had to restart the web app on Azure and then try the debug again against the debug build.
I also struggled with this (VS2015 Enterprise) but found a solution that works pretty consistently.
This works for me almost every time. Note that stopping and starting the web app from w/in Visual Studio does not work consistently.
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