I am evaluating the 'Pro' version and have a small issue with the prerequisite configuration.
I have a number of packages to create, install and periodically update for our own internal company use. (they wont be made public)
Most will be auto-installed but there may be a few cases where some need to be downloaded and installed by the end user. (ie laptops)
Each package will contain a sub set of document templates, each grouped according to function.
There is also one package which contains files that are common to all the packages.
eg:
P1.msi contains document templates on buying a car.
P2.msi contains document templates on buying a house.
P3.msi contains document templates on buying a train.
P4.msi contains document templates on buying a plane.
PBase.msi contains document templates which are used by all these packages, eg like a list of phone numbers.
Any of the files in P1-P4 and PBase could be updated at each update cycle. (ie PBase does not contain only static files, they may change)
I tried adding PBase as a prerequisite on P1 and P2 and P3 and P4. When I test installed P1, it also installed PBase successfully. When installed P2, it did not install PBase again. Same with P3 and P4. All good.
However, and here is the issue, if I uninstall P3, it removes PBase as well, even though P1 and P2 and P4 are still installed, thus breaking the whole installation.
Is there a switch/option/etc to tell the un-installer to not remove the prerequisite file installation?
Or some counter that does not remove the prerequisite file if any of the parent package are still installed. ?
In my case, I don't care if the prerequisite packages are left behind and not removed at all. I just want to stop them being uninstalled.
I considered making PBase a separate download, but that would require the end user to download and install it as well as P1 (or P2 or p3 or P4) which adds another step that could go wrong, be ignored, or overlooked.
Cheers,
Darryl
FOLLOW US
Get the latest news in Application Packaging