Discover and update the C#-specific properties in: Administration > General Settings > Languages > C#.
To analyze tool-generated code (e.g. WCF code generated by
SvcUtil.exe, protobuf code generated by
protoc, Swagger client code generated by
NSwag) for a specific C# project, enable the "Analyze generated code" setting inside Project > Administration > General Settings > C#. By default, tool-generated code files are skipped from analysis.
The detection of generated code is based on file name, special comments and attributes. The currently recognized values are in GeneratedCodeRecognizer.cs.
To analyze C# code, you need to use the SonarScanner for .NET version 4.x or newer.
Files to be excluded should be set in the project configuration. Excluded files are still going to be analyzed during the compilation and the results will be filtered according to the exclusion settings.
As an alternative, an
.editorconfig file can be used to disable the analysis for a specific rule on a file or directory. This can solve performance problems on large files.
- Importing external issues (VSTest, NUnit, MSTest, xUnit)
- Excluding external Roslyn issues (See "Notes on external .NET issues")
- Test coverage and execution (Visual Studio Code Coverage, dotCover, OpenCover, Coverlet, Altcover)
- SonarScanner for .NET
- SonarQube extension for Azure DevOps
- Analysis of product projects vs. test projects
- Troubleshooting guide for .NET code coverage import
- Investigating the performance of .NET Analysis
© 2008-2023, SonarSource S.A, Switzerland. Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution-NonCommercial 3.0 United States License. SONARQUBE is a trademark of SonarSource SA. All other trademarks and copyrights are the property of their respective owners.