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

        General or reserved exceptions should never be thrown

        intentionality - complete
        maintainability
        Code Smell
        • cwe
        • error-handling

        This rule raises an issue when a general or reserved exception is thrown.

        Why is this an issue?

        How can I fix it?

        More Info

        Throwing general exceptions such as Exception, SystemException and ApplicationException will have a negative impact on any code trying to catch these exceptions.

        From a consumer perspective, it is generally a best practice to only catch exceptions you intend to handle. Other exceptions should ideally be let to propagate up the stack trace so that they can be dealt with appropriately. When a general exception is thrown, it forces consumers to catch exceptions they do not intend to handle, which they then have to re-throw.

        Besides, when working with a general type of exception, the only way to distinguish between multiple exceptions is to check their message, which is error-prone and difficult to maintain. Legitimate exceptions may be unintentionally silenced and errors may be hidden.

        For instance, if an exception such as StackOverflowException is caught and not re-thrown, it may prevent the program from terminating gracefully.

        When throwing an exception, it is therefore recommended to throw the most specific exception possible so that it can be handled intentionally by consumers.

        Additionally, some reserved exceptions should not be thrown manually. Exceptions such as IndexOutOfRangeException, NullReferenceException, OutOfMemoryException or ExecutionEngineException will be thrown automatically by the runtime when the corresponding error occurs. Many of them indicate serious errors, which the application may not be able to recover from. It is therefore recommended to avoid throwing them as well as using them as base classes.

          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