This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- FlexNet Connect
- :
- FlexNet Connect Forum
- :
- Re: Product version comparison on 3 fields?
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 06, 2005
10:23 AM
Product version comparison on 3 fields?
Hi there
Maybe I don't really understand the product version comparison in update service 4.5 (professional edition). Is it possible, that the update service only compare the first two fields of the product version, when the customer search for new updates?
For example, I have installed MyProduct 5.1.0 on my computer. Now I publish a patch 5.1.1 (a hotfix or so) who should be only available for MyProduct with version 5.1.0. After I've installed the patch my installed program has the version MyProduct 5.1.1. That's right so. But now, when I search for new updates, the update service shows me still the patch 5.1.1 as available update for my installed product. It seems, that the update service compare only the first two fields of the product version (ex: patch 5.1(.1) - is available for MyProduct 5.1(.0) and MyProduct 5.1(.1) and so forth.)
Is there any other way to solve this problem, than that I have to create a minor update patch (with a minor upgrade the second field of version number will change to 5.2 and not only to 5.1.1)?
Regards, Stefan
Maybe I don't really understand the product version comparison in update service 4.5 (professional edition). Is it possible, that the update service only compare the first two fields of the product version, when the customer search for new updates?
For example, I have installed MyProduct 5.1.0 on my computer. Now I publish a patch 5.1.1 (a hotfix or so) who should be only available for MyProduct with version 5.1.0. After I've installed the patch my installed program has the version MyProduct 5.1.1. That's right so. But now, when I search for new updates, the update service shows me still the patch 5.1.1 as available update for my installed product. It seems, that the update service compare only the first two fields of the product version (ex: patch 5.1(.1) - is available for MyProduct 5.1(.0) and MyProduct 5.1(.1) and so forth.)
Is there any other way to solve this problem, than that I have to create a minor update patch (with a minor upgrade the second field of version number will change to 5.2 and not only to 5.1.1)?
Regards, Stefan
(5) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 06, 2005
10:27 AM
First thing that comes to mind is to add a condition to your update using a registry key value (assuming your package updates the registry). That way, you could show the update if the registry value was "blah" or whatever...
This is just off the top of my head with no thorough thought, so it may not be the best of ideas, but I think it'd work for you.
Kelly
This is just off the top of my head with no thorough thought, so it may not be the best of ideas, but I think it'd work for you.
Kelly
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 06, 2005
10:42 AM
You are correct that Update Service by default uses major and minor version elements.
Please refer to help and search for
Add the Update Service Agent to the Installation Setup
You should find topics like
Add the Update Service Agent to the Installation Setup: InstallShield Developer and DevStudio
or
Add the Update Service Agent to the Installation Setup: InstallShield Professional
Any of these help topics should help you use customize version scheme.
Thanks
-Sunny
Please refer to help and search for
Add the Update Service Agent to the Installation Setup
You should find topics like
Add the Update Service Agent to the Installation Setup: InstallShield Developer and DevStudio
or
Add the Update Service Agent to the Installation Setup: InstallShield Professional
Any of these help topics should help you use customize version scheme.
Thanks
-Sunny
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 07, 2005
01:21 AM
Thank you for the quick advice! I think, it should work so.
Best regards, Stefan
Best regards, Stefan
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 07, 2005
09:41 AM
Kelly,
In this case, setting the DWUSVERSION in the Property Manager to 5.x.x (where x.x = current installed minor/build) should solve swalser's issue?
In this case, setting the DWUSVERSION in the Property Manager to 5.x.x (where x.x = current installed minor/build) should solve swalser's issue?
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 31, 2005
10:20 AM
While DWUSVERSION seems to working OK for .MSI packages, it does not seemed to be picked up by .MSP patches. Any ideas everyone?
Thanks. :confused:
Thanks. :confused:
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)