VB Migration Partner


Previous | Index | Next 

[PRB] “Class” suffix may cause compilation errors

During the migration process, VB Migration Partner may need to append the “Class” suffix to the name of a COM class, for example ADODB.Recordset. This mechanism is thoroughly explained in this article, where you can also learn a few ways to get rid of this suffix when possible.

It turns out that in some circumstances under Visual Studio 2010 the “Class” suffix must be removed. The cause seems to be a bug in Visual Studio that has been confirmed yet not fixed as of this writing, as you can read here and here.

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