Shared DLL Count Clarification
Hi,
Bit of a naive question here but I'm looking for clarification on what I should do with the shared DLL count in the registry. My package increments the count for both the mfc42.dll and msvcrt.dll also adds a new one for its own SPR32X35.ocx file. Whats the best way to handle this in my package? should I remove those values or leave them in?
Many Thanks in advance
Bit of a naive question here but I'm looking for clarification on what I should do with the shared DLL count in the registry. My package increments the count for both the mfc42.dll and msvcrt.dll also adds a new one for its own SPR32X35.ocx file. Whats the best way to handle this in my package? should I remove those values or leave them in?
Many Thanks in advance
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
anonymous_9363
15 years ago
Posted by:
turbokitty
15 years ago
If application "A" installs a dll, then application "B" tries to install the same dll, instead of copying over it, Windows Installer (WI) will increment the reference count for that file..
When uninstalling app "A" (or "B"), WI will check the reference count to see if any other applications are still using that dll. If they are, then WI will decrement the counter by 1 and leave the dll behind. When that counter hits zero, the dll will be uninstalled by the next application that tries to remove it.
When uninstalling app "A" (or "B"), WI will check the reference count to see if any other applications are still using that dll. If they are, then WI will decrement the counter by 1 and leave the dll behind. When that counter hits zero, the dll will be uninstalled by the next application that tries to remove it.
Posted by:
AngelD
15 years ago
Posted by:
turbokitty
15 years ago
Posted by:
Inabus
15 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.