ATL attributes - Custom registration script

[Ashok K Kumar]

Hi,

I have a ATL Attributed DLL which exposes a COM Component. My requirement
is, whenever, the DLL is registered, I also would like to add some entries to
the HKLM/Softwares/CompanyName..... along with the Component registration. By
default, when we create an attributed COM Component, it adds, vi_progid,
progid, coclass, uuid, etc.. This is enough to register the component. But, I
need to add additional registration information like adding a couple of
entries in the HKLM apart from the usual Component registration. How do i do
that?

I tried using registration_script attribute to specify a custom.rgs file
which has the ATL registrar (ATL 3.0 style) registry entries. But the problem
is that, once we mention this attribute, the component registration does not
happen. Does this mean I have to include my component registration also in
the custom.rgs file itself? Can I not use the existing coclass attribute to
do this work? Or am I missing something?

Thanks in advance.

Ashok K Kumar

[Alexander Nickolov]

Inline.

--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: ag********@mvps.org
MVP VC FAQ: http://www.mvps.org/vcfaq
=====================================

"Ashok K Kumar" <as***@newsgroup.nospam> wrote in message
news:EE**********************************@microsof t.com...

Hi,

I have a ATL Attributed DLL which exposes a COM Component. My requirement
is, whenever, the DLL is registered, I also would like to add some entries
to
the HKLM/Softwares/CompanyName..... along with the Component registration.
By
default, when we create an attributed COM Component, it adds, vi_progid,
progid, coclass, uuid, etc.. This is enough to register the component.
But, I
need to add additional registration information like adding a couple of
entries in the HKLM apart from the usual Component registration. How do i
do
that?

I tried using registration_script attribute to specify a custom.rgs file
which has the ATL registrar (ATL 3.0 style) registry entries. But the
problem
is that, once we mention this attribute, the component registration does
not
happen. ... Does this mean I have to include my component registration also in
the custom.rgs file itself?
Yes.
... Can I not use the existing coclass attribute to
do this work?
No. You are overriding it entirely.
... Or am I missing something?
Yes - the coclass registration. Also, it'd make more sense to override the
module registration, not the registration of an object in your server...

Thanks in advance.

Ashok K Kumar