Re: [WiX-users] Upgrade mechanism
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 Cocovcotirl...@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=yeswhich 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#174; 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#174; 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
Re: [WiX-users] Upgrade mechanism
Hi Pally, I actually wanted to have the upgrade code inside from my very first version, as this is the way suggested by the WiX tutorial (chapter 4.2): Also note that this same installer works as a first time installer as well: if it founds a previous version, it will remove the previous version and install the current one. If it is run on a clean system, it will simply install the current application; there is no need to create separate upgrade and full installers. So I ended up doing as Curtis suggested, pls see my answer to his email. Thanks, Viv On 3/30/2010 1:33 PM, Pally Sandher wrote: You only need to put that code into your newer releases which will be doing the upgrading e.g. v1.0.0.1 Your v1.0.0.0 has nothing to upgrade so the code isn't needed. I'd suggest commenting it out for your first release so you can add it back for subsequent releases. You may find that code doesn't pass ICE61 in your v1.0.0.0 due to clashing VersionMin/VersionMax. Your properties won't both be set as when the user installs this version there's nothing for Windows Installer to detect as an older version. Palbinder Sandher Software Deployment IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with theVirtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Viv Coco [mailto:vcotirl...@hotmail.com] Sent: 30 March 2010 12:12 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Upgrade mechanism 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=yeswhich 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? Thx, Viv ;) -- Download Intel#174; 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#174; 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#174; 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
[WiX-users] Upgrade mechanism
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=yeswhich 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? Thx, Viv ;) -- Download Intel#174; 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
Re: [WiX-users] Upgrade mechanism
You only need to put that code into your newer releases which will be doing the upgrading e.g. v1.0.0.1 Your v1.0.0.0 has nothing to upgrade so the code isn't needed. I'd suggest commenting it out for your first release so you can add it back for subsequent releases. You may find that code doesn't pass ICE61 in your v1.0.0.0 due to clashing VersionMin/VersionMax. Your properties won't both be set as when the user installs this version there's nothing for Windows Installer to detect as an older version. Palbinder Sandher Software Deployment IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Viv Coco [mailto:vcotirl...@hotmail.com] Sent: 30 March 2010 12:12 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Upgrade mechanism 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=yeswhich 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? Thx, Viv ;) -- Download Intel#174; 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#174; 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
Re: [WiX-users] Upgrade mechanism
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=yeswhich 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#174; 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
