Q: Automatically generate update using same project

[ChristianLA]

Background info:

• We have an automated build system to create installers from the same project and we constantly create updates on it.
• Currently for every update we have to:
  • 1. Reopen the AIP projects (in new streams on our SVN)
    2. Change the product version and product code (including all language product code) to create an update (we generate MSI and EXEs)
    3. Also we remove all files and populate it with the new ones (using folder synchronization), this is because we realized that sometimes after an upgrade some DLLs or EXEs are missing (componen count maybe). By repopulating files the components GUID updates and fixes the issue

Attempt:
We have tried to use the same project without opeining it to modify it and send parameters through the COM builder of AI to create installers and we notice this:

• Sending a greater Mayor.Minor (using SetVersion AI property) generates a new ProductCode each time (it does not happen when you just update the build portion only)
  • This obiously causes unwanted side by side installations in between same major.minor.patch.xxxx artifacts
• On the generated artifact only clean new installation places all files, but upgrades sometimes misses some critical DLLs or even EXEs

Is this a normal behabior on AI?

[Eusebiu]

Hi,

I apologize for the delayed reply.

Sending a greater Mayor.Minor (using SetVersion AI property) generates a new ProductCode each time (it does not happen when you just update the build portion only)
This obiously causes unwanted side by side installations in between same major.minor.patch.xxxx artifacts

I'm afraid that Windows Installer uses only the first three fields of the Product Version while the fourth one is ignored. For more details you can take a look on the "ProductVersion" article. You can also read the "How do I remove the old version when using the fourth field of the Product Version" FAQ which might help you.

On the generated artifact only clean new installation places all files, but upgrades sometimes misses some critical DLLs or even EXEs

This may happen if the files from the upgraded package have a lower version than the files from the old package. Please read the "Why some files are missing from the installation folder when performing an upgrade" FAQ which talks about this problem.

Just let me know if you have other questions.

Best regards,
Eusebiu