AppId Registry purpose?

[Peter Tribout]

I wonder what the exact function of

"HKEY_ROOT_CLASSES\AppID"

I have a "MYServer.exe" applicatin with several classes
(eg MyClass1, MYClass2,...)

What should I expect to see in here and what is the relation with DCOM????

Greetings Peter

[ranga raghunathan]

hello
a couple of points that i hope will be helpful to you

a) appids are created by the mts/com+ catalog manager
b) in your case, 2 appids will be created, one for each class, pointing to
the remote server..this appid entry is created when you install the exported
client executable in the client machine
c) i searched under appId in msdn and got a reference to the duwamish book
sample code - cut and pasted below for your ref\

[HKEY_CLASSES_ROOT\AppID\{56B9A91D-58B4-11D2-9232-00C04FD91B93}]@="d35bll.cBusLogic"
/ "RemoteServerName"="<RemoteServerName>"

Of particular interest is the appID registry entry—RemoteServerName. This
can be changed directly in the registry or changed with DCOM configuration
(Dcomcnfg.exe) to allow the server application to be located on a different
server.

d) i am not sure why it has to generated an appid for each class.. let me
know if you find out why.

thanks
ranga
"Peter Tribout" <ptribout@wvem.be> wrote:
>I wonder what the exact function of
>
>"HKEY_ROOT_CLASSES\AppID"
>
>I have a "MYServer.exe" applicatin with several classes
> (eg MyClass1, MYClass2,...)
>
>What should I expect to see in here and what is the relation with DCOM????
>
>Greetings Peter
>
>
>

[darin darin]

The APPID key contains security information (RUNAS, etc) about a collection
of object classes that collectively make up a single APPID. COM doesn't store
security info on each class seperately, only on APPIDS as a whole. This might
be different in COM+. not sure. Haven't used it. Don't plan to.

MTS registers the APPID one way but if you check the "create remote server
files" in vb's make dialog, and check out the VBR file, you'll see how VB
creates the APPID's.

Hope that helps!



"ranga raghunathan" <ranga1@msn.com> wrote:
>
>hello
>a couple of points that i hope will be helpful to you
>
>a) appids are created by the mts/com+ catalog manager
>b) in your case, 2 appids will be created, one for each class, pointing
to
>the remote server..this appid entry is created when you install the exported
>client executable in the client machine
>c) i searched under appId in msdn and got a reference to the duwamish book
>sample code - cut and pasted below for your ref\
>
>[HKEY_CLASSES_ROOT\AppID\{56B9A91D-58B4-11D2-9232-00C04FD91B93}]@="d35bll.cBusLogic"
>/ "RemoteServerName"="<RemoteServerName>"
>
>Of particular interest is the appID registry entry—RemoteServerName. This
>can be changed directly in the registry or changed with DCOM configuration
>(Dcomcnfg.exe) to allow the server application to be located on a different
>server.
>
>d) i am not sure why it has to generated an appid for each class.. let me
>know if you find out why.
>
>thanks
>ranga
>"Peter Tribout" <ptribout@wvem.be> wrote:
>>I wonder what the exact function of
>>
>>"HKEY_ROOT_CLASSES\AppID"
>>
>>I have a "MYServer.exe" applicatin with several classes
>> (eg MyClass1, MYClass2,...)
>>
>>What should I expect to see in here and what is the relation with DCOM????
>>
>>Greetings Peter
>>
>>
>>
>