Pre-existing install components - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

renfrow
Posts: 6
Joined: Tue Apr 16, 2013 12:10 am

Pre-existing install components

I am doing Java application installs. I install libraries to a standard location. Currently, if I uninstall that application, its installed libraries are removed. However, if any of those libraries already existed, at install time, that means some other application installed them, and they should not be removed.

Thanks!

Tom Kimpton.
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Pre-existing install components

Hello Tom,

I'm afraid I don't fully understand your scenario. Can you please give us more details about your scenario (maybe exemplify)?

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
renfrow
Posts: 6
Joined: Tue Apr 16, 2013 12:10 am

Re: Pre-existing install components

Steps to reproduce:
  • Build app1 (with Advanced Installer) containing lib1,lib2,lib3, that will install libs to C:\Java\Lib
    Install app1
    Run app1 to see that it works
    Build app2 (with Advanced Installer) containing lib1,lib2,lib3, that will install libs to C:\Java\Lib
    Install app2
    Run app2 to see that it works
    Uninstall app2 (which removes lib1,lib2,lib3)
    Run app1 to see that it fails because it is missing one of lib1,lib2,lib3
The behavior that I desire is that the pre-existence of lib1,lib2,lib3 are recorded at install time of app2 so that at uninstall time they are not removed. What would be great would be link counts kept so that if either app1 or app2 were uninstalled, the link counts would be decremented, and only removed if link count went to 0.

Thanks!

Tom Kimpton.
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Pre-existing install components

Hello Tom,

In order to achieve what you want you should create a merge module which will contain the related files (lib1, lib2, lib3). Then, you should add the merge module within your installation packages.

If you have any questions let us know.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
renfrow
Posts: 6
Joined: Tue Apr 16, 2013 12:10 am

Re: Pre-existing install components

Are there any plans on integrating this functionality into the Java version of the installer? It says that this feature is in the Enterprise version, but, NOT removing existing libraries, when uninstalling, REALLY needs to be a basic feature.

Thanks!

Tom Kimpton.
renfrow
Posts: 6
Joined: Tue Apr 16, 2013 12:10 am

Re: Pre-existing install components

Or is there any way to mark a file as 'Do not remove' for uninstallation? I simply cannot risk having a user uninstall my app and break one (or more) of their other apps. I'd rather leave 2-3 megabytes on their machine than break something.

Tom Kimpton.
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Pre-existing install components

Hello Tom,

Indeed, our "Create Merge Module" feature is an "Enterprise" feature. However, in order to achieve what you want you can add the related files in a separate component having the same name and same GUID in both of your installation project. Please take a look on our "How can I share a file between multiple packages so when one of the packages is uninstalled the file is not deleted?" article which debates a similar issue.
Or is there any way to mark a file as 'Do not remove' for uninstallation?
For this you can mark the above files component as "Permanent", from "Organization" page.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Feature Requests”