13 December 2012 CI Team

image1677

If you are building setups/installer (Do you know the difference?) in the world of windows you might have heard about the Windows Installer XML (Wix) toolset.

Version number in Wix

While building an installer it is possible to define a version number after the usual system Major.Minor.Build.Revision which will be visible at the programs in the system administration:

image

What’s important in the case of an update

If the software is installed in version 1.0.0.0 and you wish to install the new version 2.0.0.0 Wix is going to recognize the difference and delete the older version automatically.

The problem appears if you change the last number of the version because Wix won’t recognize this.

Example:

Version 1.0.0.0 is currently installed and now version 1.0.0.1 is delivered. In this case the installer won’t delete the older version but reinstall it. Not until you reach version 1.0.1.0 he will recognize the difference and the usual upgrade-process works properly.

More information’s on the official website.

How did I recognize the problem?

I’ve found this problem because that’s how our Nightly Build System generated version numbers after this system till now: 1.0.YYMM.DDBuildNumber – that means a lot of useless dead weight for my system at the end of the month Zwinkerndes Smiley

Thanks a lot also to Sebastian Seidel – who provides me with several good hints about Installers on Twitter.

Also be aware: The "FileVersion" is important - the "ProductVersion" flag can be anything and is not important for the WIX update process!

Conclusion

Wix-Version system: Number.Number.Number.doesn’t matter