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
  • ShellShell
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
VB6

VB6 static code analysis

Unique rules to find Bugs, Security Hotspots, and Code Smells in your VB6 code

  • All rules 45
  • Bug1
  • Security Hotspot1
  • Code Smell43
Filtered: 9 rules found
convention
    Impact
      Clean code attribute
        1. Multiple variables should not be declared on the same line

           Code Smell
        2. Sub and function names should comply with a naming convention

           Code Smell
        3. Comments should not be located at the end of lines of code

           Code Smell
        4. Statements should be on separate lines

           Code Smell
        5. Constant names should comply with a naming convention

           Code Smell
        6. Lines should not end with trailing whitespaces

           Code Smell
        7. Source code should be indented consistently

           Code Smell
        8. Tabulation characters should not be used

           Code Smell
        9. Lines should not be too long

           Code Smell

        Constant names should comply with a naming convention

        consistency - identifiable
        maintainability
        Code Smell
        • convention

        Constants should be named consistently to communicate intent and improve maintainability. Rename your constants to follow your project’s naming convention to address this issue.

        Why is this an issue?

        How can I fix it?

        Constants are variables whose value does not change during the runtime of a program after initialization. Oftentimes, constants are used in multiple locations across different subroutines.

        It is important that the names of constants follow a consistent and easily recognizable pattern. This way, readers immediately understand that the referenced value does not change, which simplifies debugging.

        This rule checks that all constant names match a given regular expression.

        What is the potential impact?

        Ignoring the naming convention for constants makes the code less readable since constants and variables are harder to tell apart. Code that is hard to understand is also difficult to maintain between different team members.

          Available In:
        • SonarQube ServerAnalyze code in your
          on-premise CI
          Enterprise
          Edition
          Available Since
          9.1

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use