Azure Data Studio is a new open source, cross-platform database tool from Microsoft that offers a modern editor experience with IntelliSense, code snippets, source control integration, and an integrated terminal. In this first look I'm going to try out the new editor and two of my most common data related tasks: Backup and Profiling.

HTTPS has become a basic requirement for a website, I want to show I added a free SSL certificate from Let's Encrypt to my website running on Azure App Service.

I wrote once previously about how I used EF Core migrations to upgrade production database. I have two slots production and staging and I swap them every time I push new code that don't involve database changes. This week I had to make a data change to production database, it's a reminder of when to use the Swap with preview feature provided by Azure App Services.

I recently made some progress on this blog and wanted to push the latest changes live. I've been using EF Core migrations to assist with any data related changes, and it has worked out very well in development. When it's time to push to production, I think it should also work just fine but nonetheless I want to see what others think about using EF migrations against a production database. So I found this StackOverflow question Is it OK to update a production database with EF migrations? The short answer is YES!

When you create an Azure Web app, you are given an Azure website URL like mine fanray.azurewebsites.net, in this post I will show how to 1) use my custom domain fanray.com instead of fanray.azurewebsites.net and 2) buy an SSL certificate so my site URL can use HTTPS instead of HTTP.

Fanray can be deployed to any environment .NET Core runs on, Azure App Service is the best choice for most web apps. In this post I will show you how to set everything up and running on Azure!