User comments on Project Analyzer

These testimonials are spontaneous, authentic stories told us by real, live Project Analyzer users.

Authentic feedback from real users

Analyzing large projects

Matt Warner, TaxWorks

Understanding legacy code

Mike Donnellan

Converting from VB to C#

Curtis Forrester

Getting feedback when working alone

Kamilche

Identifying controls to replace

Ken Garrison, Fiserv

Reducing program size

Lance Keene, Sarbrook Company

Corey Alix

Toby Bascom

Cleaning up unused code

Justin H.

Larry Marshall

Spotting more dead code

Ken Halter, MS-MVP-VB
microsoft.public.vb.general.discussion

Improving quality of undocumented code

Theo de Roo, MAF Europe

Turning a project to another programmer

Danny Ringo, Odyssey Consulting Corp.

Discovering garbage in code

Torsten Borg, Fisa

Running code review

  1. Dead code, dead variables
  2. clearing violations, i.e. deallocating arrays or objects when finished using them
  3. notification of method arguments or local/member variables that are only written to or read from
  4. variables read before they have been written
  5. return values from functions that are either not declared, assigned, or used by calling methods.
  6. data types not declared for named constants
  7. ByVal parameter missing from method arguments
  8. When LenB or Trim$, etc. functions would be better to use
  9. Code not being reached
  10. Excess scope of a method or variable
  11. Possible short circuit issues with condition statements
  12. Use of As New in variable declaration
  13. Empty Case or condition statement blocks
  14. Optional argument missing default value

Carl Hoelzlhammer, Emerson Process Management

Independent reviews

Checking out Aivosto VB Project Analyzer's compatibility checklist

Francesco Balena

Visual Basic 6 to .Net Migration

Peter Aitken at DevSource.com

Pointing out where you need improvements

John Percival at Developer.com

A must

Aldo Vargas at Betanews.com

Thank you for sending us your comments.

©Aivosto Oy -