Generate code with consistent line endings #412
Conversation
This worksaround VS's annoying dialog when opening generated code that offers to normalize line endings (on the readonly file). Fixes #369
| } | ||
| } | ||
|
|
||
| private static void AssertConsistentLineEndings(SyntaxTree syntaxTree) |
There was a problem hiding this comment.
💡 You could use the new EqualOrDiff functionality from dotnet/roslyn-sdk for this assertion by asserting the syntaxTree.GetText() is the same as syntaxTree.GetText().Replace("\r\n", "\n").
There was a problem hiding this comment.
Ooh, that's nice. Thanks for the tip. Where is this EqualOrDiff method exposed, or would I need to copy its source?
There was a problem hiding this comment.
If you already reference MS.CA.Testing, you can use DefaultVerifier with this extension method. Otherwise the source is reasonably easy to copy.
There was a problem hiding this comment.
Note that EqualOrDiff was originally implemented by you, but we modified it in dotnet/roslyn-sdk#878 and dotnet/roslyn-sdk#886 to specifically support cases where only the line endings changed.
There was a problem hiding this comment.
Ya, I thought I remembered that I had shared it. We developed it for vs-mef.
This worksaround VS's annoying dialog when opening generated code that offers to normalize line endings (on the readonly file).
Fixes #369