﻿<?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 Managing Complex Build Scripts: Quick &amp; Dirty Solutions</title><description>It is already on SVN, but this is what I define as a utility, not real code. This means that it is there to serve a very specific need, and may be in appropriate for many scenarios.
  
https://rhino-tools.svn.sourceforge.net/svnroot/rhino-tools/trunk/Utilities/BuildEditor
</description><link>http://ayende.com/2422/managing-complex-build-scripts-quick-dirty-solutions#comment3</link><guid>http://ayende.com/2422/managing-complex-build-scripts-quick-dirty-solutions#comment3</guid><pubDate>Tue, 22 May 2007 05:37:04 GMT</pubDate></item><item><title>shawn commented on Managing Complex Build Scripts: Quick &amp; Dirty Solutions</title><description>This is pretty cool. Right now we're using multiple CCNet projects to accomplish a much less complete version of this. Are you planning on adding this to Rhino.Commons or something?
</description><link>http://ayende.com/2422/managing-complex-build-scripts-quick-dirty-solutions#comment2</link><guid>http://ayende.com/2422/managing-complex-build-scripts-quick-dirty-solutions#comment2</guid><pubDate>Mon, 21 May 2007 23:57:09 GMT</pubDate></item><item><title>Tomas Restrepo commented on Managing Complex Build Scripts: Quick &amp; Dirty Solutions</title><description>Around here, that's what we call "engineer's UI" :)
  
Looks pretty cool, though!
</description><link>http://ayende.com/2422/managing-complex-build-scripts-quick-dirty-solutions#comment1</link><guid>http://ayende.com/2422/managing-complex-build-scripts-quick-dirty-solutions#comment1</guid><pubDate>Mon, 21 May 2007 23:55:19 GMT</pubDate></item></channel></rss>