Why using a build system like Ruby rake or some other next generation tool (psake looks promising) to build your .net application or library?
A) Builds are not data. Xml is for data. It may be that the files or configurations are stored as xml, but does your build program need to be in xlm? B) Custom tasks are easy to write. Take a look at albacore for instance. C) It is easy to manage nontrivial tasks. D) It’s readable. Write your build in rake or something similar. Write it in msbuild. You will see that as usual there is a cost to writing it in xml: It adds cruft and that angle-bracket tax.
Or you might like the xml files for some reason: Jonathan Pryor: Defending XML-based Build Systems He is arguing for the use of xml-basked build files. One reason is that xml is easily parsed and can be used in custom tools.
Personally I feel that coding should be done mostly by writing code. Sure, there might be nifty code generation tools that can be used to simplify some tasks, but at the end of the day you still need to get your hands dirty and make sure that it does what it’s supposed to do.
Do you want to send a comment or give me a hint about any issues with a blog post: Open up an issue on GitHub.
Do you want to fix an error or add a comment published on the blog? You can do a fork of this post and do a pull request on github.