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: 12 rules found
api-design
    Impact
      Clean code attribute
        1. Custom attributes should be marked with "System.AttributeUsageAttribute"

           Code Smell
        2. Assemblies should explicitly specify COM visibility

           Code Smell
        3. Assemblies should be marked as CLS compliant

           Code Smell
        4. "Generic.List" instances should not be part of public APIs

           Code Smell
        5. Classes that provide "Equals(<T>)" should implement "IEquatable<T>"

           Code Smell
        6. Exception types should be "public"

           Code Smell
        7. "ServiceContract" and "OperationContract" attributes should be used together

           Code Smell
        8. Caller information parameters should come at the end of the parameter list

           Bug
        9. Generic type parameters should be co/contravariant when possible

           Code Smell
        10. Method parameters should be declared with base types

           Code Smell
        11. "is" should not be used with "this"

           Code Smell
        12. Properties should not make collection or array copies

           Code Smell

        Properties should not make collection or array copies

        intentionality - clear
        maintainability
        Code Smell
        • api-design
        • performance

        Why is this an issue?

        How can I fix it?

        More Info

        Most developers expect property access to be as efficient as field access. However, if a property returns a copy of an array or collection, it will be much slower than a simple field access, contrary to the caller’s likely expectations. Therefore, such properties should be refactored into methods so that callers are not surprised by the unexpectedly poor performance.

        This rule tracks calls to the following methods inside properties:

        • Enumerable.ToList
        • Enumerable.ToArray
        • Array.Clone
          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