[RESOLVED] The trick's Library-info-2: Error in loading DLL

[SearchingDataOnly]

I got an error while testing The trick's Library-info-2: Error in loading DLL

The test process is as follows:

(1) Open the RC6 .dll

(2) Click cVBDraw in the left listbox, and the system will pop up the error message: Error in loading DLL

[jpbro]

If you trap the error in frmLibInfo.LoadCoClass like this:

        On Error Resume Next
        Set impl = Nothing
        Set impl = typ.GetRefTypeInfo(hType)
        On Error GoTo 0
        
        If impl Is Nothing Then
         Debug.Print i
        Else
        impl.GetDocumentation -1, Name, vbNullString, 0, vbNullString

You can see that type.GetRefTypeInfo(hType) fails on indexes #1 and #3.... not sure why though.

[VanGoghGaming]

The RC6 dll is alive and it's protecting itself against inspection!

[jpbro]

The RC6 dll is alive and it's protecting itself against inspection!

And it's inside the room!

[Schmidt]

You can see that type.GetRefTypeInfo(hType) fails on indexes #1 and #3.... not sure why though.

cVBDraw maps "VB-Drawing- and -Scaling" to "antialiased Cairo-Drawing ... and Scaling" -
and its behaviour is tricky, because for that it had to implement the VB.Printer-interface -
as well as two additional interfaces (to account for the "weird-syntax": Print- as well as Line-, Circle- and Pset-calls).

Implements VB.Printer
Implements VBGraphics.IVBPrint
Implements VBGraphics.IVBGraphics

It compiles without problems - but the Print- Line- Circle- and Pset- commands are "special"
(not only syntax-wise) ... as we all know.

So, perhaps it is caused due to a "typelib-overlap" of VBGraphics.tlb with VBs intrinsic typelib-defs for IVBPrint and IVBGraphics...

Not sure about that (and at the moment "unwilling to investigate", due to time-constraints)...

Olaf

[The trick]

It's because VBGraphics.tlb isn't registered on end user machine. In order to see all the methods you should register it.

[SearchingDataOnly]

cVBDraw maps "VB-Drawing- and -Scaling" to "antialiased Cairo-Drawing ... and Scaling" -
and its behaviour is tricky, because for that it had to implement the VB.Printer-interface -
as well as two additional interfaces (to account for the "weird-syntax": Print- as well as Line-, Circle- and Pset-calls).

Implements VB.Printer
Implements VBGraphics.IVBPrint
Implements VBGraphics.IVBGraphics

It compiles without problems - but the Print- Line- Circle- and Pset- commands are "special"
(not only syntax-wise) ... as we all know.

So, perhaps it is caused due to a "typelib-overlap" of VBGraphics.tlb with VBs intrinsic typelib-defs for IVBPrint and IVBGraphics...

Not sure about that (and at the moment "unwilling to investigate", due to time-constraints)...

Olaf

I see, it's not a big problem, it doesn't affect my current work. Thank you, Olaf.

[SearchingDataOnly]

It's because VBGraphics.tlb isn't registered on end user machine. In order to see all the methods you should register it.

Thank you, The trick.