VB Migration Partner


Previous | Index | Next 

[HOWTO] Have VB Migration Partner correctly locate TlbImp and other .NET SDK tools

VB Migration Partner uses the TlbImp, AxImp, and other command line tools behind the scenes. These tools are part of the .NET Framework and are installed in a location that depends on the current .NET Framework version, for example c:\Program Files\Microsoft SDKs\Windows\v7.0A\Bin\NETFX 4.0 Tools (for .NET 4.0) or c:\Program Files\Microsoft SDKs\Windows\v6.0\Bin (for .NET 3.5)

VB Migration Partner is usually able to correctly locate these tools, but in some cases the search fails or you might want VB Migration Partner to use a specific TlbImp or AxImp version. In such circumstances, you can specify a different folder for these .NET SDK utilities by setting a value in an entry near the and of the VBMigrationPartner.exe.config file:

        <setting name="FrameworkSdkPath" serializeAs="String">
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