VB Migration Partner


Previous | Index | Next 

[BUG] #IF statement that use compiler constants starting with “vb”

A bug in current version of VB Migration Partner prevents the correct migration of #IF and #ELSEIF directives that use compiler constants whose name start with “vb”, as in this code:


#If vbExplorer Or vbElev Or vbFab Or vbInterface Then
     Public GrsElevationDetails As ADODB.Recordset 
#End If

The only available workaround is using a PreProcess pragma that modifies these names before the migration together with a PostProcess pragma that restores the correct names;

'## PreProcess "\bvb(?<name>Explorer|Elev|Fab|Interface)\b, "${name}VB"  
'## PostProcess "\b(?<name>Explorer|Elev|Fab|Interface)VB\b", "vb${name}"
Previous | Index | Next 

Follow Francesco Balena on VB6 migration’s group on


Read Microsoft Corp’s official case study of a VB6 conversion using VB Migration Partner.

Code Architects and its partners offers remote and onsite migration services.

More details

Subscribe to our free newsletter for useful VB6 migration tips and techniques.


To learn more about your VB6 applications, run VB6 Analyzer on your source code and send us the generated text file. You will receive a detailed report about your VB6 applications and how VB Migration Partner can help you to quickly and effectively migrate it to .NET.

Get free advice

A fully-working, time-limited Trial Edition of VB Migration Partner allows you to test it against your actual code

Get the Trial

The price of VB Migration Partner depends on the size of the VB6 application, the type of license, and other factors

Request a quote

Migrating a VB6 application in 10 easy steps

Comparing VB Migration Partner with Upgrade Wizard

Migration tools: Feature Comparison Table

All whitepapers