VB Migration Partner


Previous | Index | Next 

[PRB] The VB.Global object isn’t migrated

Expert VB6 developers may sometimes pass the VB.Global object from the main VB6 project to a method exposed by an ActiveX DLL object. This advanced techniques was useful to allow the external DLL to access the current printer, the App object or the Forms collection of the main project.

Please notice that passing the VB.Global object to another DLL wasn’t a recommended VB6 practice, because the VB.Global class was private. (In fact, the receiving method has to declare a parameter of type Object or Variant, and access the object via late-binding.)

VB Migration Partner doesn’t support the migration of the VB.Global object. All occurrences of the VB.Global object are turned into references to CodeArchitects.VBMigrationEngine.Mirror_VB.GlobalObject, which cause a compilation error in the migrated project.

From the VB Migration Partner’s perspective, there is no VB.Global *instance* because the Forms, Screen, App, Printer, etc. global objects are defined in the VisualBasic_Support standard module (or in the VB6Project class if converting to C#). There are two ways to work around this limitation:

First, you can pass individual Forms, App, Printer, etc. properties instead of a single VB.Global object. This is the simplest technique, even though it requires that you modify either the original VB6 code or the migrated VB.NET code.

Second, insert the following class in a proper location of the current project:

    Public Class VB6Globals  
      Public Shared ReadOnly Instance As New VB6Globals  
      Public ReadOnly Property Forms6() As VB6Forms 
          Return VisualBasic6_Support.Forms6 
        End Get 
      End Property  
'similar code for other App, Printer, and other global objects
    End Class
           public class VB6Globals
               public static VB6Globals Instance = new VB6Globals();

               public VB6Forms Forms6
                       return VB6Project.Forms6;

             // similar code for other App, Printer, and other global objects


then modify all occurrences of the CodeArchitects.VBMigrationEngine.Mirror_VB.GlobalObject into VB6Globals.Instance. (You can automate these two tasks by means of pragmas: use a PostInclude or OutputMode pragmas to insert the new class in a proper location of your code, and use a PostProcess pragma to change all references to VB6Global.Instance.)

If you pass the VB6Globals.Instance reference to a different DLL, it is mandatory that you access its properties via late-binding, because the VB6Globals class defined in project A is different from the VB6Globals class defined in project B. For this reason, the receiving parameter in Project B can only be of type Object.

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