This repository contains an implementation of the stylecop (SA1600+) quick fixes for property and method documentation For a full implementation of all the stylecop rules, please see Stylecop.Analyzers

Stylecop.Analyzers do not provide automatic documentation generation. This project aims to fill that gap by providing minimal documentation generation for properties / methods and method parameters to save time.

The preferable way to use the analyzers is to add the nuget package Documentation.Analyser to the project where you want to provide quick fixes.

The severity of individual rules may be configured using rule set files

Documentation.Analyser can be installed using the NuGet Package Manager in Visual Studio 2015.

From this bare declaration.

public void BuildVogonConstructorFleets(int fleetCount)
{
}

To a well documented method.

/// <summary>
/// build the vogon constructor fleets.
/// </summary>
/// <param name="fleetCount">the fleet count.</param>
public void BuildVogonConstructorFleets(int fleetCount)
{
}

From this bare property

public Fleet[] VogonConstructorFleet { get; set; }

To a well documented property.

/// <summary>
/// Gets or sets the vogon constructor fleet.
/// </summary>
public Fleet[] VogonConstructorFleet { get; set; }

From this base method

public Fleet BuildVogonDestroyerFleet<TMunitionsPayload>(int destroyerCount)
{
}

To a well documented method, with type parameters.

/// <summary>
/// build the vogon destroyer fleet.
/// </summary>
/// <param name="destroyerCount">the destroyer count.</param>
/// <returns>the fleet.</returns>
/// <typeparam name="TMunitionsPayload">a type of munitions payload.</typeparam>
public Fleet BuildVogonDestroyerFleet<TMunitionsPayload>(int destroyerCount)
{
}

If you use older versions of Visual Studio in addition to Visual Studio 2015, you may still install these analyzers. They will be automatically disabled when you open the project back up in Visual Studio 2013 or earlier.

Opinions vary, but my feeling is that if the generated documentation does not read correctly and precisely, then you have fallen prey to one of the two 'hard things to get right' in software engineering.

• Naming Things.
• Cache Invalidation.
• Off by One Errors.

(Phil Karlton)

• Feel free to add issues via github if you have any suggestions for improvement.