<?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>How We Address Developer Documentation Comments</title><link>http://blogs.msdn.com/sharepointdeveloperdocs/archive/2008/06/09/how-we-address-developer-documentation-comments.aspx</link><description>One of the things I've wanted to do on this blog is give people a clearer view into how we actually produce developer documentation for SharePoint; the processes we use, the decisions we make, and what factors influence those decisions. (The Office client</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Dog Breeding &amp;raquo; How We Address Developer Documentation Comments</title><link>http://blogs.msdn.com/sharepointdeveloperdocs/archive/2008/06/09/how-we-address-developer-documentation-comments.aspx#8587372</link><pubDate>Mon, 09 Jun 2008 23:46:37 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8587372</guid><dc:creator>Dog Breeding &amp;raquo; How We Address Developer Documentation Comments</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://dogs-pets.info/dog-breeding/?p=991"&gt;http://dogs-pets.info/dog-breeding/?p=991&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>