Create and Configure a SQL Database and ASP.NET Core Web API in Azure: Dev To Azure - Part 2

We walk you through how to create and configure a SQL server, SQL Server database and ASP.NET Core Web API in Azure.

As well as setting up the servers, we demonstrate how to successfully integrate a Web API with a database so the two can communicate with each other.

In addition, we will show you how to set up continuous integration (CI), or continuous deployment (CD). Through Azure Devops, we set up a release pipeline for the ASP.NET Core Web API.

Once a commit is made to a particular branch, Azure Devops automatically builds the ASP.NET Core Web API and releases it to the relevant Azure server.

This continues our four-part "Dev To Azure" series. In part 1, we went ahead and set up a Blazor Wasm and ASP.NET Core Web API application in Azure Devops. You can view it here:

In later episodes, we will deploy our Blazor Wasm application and set up continuous integration. In addition, we will look at access restrictions & errors when running an ASP.NET Core application in Azure.

📖 Learn .NET and C# with our online courses 📖

#azure #webapi #sqlserver

[RewStein]

I got it Awesome Video Still Took a little while after

[MarkInChicago]

Thanks for the videos Dave. There is something I'm missing though. I saw you setup the connection string in the API, but how/what do you need to change/code in the API so it picks up the connection string from Azure that points to the SQL DB in Azure? When you code locally, the connection string points to your local DB. When you move code to Azure, how does the connection string in AppSettings.json get swapped from the local DB to the DB in the cloud?

[Aaron-henj]

I wish I found this a few days ago. I was stuck in Azure hell for a while setting up this shit.

[RewStein]

How did you create the database to export into azure? How did you get it to find your azure database while exporting it out into azure?