Hierarchical Registry-free COM access from C++ client

Question

4.00/5 (1 vote)

See more:

I've got a C++ client accessing some registry-free C++ COM DLLs.

I followed instructions here:

Registration-Free Activation of COM Components: A Walkthrough[^]

and got my client working almost OK.

However, my side-by-side DLL calls into many other COMs.
These internal COMs appear not to be working.

To clarify, I have COM A and COM B.
I do a CreateInstance inside my client to COM A and it works.
Inside COM A there is a CoCreateInstance to COM B and this appears not to work.

The manifest file describes all the COMs involved, and I have made sure the manifest file is being read (if I deliberately mess up the entry for COM A, the client says it can't find the specified module).

I've only ever managed to get this set of DLLs to work as registry-free COMs from a .NET C# application, where you stick all relevant DLLs in as references, register the COMs at build time, unregister at run time and they work.

However, in C++ I don't know what the equivalent of adding references is.

Any help, greatly appreciated!

Posted 10-Apr-13 23:16pm

PaulowniaK

Updated 11-Apr-13 0:22am

Tadit Dash (ତଡିତ୍ କୁମାର ଦାଶ)

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

shailesh91082 · Answer 1 · 2013-04-12T21:47:00

Solution 1

In C++ equivalent of adding reference is using #import "comserverdllname" ex:#import "test.dll"

Posted 12-Apr-13 21:47pm

shailesh91082

Comments

PaulowniaK 15-Apr-13 2:51am

Thanks for the tip. That makes sense!
However, I have another problem. #import "mydll.dll" is fine, but the dll's name and the type library's name are different so causes a compilation error.

Basically, it can find mydll.dll but it can't find its type library which is mydllobject (although the actual file name is mydll.tlb).

When I do all this in C#, adding mydll.dll to references automatically lists up mydllobject.

Could you please help?

Thanks.