Re: DCOM - How to configure the client?
- From: Kannan <Kannan@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 19 Sep 2007 13:32:05 -0700
Thank you Alexander.
By now I figured out that the client machine need the registry setting
regarding the Class id(s) and the App id and the app id links to a
RemoteServer.
I can create a registry editing script by hand. but for a large project
there will a quite a few DLLs that need to be "DCOMed" and even worse each
dll will contain many interfaces/classes. May be I could automate this
through some (VB) scripts.
I see that Visual Studio generates some ".rgs" files (also a ".idl" file and
a "*_i.c", which contains the GUIDs ), does it do any good to automate the
edit registry in client machine or to create a ".reg" file? It would have
been nice if Visual Studio generates a comprehensive ".reg" file that can be
directly executed in client machines.
I think there should be some mechanism to automate the client settings,
rather than copying the server side binary code to each client machine.
Please post your thoughts about this.
Thank you once again for the reply.
-Kannan
"Alexander Nickolov" wrote:
You'll need to create a registration script for your client by hand..
One way to do it is by exporting the server registry settings
and then deleting the LocalServer32 entry and modifying the
AppID's values (that's why people usually copy the original
server to the client). You can certainly type it by hand of course...
--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@xxxxxxxx
MVP VC FAQ: http://vcfaq.mvps.org
=====================================
"Kannan" <Kannan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8C38E2E4-2E42-4729-96F7-1C9B8AE2D3D0@xxxxxxxxxxxxxxxx
Hi,
I am trying to call a service on a remote server machine from a client
machine connect through TCP/IP. I have created a DLL and registered the
DLL
at the server side. Launched DCOMCNFG and done the necessary settings at
the
server side.
My question is at the client machine(s) side how will I specify where
(which
machine) to look for this service? I don't want to copy the DLL to the
client
machine even for any initial setup or registering.
What I know:
In a demo project's documentation I downloaded from microsoft website,
they
use the same server service exe (that was an exe not a dll) to register
the
service in client. Once we have done that we can use DCOMCNFG to specify
which computer we want to look for this service. But here we need to copy
the
server exe to the client machine(s), I don't want to do that for the
solution
I am looking for.
I greatly appreciate any help.
Thank you for your time.
-Kannan
- Follow-Ups:
- Re: DCOM - How to configure the client?
- From: Alexander Nickolov
- Re: DCOM - How to configure the client?
- From: Brian Muth
- Re: DCOM - How to configure the client?
- References:
- Re: DCOM - How to configure the client?
- From: Alexander Nickolov
- Re: DCOM - How to configure the client?
- Prev by Date: Re: DCOM - How to configure the client?
- Next by Date: Re: DCOM - How to configure the client?
- Previous by thread: Re: DCOM - How to configure the client?
- Next by thread: Re: DCOM - How to configure the client?
- Index(es):
Relevant Pages
|
Loading