<?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>IronPython Integration Sample and the WPF Designer</title><link>http://blogs.msdn.com/aaronmar/archive/2007/08/01/ironpython-integration-sample-and-the-wpf-designer.aspx</link><description>[Update Jan 04, 2008: Made &amp;lt;system.codedom&amp;gt; instructions more clear. Thanks to Cory Bloyd for the suggestion.] If you've had the opportunity to work with WPF/.NET 3.0 yet, you've likely run into the x:Class attribute in XAML. If you specify a x:Class</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>MSDN Blog Postings  &amp;raquo; VSX Community Letter for August 2007</title><link>http://blogs.msdn.com/aaronmar/archive/2007/08/01/ironpython-integration-sample-and-the-wpf-designer.aspx#4323620</link><pubDate>Fri, 10 Aug 2007 21:16:40 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:4323620</guid><dc:creator>MSDN Blog Postings  » VSX Community Letter for August 2007</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://msdnrss.thecoderblogs.com/2007/08/10/vsx-community-letter-for-august-2007/"&gt;http://msdnrss.thecoderblogs.com/2007/08/10/vsx-community-letter-for-august-2007/&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>