<?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>LiveRun - a VS plugin to see the output of your program immediately</title><link>http://blogs.msdn.com/lucian/archive/2008/10/16/liverun-a-vs-plugin-to-see-the-output-of-our-program-immediately.aspx</link><description>Say you're demonstrating a compiler at a conference. What's the best way to do it? Should you just type in code in the code window? Doing this, you're relying on the audience's imagination -- that they form a mental picture of how the program will behave.</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: LiveRun - a VS plugin to see the output of your program immediately</title><link>http://blogs.msdn.com/lucian/archive/2008/10/16/liverun-a-vs-plugin-to-see-the-output-of-our-program-immediately.aspx#9011635</link><pubDate>Wed, 22 Oct 2008 23:17:25 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9011635</guid><dc:creator>DonXML</dc:creator><description>&lt;p&gt;Nice idea, but it would be even cooler if you used a MSUnit project type and displayed the test results (and Console if you had to). &amp;nbsp;It would encourage folks to write unit tests.&lt;/p&gt;
&lt;p&gt;I prefer using MSUnit (or any xUnit framework) over console projects to demo code.&lt;/p&gt;
</description></item></channel></rss>