-
Notifications
You must be signed in to change notification settings - Fork 470
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
Intermittent NullReferenceException in CSharpDiagnosticAnalyzerApiUsageAnalyzer #1771
Comments
From @sharwell on August 7, 2018 16:24 @jinujoseph Can you move this to dotnet/roslyn-analyzers |
@yaakov-h I am unable to build your solution:
|
Ah, I was missing executing https://github.com/WiseTechGlobal/WTG.Analyzers/blob/master/appveyor.yml#L23. |
I'm using the latest bits and I still get this warning. I don't want to see any warnings at all. How do I get rid of these? |
Here's how you can solve this for the time being: agracio/edge-js#61 |
@camainc @niklaskihl Do you have a repro that I can use to investigate? Meanwhile, you can workaround by adding a
|
@camainc @niklaskihl Can you see if this comment matches your repro: #1888 (comment)? If so, can you try to add an explicit package reference to Microsoft.CodeAnalysis.Analyzers version 2.6.3 in your failing project? |
@mavasani This seems to have solved it for us anyway! Thanks! |
I'm writing my own analyzer and ran into this exception in the project were I used the analyzer. After some time I finally found out that the way I references From my analyzer csproj: This comment might be misplaced, but I fixed "the issue" for me :) |
I looked at the whole thread, I am using VS 2019 Preview, latest patch and I have always had this error on my .Net Core 3.0 projects.
None of the above fixes works for me, I also do not reference Microsoft.CodeAnalysis.Analyzers. |
@PeterPann23 - The analyzer in your repro ( |
From @yaakov-h on August 7, 2018 3:58
Version Used:
Microsoft.CodeAnalysis.Analyzers v2.6.1
Steps to Reproduce:
Expected Behavior:
No null reference exceptions in MS analyzers
Actual Behavior:
Sometimes null reference exception in MS analyzers
Copied from original issue: dotnet/roslyn#29119
The text was updated successfully, but these errors were encountered: