Clever Geek Handbook

Failed to debug Azure Websites - webjob processes are not showing in the Attach to Process dialog

Visual Studio 2013 Update 3. I have deployed several Webjobs for Azure, both manually (download the package through the portal) and publish directly from Visual Studio. The web objects I am testing with are set to run "Continuous" and have code that runs inside while (true) {} loop; therefore, the process never ends. The Webjobs are functioning as expected and I can see their output at runtime in the Log Output screen of the Webjobs Toolbar.

I have enabled remote debugging on the website. When I select Debug, Attach to process, the webjob process names never appear in the list. All I can see are the remote debugger and w3wp.exe processes.

Attach to process dialog box

Ideas?

+3


source to share


1 answer


Instead of connecting to SITENAME.azurewebsites.net, try connecting to SITENAME.scm.azurewebsites.net. Use the same credentials as for a regular debug connection. WebJobs run in a different context (Kudu), hence different endpoints.



+8


source






More articles:


All Articles