<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.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>Code Coverage Instrumentation</title><link>http://blogs.msdn.com/phuene/archive/2007/05/03/code-coverage-instrumentation.aspx</link><description>For my first on-topic blog post, I would like to give an overview of how code coverage instrumentation works in Visual Studio (it seems like a good a place to start as any). For basic information about what code coverage is, check out wikipedia's Code</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Code Coverage Collection</title><link>http://blogs.msdn.com/phuene/archive/2007/05/03/code-coverage-instrumentation.aspx#2632925</link><pubDate>Mon, 14 May 2007 23:52:38 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2632925</guid><dc:creator>Peter Huene's Blog</dc:creator><description>&lt;p&gt;By the end of my last post about code coverage instrumentation , we have instrumented our executable&lt;/p&gt;
</description></item></channel></rss>