Hi Mr Magoo,
> If I see a certain .dll path as shown in the example below:
> HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDlls\C:\WINDOWS\system32\mydll.dll
[quoted text clipped - 6 lines]
> is just added to the registry key above, but the application is not
> active.
Windows installer uses this information to keep track of dlls which might be
installed by different products and thus are potentially shared. So an
install count is used to delete the dll only when the last uninstaller has
run and no product uses that dll anymore.
This is typically a standard feature of installer products, so even if dlls
are only built for and used by one application they are often installed as
shared dlls.
Dll cannot run or by active by themselfes. They will always need a process
which loads them and call functions of them. You can use a tool like Process
Explorer which can show you which processes have which dll loaded. So you
can verify for yourself.
--
SvenC
Ben Voigt [C++ MVP] - 17 Sep 2007 20:18 GMT
> Hi Mr Magoo,
>
[quoted text clipped - 16 lines]
> dlls are only built for and used by one application they are often
> installed as shared dlls.
On the other hand, if you saw something in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Windows\AppInit_DLLs then that would be loaded all the
time.
> Dll cannot run or by active by themselfes. They will always need a process
> which loads them and call functions of them. You can use a tool like
[quoted text clipped - 3 lines]
> --
> SvenC