Tip
If not using the Visual Studio IDE, the various managed language compilers support a /doc command line option that will produce the XML comments file. See your language compiler command line option documentation for details.
This walkthrough will describe the steps needed to enable XML comments file output in your Visual Studio projects, provides information on where to get more information on using XML comments to decorate your code, and describes how to open help file builder projects from within Visual Studio.
In order to create a help file that contains reference content (API documentation), you must enable XML comments in your Visual Studio projects so that an XML file is generated to contain them when the project is built.
In the Solution Explorer, right click on the project and select Properties.
Select the Build property page.
In the Output section, check the checkbox next to the Xml documentation file text box and specify a name for the XML file. Although not required, a common convention is to name the XML comments file after the related assembly (except with a .xml extension). The assembly name can be found on the Application property page.
If you have a solution with multiple projects that need to be documented, repeat the above steps for each project in the solution. It is recommended that you give each project's XML comments file a unique name.
If documenting a managed C++ project, the procedure differs and you need to follow these steps instead.
In the Solution Explorer, right click on the project and select Properties.
Expand the Configuration Properties category and then expand the C/C++ sub-category and select the Output Files option below it.
In the Output Files options, change the Generate XML Documentation Files option to Yes (/doc).
By default, the comments file is named after the project target with a .xml extension and is placed in the target folder. If you want to change the name, select the XML Document Generator category below the Configuration Properties category and change the filename using the Output Document File property.
If you have a solution with multiple projects that need to be documented, repeat the above steps for each project in the solution. If you explicitly specify a name for the comments file, it is recommended that you give each project's XML comments file a unique name.
Once the above has been done, Visual Studio will create the XML comments file each time the project is built.
In addition to setting the project option to create the file, you must also add XML comments to your source code. At a minimum, you should add a <summary> element to each public type and to the public and protected members of those types. There are many other elements available that will help improve the quality of your documentation. See the other sections in this guide for more information
The XML comments elements and their format is consistent across all languages. The only variable is the comment characters that precede them. Here are some examples.
''' <summary>
''' This is an example of triple apostrophe XML comments. These are the only
''' delimiters supported by Visual Basic.
''' </summary>
/// <summary>
/// This is an example of triple slash XML comments. This is the most common
/// form of XML comments delimiter in C#, C++, and F# code.
/// </summary>
NOTE: The multi-line XML comments delimiters shown below are only supported by C# and C++.
/** <summary>
* This is an example of using the multi-line XML comments delimiters. In this
* case, the common pattern " * " at the start of each line after the first one
* is ignored by the compiler and will not appear in the comments.
* </summary>
*/
/**
<summary>This example does not use a common leading pattern on each line of
the summary comments using the multi-line XML comments delimiters.</summary>
*/
/** <summary>A single-line summary using the multi-line delimiters.</summary> */
Refer to the other sections in this guide for more information about the various XML comments elements and how to use them.