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: 23 rules found
unused
    Impact
      Clean code attribute
        1. Unread "private" fields should be removed

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

           Code Smell
        3. Method overloads with default parameter values should not overlap

           Code Smell
        4. Events should be invoked

           Code Smell
        5. Namespaces should not be empty

           Code Smell
        6. Methods should not return values that are never used

           Code Smell
        7. Redundant parentheses should not be used

           Code Smell
        8. "GC.SuppressFinalize" should not be invoked for types without destructors

           Code Smell
        9. "ThreadStatic" should not be used on non-static fields

           Bug
        10. "catch" clauses should do more than rethrow

           Code Smell
        11. Conditionally executed code should be reachable

           Bug
        12. Redundant modifiers should not be used

           Code Smell
        13. Unused type parameters should be removed

           Code Smell
        14. Test classes should contain at least one test case

           Code Smell
        15. Values should not be uselessly incremented

           Bug
        16. Related "if/else if" statements should not have the same condition

           Bug
        17. Unused assignments should be removed

           Code Smell
        18. Unused local variables should be removed

           Code Smell
        19. Sections of code should not be commented out

           Code Smell
        20. Unused method parameters should be removed

           Code Smell
        21. Unused private types or members should be removed

           Code Smell
        22. Unnecessary "using" should be removed

           Code Smell
        23. Empty statements should be removed

           Code Smell

        Unused local variables should be removed

        intentionality - clear
        maintainability
        Code Smell
        • unused

        Why is this an issue?

        How can I fix it?

        An unused local variable is a variable that has been declared but is not used anywhere in the block of code where it is defined. It is dead code, contributing to unnecessary complexity and leading to confusion when reading the code. Therefore, it should be removed from your code to maintain clarity and efficiency.

        What is the potential impact?

        Having unused local variables in your code can lead to several issues:

        • Decreased Readability: Unused variables can make your code more difficult to read. They add extra lines and complexity, which can distract from the main logic of the code.
        • Misunderstanding: When other developers read your code, they may wonder why a variable is declared but not used. This can lead to confusion and misinterpretation of the code’s intent.
        • Potential for Bugs: If a variable is declared but not used, it might indicate a bug or incomplete code. For example, if you declared a variable intending to use it in a calculation, but then forgot to do so, your program might not work as expected.
        • Maintenance Issues: Unused variables can make code maintenance more difficult. If a programmer sees an unused variable, they might think it is a mistake and try to 'fix' the code, potentially introducing new bugs.
        • Memory Usage: Although modern compilers are smart enough to ignore unused variables, not all compilers do this. In such cases, unused variables take up memory space, leading to inefficient use of resources.

        In summary, unused local variables can make your code less readable, more confusing, and harder to maintain, and they can potentially lead to bugs or inefficient memory use. Therefore, it is best to remove them.

        Exceptions

        Unused locally created resources in a using statement are not reported.

        using(var t = new TestTimer()) // t never used, but compliant.
        {
          //...
        }
        
          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