Build and Deployment Pipeline

So this is a very behind the scenes update and has taken me a very long time to work on. I began about a month back to try and get some of the custom software we use a little more organised. Primarily this is concerning the behind the scenes admin tools that we use. We have an 'admin portal' website that allows admins to ban players from the servers, a 'rcon sync' service that monitors the servers and adds player details to a database and a 'ban sync' service that synchronises ban files across the game servers. 

The issue that I had been having is that these three applications are so tied in to each other and if I wanted to make a small change to any of them I would have to build and deploy them all which was a headache. Now each has its own Build and Deployment pipelines fully automated. The database aspect has been pulled out and is now separate with all of the applications using a NuGet package with defined contracts to access it. I would like to move to an API based data access layer in the future though. 

So what does it look like?

Here are the builds in VSTS and below that what the release process looks like for the Admin Portal website: