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
FOLLOW US
Get the latest news in Application Packaging