Marcel Dutt

I am facing a similar issue. I want to export a solution from the DEV system and import it into another Sandbox system (aka the next stage). I can connect...

> The weird part is that the exact same connection string works for the source system. The only difference between the two is that the destination system has only recently...

I would also like to see this feature implemented

This also is true in another case I encountered yesterday. A developer used an extension to mimic `!string.IsNullOrEmpty(instance)` so he can write `instance.IsNotNullOrEmpty()`. This is currently not recognized by the...

@fiveisprime Could you please give an update on this feature? This issue is open for 4 years now and developers and other IT personnel out there struggle with this shortcoming...

@JasonYeMSFT That's great! Thank you for implementing this! Will it also provide a possibility to export the queried results?

@xiaxyi Yes, that is correct. Some context for you: in our non-production environments we use consumption plans to keep the costs low. In the stage and production environments we use...

Thanks for the workaround! I also noticed that I have to use version 3 of the task to trigger even classic pipelines and if I set the branchName there, the...

> [@brianhodgman](https://github.com/brianhodgman) > > One could use a workaround, as mentioned in this comment: [#25406 (comment)](https://github.com/Azure/azure-cli/issues/25406#issuecomment-1438417076) > > ``` > # This is a workaround for a bug in Azure...

> Hey [@sit-md](https://github.com/sit-md), maybe try the above to see if that works for you? This did it for us. Thank you very much! Pipeline is up and running again 👍