Friday, 29 November 2013

One configuration file to rule them all. Automated deployment for multiple .NET websites.

Spring is almost over and my garden is now full of weeds (especially that evil crab grass), apart from a two metre square where I went nuts for an hour.
So naturally, being at one with nature, I was thinking about build and deploy scripts. About the sticky tape and chewing gum shambles of third party libraries and configuration it's been my pleasure to marshall into release packages over the years.
Image of overgrown garden
It doesn't have to be that way.  As I watch a line of ants crawl up a weed into the car..
Build and deployment can be challenging to manage. I have settled on a strategy I find flexible enough to cope with complex web deployments and easy enough to reliably maintain.

The Plan

So in short, here's the plan