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: 27 rules found
clumsy
    Impact
      Clean code attribute
        1. "Trace.WriteLineIf" should not be used with "TraceSwitch" levels

           Code Smell
        2. Arrays should not be created for params parameters

           Code Smell
        3. Jump statements should not be redundant

           Code Smell
        4. Empty "default" clauses should be removed

           Code Smell
        5. Empty "case" clauses that fall through to the "default" should be omitted

           Code Smell
        6. "string.ToCharArray()" and "ReadOnlySpan<T>.ToArray()" should not be called redundantly

           Bug
        7. Redundant property names should be omitted in anonymous classes

           Code Smell
        8. Declarations and initializations should be as concise as possible

           Code Smell
        9. "string.IsNullOrEmpty" should be used

           Code Smell
        10. Default parameter values should not be passed as arguments

           Code Smell
        11. Constructor and destructor declarations should not be redundant

           Code Smell
        12. The simplest possible condition syntax should be used

           Code Smell
        13. LINQ expressions should be simplified

           Code Smell
        14. Sequential tests should not check the same condition

           Code Smell
        15. "catch" clauses should do more than rethrow

           Code Smell
        16. Redundant modifiers should not be used

           Code Smell
        17. "try" statements with identical "catch" and/or "finally" blocks should be merged

           Code Smell
        18. Trivial properties should be auto-implemented

           Code Smell
        19. Runtime type checking should be simplified

           Code Smell
        20. Classes should not be empty

           Code Smell
        21. Inheritance list should not be redundant

           Code Smell
        22. Redundant casts should not be used

           Code Smell
        23. "ToString()" calls should not be redundant

           Code Smell
        24. A "while" loop should be used instead of a "for" loop

           Code Smell
        25. Overriding members should do more than simply call the same member in the base class

           Code Smell
        26. Boolean literals should not be redundant

           Code Smell
        27. Mergeable "if" statements should be combined

           Code Smell

        Constructor and destructor declarations should not be redundant

        intentionality - clear
        maintainability
        Code Smell
        Quick FixIDE quick fixes available with SonarLint
        • finding
        • clumsy

        Why is this an issue?

        Since the compiler will automatically invoke the base type’s no-argument constructor, there’s no need to specify its invocation explicitly. Also, when only a single public parameterless constructor is defined in a class, then that constructor can be removed because the compiler would generate it automatically. Similarly, empty static constructors and empty destructors are also wasted keystrokes.

        Noncompliant code example

        class X
        {
          public X() { } // Noncompliant
          static X() { }  // Noncompliant
          ~X() { } // Noncompliant
        
          ...
        }
        
        class Y : X
        {
          public Y(int parameter) : base() // Noncompliant
          {
            /* does something with the parameter */
          }
        }
        

        Compliant solution

        class X
        {
          ...
        }
        
        class Y : X
        {
          public Y(int parameter)
          {
            /* does something with the parameter */
          }
        }
        
          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.

        Privacy Policy | Cookie Policy | Terms of Use