Publish fails if one of multiple subscription cannot register the Azure DevSpaces provider about dev-spaces HOT 16 CLOSED

@GiancarloLelli could you make sure you have the latest VS extension installed? We had an issue with multiple subscriptions in the past and this might help.
@mthalman-msft could we have a better handling of scenarios in which we cannot register our provider in all the subscriptions that are accessible to the user?

from dev-spaces.

@lolodi I've checked and it looks like I have the latest version of the tooling. See below.

from dev-spaces.

@GiancarloLelli Would you be able to provide some more diagnostic information? I'm wondering whether there's an underlying exception being thrown that could provide more context. Can you please attach a second instance of VS to the VS instance that produces this error. And then configure the debugging VS instance to break on exceptions. The exception to look for is named InvalidUsageException. I'm interested in knowing if it has an InnerException and what the details of that InnerException are.

from dev-spaces.

@mthalman-msft I don't see any exception being thrown. Once this dialog pops up the output window is clear and it only displays the AppInsights Telementry logs.

from dev-spaces.

Have you disabled the "Enable Just My Code" option in Tools -> Options -> Debugging?

from dev-spaces.

@mthalman-msft Right, forgot about that - now I can see the exception.

I'm unable to load the PBDs to drill down with historical debugging, if you can help me with that I can see if I can gather some more detailed information.

from dev-spaces.

Yeah, that's just showing what we already know from the error message. I need to know what the InnerException is. You shouldn't need to use historical debugging. Just configure VS to break on all CLR exceptions and keep executing until you hit this InvalidUsageException. Then you should be able to examine its InnerException.

from dev-spaces.

Gotcha - but it is the same message, even the Inner exception.

from dev-spaces.

Ah, got it. This should give us the required information we need to fix the bug anyway. I would anticipate we can have a fix available for next week. Unfortunately, there's not a workaround at this time.

from dev-spaces.

Great, glad I could help :)

from dev-spaces.

Im facing exactly the same error. It seems that VS extension validate DevSpaces against all the subscriptions, and if one of them failes (in my case DreamSpark subscription which doesn't has permission to register this provider) - whole extension fail, and i cannot set-up DevSpace in another subscription. There is no workaround for this? :(

from dev-spaces.

@darthkurak sorry to hear you are hitting it too :( The fix for this problem is checked in, but we've had some unrelated issues that have prevented us from releasing a new version of the extension. I'm pushing to get an updated build released in the next few days. I'll keep you posted.

from dev-spaces.

Hi @GiancarloLelli and @darthkurak - we just pushed a new version of the extension that should address this issue. Can you give it a shot and let me know if it helps? Thanks!

from dev-spaces.

Hi! It works now! Thanks for quick response.
I wonder - this debugging feature doesn't work for .net core console app in AKS? Because, i cannot choose Azure Dev Space when switching to it. :(

from dev-spaces.

Dev Spaces doesn't currently support console apps, but we've gotten that feature request from other customers as well, and it's under consideration :)

from dev-spaces.

@lisaguthrie @mthalman-msft Thanks guys. It works now :)

from dev-spaces.