Why do cross process QI calls fail

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Bill Rust - 23 Mar 2005 19:53 GMT

I'm creating an VB.NET class the implements 2 COM interfaces, call them IFoo
and IBar. If I create an object in my local process, I can call IFoo->QI and
get back the IBar interface, but if the object is hosted in a different
process, the QI fails. Any ideas how I can get this working?

Reply to this Message

Bill Rust - 24 Mar 2005 00:23 GMT

I just modified my code so that it inherits from System.MarshalByRefObject
and now it is working.

> I'm creating an VB.NET class the implements 2 COM interfaces, call them IFoo
> and IBar. If I create an object in my local process, I can call IFoo->QI and
> get back the IBar interface, but if the object is hosted in a different
> process, the QI fails. Any ideas how I can get this working?

Reply to this Message

Bill Rust - 24 Mar 2005 17:51 GMT

Looks like I spoke to soon. I'm still having problems QI'ing for a different
interface on my .NET object when it is in a different process. Thanks in
advance for any suggestions.

> I just modified my code so that it inherits from System.MarshalByRefObject
> and now it is working.
[quoted text clipped - 3 lines]
> > get back the IBar interface, but if the object is hosted in a different
> > process, the QI fails. Any ideas how I can get this working?

Reply to this Message

Why do cross process QI calls fail

Free Magazines