We have two editions of our software, with different serial numbers for each; call the editions A and B. A is a cut-down version of B, and so an upgrade from A to B is supported. A and B have the required upgrade codes so that if A is currently installed, installing B will uninstall A and then install B. This is what we want to happen. We also have enabled the serial number search facility in AI (we store it in the registry), so that if someone upgrades an older version of A to a newer version of A, or an older version of B to a newer version of B, the serial number is automatically populated for them.
However, if we have A installed, and run an install of B, the serial number dialog is pre-populated with the A serial number. This fails validation (as expected). It's more of a problem if we run an unattended install, running a B install and passing PIDKEY=<B serial number> on the command line. The install reads the existing A serial number, which fails validation by the B install, so the B install terminates. The result of this is that there is no way to do an unattended upgrade of A to B.
Is there some way that I can override the search for the existing serial number with a custom action of some kind? We use other custom actions so writing a DLL in C++ to do this is not a problem.
If the search for PIDKEY finds a serial number, and a different one is passed on the command line, can I somehow read both of them?
FOLLOW US
Get the latest news in Application Packaging