Is there any way for the auto updater client to ask for a specific version to upgrade to?
For example, if I have the following versions 4.0, 4.1, 4.2 and the client is at 4.0 and wants to upgrade only to 4.1 is that possible with Advanced Installer?
Suggested Articles
-
rich.pruitt
- Posts: 2
- Joined: Fri Aug 31, 2012 2:18 am
-
mihai.petcu
- Posts: 3860
- Joined: Thu Aug 05, 2010 8:01 am
Re: Define Update Version
Hi Rich and welcome to Advanced Installer forums,
Here are a couple of related user guide articles(with links and subarticles) to get you started understanding and configuring the Advanced Updater:
Using The Auto Updater
Auto Updater
Since you are new, I highly recommend you read our tutorials for a better understanding of how to use Advanced Installer to efficiently deploy your products.This will also help you better understand support team's suggestions now and in the future. The Simple and Professional tutorials are especially important.
Let us know if you have any questions.
All the best,
Mihai
Yes it is. There's a screenshot sample of how this looks like on our Auto Updater web-page in the "Improved end-user update experience" section.For example, if I have the following versions 4.0, 4.1, 4.2 and the client is at 4.0 and wants to upgrade only to 4.1 is that possible with Advanced Installer?
Here are a couple of related user guide articles(with links and subarticles) to get you started understanding and configuring the Advanced Updater:
Using The Auto Updater
Auto Updater
Since you are new, I highly recommend you read our tutorials for a better understanding of how to use Advanced Installer to efficiently deploy your products.This will also help you better understand support team's suggestions now and in the future. The Simple and Professional tutorials are especially important.
Let us know if you have any questions.
All the best,
Mihai
-
rich.pruitt
- Posts: 2
- Joined: Fri Aug 31, 2012 2:18 am
Re: Define Update Version
Mihai, thanks for the response.
Just to be clear, I want to ensure that I can specify which version the client updates to.
In the example's you cited the main features I saw were to allow a client to pick the upgrade version -or- updating based on a valid license. Neither of which would solve my problem exactly.
The only way I could think of controlling what version I want:
- By specifying a different update config file to look at so that they point to a config file that has the version they need to upgrade to as the latest version and no higher versions are in the config file.
- So in my example with versions 4.0, 4.1, 4.2; I could point to a file that says the latest version is 4.1 so that is what the client upgrades to.
It looks like the license check is a yes or no (i.e. can you upgrade), it does not redirect you to the latest version you can get based on your license. Assume I could add a Expiration check as a workaround.
Is there another preferred way to control what version to upgrade to by client? If so, how?
My use case is that I have a client - server application and the client has to be on the same version as the server. So if the server upgrades from 4.0 to 4.1 then the client has to do the same, even though there is a 4.2 version available.
The http://www.advancedinstaller.com/update ... -shot.html you mentioned does allow them to pick the version (nice presentation), but I was wanting to prevent them from picking. I wanted to force them to go to version 4.1, else they might incorrectly pick 4.2.
Just to be clear, I want to ensure that I can specify which version the client updates to.
In the example's you cited the main features I saw were to allow a client to pick the upgrade version -or- updating based on a valid license. Neither of which would solve my problem exactly.
The only way I could think of controlling what version I want:
- By specifying a different update config file to look at so that they point to a config file that has the version they need to upgrade to as the latest version and no higher versions are in the config file.
- So in my example with versions 4.0, 4.1, 4.2; I could point to a file that says the latest version is 4.1 so that is what the client upgrades to.
It looks like the license check is a yes or no (i.e. can you upgrade), it does not redirect you to the latest version you can get based on your license. Assume I could add a Expiration check as a workaround.
Is there another preferred way to control what version to upgrade to by client? If so, how?
My use case is that I have a client - server application and the client has to be on the same version as the server. So if the server upgrades from 4.0 to 4.1 then the client has to do the same, even though there is a 4.2 version available.
The http://www.advancedinstaller.com/update ... -shot.html you mentioned does allow them to pick the version (nice presentation), but I was wanting to prevent them from picking. I wanted to force them to go to version 4.1, else they might incorrectly pick 4.2.
-
mihai.petcu
- Posts: 3860
- Joined: Thu Aug 05, 2010 8:01 am
Re: Define Update Version
Hello,
If you don't want the user to see 4.2 just don't add to the updates list in the update configuration project.
Am I missing something from your explanation?
FYI: The "Client/Server Application Installation Package" specialized template may also help. This template allows you to configure an installer for a client/server application and it requires an Enterprise license.
All the best,
Mihai
As I think you already noticed, you can control what the user will see in the "Updates Found" dialog depending on the configuration file. The configuration file is generated by an Advanced Installer "Updates Configuration" project type as described in the above tutorials I previously posted.My use case is that I have a client - server application and the client has to be on the same version as the server. So if the server upgrades from 4.0 to 4.1 then the client has to do the same, even though there is a 4.2 version available.
If you don't want the user to see 4.2 just don't add to the updates list in the update configuration project.
Am I missing something from your explanation?
FYI: The "Client/Server Application Installation Package" specialized template may also help. This template allows you to configure an installer for a client/server application and it requires an Enterprise license.
All the best,
Mihai