NDoc

NDoc uses two sources to generate documentation. The first is an assembly file produced by compiling the source code. The other is a pre-generated XML documentation file, usually produced by parsing the source code for special comments (C# compilers from .NET Framework and Mono support this using the "/doc" command-line argument).

The assembly file is queried using reflection to obtain the list of classes, methods, etc. The XML file is parsed for the documentation text.

NDoc uses plug-ins to support several different output formats, including CHM, Microsoft Help Viewer, MSDN-style web pages. Incomplete plug-ins are also included as starting points for developers, like the LaTeX plug-in and Javadoc-style web pages. NDoc comes with a graphical user interface to ease the generation process.

The latest release version of NDoc does not support .NET Framework version 2.0. Although there are internal alpha versions[1][2] that support .NET 2.0, as of 2006, there is very little activity on the NDoc project. The developer of NDoc, Kevin Downs, has said that he is not working on NDoc anymore due to lack of funding and threats against him, and that he is willing to hand over administration of the project.[3] More recently, Kim Christensen picked up the ball and continues development of the original NDoc as NDoc3[4]

• Doxygen - a mature document generation tool that can also build class diagrams and produce documentation from many other languages.
• Sandcastle — a similar application by Microsoft.
• Sandcastle Help File Builder — a freeware GUI front-end for Sandcastle that provides Ndoc-like features.
• Visual Expert - a documentation generator that also provides call trees, CRUD matrix, impact analysis, code review for PL/SQL, Transact-SQL and other languages.
• Comparison of documentation generators

• Official website of NDoc
• Website of NDoc3, official successor to NDoc
• NDoc 2005 and NDoc Reloaded — forks of NDoc