Tom Conneely

Sign in

Azure DevOps

Using XML Transformations when deploying to Azure App Service using VSTS

Using XML Transformations when deploying to Azure App Service using VSTS

I recently changed some web apps that had originally used the Azure Cloud Service (Classic) to use the newer Azure App Service mainly to bring the deployment time down without having to sacrifice the app's performance. We already have a CI build and release process and I needed

Using AssemblyInfo in Deployment Labels in VSTS Release Defintions

The Problem Like I wrote in my previous post [https://tommyconneely.com/using-assemblyinfo-in-vsts-build-numbers/], the company I work for have used the assembly version for keeping track of deployments and we wanted to continue this practice when moving to use VSTS build and release management. We currently use the Azure Cloud

Using AssemblyInfo in VSTS Build Numbers

Using AssemblyInfo in VSTS Build Numbers

The Problem The company I work for have used the assembly version for keeping track of deployments and we wanted to continue this practice when moving to use VSTS build and release management. You can set the build name in the Options tab of the build definition. You can see

Fix for Gated Check-In "Shelveset could not be found" Error in VSTS

I ran into some trouble at work this week when the gated check in builds that I had setup using Visual Studio Team Services suddenly stopped working. The builds were completing but failing on the final step when the when the gated changes were due to be checked in. I