Default structure of generated documentation is quite simple and it only contains automatically generated API reference. A table of contents (TOC) looks like:

Help Title
  Namespace1 API
  Namespace2 API
   ...
  NamespaceN API

But VSdocman allows you to define your own custom topics and TOC structure. Using WYSIWYG editor, you can create any number of custom topics such as overview, examples and demos, license agreement, usage descriptions, company description, etc. You can define your own structure of table of contents (TOC) with topics and chapters. You can place generated API documentation anywhere in the TOC. You can even split API reference and insert specified namespaces at various places. This makes VSdocman really powerful tool for creating complete end-user documentation for your class libraries and applications.

This is an example of custom documentation layout:

Overview
TestDLL Usage
  Basic Functionality
  Advanced
TestDLL Class Reference
  Namespace2 API
   ...
  NamespaceN API
License Agreement
About
Appendix: Demo Reference
  Namespace1 API

As you can see, this is a complete end-user documentation for your class library. You can use all XML tags that you use in your XML comments. Links to and from your custom topics are fully supported too.

You can define your custom topics on Output - Custom Topics page.

See Also