<?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>Warning? XSD? XAML? Whatever...</title><link>http://blogs.msdn.com/wpfsdk/archive/2006/12/08/warning-xsd-xaml-whatever.aspx</link><description>Today's blog entry is brought to you by the letters W, and X ... For those of you that have been developing in the release versions of Microsoft Visual Studio, along with the Visual Studio 2005 Extensions for .NET Framework 3.0 (WCF &amp;amp; WPF), you have</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Link Roundup 2006.12.13</title><link>http://blogs.msdn.com/wpfsdk/archive/2006/12/08/warning-xsd-xaml-whatever.aspx#1273657</link><pubDate>Wed, 13 Dec 2006 13:02:27 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1273657</guid><dc:creator>Life, Universe and Everything according to Dirk</dc:creator><description>&lt;p&gt;Announcing the release of the first &amp;quot;WPF/E&amp;quot; CTP Adobe Illustrator XAML exporter for &amp;quot;WPF/E&amp;quot; The Outlook&lt;/p&gt;
</description></item><item><title>Dark Secrets of WPF SDK Documentation Conventions Exposed!</title><link>http://blogs.msdn.com/wpfsdk/archive/2006/12/08/warning-xsd-xaml-whatever.aspx#2514206</link><pubDate>Thu, 10 May 2007 04:43:10 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2514206</guid><dc:creator>Windows Presentation Foundation SDK </dc:creator><description>&lt;p&gt;Dark Secrets of WPF SDK Documentation Conventions Exposed! * Introduction Those of you that have been&lt;/p&gt;
</description></item><item><title>Dark Secrets of the WPF SDK Exposed!</title><link>http://blogs.msdn.com/wpfsdk/archive/2006/12/08/warning-xsd-xaml-whatever.aspx#2514292</link><pubDate>Thu, 10 May 2007 04:47:56 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2514292</guid><dc:creator>Windows Presentation Foundation SDK </dc:creator><description>&lt;p&gt;* Introduction Those of you that have been on the .NET journey since versions 1.0, 1.1, and 2.0 have&lt;/p&gt;
</description></item><item><title>re: Warning? XSD? XAML? Whatever...</title><link>http://blogs.msdn.com/wpfsdk/archive/2006/12/08/warning-xsd-xaml-whatever.aspx#8578610</link><pubDate>Fri, 06 Jun 2008 21:10:57 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8578610</guid><dc:creator>wcsdkteam</dc:creator><description>&lt;p&gt;A reality update for anyone that finds this blog entry delivered by their Internet wayback machine ...&lt;/p&gt;
&lt;p&gt;Visual Studio 2008 is out there now. Visual Studio 2008 has solved a number of the discussed issues for XAML and Intellisense by implementing a &amp;quot;language service&amp;quot; that works both with the visual design surface and the XAML markup editing. The XAML language service is able to anticipate the WPF XAML compilation and load rules, even for custom types, and can provide much better design-time guidance than a schema ever could. If you aren't using Visual Studio 2008 to edit your XAML (or maybe one of the Expression products, if you are taking more of a design angle) ... why not?&lt;/p&gt;
</description></item></channel></rss>