Mike Hearn wrote:
CCing to wine-devel as the original reply will be forwarded soon too by
Jeroen ..
On Fri, 2004-07-23 at 17:58 +0200, Jeroen Janssen wrote:
I had a short look at the 'world of com' patch, and it looks like there
is something in there that implements the IRemUnknown stuff. Is th
Jeroen Janssen wrote:
Robert Shearman wrote:
Jeroen Janssen wrote:
Hello,
I'm mailing the both of you with a small (com) example attached.
It is a client/server/proxystub example (with binaries), so you need to
/RegServer the server and regsvr32 the proxy.
Now I first manually start the server in a
Forwarding this to the wine-devel mailinglist.
Robert Shearman wrote:
Jeroen Janssen wrote:
Hello,
I'm mailing the both of you with a small (com) example attached.
It is a client/server/proxystub example (with binaries), so you need to
/RegServer the server and regsvr32 the proxy.
Now I first m
CCing to wine-devel as the original reply will be forwarded soon too by
Jeroen ..
On Fri, 2004-07-23 at 17:58 +0200, Jeroen Janssen wrote:
> I had a short look at the 'world of com' patch, and it looks like there
> is something in there that implements the IRemUnknown stuff. Is there
> any easy
On Thu, 22 Jul 2004 17:38:43 +0100, Robert Shearman wrote:
> Unfortunately, you have stumbled into one of the most confusing areas of
> the Win32 API that I think only one person in the world fully
> understands (Don Box in case you are wondering).
Yeah. I'm starting to suspect that Don kept pil
Jeroen Janssen wrote:
I am not sure, but there seems to be a difference in the outproc handling
of the CoCreateInstance call?
This goes ok:
hr = CoCreateInstance(CLSID_Component1, NULL, clsctx, IID_IX, (void**)&pIX) ;
However this seems to go wrong?:
hr = CoCreateInstance(CLSID_Component1, NULL, cl
> From: Mike Hearn <[EMAIL PROTECTED]>
>> Maybe my 'real' problem is that based upon the logging, I also see a
>> CFProxy Unhandled interface for the first interface that the client is
>> trying to access (but I need to know more about how COM/wine deals with
>> this).
>
> Are you sure you're using
On Thu, 22 Jul 2004 14:45:31 +0200, Jeroen Janssen wrote:
> Maybe my 'real' problem is that based upon the logging, I also see a
> CFProxy Unhandled interface for the first interface that the client is
> trying to access (but I need to know more about how COM/wine deals with
> this).
Are you sure
> IRunnableObject does not have anything to do with COM marshalling; it is
> an OLE thing. MSDN says this about it: "The *IRunnableObject *interface
> enables a container to control the running of its embedded objects". So
> basically, I don't see any reason why CFProxy (IClassFactory proxy)
> shou
Jeroen Janssen wrote:
Hello,
I'm trying to run 2 programs:
1) is a COM server program
2) is a COM client program
Now, program 2) tries to access a COM component from 1) (outproc).
It seems some marshalling is being done, but eventually I get:
fixme:ole:CFProxy_QueryInterface Unhandled interface:
{0
Hello,
I'm trying to run 2 programs:
1) is a COM server program
2) is a COM client program
Now, program 2) tries to access a COM component from 1) (outproc).
It seems some marshalling is being done, but eventually I get:
fixme:ole:CFProxy_QueryInterface Unhandled interface:
{0126---
11 matches
Mail list logo
