Code review rules

Code review rules by type

• Optimization
  Lines that slow down your program and consume extra memory. Unused code you can remove.
  • Optimization issues
  • Dead code detection
• Style
  Issues affecting programmers, not end-users. Inconsistent style may lead to lower understandability and errors in maintenance.
  • Style suggestions: declarations, disallowed statements and more
  • Class design style rules
  • Explicit clearing of variables: objects and dynamic arrays
  • Resource leak detection for API handles
  • Project NameCheck naming standards
• Logic
  Questionable control and data flows, erratic behavior, hidden flaws and problems waiting to emerge later.
  • Logic flaws
• Functionality
  Problems with run-time behavior and user interface. Potential sources of complaints by end-users.
  • Functionality problems
• Metrics (Enterprise Edition)
  Set metric targets and detect locations exceeding limits. Metrics is a sub-category of Style.
  • Metrics limits
• VB.NET Compatibility (Enterprise Edition)
  Incompatibilities between VB6 and VB.NET syntax.
  • VB.NET Compatibility Check
  • Compatibility rules

Severity levels

Critical. This problem makes your program worse. Fix these ones first.

Warning. The problem is not critical, but fixing it will improve your program.

Limitation. Analysis is limited by an error such as file not found. Right-click to view a suggested solution.