For other people struggling with this, it turns out that VS2015, even with all the latest updates, does not "know" about the work of dnx under Azure. Therefore, it joins the wrong process on the Azure site.
After doing "Debugging the Debugger" in Cloud Explorer or Server Explorer, you should go to Debug β Attach to Process and do two things:
- change the qualifier so that it points to a remote Azure site
- manually connect to the dnx.exe process
The first step seems to be "remembered" by VS 2015. The second step is definitely not; You must do this every time you make a remote debugging application.
In addition, you need to update the site in your browser by doing all this to start the debugging cycle.
Here's a link that explains this a bit more: https://blogs.msdn.microsoft.com/webdev/2016/03/21/remote-debug-aspnet-core-on-azure/
source share