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

        Cognitive Complexity of methods should not be too high

        adaptability - focused
        maintainability
        Code Smell
        • architecture
        • brain-overload

        This rule raises an issue when the code cognitive complexity of a function is above a certain threshold.

        Why is this an issue?

        How can I fix it?

        More Info

        Cognitive Complexity is a measure of how hard it is to understand the control flow of a unit of code. Code with high cognitive complexity is hard to read, understand, test, and modify.

        As a rule of thumb, high cognitive complexity is a sign that the code should be refactored into smaller, easier-to-manage pieces.

        Which syntax in code does impact cognitive complexity score?

        Here are the core concepts:

        • Cognitive complexity is incremented each time the code breaks the normal linear reading flow.
          This concerns, for example, loop structures, conditionals, catches, switches, jumps to labels, and conditions mixing multiple operators.
        • Each nesting level increases complexity.
          During code reading, the deeper you go through nested layers, the harder it becomes to keep the context in mind.
        • Method calls are free
          A well-picked method name is a summary of multiple lines of code. A reader can first explore a high-level view of what the code is performing then go deeper and deeper by looking at called functions content.
          Note: This does not apply to recursive calls, those will increment cognitive score.

        The method of computation is fully detailed in the pdf linked in the resources.

        What is the potential impact?

        Developers spend more time reading and understanding code than writing it. High cognitive complexity slows down changes and increases the cost of maintenance.

          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