I have build a COM DLL.How can I let other people use my COM remotely ?

Question

0.00/5 (No votes)

See more:

I have build a COM DLL, and register it on my computer.

Now I want to share this COM to my friends ,but without copy this DLL to them.

How can I let other people use my COM remotely ?

What's the most proper solution in this case?

Should I Use Com+ or DCOM? But I don't have any experience on that. Is there any example? And Should I modify my COM DLL code?

Posted 8-Jun-11 0:01am

GhostEx

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)

barneyman · Accepted Answer · 2011-06-08T03:35:00

DCOM is what you need, however, that falls into the 'badly documented, poorly supported' realm of MS technology

First - you need to distribute the proxystub.dll that is created from your COM object - it needs to be registered (regsvr32) at both the client and server end - it is responsible for 'de/remoting' the call

Second - the client needs to use CoCreateInstanceEx to get a remote ref (caveat here for testing, asking for a REMOTESERVER when the server is localhost will fail)

Third - you need to understand the join between the CLSID and the APPID

As regards third, the MS wizards fail spectacularly to help you out here, and DCOMCNFG just confuses the issue ...

Ensure that your <object>.rgs declares the APPID, then ensure that your <COCLASS>.rgs references the APPID (neither happens automatically)

Once that is all sorted, DCOMCNFG should be your point of call; however, the default machine limit may get in the way