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: 6 rules found
azure
    Impact
      Clean code attribute
        1. Interfaces for durable entities should satisfy the restrictions

           Code Smell
        2. Azure Functions should log all failures

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

           Code Smell
        4. Azure Functions should use Structured Error Handling

           Code Smell
        5. Client instances should not be recreated on each Azure Function invocation

           Code Smell
        6. Azure Functions should be stateless

           Code Smell

        Azure Functions should be stateless

        intentionality - complete
        maintainability
        Code Smell
        • azure
        • bad-practice

        Why is this an issue?

        More Info

        An Azure Function should be stateless as there’s no control over where and when function instances are provisioned and de-provisioned. Managing and storing data/state between requests can lead to inconsistencies. If, for any reason, you need to have a stateful function, consider using the Durable Functions extension of Azure Functions.

        Noncompliant code example

            public static class HttpExample
            {
                private static readonly int port = 2000;
                private static int numOfRequests = 1;
        
                [FunctionName("HttpExample")]
                public static async Task<IActionResult> Run( [HttpTrigger(AuthorizationLevel.Anonymous, "get", Route = null)] HttpRequest request, ILogger log)
                {
                    numOfRequests += 1; // Noncompliant
                    log.LogInformation($"Number of POST requests is {numOfRequests}.");
        
                    string responseMessage = $"HttpRequest was made on port {port}."; // Compliant, state is only read.
        
                    return new OkObjectResult(responseMessage);
                }
            }
        

        Compliant solution

            public static class HttpExample
            {
                private static readonly int port = 2000;
        
                [FunctionName("HttpExample")]
                public static async Task<IActionResult> Run( [HttpTrigger(AuthorizationLevel.Anonymous, "get", Route = null)] HttpRequest request, ILogger log)
                {
                    // A compliant solution would be to manage the `numOfRequests` with an entity function or would use storage (e.g., Azure Blob storage, Azure Queue Storage)
                    // to share the state between functions.
        
                    string responseMessage = $"HttpRequest was made on port {port}.";
        
                    return new OkObjectResult(responseMessage);
                }
            }
        
          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.6
        • SonarQube ServerAnalyze code in your
          on-premise CI
          Developer Edition
          Available Since
          9.6

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use