<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: About-city</title>
	<link>http://thediscoblog.com</link>
	<description>Can you dig it man?</description>
	<pubDate>Sat, 17 May 2008 20:30:03 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>By: Integrate Button Blog &#187; Blog Archive &#187; CI Inspection Tools for .NET</title>
		<link>http://thediscoblog.com/about/#comment-13436</link>
		<dc:creator>Integrate Button Blog &#187; Blog Archive &#187; CI Inspection Tools for .NET</dc:creator>
		<pubDate>Mon, 11 Jun 2007 21:32:15 +0000</pubDate>
		<guid>http://thediscoblog.com/about/#comment-13436</guid>
		<description>[...] In Chapter 7, Andy covers practices for automated static/dynamic analysis so that you can discover overly complex code, code coverage, or code that doesn&#8217;t adhere to your project&#8217;s standards early in the lifecycle. He uses plenty of examples for the Java and .NET platforms. Below, is a list of inspection tools for .NET: [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] In Chapter 7, Andy covers practices for automated static/dynamic analysis so that you can discover overly complex code, code coverage, or code that doesn&#8217;t adhere to your project&#8217;s standards early in the lifecycle. He uses plenty of examples for the Java and .NET platforms. Below, is a list of inspection tools for .NET: [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
