<?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>WPF Composite Client</title><link>http://blogs.msdn.com/b/blaine/archive/2007/10/29/wpf-composite-client.aspx</link><description>The Acropolis team just announced that the core Acropolis concepts will be rolled into future .NET Framework releases. As Glenn just announced, the patterns &amp;amp; practices team will develop WPF Composite Client guidance. This is not a new version of</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>The future of WPF Guidance</title><link>http://blogs.msdn.com/b/blaine/archive/2007/10/29/wpf-composite-client.aspx#5770206</link><pubDate>Mon, 29 Oct 2007 22:54:02 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5770206</guid><dc:creator>Espresso Fueled Agile Development</dc:creator><description>&lt;p&gt;There is a lot of new information, all announced today, about the future of Acropolis, CAB, and WPF guidance&lt;/p&gt;
&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=5770206" width="1" height="1"&gt;</description></item></channel></rss>