dotnet/roslyn

Can't diagnose analyzer error related to generated file.

Open

#50,166 opened on Dec 29, 2020

View on GitHub
 (3 comments) (0 reactions) (1 assignee)C# (4,257 forks)batch import
Area-AnalyzersBugFeature - Source Generatorshelp wanted

Repository metrics

Stars
 (20,414 stars)
PR merge metrics
 (Avg merge 6d 17h) (256 merged PRs in 30d)

Description

Running build.cmd -a on roslyn, i get:

C:\github\roslyn\src\Compilers\CSharp\Portable\CSharpSyntaxGenerator\CSharpSyntaxGenerator.SourceGenerator\Syntax.xml.Main.Generated.cs(4565,44): error RS0016: Symbol 'UsingDirective' is not part of the declared API [C:\github\roslyn\sr
c\Compilers\CSharp\Portable\Microsoft.CodeAnalysis.CSharp.csproj]
C:\github\roslyn\src\Compilers\CSharp\Portable\CSharpSyntaxGenerator\CSharpSyntaxGenerator.SourceGenerator\Syntax.xml.Main.Generated.cs(4574,44): error RS0016: Symbol 'UsingDirective' is not part of the declared API [C:\github\roslyn\sr
c\Compilers\CSharp\Portable\Microsoft.CodeAnalysis.CSharp.csproj]
C:\github\roslyn\src\Compilers\CSharp\Portable\CSharpSyntaxGenerator\CSharpSyntaxGenerator.SourceGenerator\Syntax.xml.Main.Generated.cs(4578,44): error RS0016: Symbol 'UsingDirective' is not part of the declared API [C:\github\roslyn\sr
c\Compilers\CSharp\Portable\Microsoft.CodeAnalysis.CSharp.csproj]

However, when i go to try to open those files to look at those lines so i can see what is being complained about, i don't see those files on disk at the path the error message specifies. So i can't figure out what's gone wrong or how to fix it.

Contributor guide

Research direction
Locate the generated file Syntax.xml.Main.Generated.cs in the output directory. The file is generated during the build process. Check the Roslyn source generators to understand how the file is produced and why 'UsingDirective' is missing from the declared API. The error RS0016 indicates a public API surface mismatch.
Tech stack
csharp
Domain
compilers
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40