﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Toni commented on Generating API Documentation</title><description>About a year ago I was using DocProject, 
[http://docproject.codeplex.com/](http://docproject.codeplex.com/). It installs VS template which you can use to create the project and integrates into msbuld quite nicely.
</description><link>http://ayende.com/4635/generating-api-documentation#comment9</link><guid>http://ayende.com/4635/generating-api-documentation#comment9</guid><pubDate>Thu, 23 Sep 2010 05:46:41 GMT</pubDate></item><item><title>Ayende Rahien commented on Generating API Documentation</title><description>Matt,
  
Thanks, that took over 2 minutes from the help build time
</description><link>http://ayende.com/4635/generating-api-documentation#comment8</link><guid>http://ayende.com/4635/generating-api-documentation#comment8</guid><pubDate>Tue, 21 Sep 2010 07:25:39 GMT</pubDate></item><item><title>Dave Barone commented on Generating API Documentation</title><description>This is something that's puzzled me for a while - Why .NET does not have a standard document generator. Ruby has RDoc. I too tried Sandcastle a couple of years ago but gave up as well. It's not a product but a set of (very raw) tools - it's just too much hard work to use. Doxygen on the other hand is good, but is not .NET specific, and does not seem to cope with all edge cases in .NET. Maybe the thought of building Rhino.Doc isn't such a bad idea ???
</description><link>http://ayende.com/4635/generating-api-documentation#comment7</link><guid>http://ayende.com/4635/generating-api-documentation#comment7</guid><pubDate>Tue, 21 Sep 2010 00:07:02 GMT</pubDate></item><item><title>Paul Hatcher commented on Generating API Documentation</title><description>Another vote for Document X - the other nice thing is that you can put topics other than straight API stuff
</description><link>http://ayende.com/4635/generating-api-documentation#comment6</link><guid>http://ayende.com/4635/generating-api-documentation#comment6</guid><pubDate>Mon, 20 Sep 2010 15:17:18 GMT</pubDate></item><item><title>Frans Bouma commented on Generating API Documentation</title><description>You didn't try Document! X?
  
  
It's commercial, true, but gives the least # of friction (although VSDocMan also looks nice) as in: you don't have to spent extra time when writing code. 
</description><link>http://ayende.com/4635/generating-api-documentation#comment5</link><guid>http://ayende.com/4635/generating-api-documentation#comment5</guid><pubDate>Mon, 20 Sep 2010 14:40:59 GMT</pubDate></item><item><title>Christopher Bennage commented on Generating API Documentation</title><description>What?! No Rhino.Doc?
  
(Sorry, I know the joke is getting old.)
  
  
We settled on Doxygen for Caliburn (though I believe that was two years ago).
</description><link>http://ayende.com/4635/generating-api-documentation#comment4</link><guid>http://ayende.com/4635/generating-api-documentation#comment4</guid><pubDate>Mon, 20 Sep 2010 13:30:34 GMT</pubDate></item><item><title>Matt Salmon commented on Generating API Documentation</title><description>Hi Ayende
  
  
With Sandcastle, you can speed up the build substantially doing the following:
  
  
Click on the "ComponentConfigurations" properties button, and add "Cached Framework Comments Index Data", "Cached MSDN URL References", and "Cached Reflection Index Data".  
  
  
HTH,
  
Matt
  
</description><link>http://ayende.com/4635/generating-api-documentation#comment3</link><guid>http://ayende.com/4635/generating-api-documentation#comment3</guid><pubDate>Mon, 20 Sep 2010 13:29:17 GMT</pubDate></item><item><title>bjjonker commented on Generating API Documentation</title><description>"I didn’t know whatever you can easily put it in a build script."
  
  
The saved file output from the Sandcastle Help File Builder is an MSBuild-based project file, so it should integrate well with a build script. 
</description><link>http://ayende.com/4635/generating-api-documentation#comment2</link><guid>http://ayende.com/4635/generating-api-documentation#comment2</guid><pubDate>Mon, 20 Sep 2010 12:58:14 GMT</pubDate></item><item><title>commenter commented on Generating API Documentation</title><description>" it gave me an error there as well, something about duplicate mscorlib,"
  
  
Could be you need to bump up the tools version in the csproj.
  
2.0 tools don't know how to build 4.0 projects so they always pull in the old mscorlib.
</description><link>http://ayende.com/4635/generating-api-documentation#comment1</link><guid>http://ayende.com/4635/generating-api-documentation#comment1</guid><pubDate>Mon, 20 Sep 2010 10:17:34 GMT</pubDate></item></channel></rss>