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 method parameters should be removed

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

        Why is this an issue?

        How can I fix it?

        A typical code smell known as unused function parameters refers to parameters declared in a function but not used anywhere within the function’s body. While this might seem harmless at first glance, it can lead to confusion and potential errors in your code. Disregarding the values passed to such parameters, the function’s behavior will be the same, but the programmer’s intention won’t be clearly expressed anymore. Therefore, removing function parameters that are not being utilized is considered best practice.

        This rule raises an issue when a private method or constructor of a class/struct takes a parameter without using it.

        Exceptions

        This rule doesn’t raise any issue in the following contexts:

        • The this parameter of extension methods.
        • Methods decorated with attributes.
        • Empty methods.
        • Methods which only throw NotImplementedException.
        • The Main method of the application.
        • virtual, override methods.
        • interface implementations.
          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