Re: another COM-Question: how to inject a type-lib into a dll?

Tech-Archive recommends: Fix windows errors by optimizing your registry

Igor Tandetnik wote:

> be SomeObject*. Why does it not just say so and declare SomeObject* as a
> parameter?

ha! that's the point, you got me! :) How can I do that? I mean, COM is
essentially a procedural interface, isn't it? If that object should
pass process boundaries (which is doesn't in that case, but still) it
would have to be serialized (marshalled?).
Also the MIDL compiler complains about not knowing to serialize that
object parameter (well, last time I tried he complained about an enum,
so I didn't try full objects).

So is it done by just saying
STDMEDTHODIMP someComFunc(a,b,c, MyObj *mine) {...}
....?

I mean, as far as I know I can't use *objects* from COM serves, only
their *interfaces*. Using objects would make things here so much easier
for me :) . Or did I miss something very critical ... ?


Many thanks again & greetings,

Axel.


p.s.: but still - *could* that IPointer - object pointer conversion
work if that's the very object I created in another part of my COM
server? And I define sides as follows: COM side = inside the COM
server. APP side = the app _using_ the COM server.

.