Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://docs.sonarsource.com/sonarqube/latest/analyzing-source-code/languages/csharp/ below:

C# | SonarQube Server Documentation

The level of support for a language is defined as follows: 

• Fully supported: Analysis will complete. All the language features are understood and examined.
• Supported: Most language features are understood and examined but the version includes unsupported features. Analysis might break or provide incomplete results.

C#1 to C#13: Fully supported

ASP.NET MVC, ASP.NET Core MVC

Discover and update the C#-specific properties in: Administration > Configuration > 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 Settings > General Settings > Languages > 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 .

When a Generated comment is present in the file, SonarQube ignores the entire file, even if only parts of it were generated. It's possible to enable or disable analysis of files containing generated code at the instance or project level in General Settings > Languages > Your language > Analyze generated code.

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.

[Path/File.cs]
dotnet_diagnostic.Sxxx.severity = none

• Importing external issues (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, VSTest)
• Introduction to the 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

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4