OS: Windows 10 - 64 Bit
Hello support,
I'm experimenting some problems when trying to install a file that is shared. I have tried with the SharedDLL count (Organization -> Component Properties) and also using the same GUID for the shared file. Unfortunately, both approaches end with an undesired behavior.
Installation description:
- There are several Merge-Modules that use the same file
- A main Setup have several features, one feature for each merge-module
- The features can be selected to be installed --> the shared file can be installed several times from the same Setup, over different merge modules
- The main Setup can be modified --> Features can be added and/or removed after installation
Test: The main Setup is configured to install two features (shared file is installed two times)
Results:
- After installation, the file is added to the list of shared DLLs (HKLM\Software\Microsoft\Windows\CurrentVersion\SharedDLLs) --> OK
- After installation, the SharedDLL counter is set to 2 --> OK
- Adding and/or removing features successfully update the counter --> OK
- After uninstall, the DLL is no longer in the list of SharedDLLs (HKLM\Software\Microsoft\Windows\CurrentVersion\SharedDLLs) --> OK
- The shared file is left installed --> NOT OK
Approach 2: The file is NOT marked as SharedDLL in any place, but it uses the same GUID wherever it appears --> in each merge module.
Test: The main Setup is configured to install two features (file with same GUID is installed two times)
Results:
- The Installation succeeds, no entry to the list of shared DLLs is made --> OK
- Removing one feature is enought to get the "shared" file uninstalled --> NOT OK
- Doing an uninstall DOESN'T remove the other feature, i.e. files are left installed --> NOT OK
- Note that, if I use the merge modules in different Msi, then it works.
- Regarding approach 1: It seems as the SharedDLL mechanism is working well, up to the point where the file has to be removed. Could be that inside of AI the counter for the file stays as 1 instead of 0, or something like that?
- regarding approach 2: It seems as the problem can be tied to the fact, that the shared file is inside of merge modules. It is possible that the GUID of a merge module is being combined with that from the file and for that reason is not being taken as a shared file but as two different files?
- Here is an image that shows the setup configuration for better understanding: Thanks in advance for your help.
Best regards,
Keneth
FOLLOW US
Get the latest news in Application Packaging