Re: COM object created in wrong process?

From:

"Alexander Nickolov" <agnickolov@mvps.org>

Newsgroups:

microsoft.public.vc.atl

Date:

Tue, 29 May 2007 12:48:15 -0700

Message-ID:

<OBJONpioHHA.4428@TK2MSFTNGP06.phx.gbl>

I've posted a few in this group in the past, others have as well
(Igor and Brian for sure). The basic idea goes like this:

class CMyCallback :
public CComObjectRootEx<...>,
public ICallback {
....
};

CComObject<CMyCallback>* pObj = NULL;
HRESULT hr = CComObject<CMyCallback>::CreateInstance(&pObj);
// Internal callback object initialization here
pObj->Init(...);
CComPtr<ICallback> pCallback;
pObj->GetUnknown()->QueryInterface(&pCallback);
// No direct C++ access to the callback object after this point
pObj = NULL;
// Pass the callback to the source object
pSource->SetCallback(pCallback);
pCallback.Release();

Error handling omitted for brevity and clarity.

--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://vcfaq.mvps.org
=====================================

"Scott McPhillips [MVP]" <org-dot-mvps-at-scottmcp> wrote in message
news:h6SdnY4gwvWV-8HbnZ2dnUVZ_sSmnZ2d@comcast.com...

Alexander Nickolov wrote:

You are supposed to create an internal object in your DLL and
pass it as a callback to your EXE server. Otherwise the EXE
server simply loads another copy of your DLL.

Thank you. That explains what was happening. Can you direct me to an
example of what you suggested?

--
Scott McPhillips [MVP VC++]