<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.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>Windows 7 Application Compatibility Toolkit 5.5: Interview with Jeremy Chapman</title><link>http://blogs.technet.com/springboard/archive/2009/04/03/windows-7-application-compatibility-toolkit-5-5-interview-with-jeremy-chapman.aspx</link><description>Hello again from Redmond. Let’s talk compatibility – a big component of any operating system deployment project is knowing what applications, hardware and devices your users have and whether they will work on the new OS. With Windows 7 approaching fast,</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Topics about Printers  &amp;raquo; Archive   &amp;raquo; Windows 7 Application Compatibility Toolkit 5.5: Interview with&amp;#8230;</title><link>http://blogs.technet.com/springboard/archive/2009/04/03/windows-7-application-compatibility-toolkit-5-5-interview-with-jeremy-chapman.aspx#3222213</link><pubDate>Sat, 04 Apr 2009 03:24:28 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3222213</guid><dc:creator>Topics about Printers  &amp;raquo; Archive   &amp;raquo; Windows 7 Application Compatibility Toolkit 5.5: Interview with&amp;#8230;</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://printers.linkablez.info/2009/04/03/windows-7-application-compatibility-toolkit-55-interview-with/"&gt;http://printers.linkablez.info/2009/04/03/windows-7-application-compatibility-toolkit-55-interview-with/&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>Application Compatibility Toolkit for Windows 7</title><link>http://blogs.technet.com/springboard/archive/2009/04/03/windows-7-application-compatibility-toolkit-5-5-interview-with-jeremy-chapman.aspx#3222217</link><pubDate>Sat, 04 Apr 2009 03:48:55 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3222217</guid><dc:creator>The Edge</dc:creator><description>&lt;p&gt;Windows 7 will be here before you know it. So far, Windows 7 is getting much attention and rave reviews&lt;/p&gt;
</description></item><item><title>re: Windows 7 Application Compatibility Toolkit 5.5: Interview with Jeremy Chapman</title><link>http://blogs.technet.com/springboard/archive/2009/04/03/windows-7-application-compatibility-toolkit-5-5-interview-with-jeremy-chapman.aspx#3222228</link><pubDate>Sat, 04 Apr 2009 05:16:03 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3222228</guid><dc:creator>someone</dc:creator><description>&lt;p&gt;My biggest gripes with app compatibility during the Vista timeframe were broken Microsoft apps like Visual Studio .NET 2003 and Office XP. When Vista was released, VS 2008 wasn't released, so 2003 was just a version older. Microsoft did not care about those customers citing excuses like insufficient resources. Will Windows 7 rescue Microsoft broken apps? Microsoft is trying to positive spin on Windows 7 by saying there won't be app compatibility issues like Vista, but the issues are still there for XP migrations. MS has no solution to that. Why not make application virtualization available to small business and home users?&lt;/p&gt;
</description></item><item><title>re: Windows 7 Application Compatibility Toolkit 5.5: Interview with Jeremy Chapman</title><link>http://blogs.technet.com/springboard/archive/2009/04/03/windows-7-application-compatibility-toolkit-5-5-interview-with-jeremy-chapman.aspx#3223113</link><pubDate>Mon, 06 Apr 2009 22:54:13 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3223113</guid><dc:creator>exexpat</dc:creator><description>&lt;p&gt;There seems to be a lot of misperception about application virtualization and compatibility. App-V does not fix application-to-OS compatibility. It does change how apps are provisioned and app-to-app issues (run multiple versions of same app for example), but app-v doesn't fix application compatibility as described/sought above.&lt;/p&gt;
</description></item></channel></rss>