In Part 3, we pulled back the curtain on Visual Studio Publish to gain insight into what it was doing in order to deploy our NServiceBus endpoint to Azure. Using that newfound knowledge, we'll be "graduating" from right-click/Publish to Azure DevOps.

In Part 2, we used Visual Studio's Publish feature to deploy our NServiceBus endpoint to an Azure App Service, and after only one manual change in the Azure Portal, saw our endpoint successfully running by viewing the app service logs. In this post, we'll be pulling back the curtain on Visual Studio Publish to examine what's happening in your local solution and in Azure.

In the last post we coded an NServiceBus endpoint running in a hosted service in the .NET Core generic host. Now that we have an endpoint, how do we deploy it to an Azure App Service? Like all things in life, when in doubt, right-click! More specifically, right-click, Publish.

As the cloud slowly becomes the norm rather than the exception, frameworks built with .NET have to find a way to run in new cloud-based hosting models. This post is the first in a series on how to code, build, deploy and run an NServiceBus endpoint in Azure App Services.