I'm trying to understand the "best" way to install shared DLLs (or other files). By shared I mean than two installations install the same file, and the file only gets removed when both installations are removed.
AI supports the concept of updating HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDLLs with the path to a file, and a reference count to it.
Am I right in saying that the "correct" Windows Installer method is to get two installs to both use a component with the same GUID (making sure they contain the same files), and not use the registry? It seems that the SharedDLLs registry method is only needed when you need to make non-Windows Installer products aware of the shared file.
If I don't have to worry about legacy installs, can I ignore the Shared Dll Reference Count checkbox in the component properties, and simply make my shared components have the same GUID between different AI projects?
FOLLOW US
Get the latest news in Application Packaging