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

        "ValueTask" should be consumed correctly

        intentionality - complete
        maintainability
        Code Smell
        • async-await

        Why is this an issue?

        How can I fix it?

        More Info

        ValueTask<TResult> provides a value type that wraps a Task<TResult> and the corresponding TResult. It was introduced in .NET Core 2.0 to optimize memory allocation when functions return their results synchronously.

        Using ValueTask and ValueTask<TResult> in the following ways is discouraged as it could result in a race condition:

        • Calling await multiple times on a ValueTask/ValueTask<TResult>. The wrapped object may have been reused by another operation. This differs from Task/Task<TResult>, on which you can await multiple times and always get the same result.
        • Calling await concurrently on a ValueTask/ValueTask<TResult>. The underlying object is not thread safe. What’s more, it has the same effect as awaiting multiple times a ValueTask/ValueTask<TResult>. This again differs from Task/Task<TResult>, which support concurrent await.
        • Using .Result or .GetAwaiter().GetResult() without checking if the operation is completed. IValueTaskSource/IValueTaskSource<TResult> implementations are not required to block until the operation completes. On the other hand, Task/Task<TResult> blocks the call until the task completes.

        It is recommended to use ValueTask/ValueTask<TResult> either by calling await on the function returning it, optionally calling ConfigureAwait(false) on it, or by calling .AsTask() on it.

        This rule raises an issue when the following operations are performed on a ValueTask/ValueTask<TResult> instance unless it happens in a loop:

        • Awaiting the instance multiple times.
        • Calling AsTask multiple times.
        • Using .Result or .GetAwaiter().GetResult() multiple times
        • Using .Result or .GetAwaiter().GetResult() when the operation has not yet completed
        • Using of these ways to consume the instance multiple times.
          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