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: 8 rules found
async-await
    Impact
      Clean code attribute
        1. Awaitable method should be used

           Code Smell
        2. Calls to "async" methods should not be blocking in Azure Functions

           Code Smell
        3. "ValueTask" should be consumed correctly

           Code Smell
        4. Non-async "Task/Task<T>" methods should not return null

           Bug
        5. Calls to "async" methods should not be blocking

           Code Smell
        6. Parameter validation in "async"/"await" methods should be wrapped

           Code Smell
        7. "ConfigureAwait(false)" should be used

           Code Smell
        8. "async" methods should not return "void"

           Bug

        "async" methods should not return "void"

        consistency - conventional
        reliability
        Bug
        • multi-threading
        • async-await

        Why is this an issue?

        How can I fix it?

        More Info

        An async method with a void return type does not follow the task asynchronous programming (TAP) model since the return type should be Task or Task<TResult>

        Doing so prevents control over the asynchronous execution, such as:

        • waiting for the execution to complete
        • catching any exception that might occur during execution
        • testing execution behavior

        Exceptions

        • Methods implementing an interface
        • Methods overriding a base class method
        • Virtual methods
        • Methods with the EventHandler delegate signature Using void for EventHandler is compliant with the TAP model.
          public async void button1_Click(object sender, EventArgs e)
          {
            await DoSomethingAsync();
          }
          
        • Methods name matching On[A-Z]\w* pattern Some frameworks may not use the same EventHandler method signature.
          public async void OnClick(EventContext data)
          {
            await DoSomethingAsync();
          }
          
          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