<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:pingback="http://madskills.com/public/xml/rss/module/pingback/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>Where did the time go? - Documentation</title>
    <link>http://blog.j-maxx.net/</link>
    <description>Brain Powered</description>
    <language>en-us</language>
    <copyright>Jeff Klawiter</copyright>
    <lastBuildDate>Mon, 30 Jun 2008 01:57:50 GMT</lastBuildDate>
    <generator>newtelligence dasBlog 2.1.8102.813</generator>
    <managingEditor>Jeff.Klawiter@sierra-bravo.com</managingEditor>
    <webMaster>Jeff.Klawiter@sierra-bravo.com</webMaster>
    <item>
      <trackback:ping>http://blog.j-maxx.net/Trackback.aspx?guid=e4e4b464-2924-4671-849e-f064ea605229</trackback:ping>
      <pingback:server>http://blog.j-maxx.net/pingback.aspx</pingback:server>
      <pingback:target>http://blog.j-maxx.net/PermaLink,guid,e4e4b464-2924-4671-849e-f064ea605229.aspx</pingback:target>
      <dc:creator>Jeff Klawiter</dc:creator>
      <wfw:comment>http://blog.j-maxx.net/CommentView,guid,e4e4b464-2924-4671-849e-f064ea605229.aspx</wfw:comment>
      <wfw:commentRss>http://blog.j-maxx.net/SyndicationService.asmx/GetEntryCommentsRss?guid=e4e4b464-2924-4671-849e-f064ea605229</wfw:commentRss>
      <body xmlns="http://www.w3.org/1999/xhtml">Documenting code is one of those things
