-
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
IdentifiersShouldHaveCorrectSuffixAnalyzer AD0001 #3414
Comments
Hmm how did you encounter this? Was it from build or live analysis? Expanding the IDE live analysis diagnostic in error list should always give you a callstack and richer exception information |
Wondering if the issue here is that BaseType can be null: Lines 129 to 131 in 6a5f5a1
/// <summary>
/// The declared base type of this type, or null. The object type, interface types,
/// and pointer types do not have a base type. The base type of a type parameter
/// is its effective base class.
/// </summary>
INamedTypeSymbol? BaseType { get; } |
I am using the last pre-release nuget package. And I don't have any expand option which is why I was asking. Regarding the location you are pointing to, yeah that seems like a bug. |
Tag @sharwell - seems like this is an AD0001 from command line build. Support to have context information was added in dotnet/roslyn#35871, but likely MSBuild output filters out extra info? |
Switching to MSBuild build output verbosity to detailed shows the exception information:
|
This NRE seems to be occur very commonly on just released https://www.nuget.org/packages/Microsoft.CodeAnalysis.FxCopAnalyzers/3.0.0-beta2.final. I will send out a fix and try to release a 3.0.0-beta3.final with a fix soon. |
Thank you for the fix and sorry to have miss this case when doing the implementation. |
No worries @Evangelink! Thanks for your help. |
Analyzer package
Microsoft.CodeAnalysis.FxCopAnalyzers
Package Version
3.0.0-beta2.20170.4
Issue
I don't have any stacktrace in my IDE, is there any option somewhere I can switch?
The text was updated successfully, but these errors were encountered: