<?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>XAML guidelines part 3</title><link>http://blogs.msdn.com/jaimer/archive/2009/01/13/xaml-guidelines-part-3-draft.aspx</link><description>There were 3 goals to the XAML guidelines series: Show that there is not a single right answer (that is why we interviewed multiple people, multiple projects) Document common practices and previous experiences that worked. Inspire others to share their</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>XAML Guidelines released!</title><link>http://blogs.msdn.com/jaimer/archive/2009/01/13/xaml-guidelines-part-3-draft.aspx#9314267</link><pubDate>Tue, 13 Jan 2009 13:45:57 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9314267</guid><dc:creator>Rudi Grobler</dc:creator><description>&lt;p&gt;One of the most frequently asked questions from WPF practitioners is “What are the recommended practices&lt;/p&gt;
</description></item><item><title>re: XAML guidelines part 3</title><link>http://blogs.msdn.com/jaimer/archive/2009/01/13/xaml-guidelines-part-3-draft.aspx#9315840</link><pubDate>Tue, 13 Jan 2009 19:36:48 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9315840</guid><dc:creator>Mark Rendle</dc:creator><description>&lt;p&gt;Very useful. I've posted a recently-formed guideline of my own at &lt;a rel="nofollow" target="_new" href="http://blog.markrendle.net/post/XAML-guidelines.aspx"&gt;http://blog.markrendle.net/post/XAML-guidelines.aspx&lt;/a&gt; if you're interested.&lt;/p&gt;
</description></item><item><title>XAML Guidelines</title><link>http://blogs.msdn.com/jaimer/archive/2009/01/13/xaml-guidelines-part-3-draft.aspx#9316392</link><pubDate>Tue, 13 Jan 2009 21:00:14 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9316392</guid><dc:creator>Marc: My Words</dc:creator><description>&lt;p&gt;Organising WPF projects is a black art, and when I’m coding some WPF (stop laughing) then I definitely&lt;/p&gt;
</description></item><item><title>re: XAML guidelines part 3</title><link>http://blogs.msdn.com/jaimer/archive/2009/01/13/xaml-guidelines-part-3-draft.aspx#9316514</link><pubDate>Tue, 13 Jan 2009 21:21:01 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9316514</guid><dc:creator>swildermuth</dc:creator><description>&lt;p&gt;I am disappointed the &amp;quot;XAML Guidelines&amp;quot; would only take WPF into account. Any plans for a Rev that covers SL too?&lt;/p&gt;
</description></item><item><title>re: XAML guidelines part 3</title><link>http://blogs.msdn.com/jaimer/archive/2009/01/13/xaml-guidelines-part-3-draft.aspx#9316630</link><pubDate>Tue, 13 Jan 2009 21:45:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9316630</guid><dc:creator>jaimer</dc:creator><description>&lt;p&gt;Shawn, &lt;/p&gt;
&lt;p&gt;It can't be the same document. Silverlight optimizes for size and the subset of features (in particular resources) is meaningful enough that SL should get their own document. &amp;nbsp; &lt;/p&gt;
&lt;p&gt;I am most interested in the &amp;quot;sharing code&amp;quot; between SL and WPF. That is on my radar for right around or after MIX 09 time-frame.. to be candid I need more &amp;quot;hands-on&amp;quot; into that scenario before I can truly share advise that I know is proven. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;I do get your point with the name.. I will make sure to update it to some thing like &amp;quot;WPF XAML guidelines&amp;quot;&lt;/p&gt;
&lt;p&gt;Cheers,&lt;/p&gt;
</description></item><item><title>Silverlight Cream for January 14, 2009 -- #486</title><link>http://blogs.msdn.com/jaimer/archive/2009/01/13/xaml-guidelines-part-3-draft.aspx#9320105</link><pubDate>Thu, 15 Jan 2009 08:23:10 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9320105</guid><dc:creator>Community Blogs</dc:creator><description>&lt;p&gt;In this issue: Quadra Silverlight Outsourcing, Denis Dollfus, Karsten Januszewski, Tim Greenfield, Alex&lt;/p&gt;
</description></item><item><title>#.think.in infoDose #16 (12th Jan - 16th Jan)</title><link>http://blogs.msdn.com/jaimer/archive/2009/01/13/xaml-guidelines-part-3-draft.aspx#9338877</link><pubDate>Mon, 19 Jan 2009 01:32:02 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9338877</guid><dc:creator>#.think.in</dc:creator><description>&lt;p&gt;#.think.in infoDose #16 (12th Jan - 16th Jan)&lt;/p&gt;
</description></item><item><title>re: XAML guidelines part 3</title><link>http://blogs.msdn.com/jaimer/archive/2009/01/13/xaml-guidelines-part-3-draft.aspx#9340267</link><pubDate>Mon, 19 Jan 2009 19:16:31 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9340267</guid><dc:creator>Corey Hart</dc:creator><description>&lt;p&gt;I'd like to see some best practices on databinding.&lt;/p&gt;
&lt;p&gt;For example, would it be better to bind directly to a method in a service reference, or to create some sort of data manager and bind to that?&lt;/p&gt;
</description></item><item><title>Learning WPF</title><link>http://blogs.msdn.com/jaimer/archive/2009/01/13/xaml-guidelines-part-3-draft.aspx#9388908</link><pubDate>Mon, 02 Feb 2009 03:41:24 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9388908</guid><dc:creator>Evangelism 2.0: riflessioni sul business del software da un punto di vista privilegiato!</dc:creator><description>&lt;p&gt;WPF, e pi&amp;#249; in generale la realizzazione di interfacce utente, sono tematiche che esulano un p&amp;#242; dalla&lt;/p&gt;
</description></item><item><title>Roundup of 11 Recent Microsoft Technology Releases</title><link>http://blogs.msdn.com/jaimer/archive/2009/01/13/xaml-guidelines-part-3-draft.aspx#9393430</link><pubDate>Tue, 03 Feb 2009 19:56:21 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9393430</guid><dc:creator>Chris Bowen's Blog</dc:creator><description>&lt;p&gt;There have been quite a few developer and technology releases in the past couple of weeks, so in case&lt;/p&gt;
</description></item><item><title>XAML Guidelines Document for WPF (and Silverlight)</title><link>http://blogs.msdn.com/jaimer/archive/2009/01/13/xaml-guidelines-part-3-draft.aspx#9413289</link><pubDate>Wed, 11 Feb 2009 22:49:25 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9413289</guid><dc:creator>Katrien's MSDN Blog</dc:creator><description>&lt;p&gt;If you are looking for best practices for running XAML WPF projects, this is a must read. Jaime Rodriguez&lt;/p&gt;
</description></item><item><title>re: XAML guidelines part 3</title><link>http://blogs.msdn.com/jaimer/archive/2009/01/13/xaml-guidelines-part-3-draft.aspx#9413353</link><pubDate>Wed, 11 Feb 2009 23:24:36 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9413353</guid><dc:creator>jackbond</dc:creator><description>&lt;p&gt;Thank you for generating an XPS version. One grows tired of seeing documents exclusively generated for Adobe's crapware.&lt;/p&gt;
</description></item></channel></rss>