Analyze generated code with SonarAnalyzer

Hello,

In SonarQube we have configured the analysis of the files generated by using sonar.scm.exclusions.disabled=true, but using Visual Studio we have the SonarAnalyzer.Csharp and we want it to also analyze the files generated. We try creating a .editorConfig with generated_code=false but this active all other analyzers like Stylecop but the SonarAnalyzer is not activated. Could you tell us how to activate the analysis of the generated code for the SonarAnalyzer?

Hi @eugeniolt

Just for clarity, you are not using SonarLint right? But directly reference SonarAnalyzer.Csharp as NuGet package in your project?

We are not using SonarLint, we are using SonarAnalyzer.Csharp as NuGet package.

Hi @eugeniolt

You need to configure a SonarLint.xml configuration file for your project(s).

You can find instructions in our README .

After you generate the SonarLint.xml, update the following setting to true

    <Setting>
      <Key>sonar.cs.analyzeGeneratedCode</Key>
      <Value>true</Value>
    </Setting>

We have been doing tests and we have managed to activate the SonarAnalyzer for all the generated code using:

    <Setting>
      <Key>sonar.cs.analyzeGeneratedCode</Key>
      <Value>true</Value>
    </Setting>

Now we want is to exclude some folders and files from the analysis, but we have tried putting it in the SonarLint.XML file and we have not succeeded:

    <Setting>
      <Key>sonar.exclusions</Key>
      <Value>**/Fakes/*.*, **/rules.cs</Value>
    </Setting>

Could you tell us how do it?

@eugeniolt there isn’t currently a Sonar-specific way to exclude C# files or folders from analysis.
It is on the roadmap for 2022 for SonarLint for VS.

As you are using the SonarAnalyzer.CSharp NuGet package directly, you can use standard VS Roslyn features to configure the analysis. You might be able to use an .editorconfig file to disable rules for specific set of files or folders.