"Shared legacy" components

Having trouble running Advanced Installer? Got a bug to report? Post it all here.
Post Reply
icke_qps
Posts: 7
Joined: Thu Apr 25, 2019 10:26 am

"Shared legacy" components

Post by icke_qps » Mon May 13, 2019 3:39 pm

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

Eusebiu
Posts: 4558
Joined: Wed Nov 14, 2012 2:04 pm

Re: "Shared legacy" components

Post by Eusebiu » Tue May 14, 2019 3:35 pm

Hi Peter,

Yes, the reference count for the components (shared legacy) should work regardless the installer authoring tool. Did you encounter any problems with this?

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Post Reply