Standard documentation fix and perhaps analyzer.

[JohanLarsson]

Generate standard document comments.
Examples:
For:

• Parameter of type CancellationToken
• Backing field for a WPF dependency property.
• Attached property Get & Set methods
• ...

There is also an analyzer opportunity that checks that things that have a standard documentation are using it.

[sharwell]

Here's the standard documentation for a CancellationToken cancellationToken parameter of an asynchronous method:

<param name="cancellationToken">The <see cref="CancellationToken"/> that the task will observe.</param>

We don't enforce this (like we do for standard constructor text), but it would be acceptable to generate it if/when missing.

[JohanLarsson]

We should probably create an issue per case that comes up. So it can be discussed and used for tracking commits. The list is probably pretty long so one thread would be messy, wrote this to check what other people think.

Where does the standard documentation for CancellationToken come from btw?

[sharwell]

I hate to open the door for an unknown number of proposals (😆) but here's one from docs.microsoft.com:

The token to monitor for cancellation requests.