Skip to content
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

Build failures due to CSharpDiagnosticAnalyzerApiUsageAnalyzer #1803

Closed
sharwell opened this issue Sep 4, 2018 · 6 comments · Fixed by #1843
Closed

Build failures due to CSharpDiagnosticAnalyzerApiUsageAnalyzer #1803

sharwell opened this issue Sep 4, 2018 · 6 comments · Fixed by #1843
Assignees
Labels
Area-Microsoft.CodeAnalysis.Analyzers Bug The product is not behaving according to its current intended design Resolution-Fixed

Comments

@sharwell
Copy link
Member

sharwell commented Sep 4, 2018

Analyzer package

Microsoft.CodeAnalysis.CSharp.Analyzers.MetaAnalyzers.CSharpDiagnosticAnalyzerApiUsageAnalyzer

Package Version

v2.6.1

Expected behavior

Build succeeds.

Actual behavior

https://ci.appveyor.com/project/sharwell/stylecopanalyzers/build/1.0.3466

CSC : error AD0001: Analyzer 'Microsoft.CodeAnalysis.CSharp.Analyzers.MetaAnalyzers.CSharpDiagnosticAnalyzerApiUsageAnalyzer' threw an exception of type 'System.NullReferenceException' with message 'Object reference not set to an instance of an object.'. [C:\projects\stylecopanalyzers\StyleCop.Analyzers\StyleCop.Analyzers.Test.CSharp7\StyleCop.Analyzers.Test.CSharp7.csproj]
sharwell added a commit to sharwell/StyleCopAnalyzers that referenced this issue Sep 4, 2018
@mavasani
Copy link
Contributor

mavasani commented Sep 4, 2018

Dupe of #1711

@mavasani
Copy link
Contributor

mavasani commented Sep 4, 2018

Re-opening as @sharwell mentioned the failing build didn't have any error types, which was the cause of the crash in #1711.

@mavasani mavasani reopened this Sep 4, 2018
@mavasani mavasani added Bug The product is not behaving according to its current intended design Area-Microsoft.CodeAnalysis.Analyzers and removed Resolution-Duplicate labels Sep 4, 2018
@mavasani mavasani self-assigned this Sep 4, 2018
@mavasani mavasani added this to the 15.9 milestone Sep 4, 2018
@alphaleonis
Copy link

We also get a whole heap of these warnings after upgrading to VS 15.8. Haven't been able to make a simple repro however, but I'm guessing you're on top of this? Any timeline for a fix?

@mavasani
Copy link
Contributor

mavasani commented Oct 4, 2018

I have a repro:

namespace N
{
    internal delegate void MyDelegate();
}

@adamralph
Copy link
Contributor

In which version was this fixed?

I'm using 2.10.0 and I'm having this problem.

@adamralph
Copy link
Contributor

FWIW, I've confirmed that 2.4.0 does not contain this bug, so I've reverted to that version.

FYI although 2.6.1 contains this bug, I didn't want to revert to 2.6.0 because 2.6.1 must be fixing some other bugs, and 2.6.1 is listed as the supported version in the 2.6.x range.

I can't upgrade past 2.10.0 because my analyzer needs to support VS 2017.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Microsoft.CodeAnalysis.Analyzers Bug The product is not behaving according to its current intended design Resolution-Fixed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants