<?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>A VS plugin to background-run your code and see the output (Lucian Wischik)</title><link>http://blogs.msdn.com/vbteam/archive/2008/10/18/a-vs-plugin-to-background-run-your-code-and-see-the-output.aspx</link><description>Say you're demonstrating some code at a conference. What's the best way to do it? If you show only the code window, then you're counting on the audience's imagination about how the code will work (and their trust that it does!). But if you hit F5 to run</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: A VS plugin to background-run your code and see the output (Lucian Wischik)</title><link>http://blogs.msdn.com/vbteam/archive/2008/10/18/a-vs-plugin-to-background-run-your-code-and-see-the-output.aspx#9005105</link><pubDate>Sat, 18 Oct 2008 20:15:31 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9005105</guid><dc:creator>Michael Bakker</dc:creator><description>&lt;p&gt;This is a truly nice feature. It may help those people &amp;nbsp;- like me - who have trouble visualizing the output of their own convoluted codes, and thus do some simple testing and speed up the let's call it 'realization delay', i.e. the time it takes to realize that this is not the way to go..&lt;/p&gt;
</description></item></channel></rss>