Although good naming and a set of well written tests can bring us so far, good documentation is sometimes indispensible.
Before releasing a component I was documenting a public API using the Visual Studio XML documentation. The exposed API was using generics, but I didn’t know what the correct documentation structure was.
MSDN brought the answer:
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
/// <summary> | |
/// GenericClass. | |
/// </summary> | |
/// <remarks> | |
/// This example shows how to specify the <see cref="GenericClass{T}"/> type as a cref attribute. | |
/// </remarks> | |
class GenericClass<T> | |
{ | |
// Fields and members. | |
} |