Youssef Victor
Youssef Victor
You may find the unit tests I've [here](https://github.com/Youssef1313/PrintMembersGenerator/tree/master/src/PrintMembersGeneratorTests) useful. I haven't worked hard to get a neat test infrastructure, so there is much room to improve. But it's a good...
SA1000 was already fixed. See https://github.com/DotNetAnalyzers/StyleCopAnalyzers/issues/3561
https://github.com/YairHalberstadt/stronginject/commit/40c27214a3405a3e8f3a2cbd83aed27566cbc797 for an example where this was done.
@sharwell Message: ``` Microsoft.CodeAnalysis.Testing.Verifiers.EqualWithMessageException : Context: Iterative code fix application Expected '0' iterations but found '1' iterations. ``` The scenario was: A codefix is offered with no changes, i.e: ...
Why not try to re-write the existing analyzers as operation analyzers? That has many benefits: - More performant. - Less error-prone. - Gives VB for free (one analyzer implementation for...
Does https://docs.microsoft.com/dotnet/csharp/roslyn-sdk/tutorials/how-to-write-csharp-analyzer-code-fix sounds like a good place to document this?
I think this relates to dotnet/roslyn-sdk repository. https://github.com/dotnet/roslyn-sdk/tree/8647b801e8696dfc566bf18f2e7df34822ad3255/src/VisualStudio.Roslyn.SDK/Roslyn.SDK
@sharwell I think using https://github.com/dotnet/versionsweeper in the repository would be a good idea.
Does PR #1895 fix that ?