Was asked to analyse a library of Visual Basic 6 to determine the effort required to migrate it Visual Basic 2005/2008.

The good news was that most of the VB6 programs share common modules, so it will just be a case of fixing those modules once, then compiling and testing.

The bad news is that, yes, indeedly, the past is another country, they did things differently there; the code isn’t widely documented, and not what you’d call best practice these days.

An example is the use of the RtlCopyMemory function, which now is “banned” by Microsoft as it’s not secure.

Anyhow, to count the lines of VB6 code we have, I used a free utility called VB 6 Pure Code Lines Calculator, and I found it to be fast and accurate.

Related posts:

Get the logged on user – code which works! Code to launch an Internet Explorer window from VBscript. “VBA? You wrote VBA code for that?”

Powered by YARPP.