<?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>An in depth look at the Historical Debugger in Visual Studio 2010 (Part IV)</title><link>http://blogs.msdn.com/b/habibh/archive/2009/06/11/an-in-depth-look-at-the-historical-debugger-in-visual-studio-2010-part-iv.aspx</link><description>In this segment on the Historical Debugger, I’m going to focus on how the Historical Debugger can help in debugging Build Acceptance Test failures or what is commonly referred to as Build Verification Tests (BVTs). Imagine this scenarios: As part of your</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>Dew Drop - June 12, 2009 | Alvin Ashcraft's Morning Dew</title><link>http://blogs.msdn.com/b/habibh/archive/2009/06/11/an-in-depth-look-at-the-historical-debugger-in-visual-studio-2010-part-iv.aspx#9734013</link><pubDate>Fri, 12 Jun 2009 15:38:56 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9734013</guid><dc:creator>Dew Drop - June 12, 2009 | Alvin Ashcraft's Morning Dew</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://www.alvinashcraft.com/2009/06/12/dew-drop-june-12-2009/"&gt;http://www.alvinashcraft.com/2009/06/12/dew-drop-june-12-2009/&lt;/a&gt;&lt;/p&gt;
&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9734013" width="1" height="1"&gt;</description></item></channel></rss>