bugreport: VBControlExtender miseries

[Vlad Vissoultchev]

finally nailed it. this has bugged me for FOUR YEARS. somebody better report
it to microsoft (or is it too late for VB6:-))

---- the problem:

if you are using "Private WithEvents m_oExtender As VBControlExtender" to
sink events from custom build UserControl you usually use
m_oExtender_ObjectEvent(Info As EventInfo) and inspect Info.Name. everything
is working ok UNTIL SUDDENLY STOPPING at certain point of developement!

at this time i had to change the design (used callback interface) because
couldn't find WHY this stoppage happened. later (after SP5) again
implemented the VBControlExtender design to find out it's still not working.

---- anyway, today just found WHY ON EARTH it's not working. and the reason
is:

the type library version number of your ActiveX Control component has grown
beyond 10.0 (in decimal) or a.0 (in hex)!!! this totally confuses
VBControlExtender implementation. VB obviously is accessing registry info of
the typelib INCORRECTLY

---- the fix:

just recompile your ActiveX Control project with "no compatibility" set.
this resets typelib version and voila -- here you have again all those
late-bound events :-)))

HTH,

</wqw>
Vlad Vissoultchev - MCSD, MCT