WarmuP allows you to define templates for entire projects and change them as technology changes and you learn new things. The templates are kept in source control. Both SVN and Git are supported places to keep your templates. You can also keep your templates in folders and that is the default methodology used currently.
WarmuP is not just about Visual Studio solutions, it can template any set of text files/folders.
See the following post by Rob - Getting Started.
You define a template using
__NAME__ (note the double underscore) as part of file/folder names and inside of files. Then you run WarmuP telling it what you want to replace
In the location you want the generated template to reside run:
[warmuppath]warmup template replacementName [targetDirectoryIfDifferentThanReplacementName]
warmup mvctemplate NewBob
Ensure that the warmup.exe.config has the correct path to your templates.
WarmuP will also replace custom tokens with pre-configured values.
You can add custom replacement tokens to WarmuP by adding them to the configuration. You can also run a command to add them to the configuration from the command line. WarmuP will also perform file/folder and text replacement for these values like it does
`warmup addTextReplacement findName replacementName`
warmup addTextReplacement __COMPANY__ "Somewheres, Intl"
WarmuP uses symbolic links to add new templates to the template folder and will actually create the template folder in the correct location for the first template you add if it doesn't exist. This allows you to keep your templates in disparate locations and still take advantage of WarmuP from a central usage location.
`warmup addTemplateFolder templateName "fullPath"`
warmup addTemplateFolder mvctemplate "c:\code\somefolder\somerepository\mvctemplate"
If you have Ruby 1.8.6+ (and Gems 1.3.7+) installed, you can get the current release of WarmuP to your machine quickly!
If you have Chocolatey installed, you can get the current release of WarmuP to your machine quickly!
Also available through NuGet - WarmuP
This is the best way to get to the bleeding edge of what we are doing.
git clone git://github.com/chucknorris/warmup.git
build.bat. NOTE: You must have git on the path (open a regular command line and type git).