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 c
I ran into this issue a few times.
I got it fixed by making sure the platform/configuration of my publish profile matched my local build platform/configuration.
I was publishing Debug | Any CPU, but my local build was using Debug | Mixed Platforms.
Once I changed my publish configuration to Debug | Mixed Platforms and republished, I was able to attach the remote debugger and the symbols were loaded.
Verify the symbols are loaded for the assembly you are attempting to set breakpoints in by looking in the Visual Studio 'Modules' window for the namespace/assembly name. (This is after attaching the debugger to the remote process and your VS is in Debug mode.)
After I did this, breakpoints began working for the remote process from within my local VS instance.