Chained packages + install files in folder of previous app? - 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!

akash
Posts: 3
Joined: Wed Aug 10, 2011 9:09 am

Chained packages + install files in folder of previous app?

I've created an msi for ProductA, which needs to install files in the folder of another app (ProductSuite). I've followed the instructions (http://www.advancedinstaller.com/user-g ... ation.html) and this all works fine when ProductSuite is already installed.

For the next step I want the installer for ProductSuite to have a chained package that ensures that ProductA is also installed. However, when I do this, ProductA gets installed to "C:\PRODUCT_SUITE_FOLDER" (PRODUCT_SUITE_FOLDER is the name of the property I've declared to hold the location of the ProductSuite install folder). So it seems like the search for the folder is failing and then the location is defaulting to the wrong location.

All I've done to add the chained package to the ProductSuite installer is to accept the defaults when I right click and "Add Chained Package". Can anyone point out where I've gone wrong?

Thanks
Akash

P.S. I'm using version 7.7 build 28804
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: Chained packages + install files in folder of previous a

Hi Akash and welcome to Advanced Installer forums,

As a generic observation this scenario seems to be that of patch project.
So it seems like the search for the folder is failing and then the location is defaulting to the wrong location.
If you are using a search in your chained package to retrieve the ProductSuite installation directory then there is no need to prepend the drive to the path. You can also use a MessageBox custom action to test the search before using it in the chained package.

All the best,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
akash
Posts: 3
Joined: Wed Aug 10, 2011 9:09 am

Re: Chained packages + install files in folder of previous a

mihai.petcu wrote: As a generic observation this scenario seems to be that of patch project.
I don't understand how this is similar to a patch project, maybe I'm missing something. ProductA is in fact a plugin for ProductSuite, but I need it to version independently from the ProductSuite. Maybe I should be implementing this in a different way?

Anyway, I tried using the MessageBox custom action in the ProductA installer to test the search: the message box pops up with the correct value when I run the ProductA installer by itself; it does *not* pop up when I run it via the ProductSuite installer.

Also, I am not prepending the drive to the path - see screenshot of the search defined in ProductA installer:
Screenshot
Screenshot
advanced_installer.JPG (15.66 KiB) Viewed 3150 times
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: Chained packages + install files in folder of previous a

Hello,
I don't understand how this is similar to a patch project, maybe I'm missing something. ProductA is in fact a plugin for ProductSuite, but I need it to version independently from the ProductSuite. Maybe I should be implementing this in a different way?
ProductA is obviously an Upgrade to ProductSuite and since it requires the full installation of ProductSuite on the target machine and consists of small modifications, this would be a patch scenario. Here are a couple of articles with overall information about this to help you decide:
http://www.advancedinstaller.com/user-g ... tches.html
http://msdn.microsoft.com/en-us/library ... 85%29.aspx
Anyway, I tried using the MessageBox custom action in the ProductA installer to test the search: the message box pops up with the correct value when I run the ProductA installer by itself; it does *not* pop up when I run it via the ProductSuite installer.
I am not sure why this happens. If it has no execution condition and is set with "Immediate execution" can you please send us the .AIP (project) to support at advancedinstaller dot com so we can investigate it?

All the best,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
akash
Posts: 3
Joined: Wed Aug 10, 2011 9:09 am

Re: Chained packages + install files in folder of previous a

I've emailed the .aip files to you.

On the patch/upgrade/chained package question, the scenario I need to support is as follows:

1) We release v1 of ProductSuite. Our clients needs a long time to test this software before they are happy to use in production. They complete this testing and sign off use of our product for production purposes.
2) We release a new plugin for ProductSuite (ProductA). By having a separate installer the client can see that they still have v1 of ProductSuite installed, plus v1 of ProductA. They are confident that they don't need to go through the full sign off process again.
3) We release v2 of ProductSuite. ProductA v1 is compatible with ProductSuite v2, so we want to bundle it in with the v2 installer - hence the chained packages. We also want to be able to provide the same v1 ProductA installer to existing or new clients who choose to use v1 of ProductSuite.

This does not sound like a patch/upgrade scenario to me, but I'm not an expert on installers!
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: Chained packages + install files in folder of previous a

Hello,

Indeed after reading the detailed description it seems you don't need to include ProductA as a patch.

All the best,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”