Writing the application is the part you control. Getting it running somewhere, repeatedly and without a person in the loop, is the part this page covers.
Three strands run through it. Azure, because it is where most .NET teams end up. Docker, because it is how the thing gets packaged wherever it runs. And continuous integration, because a deployment nobody can repeat is a deployment nobody should trust.
Azure Services
The Azure services a .NET application actually uses, each with the code that talks to it.
- Azure Table Storage with ASP.NET Core
- Azure Queue Storage with ASP.NET Core
- Download Multiple Files From Azure Blob Storage
- Azure Cosmos DB with ASP.NET Core Web API
- Azure SQL with ASP.NET Core Web API
- Introduction to Cloud Computing and Azure
- Creating Business Workflows with Azure Logic Apps
- Using Azure WebJobs in .NET Applications
- Creating Serverless Apps with .NET using Azure Functions
Deploying to Azure
Getting the application from a repository into a running Azure service.
- Publishing an ASP.NET Core App to Azure App Service Using Visual Studio
- Deploying ASP.NET Core Web API to Azure API Apps
- Continuous Deployment from GitHub to Azure App Service
- How to Easily Deploy ASP.NET Core Web API to Kubernetes Cluster on Azure
Docker
Packaging the application so it runs the same way everywhere, and the registry it lives in.
- Top Docker Monitoring Tools
- Docker Hub vs Creating a Local Docker Registry
- Continuous Integration with TeamCity and Docker
- Continuous Integration with Jenkins and Docker
- Preparing a Continuous Integration Environment for Docker
- Why Docker: The Docker CLI Through Examples
- Adding MySQL to ASP.NET Core App With Docker Compose
Deploying to Linux
Hosting behind Apache or nginx, for when the answer is not a cloud service.
- Deploy ASP.NET Core Applications on Linux With Apache
- Deploy ASP.NET Core Application on Linux with Nginx
Continuous Integration
Building and testing on every push, which is where most of the value of a test suite is actually collected.
- What Is Continuous Integration?
- Top 8 Continuous Integration Tools
- Continuous Integration Tools for Mobile vs Web. What's the Difference?
More Deployment
The rest, including the deployment parts of the Web API series.
Where to Go Next
What you are deploying:
The first deployment should be the boring one. If getting version one into production is exciting, every version after it will be too.
