To begin setting up Azure Continuous Delivery, you must first have Visual Studio Team Services (Team Services for short). You can also use GitHub as your repository source, but I will be covering Team Services in this series. If you do not have Team Services, you can sign up on https://www.visualstudio.com/, for free (for up to 5 team members).
After creating your Team Services, you need to set up a project by clicking the dropdown in the top left, where the Visual Studio logo is. For the purpose of setting up continuous delivery, what you enter in the project creation form doesn’t matter. I made my project to use an Agile process template and Git as version control.
Next you need to create a code repository. You can do this via the “Code” dropdown at the top, into “Manage Repositories”. This takes you to a page with an option to create a new repository. Give it a name and hit create.
Now that you have a repostiory for code, you can add your code to that repository. To get started, you can connect your Visual Studio to your Team Services. On the “Home” page, there should be an option to “Open in Visual Studio” (for me, this was located in the bottom right). You’ll be asked to authenticate and allow you to add your Team Service project into your Team Explorer.
Adding a new .net core application is as easy as clicking the “New” link in the Solutions area of Team Explorer (on the “Home” of Team Explorer). You can then commit the new project via the “Changes” option, and then push the code via the “Sync” option.
Moving on to the Azure connection to Team Services, from the Azure Portal, you have to add in your Team Services account. This seems to be a bit hidden in Azure Portal, but you should be able to find it in the “More Services” option on the sidebar and filtering on “Team Services accounts”. Add in your account and then in the Team Services blade, you can “Link” it at the top.
That’s it for part one. To recap, we create a Team Services account, create a Project in Team Services, create a new repository, link Visual Studio to Team Services, and then link Team Services to Azure.
Stay tuned for Part 2 – Azure App Service setup