c# - How to debug why a VB6 application using my .NET ActiveX control does not register for events? -

My basic question was here, to help you find out how I implemented it.

C ++ ActiveX Control I'm replacing the COM event when one of VB6 client applications (VB6 believe me, because depends.exe tells me that it uses msvbvm60.dll ) uses instant and my replacement, it is not registered for any of the events, and unfortunately, by the way it What works is that after the completion of a special method call, until an event gets fire The client application does nothing.

This same application works fine with the C ++ implementation of control.

I have tried to get TypeLib generated by tlbexp.exe , as in C ++ version as I can create, and with the exception of properties, propagate and propagation (It seems that TLBXP does this) and an OLEHALDLL property, interface and collision announcements look almost identical, and important things like IDIPP-based interfaces, etc. are similar. / P>

I have seen an issue with replacement type lib that is to export any one as tlbexp.exe as the OLE_HANDLE form of the Cocos interface To do this, it ends long term in the TLB generated from the assembly (this is referred to by the TypeLib entry in the TLB registry). Can this cause problems with the incident?

Note: My Replacement ActiveX Control to System. Windows .form. Control comes from , and set based on the MiscStatus Coklese registry entries of 131457 , as I am changing, the same honestly wish is ActiveX control , And I could not get these current customers to instantiate myself until I got inherited from the WinForms control successfully without any code changes. Object

I'm not expecting that This legacy S wants screwing the events in the event.

I have tried this approach where my cocks have specified the interface to the public event with the same name, by ComSourceInterfaces , it works 100% from the C # app, which is Xhost Uses, events are triggered.

I have also tried to implement IConnectionPointContainer and supporting all the interfaces on my replacement control, and it works 100% from the C # app, but the VB app In this case, the client does not attempt the connection point of the sync interface to call advice () any time, this

Any idea how to debug it?

only unadvise ()