Re: ATL com server can pass interface as parameters?
On Apr 18, 1:01 pm, ceasar...@gmail.com wrote:
My code is like following:
Server side
========
class CMy2 : IMy2
{
// IUnknown
HRESULT STDMETHODCALLTYPE QueryInterface(const IID& iid, void**
ppv) { return S_OK; }
ULONG STDMETHODCALLTYPE AddRef() { return 1; }
ULONG STDMETHODCALLTYPE Release() { return 1;
// IDispatch
HRESULT STDMETHODCALLTYPE GetTypeInfoCount(UINT *pctinfo){ return
S_OK; };
HRESULT STDMETHODCALLTYPE GetTypeInfo(UINT iTInfo, LCID lcid,
ITypeInfo **ppTInfo){ return S_OK; };
HRESULT STDMETHODCALLTYPE GetIDsOfNames(REFIID riid, LPOLESTR
*rgszNames, UINT cNames, LCID lcid, DISPID *rgDispId){ return S_OK; };
HRESULT STDMETHODCALLTYPE Invoke(DISPID dispIdMember, REFIID riid,
LCID lcid, WORD wFlags, DISPPARAMS *pDispParams, VARIANT *pVarResult,
EXCEPINFO *pExcepInfo, UINT *puArgErr){ return S_OK; };
};
Just a suggestion, it's much easier to use the ATL stuff to handle
IUnknown and IDispatch methods for you; they handle all the subtleties
of this stuff properly and unless you're doing something really weird
there's not much reason to override that behavior. I'm not a COM
expert, but I've done some pretty funky stuff with custom marshaling
and have never had to write my own implementations of IUnknown and
IDispatch methods.
My objects typically just use what the ATL simple object wizards put
out, e.g.:
class ATL_NO_VTABLE Cblah :
public CComObjectRootEx<CComSingleThreadModel>,
public CComCoClass<Cblah, &CLSID_blah>,
public ISupportErrorInfo,
public IDispatchImpl<Iblah, &IID_Iblah, &LIBID_something_or_other>
{
...
}
IDispatchImpl will take care of the IDispatch methods, and one of the
others (either CComObjectRootEx or CComCoClass, not sure) will take
care of IUnknown.