G
Guest
I just got my first COM interop to work... only to realize that is does not
do quite what I want it to do. my little client app (in unmanaged C++) that
calls my nice C# objects through COM does more than just call the interface
methods, it instantiates a new instance of the C# class, which is its own
executable. I understand that this is normal behavior for COM, since it
defaults to in-process work (as most COM objects are contained in DLLs).
I need to have this little client attach to an already existing and running
C# application, and then use the interface to call the functions in the other
process.
I read that this is possible, by declaring the C# object as an out of
process (outproc) server (the .exe) and requesting the right way inside the
C++ code.
I just can find no information on how to accomplish this.
Does anyone have a link of somewhere I can look to cause unmanaged C++ COM
calls to look for an out of process component first.
Possibly even moving on to a remote component as well.
Thanks in advance,
Andrew S. Giles
do quite what I want it to do. my little client app (in unmanaged C++) that
calls my nice C# objects through COM does more than just call the interface
methods, it instantiates a new instance of the C# class, which is its own
executable. I understand that this is normal behavior for COM, since it
defaults to in-process work (as most COM objects are contained in DLLs).
I need to have this little client attach to an already existing and running
C# application, and then use the interface to call the functions in the other
process.
I read that this is possible, by declaring the C# object as an out of
process (outproc) server (the .exe) and requesting the right way inside the
C++ code.
I just can find no information on how to accomplish this.
Does anyone have a link of somewhere I can look to cause unmanaged C++ COM
calls to look for an out of process component first.
Possibly even moving on to a remote component as well.
Thanks in advance,
Andrew S. Giles