Deploying a .NET application using Azure CLI sounds like an easy job. And it usually is. As with everything, sometimes problems occur, but with the help of Google (well, StackOverflow, mostly), you should be able to solve them.…
So you deployed your application to Azure App Service and are waiting for the 503 Service Unavailable status to go away, and it finally does. But instead of your app, you see an error that tells you nothing. It happens to everybody, and it might not be your fault at all!…
Recently I've been working on a little .NET 6 side-project. I used the Publish Profile from Azure Portal and successfully deployed it. To make my life easier, I decided to automate the deployments.…