IDL problem : setting Interface inside or outside typelib / Proxy stub vs Aggregation
Well, aggregator and aggregatee have to be in the same apartment, but I
don't think there is anything to prevent the aggregator to expose an
interface from the aggregatee as its own to the out-of-apartment client.
I guess that's what the OP is worried about.
It's still not clear what exactly TLB has to do with it though.
--
With best wishes,
Igor Tandetnik
"For every complex problem, there is a solution that is simple, neat,
and wrong." H.L. Mencken
Quote:
> aggregation doesn't work when marshaling is necessary!
Quote:
> Hello everyone and thanks for the help with my connection point
> problem last month.
> I have an other one to submit to you.
> We've built an object which uses structs containing arrays of structs.
> In order to communicate with other components, we use standard
> Marshalling.
> In order to build the Proxy stub we need to define the interface
> outside of the type library orelse
> the "XXXX_p.c" and the "dlldata.c" files aren't generated by MIDL.
> At the same time, we need this object A to be aggregated in another
> object B.
> If the interface of A is not defined in the typelib with all the
> structs, the interface is not available in
> the type library of B.
> So we can't query for this interface when using B.
> Do you know of any way to do that?
