This is the second in a series of sketchnotes documenting different aspects of Azure and related technologies. Hopefully you find a few gems that lead to a better understanding of Azure.
Azure For Developers
Azure Redis Cache
One of the aspects of Azure development that I have found the least amount of information written about is the deployment of your application components. This is especially the case when it comes to ALM (Application Lifecycle Management) approaches are considered. As with most things you get the WSYWG demo, but not how things should actually be done in an enterprise environment. This post will try to cover as many deployment approaches as possible. While it won’t be comprehensive it will give you enough alternatives to start coming up with your own processes.
This is usually where every demo of Azure development begins and ends. You right your web app or cloud service and “Poof!”, your solution magically ends up in your Azure environment. In this scenario you use the publish option of the project context menu to open a wizard that allows you to connect to an Azure subscription and define where you what site or service you want to publish too. The process is even simpler if you defined these parameters when you created the project.
While creating web jobs I came across this method of deployment. You zip up your web job solution and go to Web Jobs under Settings for your Web App and you will see the blade shown below. You can learn more about this in my earlier post here.
This is the point where we get to a manageable deployment process. Once you have finished coding your Cloud Service you can go to the project in Visual Studio and create a deployment package using the context menu shown below.
Once you have that visit your cloud service in the portal and select the Update button. The blade in the figure below will appear and allow you to upload the package and the appropriate configuration. Azure will then complete the deployment from the provided resources.
If you like to be hands on FTP may be the deployment approach that is right for your team. It should be familiar to anyone who is used to manually copying their files to a web server. Once you go into Deployment Credentials for your Web App as shown below and then grab the FTP host name from the properties page you will be able to navigate straight to the wwwroot directory and copy your application files to the server.
From Source Control
Any of us who have been in this game for a couple of decades know that automated builds and deployments save a lot of manual deployment mistakes. Thankfully we have a number of options for deploying from source control to Azure. Rather than explain each I’ll put a couple of links here that do a good job of explaining the process of setting these scenarios up..
Visual Studio Online
TFS On Premis
This post gives just a quick taste of Azure deployments from the quick and dirty options to methods better suited for enterprise developments processes. Be sure to try as many of them out as possible to understand they fit with your development team.