C# IntelliSense does not respect newlines in doc comments

[vsfeedback]

For any long "summary" comment, hovering over the type/method seems to strip all newlines.
This makes it very difficult to read if you have a long/verbose comment.

Using "para" isn't really much of an option as:

1. It adds 2 newlines (not just 1)
2. I don't want to have to add "para" open and close tags everywhere.

This issue has been moved from https://developercommunity.visualstudio.com/content/problem/239537/c-intellisense-does-not-respect-newlines-in-doc-co.html
VSTS ticketId: 605850
These are the original issue comments:
(no comments)
These are the original issue solutions:
(no solutions)

[sharwell]

This is normal behavior in XML. Changing the behavior is likely to negatively impact the experience for developers who expect the XML to behave as it currently does. However, we might consider reducing the size of the paragraph-separating space that appears when <para> elements are used.

Additional notes:

• Multiple paragraphs should not be appearing in the <summary> element. When used, it's typically serving as a workaround for the fact that the <remarks> and <example> elements are treated as nearly non-existent by the IDE. I filed Documentation 'remarks' and 'example' elements are not shown to users #26504 for this issue.
• The request to have paragraphs without <para> is likely a duplicate of Use Markdown in Documentation Comments to Reference Source Code csharplang#891 and/or Using YAML + Markdown format in documentation comments csharplang#878.

[jinujoseph]

Tentatively marking as By Design
We will taking this for review and will update with final conclusion.

[sharwell]

Today's design review confirmed that this behavior is By Design according to the current definition of the language. Note that it may be possible to implement an analyzer that inserts the <para> elements. I don't know of one that's readily available today, but you may be interested in openstacknetsdk/OpenStackNetAnalyzers#18 and/or DotNetAnalyzers/StyleCopAnalyzers#610 as a starting point.