Installing using chained packages - Advanced Installer Community
Morantex
Posts: 16
Joined: Tue Jun 18, 2013 7:56 pm

Installing using chained packages

I have a product that is a .Net class library and we've created an installer for this - it seems to be fine.

We also have a separate application product that uses the above class library and we're now putting together an installer for this product.

My question is can we have our new application product's installer just "call" the installer for the class library product?

If not, is there any way to leverage the already written and tested installer for the class library?

If not, is there a way to silently include and run the class library installer as a step in running the new application installer?

Finally, I do see something called "Chained" as a kind of Prerequisite, is this perhaps the way to go? when I try this the menu item for 'Chained Package' is disabled in the menu bar...

Thanks
Morantex
Posts: 16
Joined: Tue Jun 18, 2013 7:56 pm

Re: Installing using chained packages

OK after some digging I can see that I must upgrade from Pro to Enterprise in order to used Chained Packages.

The problem is that this page of your website makes no mention of this.

Had this been clearly stated then I might have been aware and then purchased the Enterprise edition.

So I have some questions:

1. How can I upgrade my Pro to Enterprise? There is a 700 USD price difference but I don't know how to purchase such an upgrade.
2. Is there a more detailed list of the differences between the various editions?
3. Is chaining the ONLY way to what I need?

Also does the chaining feature have the intelligence to show what files are installed by a chained MSI?

What I mean is that if the App installer gets chained to another installer and that other installer installs X.DLL, then we don't need to install X.DLL in the installer for App, even if App has a direct dependency on X.DLL.

How is this handled?

If we do specify X.DLL in the App installer even though its part of the other chained installer, then does this work? does the install process see its already been installed when the chained MSI was installed?





Thanks
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Installing using chained packages

Hello,
1. How can I upgrade my Pro to Enterprise? There is a 700 USD price difference but I don't know how to purchase such an upgrade.
You can upgrade your Advanced Installer license from our "License Upgrade" page. Just enter your license key and, then from your customer information page start the purchase for an upgrade to "Enterprise".
2. Is there a more detailed list of the differences between the various editions?
You can check our features list by editions from our "Feature Comparison" page.
3. Is chaining the ONLY way to what I need?
If you don't want to upgrade your license to "Enterprise", then you can add your class library installer package as a feature-based prerequisite to your main installation project. Then, in the "Full UI" field, from "Prerequisite Setup File tab -> Install Command Lines" section, you can use a silent command line parameter for your prerequisite package. Also, please keep in mind that on below Enterprise project types only the "Full UI" install command line can be used and the prerequisite will be installed only if the main package is run with full UI. So, using a "Professional" project type, you can install your prerequisite package only if the main installation package is running with full UI.
Also does the chaining feature have the intelligence to show what files are installed by a chained MSI?

What I mean is that if the App installer gets chained to another installer and that other installer installs X.DLL, then we don't need to install X.DLL in the installer for App, even if App has a direct dependency on X.DLL.

How is this handled?

If we do specify X.DLL in the App installer even though its part of the other chained installer, then does this work? does the install process see its already been installed when the chained MSI was installed?
In this case Windows Installer will overwrite the X.DLL file using the "Files Versioning Rules". For this scenario, it is recommended to use a merge module which will contain your X.DLL file and will be added to both installation packages. Also, please keep in mind that our "Create Merge Modules" features is available only in an "Enterprise" or higher project type.

If you have any questions let us know.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Morantex
Posts: 16
Joined: Tue Jun 18, 2013 7:56 pm

Re: Installing using chained packages

Daniel wrote:Hello,
1. How can I upgrade my Pro to Enterprise? There is a 700 USD price difference but I don't know how to purchase such an upgrade.
You can upgrade your Advanced Installer license from our "License Upgrade" page. Just enter your license key and, then from your customer information page start the purchase for an upgrade to "Enterprise".
2. Is there a more detailed list of the differences between the various editions?
You can check our features list by editions from our "Feature Comparison" page.
3. Is chaining the ONLY way to what I need?
If you don't want to upgrade your license to "Enterprise", then you can add your class library installer package as a feature-based prerequisite to your main installation project. Then, in the "Full UI" field, from "Prerequisite Setup File tab -> Install Command Lines" section, you can use a silent command line parameter for your prerequisite package. Also, please keep in mind that on below Enterprise project types only the "Full UI" install command line can be used and the prerequisite will be installed only if the main package is run with full UI. So, using a "Professional" project type, you can install your prerequisite package only if the main installation package is running with full UI.
Also does the chaining feature have the intelligence to show what files are installed by a chained MSI?

What I mean is that if the App installer gets chained to another installer and that other installer installs X.DLL, then we don't need to install X.DLL in the installer for App, even if App has a direct dependency on X.DLL.

How is this handled?

If we do specify X.DLL in the App installer even though its part of the other chained installer, then does this work? does the install process see its already been installed when the chained MSI was installed?
In this case Windows Installer will overwrite the X.DLL file using the "Files Versioning Rules". For this scenario, it is recommended to use a merge module which will contain your X.DLL file and will be added to both installation packages. Also, please keep in mind that our "Create Merge Modules" features is available only in an "Enterprise" or higher project type.

If you have any questions let us know.

All the best,
Daniel
Hi, thanks for the replies, much appreciated.

I added the class library as a feature based prerequisite and when I run the main installer the library gets installed.

But:

1. I tried to suppers the UI for the prerequisite but get told that this requires the Enterprise version - is there no other way to suppress this?
2. When I uninstalled the product two things happened:
a) The class library prerequisite was NOT uninstalled.
b) When I manually forced the package to uninstall (in Add/Remove programs) it complained that the path didnt exist (the path in x86 Program Files created for the main install)

So how can I get it to uninstall automatically?

Thanks
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Installing using chained packages

Hello,
1. I tried to suppers the UI for the prerequisite but get told that this requires the Enterprise version - is there no other way to suppress this?
In order to achieve what you want (using a Professional project type) you should add a silent install command line in the "Full UI" field of your prerequisite setup tab. Also, you should leave empty the "Basic UI" and "Silent (No UI)" fields.
2. When I uninstalled the product two things happened:
a) The class library prerequisite was NOT uninstalled.
In order to achieve this you should enable the "Uninstall using this command line" option, from prerequisites setup tab,and add an uninstall command line for your prerequisites package.
b) When I manually forced the package to uninstall (in Add/Remove programs) it complained that the path didnt exist (the path in x86 Program Files created for the main install)
Can you please implement the solution exposed in our "How can I share a file between multiple packages so when one of the packages is uninstalled the file is not deleted?" FAQ and see if the behavior still persist?

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

Return to “Common Problems”