﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Ayende Rahien commented on Working with Code, not Executable XML</title><description>The idea here is what happens when you want to use the build script as the project file for VS as well.
</description><link>http://ayende.com/2249/working-with-code-not-executable-xml#comment2</link><guid>http://ayende.com/2249/working-with-code-not-executable-xml#comment2</guid><pubDate>Fri, 23 Mar 2007 11:28:41 GMT</pubDate></item><item><title>Jeremy Miller commented on Working with Code, not Executable XML</title><description>Actually I thought Rake vs NAnt is a good example of the limitations of Xml.  NAnt holds up well for simple, straightforward build scripts.  Add in some flow control and branching and NAnt doesn't scale very well.  I've talked to a few people who've switched from NAnt to Rake even for .Net development when the project build file started to get too big and complex.  A real programming language will always be more expressive than xml.
</description><link>http://ayende.com/2249/working-with-code-not-executable-xml#comment1</link><guid>http://ayende.com/2249/working-with-code-not-executable-xml#comment1</guid><pubDate>Fri, 23 Mar 2007 11:12:10 GMT</pubDate></item></channel></rss>