<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://msmvps.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Rules for Framework Development</title><link>http://msmvps.com/blogs/rohanthomas/archive/2006/11/07/Rules-for-Framework-Development.aspx</link><description>Something i came across while i was developing a framework for one of my clients. Source : Brian Button&amp;#39;s Blog Brian&amp;rsquo;s Handy Dandy Rules for Framework Development Clients come before frameworks Ease of use trumps ease of implementation Quality</description><dc:language>en</dc:language><generator>CommunityServer 2008.5 SP2 (Build: 40407.4157)</generator></channel></rss>