• When I put up a new website in Azure I tend to run into the same problems. Pointing DNS to the azure website nets a lot of urls. I'll have mydomain.com, www.mydomain.com, mydomain.azurewebsites.net, and http/https versions of all of them. When talking SEO, you generally don't want duplicate ways to get to the same content. Luckily, this can be solved relatively painlessly with url rewrites in the web.config. I put together a quick reference to handle some of the scenarios.
    approx. 2 minutes. Software    azure asp.net
  • You can publish to Azure websites a number of ways. They all have their strengths and weaknesses so I tend to change them up depending on the situation. If I'm trying to get something quickly up to Azure I'll go with the git deployment. If I want full continuous integration I'll generally go WebDeploy and automate with continuous integration. This article explains how to deploy a .Net Core application to Azure websites using git.
    approx. 3 minutes. Software    .net core azure git
  • I was doing my usual Azure publishes when all of a sudden Visual Studio would hang with the “Visual Studio is Busy.” error. After hours of messing with stuff I found that if you go to your server explorer in visual studio the Azure section said “Reenter credentials.” Once I did that everything was working fine. Hope it helps someone else.
    approx. 1 minutes. Software    azure