Versioning Question

Add-in Express™ Support Service
That's what is more important than anything else

Versioning Question
 
Ben Cassell




Posts: 15
Joined: 2011-01-12
Hi,

Quick question about the versioning numbers on the add-ins. We had an add-in that we published under version number 1.0.9. It was detected and installed just fine. We then published version 1.0.10. This version was not deteced by the add-in, and it refused to update itself (using "Click-Twice").

We manually forced 1.0.10 to install, which went through fine. Upon starting our application with the add-in, it found a "newer" version and rolled back the application to 1.0.9! Attempting to publish another version, 1.0.91 forced an update.

My question is: Is version 1.0.10 not considered more up-to-date than 1.0.9? Or is the trailing zero omitted? Would version 1.0.11 be considered more up to date than 1.0.9 or the other way around?

Thanks in advance,
Ben
Posted 18 Jan, 2011 09:09:07 Top
Eugene Astafiev


Guest


Hi Ben,

Where did you change the Version property? Does it come from the MSI installer?

BTW What version and build number of Add-in Express do you use?
Posted 18 Jan, 2011 11:58:35 Top
Ben Cassell




Posts: 15
Joined: 2011-01-12
Hi Eugene,

We're using version 8.403.0.10 currently.

The version property we're setting is the Version property on the MSI file. The updates for the add-in work just fine (for example 1.0.1 to 1.0.2 or 1.0.5 to 1.0.9 etc). The only problems we're encountering are with 1.0.9 to 1.0.10.

Cheers,
Ben
Posted 19 Jan, 2011 07:50:39 Top
Eugene Astafiev


Guest


Hi Ben,

I will try to reproduce the issue on my PC and let you know the results. What version and build number of Add-in Express do you use?
Posted 20 Jan, 2011 09:58:41 Top
Ben Cassell




Posts: 15
Joined: 2011-01-12
Hi Eugene,

Sorry about that, I provided the version number for another product. It's version 6.3.3052.2005 (AddinExpress.MSO.2005).

Ben
Posted 20 Jan, 2011 10:09:17 Top
Eugene Astafiev


Guest


Hi Ben,

I have reproduce the issue you described above on my PC with Visual Studio 2010 and Office 2007 SP2. We will investigate the cause of the issue (does it belong to Add-in Express or not?) and then I will let you know the results.

Thank you for pointing this to me.
Posted 21 Jan, 2011 12:26:47 Top
Ben Cassell




Posts: 15
Joined: 2011-01-12
Hi Eugene,

Perfect, thanks. :)

Ben
Posted 24 Jan, 2011 07:05:04 Top
Eugene Astafiev


Guest


Hi Ben,

This is not a bug. Please note that the MSI installer uses three positions separated by the point to indicate the Version number (for example, 1.0.0). On the other hand the .net framework uses the AssemblyVersion attribute which allows you to specify the version number of the application, assembly and etc. It uses four positions instead (1.0.0.0). That is why the fourth position in the Version property is ignored in the ClickTwice installer (it is based on the Version property of the MSI installer). Please use the first three positions to specify the number of the next build (for example, 1.0.1).
Posted 25 Jan, 2011 05:55:59 Top
Ben Cassell




Posts: 15
Joined: 2011-01-12
Hi Eugene,

We were only using the first three positions when this behaviour occurred. The problem was going from version 1.0.9 to 1.0.10 (only three positions).

I'm wondering if it's some kind of issue with using string comparision on the numbers instead of numerical comparisons. In such a scenario, "9" would be considered "greater" than "10", as well as "110" and anything else beginning with "1".

Thanks,
Ben
Posted 25 Jan, 2011 07:15:17 Top
Eugene Astafiev


Guest


Hi Ben,

You are right! This is a bug. I have just filed it in our bug tracking system under #2393.

Thank you for pointing this to me.
Posted 25 Jan, 2011 07:29:09 Top