<?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>MIX09 Recap series part2 ,  what about WPF</title><link>http://blogs.msdn.com/jaimer/archive/2009/03/30/mix09-recap-series-part2.aspx</link><description>In between all the positive feedback at MIX, there was a lingering question that I read a lot on twits, blog posts, and heard at the Q&amp;amp;A from some sessions and I think we missed it during our planning; I felt it is one of those “we can not see the</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: MIX09 Recap series part2 ,  what about WPF</title><link>http://blogs.msdn.com/jaimer/archive/2009/03/30/mix09-recap-series-part2.aspx#9521402</link><pubDate>Tue, 31 Mar 2009 07:21:52 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9521402</guid><dc:creator>ccchai</dc:creator><description>&lt;p&gt;I am glad to hear that .Net 4 Client Profile will be approx 22 MB, and able to install to any PC. I am wondering how fast is the installation time. Also, would there be any improvement in Client Profile Configuration Designer?&lt;/p&gt;
&lt;p&gt;One of the reasons that people are moving to Silverlight development for small apps is because the current .Net 3.5 + ClickOnce installation experience is slow and terrible. And, I often receive complaints from my users for this.&lt;/p&gt;
</description></item><item><title>re: MIX09 Recap series part2 ,  what about WPF</title><link>http://blogs.msdn.com/jaimer/archive/2009/03/30/mix09-recap-series-part2.aspx#9523472</link><pubDate>Tue, 31 Mar 2009 20:50:18 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9523472</guid><dc:creator>Kosmatos</dc:creator><description>&lt;p&gt;Well said Jaime. I agree that WPF will be around for awhile, even if Silverlight might become a superstar. By the way, I think of it as &amp;quot;Full .NET framework vs. Silverlight&amp;quot; and not &amp;quot;WPF vs. Silverlight&amp;quot;. Silverlight hasn't been only about WPF ever since it was WPF/E back in the days when there was no .NET framework in WPF/E and you had to code with Javascript. When you choose Silverlight, you aren't just foregoing some missing features from WPF, but the entire .NET framework and all the richness and productivity it provides that isn't crammed in Silverlight's 4.4 MB compact edition of .NET.&lt;/p&gt;
</description></item><item><title>The weekly SyncToBlog: #5</title><link>http://blogs.msdn.com/jaimer/archive/2009/03/30/mix09-recap-series-part2.aspx#9580662</link><pubDate>Thu, 30 Apr 2009 19:25:29 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9580662</guid><dc:creator>IUpdateable from Eric Nelson</dc:creator><description>&lt;p&gt;Development related: Persistence ignorance in the Entity Framework discussed with reference to the EFPocoAdapter&lt;/p&gt;
</description></item></channel></rss>