Jon
Posts: 42
Joined: Tue Jan 14, 2014 4:26 pm

Install patch using bootstrapper option

I'd like more information on how "Install MSI as minor upgrade" under the Bootstrapper options works. I tested a simple scenario and it works. This is simpler than creating an msp. I'd like to know if I can use this option to deploy all the patches if we follow all the patch rules? What are the limitations? As an example, if I have version 1.0.0 and in the future, multiple patches are required. Can I create a 1.0.1, then 1.0.2, then 1.0.3 ai projects and all of them with this option selected (instead of creating msp installers)?
Also, when "Install MSI as minor upgrade" is selected, the option to "do not delete extracted MSI and CAB files" is unchecked and disabled. What does this mean for above scenario? As I understand, MSI's from previous installs are required to apply patches and also to do repairs.
Thanks in advance for your help!
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: Install patch using bootstrapper option

Hi,
I'd like to know if I can use this option to deploy all the patches if we follow all the patch rules? What are the limitations?
Yes, you can use this option as long as none of the patch rules is broken. The difference from a MSP package is the size of the package. A MSP package contains only the updated files and it is smaller while the package created using this option contains all the files, but it will install only the updated files, however its size is larger.
As an example, if I have version 1.0.0 and in the future, multiple patches are required. Can I create a 1.0.1, then 1.0.2, then 1.0.3 ai projects and all of them with this option selected (instead of creating msp installers)?
Yes, you can do this.
Also, when "Install MSI as minor upgrade" is selected, the option to "do not delete extracted MSI and CAB files" is unchecked and disabled. What does this mean for above scenario? As I understand, MSI's from previous installs are required to apply patches and also to do repairs.
The "Do not delete extracted MSI and CAB files" option is unchecked and disabled when the "EXE setup with resources next to it" package type is selected in the same page. If the "Single EXE setup (resources inside)" option is used, that option will be available. Indeed, it is recommended to check it in this scenario.

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Jon
Posts: 42
Joined: Tue Jan 14, 2014 4:26 pm

Re: Install patch using bootstrapper option

Thanks for the info.
I did more testing and have issue with web installer. Here is the scenario:

I have version 1.0.0 installed.
Created a web installer for version 1.0.1. Under bootstraper options, both "Install MSI as minor upgrade (if applicable)" and "Uninstall a package with the same version (if found)" are checked.
When I install the web version of 1.0.1, it gave me message saying another version is already installed. asking me to unstall first.
There is no issue with a regular package type (non-web), version 1.0.1 got installed by applying the difference - as a patch.

Is this the expected behavior for web installers? We rely on the web installer a lot so this behavior is not acceptable. Is there a solution? thanks!
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: Install patch using bootstrapper option

Hi,

I'm not sure why you encounter this problem with your web installer package. This error is displayed if the Product Code of the 1.0.0 and 1.0.1 versions is the same.

Are you sure that they do not have the same Product Code? Also, please make sure that the right version of your package is downloaded by the web installer (i.e. version 1.0.1, not 1.0.0).

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Jon
Posts: 42
Joined: Tue Jan 14, 2014 4:26 pm

Re: Install patch using bootstrapper option

I'm not familiar with msi and msp technology. Please clarify the following:

1. to use "install MSI as minor upgrade" option under Bootstrapper, should versions 1.0.0, 1.0.1 and 1.0.2 have the same product code or not the same product code? I thought the same rules need to be applied as in creating an MSP patch. So, when I created different versions of installers to test this Bootstrapper option, I selected "Keep existing" when prompted with "Generate a new product code?". Is this correct or not?

2. With msp patches, the original msi needs to be available for msp patch install to work. We deploy our software multiple ways - one being using CD. If a msp patch is required and if the user installed the software via a CD, the msp patch will look for the msi on the CD which most likely won't be found? This will be an issue with msp deployment? Is this correct? Is there a way to get around it?

3. With the Install msi as a patch option using the bootstrapper feature, does it require the msi to be available? Will I run into the same issue as #2 for msp patches?

Thanks!
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: Install patch using bootstrapper option

Hi,
1. to use "install MSI as minor upgrade" option under Bootstrapper, should versions 1.0.0, 1.0.1 and 1.0.2 have the same product code or not the same product code? I thought the same rules need to be applied as in creating an MSP patch. So, when I created different versions of installers to test this Bootstrapper option, I selected "Keep existing" when prompted with "Generate a new product code?". Is this correct or not?
Yes, this is correct, when this option is used you need to keep the same Product Code between the versions of your product.
2. With msp patches, the original msi needs to be available for msp patch install to work. We deploy our software multiple ways - one being using CD. If a msp patch is required and if the user installed the software via a CD, the msp patch will look for the msi on the CD which most likely won't be found? This will be an issue with msp deployment? Is this correct? Is there a way to get around it?
Indeed, the MSP patch will look for the original MSI package when installing it. In order to avoid this problem you can check the "Do not delete extracted MSI and CAB files" option from the "Builds" page.

The MSI package is also cached by Windows Installer and sometimes, the patch do not ask for the original MSI. For more details, you can take a look on the "Why does the .msp installation requirs original .msi" and "Why does the patch require the originial setup.msi" threads which debates a similar problem.
3. With the Install msi as a patch option using the bootstrapper feature, does it require the msi to be available? Will I run into the same issue as #2 for msp patches?
No, in this case the MSI package from the older version of the product is not required anymore.

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Jon
Posts: 42
Joined: Tue Jan 14, 2014 4:26 pm

Re: Install patch using bootstrapper option

Hi,

I'm still unable to resolve the issue with web installer not working as expected for the "Install MSI as minor upgrade" option. Here is the case:

product versions 1.0.0 and 1.0.1 have the same product code.
version 1.0.1 has "Install MSI as minor upgrade (if applicable)" checked.

Created 1.0.1 installer with following Package types and tested applying as minor upgrade:
1. Single EXE setup (resources inside) - test passed with version 1.0.1 installed by applying the difference
2. EXE setup with resources next to it - test passed with version 1.0.1 installed by applying the difference
3. web installer (downloadable small EXE) - test failed with error message: "Another version of the product is already installed...". It did not even download the msi as far as I could tell.

What am I missing?
Thanks!
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: Install patch using bootstrapper option

Hi,

I tested the scenario and, indeed, I reproduced the problem. This seems to be an Advanced Installer issue. A fix will be available in a future version of Advanced Installer, thank you for bringing it to our attention.

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Jon
Posts: 42
Joined: Tue Jan 14, 2014 4:26 pm

Re: Install patch using bootstrapper option

Thanks for your prompt followup. Can you treat this as a priority issue for the next release? This issue is critical as it impacts our ability to deploy patches when required.

thanks!
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: Install patch using bootstrapper option

You're welcome.

I set the issue to be fixed in the next release, but I'm afraid that I cannot guarantee this. There is not too much time left until the next release and the developer in charge of this functionality is currently working on other issues.

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: Install patch using bootstrapper option

Hi,

This issue have been fixed and it will be available in the next version of Advanced Installer.

However, I'm afraid that there is another issue that appears because of a Windows Installer limitation. The issue and a solution for it is described in the "minor patch update error" thread.

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Dan
Posts: 4530
Joined: Wed Apr 24, 2013 3:51 pm

Re: Install patch using bootstrapper option

Hello,

This was fixed in version 13.0 of Advanced Installer released on June 2nd, 2016.

Best regards,
Dan
Dan Ghiorghita - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Building Installers”