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: 28 rules found
convention
    Impact
      Clean code attribute
        1. Literal suffixes should be upper case

           Code Smell
        2. Method overloads should be grouped together

           Code Smell
        3. Operator overloads should have named alternatives

           Code Smell
        4. Properties should be preferred

           Code Smell
        5. Type names should not match namespaces

           Code Smell
        6. Exceptions should provide standard constructors

           Code Smell
        7. Event Handlers should have the correct signature

           Code Smell
        8. Arguments of public methods should be validated against null

           Code Smell
        9. Parameter names should not duplicate the names of their methods

           Code Smell
        10. Attribute, EventArgs, and Exception type names should end with the type being extended

           Code Smell
        11. Non-flags enums should not be used in bitwise operations

           Code Smell
        12. Members should not be initialized to default values

           Code Smell
        13. Flags enumerations zero-value members should be named "None"

           Code Smell
        14. Enumeration type names should not have "Flags" or "Enum" suffixes

           Code Smell
        15. Enumeration types should comply with a naming convention

           Code Smell
        16. Classes named like "Exception" should extend "Exception" or a subclass

           Code Smell
        17. Underscores should be used to make large numbers readable

           Code Smell
        18. An abstract class should have both abstract and concrete methods

           Code Smell
        19. Multiple variables should not be declared on the same line

           Code Smell
        20. Track lack of copyright and license headers

           Code Smell
        21. Logger fields should be "private static readonly"

           Code Smell
        22. Statements should be on separate lines

           Code Smell
        23. Files should end with a newline

           Code Smell
        24. A close curly brace should be located at the beginning of a line

           Code Smell
        25. Tabulation characters should not be used

           Code Smell
        26. Lines should not be too long

           Code Smell
        27. Types should be named in PascalCase

           Code Smell
        28. Methods and properties should be named in PascalCase

           Code Smell

        Enumeration type names should not have "Flags" or "Enum" suffixes

        consistency - identifiable
        maintainability
        Code Smell
        • convention

        Why is this an issue?

        The information that an enumeration type is actually an enumeration or a set of flags should not be duplicated in its name.

        Noncompliant code example

        enum FooFlags // Noncompliant
        {
            Foo = 1
            Bar = 2
            Baz = 4
        }
        

        Compliant solution

        enum Foo
        {
            Foo = 1
            Bar = 2
            Baz = 4
        }
        
          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