Version numbers are wrong in installed programs

51 views
Skip to first unread message

tig...@gmail.com

unread,
Nov 2, 2017, 12:23:05 PM11/2/17
to TortoiseSVN
Hello,
I'm developing a software that can show/update outdated program called UCheck.
I wanted to integrate TortoiseSVN, but facing an issue (bug?) with the version numbers put in the registry by the installer.

Current version is 1.9.7.27907, but it reads like this in the installed programs:
TortoiseSVN 1.9.7.27907 (64 bit) ---- TortoiseSVN --- 02/11/2017 -- 43.4 Mo --- 1.9.27907

As seen above, the version number is missing the bug fix level (7)
Should be major.minor.bug.build (just like in the name) but it is major.minor.build.

For my devs I cannot use that and compare to the database version.
Can anyone confirm it's a bug and let me know if it will be fixed?

Thanks,

Stefan

unread,
Nov 3, 2017, 5:28:48 PM11/3/17
to TortoiseSVN
The version numbers are not wrong, that's done on purpose.
MSI ignores the fourth version number completely, so we use the revision number in the third place instead to make sure that even intermediary builds install properly.

You should be aware that there are many tools out there which have a separate versioning system for the app and the installer. Just think of all the installers that install not just one tool but multiple tools.
So relying on the installer version is a bad idea in the first place.

tig...@gmail.com

unread,
Nov 7, 2017, 8:41:05 AM11/7/17
to TortoiseSVN
I'm not relying on installer version as a generic pattern, it's done case by case. And it works for most of them. Installers that install multiple tools aren't taken in account here.

So you are telling me this won't get fixed, fine. We'll go the other way then, finding executable at known paths and look for Version Info.

Thanks,

Stefan

unread,
Nov 9, 2017, 11:29:19 AM11/9/17
to TortoiseSVN
It won't get fixed because it's not a bug.

tig...@gmail.com

unread,
Nov 9, 2017, 11:37:43 AM11/9/17
to TortoiseSVN
Call that not a bug if you want, but it's an ugly workaround.
Reply all
Reply to author
Forward
0 new messages