#Clr dispatch code

LPDISPATCH lpdispCallInfo = callIno->GetIDispatch(FALSE) VTS_DISPATCH //VTS_VARIANT //VTS_DISPATCH Static BYTE paramInfo = VTS_UI4 VTS_UI4 VTS_I4 VTS_I4 VTS_BSTR

This IID must match the GUID that is attached to the we add support for IID_ICallInfo to support typesafe binding NOTE - the ClassWizard will add and remove mapping macros here.īEGIN_DISPATCH_MAP(CCallInfo, CCmdTarget)ĭISP_PROPERTY_ID(CCallInfo, 'CallId', dispidCallId, CallId, VT_I4) When the last reference for an automation object is released with OLE automation, the destructor calls AfxOleUnlockApp. To terminate the application when all objects created with object is active, the constructor calls AfxOleLockApp. To keep the application running as long as an OLE automation IMPLEMENT_DYNCREATE(CCallInfo, CCmdTarget)

#Clr dispatch code

The code for the source file is as below: NOTE - the ClassWizard will add and remove member functions here. I did code following C++ wrapper class for the _ICallInfo impl.ĬCallInfo() // protected constructor used by dynamic creation I tried passing IDispatch pointer for this interface impl. If IDispatch is the answer, I already did the following,

what should ideally be passed as event args accross the proces? My client SAFEARRAY(VARIANT)* info) //IDispatch* Info) ġ. NOTE - ClassWizard will maintain method information here.

Use extreme caution when editing this section. NOTE - ClassWizard will maintain property information here. Event and APIs are working fine up untill now when I intended to pass some structured data (event args) accross. I have one main inbound interface called _ISipPhone and corresponding outbound event interface called _ISipEventCallback. I wrote and maintain a high-performance COM server written in MFC (ATL guys excuse me), to provide a COM layer on top of an existing SIP protocol stack written in pure C.