We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

scotcro
Posts: 6
Joined: Fri Nov 25, 2011 4:41 am

Installed Detection using Registry Search

If I set a registry value in the Installer with the complete Version (4 parts), and the have the updater check that registry entry, will it recognize all 4 parts of the version or just the first 3?

As an alternate can I put the Product Code in the Registry and have the Updater check that Value?

The issue is my version's build number is date based, and the private (Segment 4) is time based. e.g. 2.77.16084.1121
When I do multiple releases within the same day, the updater complains that the version is already installed.

How can I force an update to always Update?
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: Installed Detection using Registry Search

Hi,

I'm afraid that this is a Windows Installer limitation which ignores the fourth field of the version. You can see more details in the "Why do I receive the "Another version of this product is already installed" message" FAQ. That message is displayed by Windows Installer, not by the updater.

However, you can set your installer to not ignore the fourth field of the version anymore by following the steps below:
- go in the Upgrades page and check the "Customize Advanced Installer upgrade rules" option
- double-click on the Advanced Installer rule that is related to the [OLDPRODUCTS] property
- in the "Product Info" tab from the newly appeared dialog, check the "Include maximum version in range" option and click "OK"
- go in the Product Details page and change the forth field of the Product Version number, then generate a new Product Code
- build and run the project

Please note that this will also allow downgrades when in the forth field of the Product Version number is written a lower value (if the first three field will be modified with a lower value, downgrade will not be possible).

Let us know if this helped, otherwise give us more details about your scenario.

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Building Installers”