SonarSource Rules
  • Products

    In-IDE

    Code Quality and Security in your IDE with SonarQube Ide

    IDE extension that lets you fix coding issues before they exist!

    Discover SonarQube for IDE

    SaaS

    Code Quality and Security in the cloud with SonarQube Cloud

    Setup is effortless and analysis is automatic for most languages

    Discover SonarQube Cloud

    Self-Hosted

    Code Quality and Security Self-Hosted with SonarQube Server

    Fast, accurate analysis; enterprise scalability

    Discover SonarQube Server
  • SecretsSecrets
  • ABAPABAP
  • AnsibleAnsible
  • ApexApex
  • AzureResourceManagerAzureResourceManager
  • CC
  • C#C#
  • C++C++
  • CloudFormationCloudFormation
  • COBOLCOBOL
  • CSSCSS
  • DartDart
  • DockerDocker
  • FlexFlex
  • GitHub ActionsGitHub Actions
  • GoGo
  • HTMLHTML
  • JavaJava
  • JavaScriptJavaScript
  • JSONJSON
  • JCLJCL
  • KotlinKotlin
  • KubernetesKubernetes
  • Objective CObjective C
  • PHPPHP
  • PL/IPL/I
  • PL/SQLPL/SQL
  • PythonPython
  • RPGRPG
  • RubyRuby
  • RustRust
  • ScalaScala
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
C#

C# static code analysis

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your C# code

  • All rules 493
  • Vulnerability46
  • Bug88
  • Security Hotspot24
  • Code Smell335

  • Quick Fix 61
Filtered: 13 rules found
brain-overload
    Impact
      Clean code attribute
        1. "goto" statement should not be used

           Code Smell
        2. Cognitive Complexity of methods should not be too high

           Code Smell
        3. Types and methods should not have too many generic parameters

           Code Smell
        4. Methods and properties should not be too complex

           Code Smell
        5. "switch" statements with many "case" clauses should have only one statement

           Code Smell
        6. Functions should not have too many lines of code

           Code Smell
        7. Control flow statements "if", "switch", "for", "foreach", "while", "do" and "try" should not be nested too deeply

           Code Smell
        8. Classes should not be coupled to too many other classes

           Code Smell
        9. "switch case" clauses should not have too many lines of code

           Code Smell
        10. Magic numbers should not be used

           Code Smell
        11. Methods should not have too many parameters

           Code Smell
        12. Expressions should not be too complex

           Code Smell
        13. Files should not have too many lines of code

           Code Smell

        "switch case" clauses should not have too many lines of code

        adaptability - focused
        maintainability
        Code Smell
        • brain-overload

        Why is this an issue?

        The switch statement should be used only to clearly define some new branches in the control flow. As soon as a case clause contains too many statements this highly decreases the readability of the overall control flow statement. In such case, the content of the case clause should be extracted into a dedicated method.

        Noncompliant code example

        With the default threshold of 8:

        switch (myVariable)
        {
            case 0: // Noncompliant: 9 statements in the case
                methodCall1("");
                methodCall2("");
                methodCall3("");
                methodCall4("");
                methodCall5("");
                methodCall6("");
                methodCall7("");
                methodCall8("");
                methodCall9("");
                break;
            case 1:
                ...
        }
        

        Compliant solution

        switch (myVariable)
        {
            case 0:
                DoSomething()
                break;
            case 1:
                ...
        }
        ...
        private void DoSomething()
        {
            methodCall1("");
            methodCall2("");
            methodCall3("");
            methodCall4("");
            methodCall5("");
            methodCall6("");
            methodCall7("");
            methodCall8("");
            methodCall9("");
        }
        
          Available In:
        • SonarQube IdeCatch issues on the fly,
          in your IDE
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
        • SonarQube Community BuildAnalyze code in your
          on-premise CI
          Available Since
          9.1
        • SonarQube ServerAnalyze code in your
          on-premise CI
          Developer Edition
          Available Since
          9.1

        © 2008-2025 SonarSource SA. All rights reserved.

        Sonar helps developers write Clean Code.
        Privacy Policy | Cookie Policy | Terms of Use