Static code analysis tools for VB6

Question

Right now we are maintaining some old project written in VB6 we are planning to implement continuous integration server for it. We would like to implement some code analysis as well to track that maintanability at least not getting worse. Basically there is only one requirement - the tool should be command line so we can call it from continuous integration server and it should work with VB6 projects. I will really appreciate any recommendations regards tools to try.

Thank you, Maksym

Inhaul

Answer 1

You could look at SourceMonitor as this says that it can produce metrics for VB6, and can be made to work from the command line.

I've only used it for C++ myself.

Torques

Thanks, you are right SourceMonitor should work for VB6, I just forgot that it is cross language. Really thanks – Inhaul

Answer 2

Have you looked at the recommendations in this question about tools for analysing VB6 source code?

I don't know whether any of these tools can be run from the command-line.

Degauss

Unfortunately, I took a look on Project Analyzer before and it looks like it does not support command line execution – Inhaul

Answer 3

The Code Advisor for Visual Basic 6 is an add-in used to review your code to ensure that it meets predetermined coding standards.

The coding standards are based on best practices developed by Microsoft to produce robust and easy-to-maintain code.

http://www.microsoft.com/en-us/download/details.aspx?id=1222

Domiciliary

Answer 4

You can use VBDepend for VB6 and VBA code, static analysis tool based on CQL, here is some of its functionality:

Compare Builds, 60 code metrics, manage Complexity and Dependencies

However VBDepend does not have a rule to check for duplicate/repeated code in the project. This was the most important rule that I was looking for.

Ballade

Answer 5

Our SD Source Code Search Engine is a tool for lightning-fast search across large code bases.

It words by breaking the text into language atoms, indexing all those atoms, and then executing queries using the indexes to guide the search. The SCSE has a VB6-specific front end (as well as front ends for a wide variety of other languages).

As a side effect of the indexing process, it produces metrics: SLOC, number of comments, Cyclomatic Complexity, Halstead measures, deepest-nested conditionals, etc. These metrics are emitted to an XML file that can be formatted/interrogated any way you like.

The indexing process is a command-line step, so you can integrate it into your scripts.

We also have a clone detector for VB6 that finds exact and near-miss duplicate blocks of code across large systems of source code.

Akee