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: 2 rules found
pitfall
    Impact
      Clean code attribute
        1. "Select Case" statements should not be nested

           Code Smell
        2. "Option Base" should not be used

           Code Smell

        "Select Case" statements should not be nested

        adaptability - focused
        maintainability
        Code Smell
        • pitfall

        Why is this an issue?

        Nested Select Case structures are difficult to understand because you can easily confuse the cases of an inner Select Case as belonging to an outer statement. Therefore nested Select Case statements should be avoided.

        Specifically, you should structure your code to avoid the need for nested Select Case statements, but if you cannot, then consider moving the inner Select Case to another function.

        Noncompliant code example

        Public Sub Foo(A As Integer, B As Integer)
            Select Case A
                Case 0
                    ' ...
                Case 1
                    Select Case B   ' Noncompliant; nested Select Case
                        Case 2
                            ' ...
                        Case 3
                            ' ...
                        Case 4
                            ' ...
                        Case Else
                            ' ...
                    End Select
                Case 2
                    ' ...
                Case Else
                    ' ...
            End Select
        End Sub
        

        Compliant solution

        Public Sub Foo(A As Integer, B As Integer)
            Select Case A
                Case 0
                    ' ...
                Case 1
                    HandleB(B)
                Case 2
                    ' ...
                Case Else
                    ' ...
            End Select
        End Sub
        
          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