Release Notes - SonarVB6 - Version 2.0 - HTML format

Bug

  • [SONARVBSIX-88] - Typo on "Default values are mandatory for optionnal parameters" rule title

New Feature

  • [SONARVBSIX-57] - Rule : Threshold on function complexity
  • [SONARVBSIX-69] - Make the Visual Basic plugin support the Developer Cockpit plugin by providing the measures comments and loc by line
  • [SONARVBSIX-75] - Rule : Avoid too complex logical expression
  • [SONARVBSIX-83] - Integrate the Sonar Common Rules
  • [SONARVBSIX-151] - Rule: "[switch|CASE]" statements should not have too many "[case|WHEN]" clauses
  • [SONARVBSIX-152] - Rule: Lines should not end with trailing whitespaces
  • [SONARVBSIX-153] - Rule: Return of boolean expressions should not be wrapped into an "if-then-else" statement
  • [SONARVBSIX-154] - Rule: Source code should be indented consistently
  • [SONARVBSIX-155] - Rule: Empty statements should be removed
  • [SONARVBSIX-156] - Rule: Unused (private fields|variables) should be removed
  • [SONARVBSIX-158] - Rule: Comments should not be located at the end of lines of code
  • [SONARVBSIX-159] - Rule: Lines should not be too long
  • [SONARVBSIX-161] - Rule: Constant names should comply with a naming convention
  • [SONARVBSIX-162] - Rule: (Function|Procedure) names should comply with a naming convention
  • [SONARVBSIX-163] - Rule: Magic numbers should not be used
  • [SONARVBSIX-164] - Rule: [Functions|Methods|Modules|Subroutines] should not have too many lines
  • [SONARVBSIX-165] - Rule: The "&" operator should be used to concatenate strings
  • [SONARVBSIX-167] - Rule: IP addresses should not be hardcoded
  • [SONARVBSIX-168] - Rule: ["switch"|"CASE"|"Select Case"] statements should have at least 3 ["case"|"WHEN"|"Case"] clauses
  • [SONARVBSIX-169] - Rule: Strings should not be compared with empty string
  • [SONARVBSIX-170] - Rule: Strings should not be set to empty string
  • [SONARVBSIX-171] - Rule: String-specific functions should be used
  • [SONARVBSIX-172] - Rule: '$' should not be used in string variable names
  • [SONARVBSIX-173] - Rule: "Chr[W]$()" should not be used for certain characters
  • [SONARVBSIX-174] - Rule: "Asc[W]" should not be called on string constants
  • [SONARVBSIX-175] - Rule: Loop invariants should not be calculated inside the loop
  • [SONARVBSIX-176] - Rule: Statements should be on separate lines
  • [SONARVBSIX-177] - Rule: "[switch|CASE]" statements should end with a "[case default|WHEN OTHERS|Case Else]" clause
  • [SONARVBSIX-178] - Rule: "[goto|GOTO]" statement should not be used
  • [SONARVBSIX-179] - Rule: "Option Base" should not be used
  • [SONARVBSIX-180] - Rule: Error handlers should not declare their own error handlers
  • [SONARVBSIX-181] - Rule: Multiple variables should not be declared on the same line
  • [SONARVBSIX-182] - Rule: The bang ("!") operator should not be used
  • [SONARVBSIX-183] - Rule: "[switch|case|CASE|WHEN]" clauses should not have too many lines
  • [SONARVBSIX-187] - Rule: Variable data types should be declared explicitly
  • [SONARVBSIX-188] - Rule: Literal boolean values should not be used in condition expressions

Task

Improvement

  • [SONARVBSIX-84] - Any parsing error should be logged in the Sonar analysis log
  • [SONARVBSIX-86] - Update url in pom.xml
  • [SONARVBSIX-87] - Move the 'General Settings > Visual Basic > License' property to 'General Settings > Licenses > Visual Basic License'
  • [SONARVBSIX-89] - Rename the "Sonar" rule engine into "SonarQube"
  • [SONARVBSIX-92] - Make the Visual Basic plugin support the multi-language feature (SonarQube 4.2)
  • [SONARVBSIX-97] - Add a "File suffixes" property that is visible in the UI
  • [SONARVBSIX-98] - Upgrade minimal required version of SonarQube to 3.7.1
  • [SONARVBSIX-100] - Create a new parser of VB6 source files based on SSLR
  • [SONARVBSIX-149] - expose file suffixes property
  • [SONARVBSIX-184] - Feed basic metrics from new parser
  • [SONARVBSIX-185] - parse errors should be less spectacular
  • [SONARVBSIX-186] - Support Developer Cockpit metrics
  • [SONARVBSIX-189] - update default on-ness

Edit/Copy Release Notes

The text area below allows the project release notes to be edited and copied to another document.