<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Inline XML Code Documentation using Sandcastle</title>
	<atom:link href="http://elegantcode.com/2008/04/01/inline-xml-code-documentation-using-sandcastle/feed/" rel="self" type="application/rss+xml" />
	<link>http://elegantcode.com/2008/04/01/inline-xml-code-documentation-using-sandcastle/</link>
	<description></description>
	<lastBuildDate>Wed, 17 Mar 2010 08:54:42 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Scott Nichols</title>
		<link>http://elegantcode.com/2008/04/01/inline-xml-code-documentation-using-sandcastle/comment-page-1/#comment-19182</link>
		<dc:creator>Scott Nichols</dc:creator>
		<pubDate>Wed, 02 Apr 2008 21:05:49 +0000</pubDate>
		<guid isPermaLink="false">http://elegantcode.com/2008/04/01/inline-xml-code-documentation-using-sandcastle/#comment-19182</guid>
		<description>Yeah, I do not think it is necessary to spend tons of time making your XML comments picture perfect either.  Okay, one exception, if you are developing commercial software such as a control library.  I think the extra effort spent in your XML comments could payoff in more sales because of better API documentation, possibly.

I would just like to see more people use XML comments (even if they take the minimalist approach) then take a tool like Sandcastle to generates docs.  Over the years I have found if someone had generated API documentation I could come up to speed on their API exponentially faster,  especially if they made go use of my favorite tag the …
&lt;example&gt;
&#160;The description of the example
&#160;&#160;&#160;&lt;code&gt;
&#160;&#160;&#160;&#160;Some source code showing how to use your class, method, etc… 
&#160;&#160;&#160;&lt;/code&gt;         
&lt;/example&gt;


</description>
		<content:encoded><![CDATA[<p>Yeah, I do not think it is necessary to spend tons of time making your XML comments picture perfect either.  Okay, one exception, if you are developing commercial software such as a control library.  I think the extra effort spent in your XML comments could payoff in more sales because of better API documentation, possibly.</p>
<p>I would just like to see more people use XML comments (even if they take the minimalist approach) then take a tool like Sandcastle to generates docs.  Over the years I have found if someone had generated API documentation I could come up to speed on their API exponentially faster,  especially if they made go use of my favorite tag the …<br />
&lt;example&gt;<br />
&nbsp;The description of the example<br />
&nbsp;&nbsp;&nbsp;&lt;code&gt;<br />
&nbsp;&nbsp;&nbsp;&nbsp;Some source code showing how to use your class, method, etc…<br />
&nbsp;&nbsp;&nbsp;&lt;/code&gt;<br />
&lt;/example&gt;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: trasa</title>
		<link>http://elegantcode.com/2008/04/01/inline-xml-code-documentation-using-sandcastle/comment-page-1/#comment-19171</link>
		<dc:creator>trasa</dc:creator>
		<pubDate>Wed, 02 Apr 2008 16:32:46 +0000</pubDate>
		<guid isPermaLink="false">http://elegantcode.com/2008/04/01/inline-xml-code-documentation-using-sandcastle/#comment-19171</guid>
		<description>One thing I&#039;ve done differently recently:  I used to spend a lot of time making my XmlDocs look good in .chm or html format (processed via ndoc), using a tool like Documentor to view the output in visual studio.  

But then this makes the comments less readable in the source code - arguably the most important place to read them!  So I still use XmlDocs and GhostDoc to help with some of the boilerplate, but I don&#039;t worry too much about formatting the xml within with &lt;para&gt; and &lt;note&gt; and so on.</description>
		<content:encoded><![CDATA[<p>One thing I&#8217;ve done differently recently:  I used to spend a lot of time making my XmlDocs look good in .chm or html format (processed via ndoc), using a tool like Documentor to view the output in visual studio.  </p>
<p>But then this makes the comments less readable in the source code &#8211; arguably the most important place to read them!  So I still use XmlDocs and GhostDoc to help with some of the boilerplate, but I don&#8217;t worry too much about formatting the xml within with
<para> and <note> and so on.</note></para>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dew Drop - April 2, 2008 &#124; Alvin Ashcraft's Morning Dew</title>
		<link>http://elegantcode.com/2008/04/01/inline-xml-code-documentation-using-sandcastle/comment-page-1/#comment-19168</link>
		<dc:creator>Dew Drop - April 2, 2008 &#124; Alvin Ashcraft's Morning Dew</dc:creator>
		<pubDate>Wed, 02 Apr 2008 13:44:59 +0000</pubDate>
		<guid isPermaLink="false">http://elegantcode.com/2008/04/01/inline-xml-code-documentation-using-sandcastle/#comment-19168</guid>
		<description>[...] Inline XML Code Documentation Using Sandcastle (Scott Nichols) [...]</description>
		<content:encoded><![CDATA[<p>[...] Inline XML Code Documentation Using Sandcastle (Scott Nichols) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tobi</title>
		<link>http://elegantcode.com/2008/04/01/inline-xml-code-documentation-using-sandcastle/comment-page-1/#comment-19150</link>
		<dc:creator>Tobi</dc:creator>
		<pubDate>Wed, 02 Apr 2008 07:42:55 +0000</pubDate>
		<guid isPermaLink="false">http://elegantcode.com/2008/04/01/inline-xml-code-documentation-using-sandcastle/#comment-19150</guid>
		<description>A couple days back Alex published a step by step howto about setting up sandcastle. Check it out:

http://saftsack.fs.uni-bayreuth.de/~dun3/archives/integrate-xml-code-comments-into-visual-studio-20052008-using-sandcastle-and-html-help-20/150.html</description>
		<content:encoded><![CDATA[<p>A couple days back Alex published a step by step howto about setting up sandcastle. Check it out:</p>
<p><a href="http://saftsack.fs.uni-bayreuth.de/~dun3/archives/integrate-xml-code-comments-into-visual-studio-20052008-using-sandcastle-and-html-help-20/150.html" rel="nofollow">http://saftsack.fs.uni-bayreuth.de/~dun3/archives/integrate-xml-code-comments-into-visual-studio-20052008-using-sandcastle-and-html-help-20/150.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Reflective Perspective - Chris Alcock &#187; The Morning Brew #64</title>
		<link>http://elegantcode.com/2008/04/01/inline-xml-code-documentation-using-sandcastle/comment-page-1/#comment-19148</link>
		<dc:creator>Reflective Perspective - Chris Alcock &#187; The Morning Brew #64</dc:creator>
		<pubDate>Wed, 02 Apr 2008 06:27:56 +0000</pubDate>
		<guid isPermaLink="false">http://elegantcode.com/2008/04/01/inline-xml-code-documentation-using-sandcastle/#comment-19148</guid>
		<description>[...] Inline XML Code Documentation using Sandcastle - Scott Nichols gathers together a collection of links for XML documentation and using SandCastle [...]</description>
		<content:encoded><![CDATA[<p>[...] Inline XML Code Documentation using Sandcastle &#8211; Scott Nichols gathers together a collection of links for XML documentation and using SandCastle [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
