How to register a COM dll for current user

How can I register a COM dll in the same system for multiple users.  The DLL location is under  C:\users<User> folder.

I want to register same dll separately for each user in the same computer.   Currently If one user uninstalled the application, the dll will be unregistered, so the applictaion will not work for another user.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

1. dont let the user uninstall the application.

2. register a 2nd copy of the dll elsewhere in the system.

3. let the application register the dll. if the user can unregister, then the application can too.
Registering the DLL seperately for each user isn't really a good idea, simply because there's only one HKCR per machine, not per user. So I'd rather opt for installing your applicaiton for all users and place that COM DLL in a shared location.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
What you are trying to do is better handled at the Installer level. Windows based installers have capabilities of keeping a reference count with shared components and if there are three different users who have installed the same package then

- shared components are installed only once
- reference count is bumped for each installation

Almost every installer builder has support for shared components so check and use that instead and put your shared dlls in a location appropriate for all users.
Rowby Goren Makes an Impact on Screen and Online

Learn about longtime user Rowby Goren and his great contributions to the site. We explore his method for posing questions that are likely to yield a solution, and take a look at how his career transformed from a Hollywood writer to a website entrepreneur.

HPFE455Author Commented:
ambience, jkr, tipsybroom

My application  supports user level installation. ie, different user accounts can be installed my application in the same system. Since the COM dll registration at the system level, if any of one of the user uninstall their product, the COM dll will be  unregistered from the system and application will not work for other users

The COM  dll location will be different for each user
ex: c:\users\admin\App
ex: c:\users\guest\App
ex: c:\users\hpfe\App
 App is the installed application path. Each App folder will contain a copy of the COM DLL

 If  the installer place the dll in the shared  location, ( I need to understand  this), how    un-installation process maintains, ie, if one user uninstalled, the dll, it should not be unregistered dll, similarway if the last user unintsalled the product, the dll should be unregistered from the system.
did you read my comment regarding installer support for reference counting?
>>The COM  dll location will be different for each user

No, it won't - the location will always be the one of the latest installation, since that one will overwrite the registration of the previous ones.
HPFE455Author Commented:
 I  have updated your suggestion to the Install team, I am waiting for the feedback.

 I agree,  "HKCR per machine, not per user -  so we can't regsiter the same dll for different users separately.

So let me try other options
An installer component (dont confuse with COM component) that is shared must be installed to say a Common Folder like C:\Program Files\Common Files\App

User specific components and data must be installed to c:\Users\.....

With support for references or reference counting the Windows Installer components will keep track of how many times a component (installer component identified by a GUID)  got installed. It will remove only when the last reference to it is removed.

Also, you can set policies like if shared components are already installed then whether you overwrite or skip or overwrite if newer.
>>must be installed to say a Common Folder

Is there an echo? I mentioned that last week already, please take the time to read the entire thread.
Theres no echo as far I can see, I said "Installer Components" but I dont find any trace of you referring to but COM dlls, which I never referred to.

Also, "installing your application for all users" is different from saying have shared "installer components" and not so shared ones.

Please take time to understand and not just "read"
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.