-
Notifications
You must be signed in to change notification settings - Fork 510
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SA1642SA1643CodeFixProvider fails (and crashes VS) #780
Comments
There is a very high likelihood that this is fixed by #609. |
Reported as a Roslyn bug and fixed by both working around the issue and adding a test that will alert us when we upgrade to a version of Roslyn which no longer suffers from the bug. |
Can you link to the Roslyn bug? |
I already did above 😉 |
Oh, right. whoops. I thought that was the bug I had filed on another argument validation bug in that same method. But I see you filed this one and it tracks something different. |
In a project with StyleCop.Analyzers.1.0.0-alpha005 installed, define this class:
Press Ctrl+. on the xml doc comment that gets a diagnostic for having a bad constructor message.
VS crashes, after throwing the exception below. Note that I have filed no less than 3 bugs with VS since we shouldn't be crashing anyway (including dotnet/roslyn#2496 and 2 more internally) but we should of course get StyleCop.Analyzers itself fixed as well.
The text was updated successfully, but these errors were encountered: