VB Migration Partner


Previous | Index | Next 

[INFO] Multithreaded VB6 applications don’t retain their multithreading behavior

The most common technique to implement a multi-threaded VB6 application is compiling the application as an ActiveX EXE component, having it expose a SingleUse class, and ensuring that the threading model option is set to Thread per Object. If the application creates an instance of such a class by means of a CreateObject method, then the code inside that instance runs in a different thread.

This threading model isn’t supported under the .NET Framework. Applications of this kind can be migrated to .NET without any error, but are converted to standard EXE projects. Instantiating the class with CreateObject still works, but the created instance runs in the same thread as the application.

The only way to implement a robust multi-threaded .NET application is by means of classes defined in the System.Threading namespace.

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