VB Migration Partner


Previous | Index | Next 

[INFO] Two .NET project can't coexist in the same directory

VB6 developers might not immediately realize that two .NET projects must be stored in different folders. If you are converting two or more VB6 projects stored in the same folder, by default VB Migration Partner selects the same output directory for both .NET projects and the neat result is that the second .NET application overwrites the first one. Therefore, please pay attention to VB Migration Partner’s warning that indicates that you are about to overwrite an existing directory.

You can avoid this minor annoyance in two ways. The first, obvious way is to reorganize the VB6 projects so that they don’t share the same folder. The second way is migrating a VB6 project group that gathers the two projects instead of migrating each project separatedly.

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