On to an upgrade question-I have an installer that just installs a
single EXE right now, and I'd like to be able to create an upgrade path
for it. The trick is, I'd like to be able to have a package that will
upgrade within the same file version. If I change only the package code
(small upgrade), and set the condition to upgrade minimum version
1.0.0.0 inclusive, the upgrade still seems to run from the command line,
but no files are actually changed unless their versions have been
modified (e.g. changing the exe's version to 1.0.0.1 from 1.0.0.0). I'd
like to be able to leave the exe as version 1.0.0.0, and then publish an
installer that will replace the version on the target machine. In
Installshield, I was able to do this by setting a property that overrode
the file version for upgrade checks-is there a way to do the same in
Wix? All I want to do is update components where the version is less
than or equal to the version in the package-not just less than. This
comes up a lot in our development/QA builds.
I'd also rather not mess with the version numbers by incorporating a
build number at the end (i.e. 1.0.0.X). All four segments are
meaningful to our apps, and you can't seem to add a fifth, so we're sort
of stuck.
Any suggestions?
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
