Re: DECLARE_REGISTRY_APPID_RESOURCEID
"Phil Da Lick!" <phil_the_lick@spammerskissmyarse.hotmail.com> wrote in
message news:%23Ta1zax4HHA.4880@TK2MSFTNGP03.phx.gbl
Igor Tandetnik wrote:
"Phil Da Lick!" <phil_the_lick@spammerskissmyarse.hotmail.com> wrote
in message news:eSHsPVp4HHA.4476@TK2MSFTNGP06.phx.gbl
That would be the APPID:
http://msdn2.microsoft.com/en-us/library/ms682359.aspx
Doesn't really say what it's for. Is this something that can safely
be ignored for objects that will never be used across a network?
It's also relevant for objects that are used across security
contexts. E.g. a COM server in a service running under a dedicated
user account, activated from a client proccess running under a
different account.
So what's the correct procedure for inserting this functionality into
an old vc6 proj? Is it ok to just generate a new GUID for this member?
Also, I notice that the wizard generated .net projects also have a
MyLibrary.rgs file which isn't present in the old proj. What to do
about this?
Well, you can simply add APPID key registration to an existing RGS. This
way it will be registered and unregistered together with your component.
Or, you can write a separate RGS file, and explicitly call
CComModule::UpdateRegistryFromResource in your Dll[Un]RegisterServer
implementation.
Yes, APPID is an arbitrary GUID. You create a key HKCR\AppID\{Your
APPID} to store the security settings, and you refer to it from your
component by creating a value named AppId under your HKCR\CLSID\{Your
CLSID} and setting it to the APPID.
--
With best wishes,
Igor Tandetnik
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925