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: 6 rules found
redundant
    Impact
      Clean code attribute
        1. Null checks should not be combined with "is" operator checks

           Code Smell
        2. Jump statements should not be redundant

           Code Smell
        3. Nullable type comparison should not be redundant

           Bug
        4. Boolean expressions should not be gratuitous

           Code Smell
        5. Redundant casts should not be used

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

           Code Smell

        Jump statements should not be redundant

        intentionality - clear
        maintainability
        Code Smell
        • redundant
        • clumsy

        Why is this an issue?

        Jump statements, such as return, yield break, goto, and continue are used to change the normal flow of execution in a program. However, redundant jump statements can make code difficult to read and maintain.

        Noncompliant code example

        void Foo()
        {
          goto A; // Noncompliant
          A:
          while (condition1)
          {
            if (condition2)
            {
              continue; // Noncompliant
            }
            else
            {
              DoTheThing();
            }
          }
          return; // Noncompliant; this is a void method
        }
        

        Compliant solution

        void Foo()
        {
          while (condition1)
          {
            if (!condition2)
            {
              DoTheThing();
            }
          }
        }
        

        Exceptions

        • return statements followed by a local function declaration are not considered redundant, as they help with readability.
          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