VS2017 - connect remote debugger to azure web service.

Question

4.50/5 (2 votes)

See more:

Hi,
We have an Azure web service running, and when I try to connect remote debug to it via "Cloud Explorer" I get the following error: "Cloud Explorer - Action is not supported in your current Azure SDK version".

If I try to connect via Debug-Attach to process:
"a-------k.azurewebsites.net:4022" I get "no connections found" (I have Show Processes from all users checked.)

Visual Studio 2017
The App service was published from my PC, using the .PublishSettings file downloaded from "Cloud Explorer".
Publisher has Debug set.
There are no pending updates under "notifications" window.

Our firewall allows port 4022.

Azure Portal
Debug is on in the Azure Portal-App Service-Gen Settings.
I am an owner of the App Service.

Remote debug worked fine when using the Azure Free Trial version, but since publishing to our corporate service it's giving the above error!

Googling "Action is not supported in your current Azure SDK version" doesn't return anything helpful.

And pointers what this could be?

What I have tried:

Googling "Action is not supported in your current Azure SDK version" doesn't return anything helpful.

Googled various combinations of how to set up remote debug...

2 days of frustration

Posted 6-Jun-19 2:39am

Member 10995123

Updated 10-Jun-19 3:56am

Add a Solution

2 solutions

Solution 1

Do you know what your current "Azure SDK version #" is?

Why do you keep ignoring that fact when it's saying that is the PROBLEM?

It would seem the logical approach is to confirm what your version # is and what is available.

You've spent "2 days" ignoring the obvious.

Azure SDK for .NET previous release downloads[^]

Posted 6-Jun-19 6:18am

Gerry Schmitz

Comments

Member 10995123 7-Jun-19 8:53am

I do have version 3.0.1 installed, - Visual Studio tends to keep it's self up to date :)

The error message seems to be a bit generic - and trust me I haven't ignored it!

BUT as I said it all worked fine, until changing server from the free trial to the corporate (paid for)! - which would make me suspect it's possibly a setting in Azure or something???

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Member 14492252 · Accepted Answer · 2019-06-10T03:56:00

I have similar issue although in my case I could not access files on webapp in Azure. Updating VS and azure development component didn't help.

What has worked for me was to revert cloud explorer to previous version:
- Launch VS in administrator mode
- From Tools menu select Extensions and Updates
- In cloud explorer extension you should see revert button
- You will have to close VS and wait for revert to take place.

hope this helps