When everything works
If everything was always working, I wouldn't be writing about it today. There's plenty of guides to show you how to do remote debugging, when everything is fine.
In my experience - more often than not - there's always some crucial little step, preventing you from quickly attaching a debugger and finding the exact cause of that elusive error that you just can't reproduce on your local environment.
Remote debugging has saved me HOURS of trying to get to that one error that only one of your users is experiencing in production.
Under normal circumstances, you would
- publish your Web App from Visual Studio in debug mode.
- go to your Cloud Explorer, scroll down to your web app
- click Attach debugger (this will activate remote debugging if not already active)
What can possible go wrong?
Well, you could:
- not be able to publish for some reason
- have forgotten to put it in Debug mode
- not see your Web App in Cloud Explorer, even though your seeing everything else and you DO have access in the Azure Portal and IT already verified that everything is working
(clearly, I'm speaking hypothetically, because this never happens)
Do it all yourself
Enable remote debugger
First, you'll need to enable remote debugging on your Web App.
- Go to your Web App in the Azure Portal.
- Go to Configuration > General Settings
- Enable Remote Debugging and choose your version of Visual Studio
Download the PublishProfile
The PublishProfile contains all endpoints and credentials you'll need for accessing this Web App.
You can download it from the Overview blade.
The file looks like this.
Obviously, I've fudged it a bit, so you wouldn't get any ideas of trying to mess with my app.
<publishData>
<publishProfile profileName="[yourApp] - Web Deploy" publishMethod="MSDeploy" publishUrl="[yourApp].scm.azurewebsites.net:443" msdeploySite="[yourApp]" userName="$[yourApp]" userPWD="[yourAppPassword]" destinationAppUrl="http://[yourApp].azurewebsites.net" SQLServerDBConnectionString="" mySQLDBConnectionString="" hostingProviderForumLink="" controlPanelLink="http://windows.azure.com" webSystem="WebSites">
<databases />
</publishProfile>
<publishProfile profileName="[yourApp] - FTP" publishMethod="FTP" publishUrl="ftp://[yourAppFTP].ftp.azurewebsites.windows.net/site/wwwroot" ftpPassiveMode="True" userName="[yourApp]\$[yourApp]" userPWD="[yourAppPassword]" destinationAppUrl="http://[yourApp].azurewebsites.net" SQLServerDBConnectionString="" mySQLDBConnectionString="" hostingProviderForumLink="" controlPanelLink="http://windows.azure.com" webSystem="WebSites">
<databases />
</publishProfile>
<publishProfile profileName="[yourApp] - ReadOnly - FTP" publishMethod="FTP" publishUrl="ftp://[yourAppFTP]dr.ftp.azurewebsites.windows.net/site/wwwroot" ftpPassiveMode="True" userName="[yourApp]\$[yourApp]" userPWD="[yourAppPassword]" destinationAppUrl="http://[yourApp].azurewebsites.net" SQLServerDBConnectionString="" mySQLDBConnectionString="" hostingProviderForumLink="" controlPanelLink="http://windows.azure.com" webSystem="WebSites">
<databases />
</publishProfile>
</publishData>The interesting bits are
- url - this should be "[yourApp].azurewebsites.net" (make sure there's no ".scm." part)
- userName - make sure to take the fully qualified one : "[yourApp]\$[yourApp]"
- userPWD
Attach your debugger
- In Visual Studio, go to Debug > Attach to process (CTRL-ALT-P)
- In the Connection target, paste your Url plus port 4022 (for VS2017, port 4024 for VS2019)
- In the popup-window, paste username and password
If your credentials are correct and there is no company firewall blocking your outgoing request, you should be able to see all running processes on the remote machine.
We want to attach to the w3wp.exe. If running a .Net Core application, this will be dotnet.exe.
And that's it, you are now remote debugging Umbraco (or whatever you're working on) and can put breakpoints where you think the problems occur.
Troubleshooting
Now, there are numerous things in the preceding steps that can go wrong and possibly many more that I haven't even encountered yet myself.
Cannot attach debugger
You get an error after entering the url of the Web App, or the popup asking for credentials does not appear.
It's most likely a connectivity issue.
- Check your corporate firewall.
- Check if it works from home (while not on any VPN), or tether via your mobile.
- Check your Web App for IP filtering.
Cannot activate breakpoints
The version of your code doesn't match the version running on your Web App.
- Try republishing the latest version.
- Try finding the source branch that matches this release.
If the problem you're investigating is in a specific class library, try building a new version of that project only and push that .dll and it's accompanying .pdb via Kudu or FTP (you have the ftp-credentials in the PublishProfile you downloaded earlier).
Make a backup of the existing .dll, so you can quickly revert.
