Re: COM object created in wrong process? SOLVED

From:

"Alexander Nickolov" <agnickolov@mvps.org>

Newsgroups:

microsoft.public.vc.atl

Date:

Thu, 31 May 2007 10:32:52 -0700

Message-ID:

<#80L4m6oHHA.4112@TK2MSFTNGP04.phx.gbl>

FWIW, I never use the add new method wizard... It's ok for
a single method, but when one defines an entire interface it's
much more convenient to look at the plain text IDL while
typing...

--
=====================================
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:q4WdnVZlxq1uZsPbnZ2dnUVZ_oOknZ2d@comcast.com...

MrAsm wrote:

On Wed, 30 May 2007 23:37:04 -0400, "Scott McPhillips [MVP]"

I've tried this with parameter types IDispatch* and IUnknown*, and also
the pointer-to-pointer equivalents. Same result for all types. (What is
the correct parameter type, given that I want to pass this pCallback?)

Just a simple Variant?

MrAsm

I got rid of the wizard error message by restoring a backup from a few
days ago and trying again - Too many clumsy attempts probably screwed
things up.

The server now receives the callback pointer like this, which is working:

STDMETHODIMP CMyServer::Init(IUnknown* pCallback)

//CComPtr <IUpdater> m_spUpdater;
m_spUpdater = CComQIPtr <IUpdater> (pCallback);

and calling m_spUpdater->Update(...);
accomplishes the callback into the client.

Thanks All.

--
Scott McPhillips [MVP VC++]