I have been reading up on using "shared legacy" components, as mentioned in the help and some topics: viewtopic.php?f=2&t=10407&p=28060&hilit ... acy#p28060
So I already know that using the same MergeModule in 2 different installers will take care of the reference count and uninstalling.
We are still in transition of 'Visual studio deployment projects' and I would like to gradually move some projects.
Now I have this scenario:
- I have a Mergemodule compiled with AdvancedInstaller
- This merge module is used in an Installer built with Advanced Installer
- This merge module is used in another Installer built with Visual Studio
Does 'shared legacy' still work in that case?
Best regards,
Peter
FOLLOW US
Get the latest news in Application Packaging