Again, I haven't been using the VS 2010 installer so it may be different.

In other versions you right-click on the setup project and select to view
the registry settings. You then add your registration information for the
addin at either HKCU or HKLM or to User/Machine Hive. If the registration is
for User/Machine Hive it will be placed in either HKCU or HKLM depending on
whether the installation is selected for all users or current user.

If you are using a shim you also have to account for any shim registration.
What I do is use the same CLSID's for the shim as for the addin dll and then
eliminate the shim registration settings for HKCU or HKLM and leave the
registration for HKCR. That way any shim registration won't conflict with
registrations for the addin and won't add it to a different hive than
selected in the installer screen.


"Sanjay" <sysmailbox@gmail.com> wrote in message
news:e3667681-6e8c-4088-b07b-b34ec24bfe1d@z25g2000vbn.googlegroups.com...
DELETING the key from HCLU solved the problem.

Last question (even I don't believe that).... what do I need to do
with the Setup code to get the addin to install in HKCU but not in the
HKLM?

Thanks
Sanjay


On Sep 24, 2:54 pm, Sanjay <sysmail...@gmail.com> wrote: