INFO: Visual Basic Object Browser Cannot See the Default Interface (258827)

MORE INFORMATION

Visual Basic uses the class module name as an alias for the default interface; that is, the Visual Basic compiler maps the class name to the default interface reference silently for you. For detailed information regarding the mapping, please see the related article listed in the "References" section.

While this transparent mapping works well in Visual Basic, the Object Browser could interpret the COM type library incorrectly when the implemented interface happens to be the default one. All default interface references are displayed as their corresponding CoClass names instead, because Visual Basic uses the CoClass name as an alias for the default interface reference to access it. For a type library from the following IDL file, the Object Browser cannot see the default interface IClass2:

library myTypeLib
{
    // Forward declare all types defined in this typelib
    interface IClass1;
    interface IClass2;

    interface IClass1 : IDispatch {
        [id(0x00000000)]
        HRESULT method1([out, retval] IClass2** pVal);
    };

    interface IClass2 : IDispatch {
        [id(0x00000000)]
        HRESULT method2([out, retval] BSTR* pVal);
    };

    coclass Class1 {
        [default] interface IClass1;
    };

    coclass Class2 {
        [default] interface IClass2;
    };
};
				

Class1's (actually interface IClass1's) method1 returns Class2 (actually IClass2 reference) instead of IClass2. This behavior occurs because Visual Basic uses the Class2 as an alias for the default interface IClass2.

In addition, when multiple CoClasses implement the same interface as a default one, the Object Browser uses the first occurring CoClass name for any reference to the default interface. This is by design.