<?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>Dodfooding Challenges Part One</title><link>http://blogs.msdn.com/kevinpilchbisson/archive/2007/11/24/dodfooding-challenges-part-one.aspx</link><description>There are a couple of issues that come up for developers who work on Visual Studio that just aren't issues for most people.&amp;#160; The first is that working on components of VS while using VS is hard.&amp;#160; It's hard for a couple of reasons. You want to</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Community Convergence XXXVII</title><link>http://blogs.msdn.com/kevinpilchbisson/archive/2007/11/24/dodfooding-challenges-part-one.aspx#6720835</link><pubDate>Mon, 10 Dec 2007 11:23:43 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6720835</guid><dc:creator>Charlie Calvert's Community Blog</dc:creator><description>&lt;p&gt;Welcome to the thirty-seventh edition of Community Convergence. Visual Studio 2008 has been released&lt;/p&gt;
</description></item><item><title>Community Convergence XXXVII</title><link>http://blogs.msdn.com/kevinpilchbisson/archive/2007/11/24/dodfooding-challenges-part-one.aspx#6721016</link><pubDate>Mon, 10 Dec 2007 11:54:09 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6721016</guid><dc:creator>Noticias externas</dc:creator><description>&lt;p&gt;Welcome to the thirty-seventh edition of Community Convergence. Visual Studio 2008 has been released&lt;/p&gt;</description></item><item><title>re: Dodfooding Challenges Part One</title><link>http://blogs.msdn.com/kevinpilchbisson/archive/2007/11/24/dodfooding-challenges-part-one.aspx#6818111</link><pubDate>Thu, 20 Dec 2007 18:21:42 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6818111</guid><dc:creator>Patrick Greene</dc:creator><description>&lt;p&gt;What about virtual machining the development PC to eliminate the need for an old remote PC?&lt;/p&gt;</description></item><item><title>re: Dodfooding Challenges Part One</title><link>http://blogs.msdn.com/kevinpilchbisson/archive/2007/11/24/dodfooding-challenges-part-one.aspx#6821412</link><pubDate>Fri, 21 Dec 2007 01:57:10 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6821412</guid><dc:creator>kevinpilch-bisson</dc:creator><description>&lt;p&gt;Hi Patrick,&lt;/p&gt;
&lt;p&gt;That's a valid option too. &amp;nbsp;I happen to use a lot of RAM while developing, and since I still have an old machine, I find it works better.&lt;/p&gt;
&lt;p&gt;There are also an (admittedly small), number of scenarios you can't test in a VM, like the smart device emulator.&lt;/p&gt;
</description></item><item><title>Getting on the virtualization bandwagon</title><link>http://blogs.msdn.com/kevinpilchbisson/archive/2007/11/24/dodfooding-challenges-part-one.aspx#8869819</link><pubDate>Fri, 15 Aug 2008 17:55:48 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8869819</guid><dc:creator>kevinpilch-bisson's WebLog</dc:creator><description>&lt;p&gt;Lately I've been trying to support work happening in a variety of our development branches, and that's&lt;/p&gt;
</description></item></channel></rss>