that programmers tend to leave out while under a tight dealine or just building a
new project. It's one of those things we tend to say, if we have time when we're done
we can do it. It can be time consuming and sometimes hard to see the benefit up front.
I'm very guilty of poor documentation and commenting. I rarely get to work in a team
so I always end up relying on my own memory for what does what and where. Then two
years go by and I forget it all.<br /><br />
I have been trying to get better about adding at least XML comments to my classes,
methods and properties. The project I am on right now is a rather large project due
in less than a month and so far we have a semi-concrete middle layer, a half mocked
up front end and a half done back end. We need more than just one or two people on
the project and I've been in charge of part of the back end and all of the middle
layer. Even though it is taking a bit more time I've been trying to add documentation
and actually use Unit Tests for my first time. (that's a whole other entry).<br /><br />
While the built in XML Commenting system C# has is great and can really help a programmer
when coding there is little to no good way of taking that and making separate documentation
out of it. That and editing it can be a real pain. After pouring over the web for
some way of exporting the XML as a CHM or MSDN type library I came across <a href="http://www.codeplex.com/DocProject">DocProject</a> .
This wonderfully free and open source VS 2005/2008 Addin is a godsend on this front.
It can create a standalone CHM or give you an MSDN library to integrate with your
VS or create a web project that has a decent Ajax interface for browsing the documentation
online. All export options can be done at once as well.<br /><br />
DocProject lets you edit every part of the XML Documenation in a rich text editor.
While I think the editor could use a bit of work (make it easier for putting code
in the Example and other regions code can exist) it does a great job of making it
much easier to write the documentation instead of just in code.<br /><br />
DocProject does have a bit of a draw back in it's requirements. To use it you must
install <a href="http://www.microsoft.com/downloads/details.aspx?FamilyId=E82EA71D-DA89-42EE-A715-696E3A4873B2&amp;displaylang=en">Sandcastle</a>,
which isn't to large. If you want to output in the new Compiled HTML 2.x format you
need to install the VS 2008 SDK. The SDK however is nearly 100MB. Though I'd recommend
having it anyway, with it you get the ability to write VS addins and other fun stuff.<br /><br />
I just started using DocProject today, so far I'm impressed and I hope it turns out
to be a good addition to the development process of this project. I'm hoping to use
DocProject's publish features to put the documentation on a site where other developers
for the project will be able to reference. I've found over the years that the projects
with the most documentation end up being the easiest to work on.<br /><p></p><img width="0" height="0" src="http://blog.j-maxx.net/aggbug.ashx?id=e4e4b464-2924-4671-849e-f064ea605229" /></body>
      <title>Project Documenting under a deadline</title>
      <guid isPermaLink="false">http://blog.j-maxx.net/PermaLink,guid,e4e4b464-2924-4671-849e-f064ea605229.aspx</guid>
      <link>http://blog.j-maxx.net/2008/06/30/ProjectDocumentingUnderADeadline.aspx</link>
      <pubDate>Mon, 30 Jun 2008 01:57:50 GMT</pubDate>
      <description>Documenting code is one of those things that programmers tend to leave out while under a tight dealine or just building a new project. It's one of those things we tend to say, if we have time when we're done we can do it. It can be time consuming and sometimes hard to see the benefit up front. I'm very guilty of poor documentation and commenting. I rarely get to work in a team so I always end up relying on my own
memory for what does what and where. Then two years go by and I forget
it all.&lt;br&gt;
&lt;br&gt;
I have been trying to get better about adding at least XML comments to my classes,
methods and properties. The project I am on right now is a rather large project due
in less than a month and so far we have a semi-concrete middle layer, a half mocked
up front end and a half done back end. We need more than just one or two people on
the project and I've been in charge of part of the back end and all of the middle
layer. Even though it is taking a bit more time I've been trying to add documentation
and actually use Unit Tests for my first time. (that's a whole other entry).&lt;br&gt;
&lt;br&gt;
While the built in XML Commenting system C# has is great and can really help a programmer
when coding there is little to no good way of taking that and making separate documentation
out of it. That and editing it can be a real pain. After pouring over the web for
some way of exporting the XML as a CHM or MSDN type library I came across &lt;a href="http://www.codeplex.com/DocProject"&gt;DocProject&lt;/a&gt; .
This wonderfully free and open source VS 2005/2008 Addin is a godsend on this front.
It can create a standalone CHM or give you an MSDN library to integrate with your
VS or create a web project that has a decent Ajax interface for browsing the documentation
online. All export options can be done at once as well.&lt;br&gt;
&lt;br&gt;
DocProject lets you edit every part of the XML Documenation in a rich text editor.
While I think the editor could use a bit of work (make it easier for putting code
in the Example and other regions code can exist) it does a great job of making it
much easier to write the documentation instead of just in code.&lt;br&gt;
&lt;br&gt;
DocProject does have a bit of a draw back in it's requirements. To use it you must
install &lt;a href="http://www.microsoft.com/downloads/details.aspx?FamilyId=E82EA71D-DA89-42EE-A715-696E3A4873B2&amp;amp;displaylang=en"&gt;Sandcastle&lt;/a&gt;,
which isn't to large. If you want to output in the new Compiled HTML 2.x format you
need to install the VS 2008 SDK. The SDK however is nearly 100MB. Though I'd recommend
having it anyway, with it you get the ability to write VS addins and other fun stuff.&lt;br&gt;
&lt;br&gt;
I just started using DocProject today, so far I'm impressed and I hope it turns out
to be a good addition to the development process of this project. I'm hoping to use
DocProject's publish features to put the documentation on a site where other developers
for the project will be able to reference. I've found over the years that the projects
with the most documentation end up being the easiest to work on.&lt;br&gt;
&lt;p&gt;
&lt;/p&gt;
&lt;img width="0" height="0" src="http://blog.j-maxx.net/aggbug.ashx?id=e4e4b464-2924-4671-849e-f064ea605229" /&gt;</description>
      <comments>http://blog.j-maxx.net/CommentView,guid,e4e4b464-2924-4671-849e-f064ea605229.aspx</comments>
      <category>C#</category>
      <category>Documentation</category>
    </item>
  </channel>
</rss>