Re: Calling .NET COM object from MFC application

From:

Alex <alsim123@hotmail.com>

Newsgroups:

microsoft.public.vc.mfc

Date:

16 May 2007 11:41:59 -0700

Message-ID:

<1179340919.544396.21410@u30g2000hsc.googlegroups.com>

On May 16, 12:19 am, "Bob Eaton" <pete_dembrow...@hotmail.com> wrote:

As I mentioned, I don't have any dll, lib or tlb files for this third
party COM.
Otherwise, I would've used it.
Though, in my C# project I have
Interop.ThirdPartyServer.dll
may be somehow I can use this file

The Interop.Third... is only a wrapper on the actual DLL. If you don't have
it, then I don't think anything will help you.

Or is it that you just don't know where it is?

Check the registery for HKEY_CLASSES_ROOT\ThirdPartyServer..., see if it has
a CLSID sub-key, and look that up in:

HKEY_CLASSES_ROOT\CLSID\{84DD1BFF-...}

and see what it says for "InprocServer32". It might/should have a reference
to where the DLL resides.

Otherwise, I'm all out :-)

Bob

"Alex" <alsim...@hotmail.com> wrote in message

news:1179264250.205887.57930@p77g2000hsh.googlegroups.com...

On May 15, 1:41 pm, "Bob Eaton" <pete_dembrow...@hotmail.com> wrote:

Do you have a type library for the COM server?

If so, does "#import <ThirdPartyServer.tlb> raw_interfaces_only" work?

that should create a ".tlh" file in your Debug/Release folder. If you
look
in that file, it should give you a COM definition of the interface. With
that, you could use CComPtr to create an object that has the same methods
you call from your .Netversion. e.g.

typedef CComPtr<IFoo> IFooPtr;
IFooPtr pFoo;
pFoo.CoCreateInstance(L"ThirdPartyServer.Server") );
if (!!pFoo)
pFoo->SomeFunction(...);

If you don't have a type library, can you create one with tlbimp from the
DLL? (Search MSDN for "Importing a Type Library as an Assembly").

There should be a way to do it... it seems silly to create a .NetDLL
just
to do this...

Bob

"Alex" <alsim...@hotmail.com> wrote in message

news:1179154790.060709.84900@n59g2000hsh.googlegroups.com...

Thank you Bob,

You got me right, i.e. "MFC exe calls C# managed DLL which in turn
calls other ...COM Server. I don't know how it was written. I
wouldn't
use C# COM, to call this third party COM, if I new how to expose it to
my MFC application. This third party didn't provide any
documentation. They just gave some exe (which I cannot find now,
stupid I'm). If I run this exe on my machine (just double click it)
it registered their COM, after this from .NETproject on the same
machine I could add corresponding reference to my C# project and use
it. In VS6 there is now this feature. I'd asked them about some
CLASSID or PROGID to be able to CreateInstance() directly from my MFC
project and use it, but didn't get anything from them. So I had to
use the method they suggested - call functions of their COM server
from .NETapplication.

Here is my code in C# COM:

MyCOMFunction()
{
ThirdPartyServer.Server tps = new ThirdPartyServer.Server ();

tps.SomeFunction(...);
}

Here is my code from MFC application;

#import "csharcom.tlb"
............................................................
............................................................
............................................................
............................................................
............................................................

CoInitialize(NULL);

CSharpCOM::Test_InterfacePtr pCom(__uuidof(CSharpCOM::TestServer));
pCom->MyCOMFunction();

Again, I think the problem is to register this third party COM Server
on a "clean machine".

Thanks again,
Alex

On May 13, 10:49 pm, "David Ching" <d...@remove-this.dcsoft.com>
wrote:

"Bob Eaton" <pete_dembrow...@hotmail.com> wrote in message

news:efP2fNSlHHA.4644@TK2MSFTNGP03.phx.gbl...

All the COM and .NetDLLs must be registered on the "clean" machine
or
they
won't be able to talk to each other (unless you go "Registry Free
COM"--search the MSDN site for "Reg-Free COM").

Much thanks for this pointer for "registry free COM". I had not heard
of
this before and am crossing my fingers it will help me deploy my Vista
gadget which relies on an ActiveX control. It would be so much easier
not
have to register that control, especially since the gadget needs to be
used
in Limited accounts.

-- David- Hide quoted text -

- Show quoted text -

Thanks, Bob

As I mentioned, I don't have any dll, lib or tlb files for this third
party COM.
Otherwise, I would've used it.
Though, in my C# project I have
Interop.ThirdPartyServer.dll
may be somehow I can use this file

By the way, this .NETdll I'm going to use not just for this "third
party COM server",
but for sending email also. I found to do it from .NETapplication
easier than from my MFC application... And may be later on I'll add
some more functions, which are available in .NETand missing in VS6

Thanks, again
Alex- Hide quoted text -

- Show quoted text -

Hi, Bob
Indeed, searching of the registry provided some info.
I think I got ClassID and ProgID
Registry entry "LocalServer32" points to some .exe, not .dll. As I
understand COM server can be written both ways as DLL or EXE.

What I'm going to do now - search same things on a "clean" machine,
where I'm getting error message (Cannot do it right away, because I
don't have an access to it at this time). If I don't find it, it's
OK, it will mean that this "third party server" is still not
registered there and error can be explained, but if I find it, then
I'm in trouble J

Thanks,
Alex