Hi, It's actually a good idea to start with a version lower than I ever released, so I ended up doing like:
[code] <?define UpgradeCode = "GUID"?> <?define CurrentVersion = "1.0.0"?> <Upgrade Id="$(var.UpgradeCode)"> <UpgradeVersion OnlyDetect="no" Property="OLDAPPFOUND" Minimum="0.0.1" IncludeMinimum="yes" Maximum="$(var.CurrentVersion)" IncludeMaximum="no" /> <UpgradeVersion OnlyDetect="yes" Property="NEWAPPFOUND" Minimum="$(var.CurrentVersion)" IncludeMinimum="yes" /> </Upgrade> [/code] Thanks a lot for the tip! Viv On 3/31/2010 12:36 AM, Curtis Jewell wrote: > > On Tue, 30 Mar 2010 13:12 +0200, "Viv Coco"<vcotirl...@hotmail.com> > wrote: > >> Hi all, >> >> I would like my application to be upgraded if a newer version is run. So >> the behaviour should be: if the user tries to install the already >> installed version (meaning current version) or an older version, the >> installer should bail out with the message "current or newer installed". >> The installer should run only if it's a newer version. >> >> For that I wrote the following: >> >> [code] >> <Upgrade Id="$(var.UpgradeCode)"> >> <UpgradeVersion Property="OLDAPPFOUND" Minimum="1.0.0.0" >> IncludeMinimum="yes" Maximum="$(var.CurrentVersion)" IncludeMaximum="no" >> /> >> <UpgradeVersion Property="NEWAPPFOUND" Minimum="$(var.CurrentVersion)" >> IncludeMinimum="yes" OnlyDetect="yes" /> >> </Upgrade> >> [/code] >> >> This sounds perfect for when the CurrentVersion would be anything grater >> than 1.0.0.0, but for the version 1.0.0.0, meaning when I release my >> first version the Minimum and Maximum are the same "1.0.0.0" and in the >> first line I say IncludeMinimum="yes"which means includes 1.0.0.0 but I >> also say IncludeMaximum="no" which means exclude "1.0.0.0". Also, for >> this version (1.0.0.0) I will have both properties set (I think): >> OLDAPPFOUND and NEWAPPFOUND. Won't I get into troubles with this? >> > I would say it would be best to set the minimum to a version lower than > you ever released (0.0.1) to start with - and yes, I would include it. > Start as you intend to finish. > > By the way, versions of msi files do not have a 4th portion, and will go > from 0.0.0 up to 255.255.32767. > > --Curtis > -- > Curtis Jewell > swords...@csjewell.fastmail.us > > %DCL-E-MEM-BAD, bad memory > -VMS-F-PDGERS, pudding between the ears > > [I use PC-Alpine, which deliberately does not display colors and pictures in > HTML mail] > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
