VB Migration Partner


Previous | Index | Next 

[HOWTO] Ignore fatal runtime errors

VB6 applications terminate when a fatal error occurs and there is no way to change this default behavior. By default, converted .NET applications behave in same way; however you can change this behavior by setting the VB6Config.LogFatalErrors property to True in the Main method or in the Load event handler of the startup form:

        ' VB.NET 
        VB6Config.LogFatalErrors = True

        // C# 
        VB6Config.LogFatalErrors = True;

If the VB6Config.LogFatalErrors property is True, fatal errors cause a message box to be displayed, but the application isn’t terminated. You can use this feature during the test phase or to remotely diagnose problems that occur at your customer’s site.

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