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: 17 rules found
error-handling
    Impact
      Clean code attribute
        1. Logging in a catch clause should pass the caught exception as a parameter.

           Code Smell
        2. Azure Functions should log all failures

           Code Smell
        3. Azure Functions should use Structured Error Handling

           Code Smell
        4. Delivering code in production with debug features activated is security-sensitive

           Security Hotspot
        5. Exceptions should not be created without being thrown

           Bug
        6. Exception types should be "public"

           Code Smell
        7. Exceptions should not be explicitly rethrown

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

           Code Smell
        9. Generic exceptions should not be ignored

           Code Smell
        10. Exceptions should not be thrown from property getters

           Code Smell
        11. Overflow checking should not be disabled for "Enumerable.Sum"

           Code Smell
        12. "Exception" should not be caught

           Code Smell
        13. Classes named like "Exception" should extend "Exception" or a subclass

           Code Smell
        14. Exceptions should be either logged or rethrown but not both

           Code Smell
        15. NullReferenceException should not be caught

           Code Smell
        16. Exceptions should not be thrown in finally blocks

           Code Smell
        17. General or reserved exceptions should never be thrown

           Code Smell

        Exceptions should not be explicitly rethrown

        intentionality - clear
        maintainability
        Code Smell
        Quick FixIDE quick fixes available with SonarLint
        • error-handling
        • confusing

        Why is this an issue?

        How can I fix it?

        More Info

        In C#, the throw statement can be used in two different ways:

        • by specifying an expression
        • without specifying an expression

        By specifying an expression

        In the software development context, an expression is a value or anything that executes and ends up being a value. The expression shall be implicitly convertible to System.Exception, and the result of evaluating the expression is converted to System.Exception before being thrown.

        try
        {
        }
        catch(Exception exception)
        {
          // code that uses the exception
          throw exception; // The exception stack trace is cleared up to this point.
        }
        

        In this case, the stack trace, will be cleared, losing the list of method calls between the original method that threw the exception and the current method.

        Without specifying an expression

        This syntax is supported only in a catch block, in which case, that statement re-throws the exception currently being handled by that catch block, preserving the stack trace.

        try
        {
        }
        catch(Exception exception)
        {
          // code that uses the exception
          throw; // The stack trace of the initial exception is preserved.
        }
        

        Exceptions

        It is allowed using the thrown exception as an argument and wrapping it in another exception.

        try
        {
        }
        catch(Exception exception)
        {
          throw new Exception("Additional information", exception);
        }
        
          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