VB Migration Partner


Previous | Index | Next 

[PRB] VB Migration Partner is unable to run Visual Studio

If VB Migration Partner fails to run Microsoft Visual Studio, chances are that your registry is corrupted. At any rate, you can specify the exact path of the Visual Studio executable (devenv.exe) by editing the VisualStudioPath setting in VBMigrationPartner.exe.config file, as in the following example:

                <setting name="VisualStudioPath" serializeAs="String">
                    <value>c:\Visual Studio 2005\bin\devenv.exe</value>

This setting affects also the VBMP and AxWrapperGen command-line tools.

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