Templify is a simple tool that aims to solve one simple problem and solve it well:
Every project starts the same way,
You create a place to put Solution Artefacts
On one file system
On one computer
Templify allows you to create a tokenised template of your entire solution. So if you’ve got a default web application framework, which includes a build system, some deployment scripts and other goodies and you want a way to package the whole solution up and allow others to share and reuse it, Templify is the answer.
It’s now almost three years old and quite a bit has changed in the world since then one of the main things being that NuGet has appeared and made package management a thing in the .NET world. The “package restore” functionality is especially interesting, as it allows you to package up just the source files for a solution without having to include the binaries, which vastly increase the size of any redistributable zip of a solution or demo you’d want to share.
In that three year period there have only really been two major bugs reported – the first was more a complaint than a bug – sometimes packing and unpacking a Templify package could be very slow. Thankfully a kindly user of Templify decided to try and get to the bottom of the problem and fixed it. The second problem reported was that some users found that Templify altered the file encoding (it would convert a file from ANSI to UTF8) of any file it tokenised. Luckily we had already solved this problem in another one of our internal build and deployment tools, so it was quite straight forward to make an IP donation to the Templify project.
One of the other changes to happen in the last three years is that Visual Studio 2012 was released and one of its key features is that it no-longer supports Visual Studio Installer Projects, which Templify uses. So as part of this new release I’ve created a new Advanced Installer based installer and our very own Paul Waller decided to spruce up the installer graphics to align with our new brand and website.