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: 11 rules found
multi-threading
    Impact
      Clean code attribute
        1. Blocks should not be synchronized on local variables

           Bug
        2. Threads should not lock on objects with weak identity

           Code Smell
        3. "Thread.Resume" and "Thread.Suspend" should not be used

           Bug
        4. "this" should not be exposed from constructors

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

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

           Bug
        7. "ThreadStatic" fields should not be initialized

           Bug
        8. Instance members should not write to "static" fields

           Code Smell
        9. Shared resources should not be used for locking

           Bug
        10. Blocks should be synchronized on read-only fields

           Bug
        11. Locks should be released on all paths

           Bug

        "ConfigureAwait(false)" should be used

        intentionality - complete
        maintainability
        Code Smell
        • multi-threading
        • async-await
        • suspicious
        • performance

        Why is this an issue?

        After an awaited Task has executed, you can continue execution in the original, calling thread or any arbitrary thread. Unless the rest of the code needs the context from which the Task was spawned, Task.ConfigureAwait(false) should be used to keep execution in the Task thread to avoid the need for context switching and the possibility of deadlocks.

        This rule raises an issue when code in a class library targeting .Net Framework awaits a Task and continues execution in the original calling thread.

        The rule does not raise for .Net Core libraries as there is no SynchronizationContext in .Net Core.

        Noncompliant code example

        var response = await httpClient.GetAsync(url);  // Noncompliant
        

        Compliant solution

        var response = await httpClient.GetAsync(url).ConfigureAwait(false);
        
          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