VB Migration Partner


Previous | Index | Next 

[PRB] VB.NET doesn’t support implicit conversions in Const statements

VB6 supports implicit conversions between numbers and string values inside Const statements, whereas VB.NET doesn’t. For example, this code is legal in VB6 but causes a compilation error in VB.NET:

        Const ONE As String = "1"
        Const TWO As Integer = ONE * 2

The current version of VB Migration Partner can’t solve this problem, even though a future version might generate code that works around this issue. In the meantime, the simpler solution to this (admittedly rare) problem is removing the offending statement, either by editing the original VB6 code or by adding a ParseReplace pragma:

        Const ONE As String = "1"
        '## ParseReplace Const TWO As Integer = 1 * 2
        Const TWO As Integer = ONE * 2
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