Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding?
Ian Elliott (Excell Data Corporation) wrote: Make sure your console.exe program has a higher version number than its predecessor. If that doesn't work, can you place your two msi's somewhere where they can be accessed? -Original Message- From: polan [mailto:[EMAIL PROTECTED] Sent: Thursday, October 09, 2008 8:34 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding? That was it - I needed to change the file version and now everything works ok. Thx for all the help! Ian Elliott (Excell Data Corporation) wrote: Ian Elliott (Excell Data Corporation) wrote: Your command line looks wrong: msiexec /i ExampleInstaller.msi REINSTALALL=ALL REINSTALLMODE=vomus should be msiexec /i ExampleInstaller.msi REINSTALL=ALL REINSTALLMODE=vomus (However, it may be another typo.) I've corrected the command and tested everything again. Ian Elliott (Excell Data Corporation) wrote: It is expected behavior to get the maintenance dialog during a minor upgrade. Once you click Install, any newer files should be installed over the old ones. I feel like a total idiot, but I still can not get it working. The file doesn't get installed over old file! I have a console application - the only thing it does is writing version string to the Console window. I change the application (it writes a new version number to the console), than change the package guid in the wix file, also the version attribute in the product tag. I run the installation and it finishes without error. Then I run my test console application and it is the same as before update :( I can get the files override is to use major upgrade or uninstalling and installing (minor) again. It doesn't seem right. I've also noticed that if I choose typical type of installation then nothing gets installed either even if it is the first installation (I think that might be connected). The only feature in the custom installation dialog is not selected to be installed by default. The feature has Level=1. I don't change the default INSTALLLEVEL. Also if I skip REINSTALL=ALL then i get a dialog with change/repair/remove - If I choose repair then the files gets override also. http://n2.nabble.com/file/n1306236/Product.wxs Product.wxs -- View this message in context: http://n2.nabble.com/How-Update---Upgrade-strategy-%28small%2C-minor%2C-major%29-affect-file-overriding--tp1304357p1312589.html Sent from the wix-users mailing list archive at Nabble.com. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- View this message in context: http://n2.nabble.com/How-Update---Upgrade-strategy-%28small%2C-minor%2C-major%29-affect-file-overriding--tp1304357p1315684.html Sent from the wix-users mailing list archive at Nabble.com. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding?
Thanks for the advice. I didn't actually mean to say commercial, I was more meaning that I've downloaded msi's from various sources - some commercial, some open source, ... and the vast majority of them haven't required me to either use msiexec or uninstall the previous version. I'm just trying to keep things as simple as possible. In the case of this installer, it's relatively unlikely that any individual developers will create a private build of the installer and install it, and the way I've got it set up at the moment it would end up with a version number 0.0.0.0. I'll have a think about it at the moment, but I think we should be ok using a wildcard. The only other thing that I can think of at the moment is having the build process generate the guid, but I'm avoiding that for the moment. Thanks for the advice. Adam -Original Message- From: Ian Elliott (Excell Data Corporation) [mailto:[EMAIL PROTECTED] Sent: 09 October 2008 19:24 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding? There is one side effect that I can think of (and have experienced) during daily development. Say your build version number changes once per day. Everything will work fine if you only attempt to install today's version over yesterday's version. Now, if you are developing and build multiple private builds during the day, there can be a problem. If you use the wix wildcard to auto generate productID's you will have those id's changing and the version number doesn't change. When people blindly try to install one private build over another you get weird things happening. It's been awhile and I can't remember exactly what the deal was but I do remember going to many machines to fix things. From earlier in the thread, Otherwise it forces the user to uninstall the previous version before installing the new version - something that I've never had to do with any serious commercial package. Most serious commercial packages that I can think of actually use some kind of setup.exe bootstrapper. I have never purchased any boxed software, for example, and launched an msi directly. The setup.exe can detect if a minor upgrade needs to be launched and adjust the command line accordingly. -Original Message- From: Adam Connelly [mailto:[EMAIL PROTECTED] Sent: Thursday, October 09, 2008 5:46 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding? I'm keen to avoid doing that since it means creating the bootstrapper. It just doesn't seem quite right to me to have to do that. Thanks for the suggestion, but I think for now I'll stick to changing the product Id. Do you know if there's any undesirable side effects to doing this? Cheers, Adam -Original Message- From: John Hall [mailto:[EMAIL PROTECTED] Sent: 08 October 2008 18:22 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding? The only way I've got this to work at the moment is by manually changing the Product Id and checking it in before doing a publish to avoid the annoying another version of this product is already installed... message. Otherwise it forces the user to uninstall the previous version before installing the new version - something that I've never had to do with any serious commercial package. Is what I'm doing wrong, and if so what alternatives do I have? You could do minor upgrades for your nightly builds - this requires passing REINSTALLMODE=vomus on the msiexec commandline, so would probably require being wrapped in a bootstrapper. Regards, John - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored
Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding?
Glad you got it working! -Original Message- From: polan [mailto:[EMAIL PROTECTED] Sent: Friday, October 10, 2008 2:13 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding? Ian Elliott (Excell Data Corporation) wrote: Make sure your console.exe program has a higher version number than its predecessor. If that doesn't work, can you place your two msi's somewhere where they can be accessed? -Original Message- From: polan [mailto:[EMAIL PROTECTED] Sent: Thursday, October 09, 2008 8:34 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding? That was it - I needed to change the file version and now everything works ok. Thx for all the help! Ian Elliott (Excell Data Corporation) wrote: Ian Elliott (Excell Data Corporation) wrote: Your command line looks wrong: msiexec /i ExampleInstaller.msi REINSTALALL=ALL REINSTALLMODE=vomus should be msiexec /i ExampleInstaller.msi REINSTALL=ALL REINSTALLMODE=vomus (However, it may be another typo.) I've corrected the command and tested everything again. Ian Elliott (Excell Data Corporation) wrote: It is expected behavior to get the maintenance dialog during a minor upgrade. Once you click Install, any newer files should be installed over the old ones. I feel like a total idiot, but I still can not get it working. The file doesn't get installed over old file! I have a console application - the only thing it does is writing version string to the Console window. I change the application (it writes a new version number to the console), than change the package guid in the wix file, also the version attribute in the product tag. I run the installation and it finishes without error. Then I run my test console application and it is the same as before update :( I can get the files override is to use major upgrade or uninstalling and installing (minor) again. It doesn't seem right. I've also noticed that if I choose typical type of installation then nothing gets installed either even if it is the first installation (I think that might be connected). The only feature in the custom installation dialog is not selected to be installed by default. The feature has Level=1. I don't change the default INSTALLLEVEL. Also if I skip REINSTALL=ALL then i get a dialog with change/repair/remove - If I choose repair then the files gets override also. http://n2.nabble.com/file/n1306236/Product.wxs Product.wxs -- View this message in context: http://n2.nabble.com/How-Update---Upgrade-strategy-%28small%2C-minor%2C-major%29-affect-file-overriding--tp1304357p1312589.html Sent from the wix-users mailing list archive at Nabble.com. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- View this message in context: http://n2.nabble.com/How-Update---Upgrade-strategy-%28small%2C-minor%2C-major%29-affect-file-overriding--tp1304357p1315684.html Sent from the wix-users mailing list archive at Nabble.com. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php
Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding?
Leaving the version number unchanged at 0.0.0.0 forces you into the small
update category which requires you to specify a command line to run the update.
Changing the ProductCode means you are in the major upgrade category and that
won't require the special command line. However, if you use this method, you
also must change the ProductVersion, too. Leaving it at 0.0.0.0 won't work.
The way I did this was to have the ProductVersion passed in (it is basically
the build system's build number) and use the wildcard to automatically generate
the ProductCode each build. That way, both values change each time as is needed
for major upgrade.
Here are some relevant snippets:
?ifndef Version?
?define Version=$(var.PRODUCT_VERSION)?
?endif ?
Product Id=*
Name=Product Name
Language=1033
Version=$(var.Version)
Manufacturer=Company Name
UpgradeCode={33B6AF43-5F2F-4e69-B9A1-FEF3FA1F13C4}
!-- _ Upgrades
___ --
Upgrade Id={33B6AF43-5F2F-4e69-B9A1-FEF3FA1F13C4}
UpgradeVersion Property=OLDAPPFOUND Minimum=0.0.0.0
Maximum=$(var.Version) IncludeMinimum=yes IncludeMaximum=no /
UpgradeVersion Property=NEWAPPFOUND Minimum=$(var.Version)
IncludeMinimum=no OnlyDetect=yes /
/Upgrade
I see your company is located in Glasgow. My great grandfather was from
Glasgow. Parents are from N. Ireland.
-Original Message-
From: Adam Connelly [mailto:[EMAIL PROTECTED]
Sent: Friday, October 10, 2008 3:54 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How Update / Upgrade strategy (small, minor, major)
affect file overriding?
Thanks for the advice. I didn't actually mean to say commercial, I was more
meaning that I've downloaded msi's from various sources - some commercial, some
open source, ... and the vast majority of them haven't required me to either
use msiexec or uninstall the previous version.
I'm just trying to keep things as simple as possible.
In the case of this installer, it's relatively unlikely that any individual
developers will create a private build of the installer and install it, and the
way I've got it set up at the moment it would end up with a version number
0.0.0.0.
I'll have a think about it at the moment, but I think we should be ok using a
wildcard. The only other thing that I can think of at the moment is having the
build process generate the guid, but I'm avoiding that for the moment.
Thanks for the advice.
Adam
-Original Message-
From: Ian Elliott (Excell Data Corporation) [mailto:[EMAIL PROTECTED]
Sent: 09 October 2008 19:24
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How Update / Upgrade strategy (small, minor, major)
affect file overriding?
There is one side effect that I can think of (and have experienced) during
daily development. Say your build version number changes once per day.
Everything will work fine if you only attempt to install today's version over
yesterday's version.
Now, if you are developing and build multiple private builds during the day,
there can be a problem. If you use the wix wildcard to auto generate
productID's you will have those id's changing and the version number doesn't
change. When people blindly try to install one private build over another you
get weird things happening. It's been awhile and I can't remember exactly what
the deal was but I do remember going to many machines to fix things.
From earlier in the thread,
Otherwise it forces the user to uninstall the previous version before
installing the new version - something that I've never had to do with any
serious commercial package.
Most serious commercial packages that I can think of actually use some kind of
setup.exe bootstrapper. I have never purchased any boxed software, for example,
and launched an msi directly. The setup.exe can detect if a minor upgrade needs
to be launched and adjust the command line accordingly.
-Original Message-
From: Adam Connelly [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 09, 2008 5:46 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How Update / Upgrade strategy (small, minor, major)
affect file overriding?
I'm keen to avoid doing that since it means creating the bootstrapper. It just
doesn't seem quite right to me to have to do that.
Thanks for the suggestion, but I think for now I'll stick to changing the
product Id. Do you know if there's any undesirable side effects to doing this?
Cheers,
Adam
-Original Message-
From: John Hall [mailto:[EMAIL PROTECTED]
Sent: 08 October 2008 18:22
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How Update / Upgrade strategy (small, minor, major)
affect file overriding?
The only way I've got this to work
Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding?
I'm keen to avoid doing that since it means creating the bootstrapper. It just doesn't seem quite right to me to have to do that. Thanks for the suggestion, but I think for now I'll stick to changing the product Id. Do you know if there's any undesirable side effects to doing this? Cheers, Adam -Original Message- From: John Hall [mailto:[EMAIL PROTECTED] Sent: 08 October 2008 18:22 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding? The only way I've got this to work at the moment is by manually changing the Product Id and checking it in before doing a publish to avoid the annoying another version of this product is already installed... message. Otherwise it forces the user to uninstall the previous version before installing the new version - something that I've never had to do with any serious commercial package. Is what I'm doing wrong, and if so what alternatives do I have? You could do minor upgrades for your nightly builds - this requires passing REINSTALLMODE=vomus on the msiexec commandline, so would probably require being wrapped in a bootstrapper. Regards, John - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding?
I thought about that, but I thought you were meant to keep track of the product Id for some reason (something I've not looked into). I might just do it though in the absence of any better way. Adam -Original Message- From: Rob Mensching [mailto:[EMAIL PROTECTED] Sent: 08 October 2008 18:04 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding? Product/@Id=* -Original Message- From: Adam Connelly [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 08, 2008 06:24 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding? The project I'm working on at the moment uses a build server to automatically build our installers, etc. As part of this, it provides the version number to the installer. Therefore, every publish we do (and in fact every checkin of source) is a different version of the product. This means that ideally I'd be able to take any published msi and install it, and it should have the correct install / upgrade behaviour without us having to manually alter the wxs files at all (fair enough it also means we have to distribute every file every time, but I'm not worried about that at the moment). The only way I've got this to work at the moment is by manually changing the Product Id and checking it in before doing a publish to avoid the annoying another version of this product is already installed... message. Otherwise it forces the user to uninstall the previous version before installing the new version - something that I've never had to do with any serious commercial package. Is what I'm doing wrong, and if so what alternatives do I have? Cheers, Adam -Original Message- From: polan [mailto:[EMAIL PROTECTED] Sent: 08 October 2008 11:39 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding? Thx for the answer Ian Elliott (Excell Data Corporation) wrote: For the minor upgrade and small update you don't make use of the Update tag at all. Ok - lets stick to minor upgrade. I don't insert the upgrade tag, I change the package guid, and version. I run the installation msiexec /i ExampleInstaller.msi REINSTALALL=ALL REINSTALLMODE=vomus And i get stuck at maintenance dialog instead of getting normal installation. What's possibly wrong? Or maybe it is just the way that minor upgrade works? (couldn't think of the good reason) The other question is - if I get through it, will the minor upgrade override the files with new versions? I enclose a file with the source (it is a very simple and short one) http://n2.nabble.com/file/n1306236/Product.wxs Product.wxs Ian Elliott (Excell Data Corporation) wrote: Also, you listed below that the package guid didn't change for one scenario. You should always have a different package guid for every package built. My mistake of course - it was supposed to be written like you say. I did it this way, just described it wrong. -- View this message in context: http://n2.nabble.com/How-Update---Upgrade-strategy-%28small%2C-minor%2C-major%29-affect-file-overriding--tp1304357p1306236.html Sent from the wix-users mailing list archive at Nabble.com. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding?
Ian Elliott (Excell Data Corporation) wrote: Your command line looks wrong: msiexec /i ExampleInstaller.msi REINSTALALL=ALL REINSTALLMODE=vomus should be msiexec /i ExampleInstaller.msi REINSTALL=ALL REINSTALLMODE=vomus (However, it may be another typo.) I've corrected the command and tested everything again. Ian Elliott (Excell Data Corporation) wrote: It is expected behavior to get the maintenance dialog during a minor upgrade. Once you click Install, any newer files should be installed over the old ones. I feel like a total idiot, but I still can not get it working. The file doesn't get installed over old file! I have a console application - the only thing it does is writing version string to the Console window. I change the application (it writes a new version number to the console), than change the package guid in the wix file, also the version attribute in the product tag. I run the installation and it finishes without error. Then I run my test console application and it is the same as before update :( I can get the files override is to use major upgrade or uninstalling and installing (minor) again. It doesn't seem right. I've also noticed that if I choose typical type of installation then nothing gets installed either even if it is the first installation (I think that might be connected). The only feature in the custom installation dialog is not selected to be installed by default. The feature has Level=1. I don't change the default INSTALLLEVEL. Also if I skip REINSTALL=ALL then i get a dialog with change/repair/remove - If I choose repair then the files gets override also. http://n2.nabble.com/file/n1306236/Product.wxs Product.wxs -- View this message in context: http://n2.nabble.com/How-Update---Upgrade-strategy-%28small%2C-minor%2C-major%29-affect-file-overriding--tp1304357p1312589.html Sent from the wix-users mailing list archive at Nabble.com. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding?
Make sure your console.exe program has a higher version number than its predecessor. If that doesn't work, can you place your two msi's somewhere where they can be accessed? -Original Message- From: polan [mailto:[EMAIL PROTECTED] Sent: Thursday, October 09, 2008 8:34 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding? Ian Elliott (Excell Data Corporation) wrote: Your command line looks wrong: msiexec /i ExampleInstaller.msi REINSTALALL=ALL REINSTALLMODE=vomus should be msiexec /i ExampleInstaller.msi REINSTALL=ALL REINSTALLMODE=vomus (However, it may be another typo.) I've corrected the command and tested everything again. Ian Elliott (Excell Data Corporation) wrote: It is expected behavior to get the maintenance dialog during a minor upgrade. Once you click Install, any newer files should be installed over the old ones. I feel like a total idiot, but I still can not get it working. The file doesn't get installed over old file! I have a console application - the only thing it does is writing version string to the Console window. I change the application (it writes a new version number to the console), than change the package guid in the wix file, also the version attribute in the product tag. I run the installation and it finishes without error. Then I run my test console application and it is the same as before update :( I can get the files override is to use major upgrade or uninstalling and installing (minor) again. It doesn't seem right. I've also noticed that if I choose typical type of installation then nothing gets installed either even if it is the first installation (I think that might be connected). The only feature in the custom installation dialog is not selected to be installed by default. The feature has Level=1. I don't change the default INSTALLLEVEL. Also if I skip REINSTALL=ALL then i get a dialog with change/repair/remove - If I choose repair then the files gets override also. http://n2.nabble.com/file/n1306236/Product.wxs Product.wxs -- View this message in context: http://n2.nabble.com/How-Update---Upgrade-strategy-%28small%2C-minor%2C-major%29-affect-file-overriding--tp1304357p1312589.html Sent from the wix-users mailing list archive at Nabble.com. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding?
There is one side effect that I can think of (and have experienced) during daily development. Say your build version number changes once per day. Everything will work fine if you only attempt to install today's version over yesterday's version. Now, if you are developing and build multiple private builds during the day, there can be a problem. If you use the wix wildcard to auto generate productID's you will have those id's changing and the version number doesn't change. When people blindly try to install one private build over another you get weird things happening. It's been awhile and I can't remember exactly what the deal was but I do remember going to many machines to fix things. From earlier in the thread, Otherwise it forces the user to uninstall the previous version before installing the new version - something that I've never had to do with any serious commercial package. Most serious commercial packages that I can think of actually use some kind of setup.exe bootstrapper. I have never purchased any boxed software, for example, and launched an msi directly. The setup.exe can detect if a minor upgrade needs to be launched and adjust the command line accordingly. -Original Message- From: Adam Connelly [mailto:[EMAIL PROTECTED] Sent: Thursday, October 09, 2008 5:46 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding? I'm keen to avoid doing that since it means creating the bootstrapper. It just doesn't seem quite right to me to have to do that. Thanks for the suggestion, but I think for now I'll stick to changing the product Id. Do you know if there's any undesirable side effects to doing this? Cheers, Adam -Original Message- From: John Hall [mailto:[EMAIL PROTECTED] Sent: 08 October 2008 18:22 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding? The only way I've got this to work at the moment is by manually changing the Product Id and checking it in before doing a publish to avoid the annoying another version of this product is already installed... message. Otherwise it forces the user to uninstall the previous version before installing the new version - something that I've never had to do with any serious commercial package. Is what I'm doing wrong, and if so what alternatives do I have? You could do minor upgrades for your nightly builds - this requires passing REINSTALLMODE=vomus on the msiexec commandline, so would probably require being wrapped in a bootstrapper. Regards, John - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding?
Thx for the answer Ian Elliott (Excell Data Corporation) wrote: For the minor upgrade and small update you don't make use of the Update tag at all. Ok - lets stick to minor upgrade. I don't insert the upgrade tag, I change the package guid, and version. I run the installation msiexec /i ExampleInstaller.msi REINSTALALL=ALL REINSTALLMODE=vomus And i get stuck at maintenance dialog instead of getting normal installation. What's possibly wrong? Or maybe it is just the way that minor upgrade works? (couldn't think of the good reason) The other question is - if I get through it, will the minor upgrade override the files with new versions? I enclose a file with the source (it is a very simple and short one) http://n2.nabble.com/file/n1306236/Product.wxs Product.wxs Ian Elliott (Excell Data Corporation) wrote: Also, you listed below that the package guid didn't change for one scenario. You should always have a different package guid for every package built. My mistake of course - it was supposed to be written like you say. I did it this way, just described it wrong. -- View this message in context: http://n2.nabble.com/How-Update---Upgrade-strategy-%28small%2C-minor%2C-major%29-affect-file-overriding--tp1304357p1306236.html Sent from the wix-users mailing list archive at Nabble.com. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding?
The project I'm working on at the moment uses a build server to automatically build our installers, etc. As part of this, it provides the version number to the installer. Therefore, every publish we do (and in fact every checkin of source) is a different version of the product. This means that ideally I'd be able to take any published msi and install it, and it should have the correct install / upgrade behaviour without us having to manually alter the wxs files at all (fair enough it also means we have to distribute every file every time, but I'm not worried about that at the moment). The only way I've got this to work at the moment is by manually changing the Product Id and checking it in before doing a publish to avoid the annoying another version of this product is already installed... message. Otherwise it forces the user to uninstall the previous version before installing the new version - something that I've never had to do with any serious commercial package. Is what I'm doing wrong, and if so what alternatives do I have? Cheers, Adam -Original Message- From: polan [mailto:[EMAIL PROTECTED] Sent: 08 October 2008 11:39 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding? Thx for the answer Ian Elliott (Excell Data Corporation) wrote: For the minor upgrade and small update you don't make use of the Update tag at all. Ok - lets stick to minor upgrade. I don't insert the upgrade tag, I change the package guid, and version. I run the installation msiexec /i ExampleInstaller.msi REINSTALALL=ALL REINSTALLMODE=vomus And i get stuck at maintenance dialog instead of getting normal installation. What's possibly wrong? Or maybe it is just the way that minor upgrade works? (couldn't think of the good reason) The other question is - if I get through it, will the minor upgrade override the files with new versions? I enclose a file with the source (it is a very simple and short one) http://n2.nabble.com/file/n1306236/Product.wxs Product.wxs Ian Elliott (Excell Data Corporation) wrote: Also, you listed below that the package guid didn't change for one scenario. You should always have a different package guid for every package built. My mistake of course - it was supposed to be written like you say. I did it this way, just described it wrong. -- View this message in context: http://n2.nabble.com/How-Update---Upgrade-strategy-%28small%2C-minor%2C-major%29-affect-file-overriding--tp1304357p1306236.html Sent from the wix-users mailing list archive at Nabble.com. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding?
Product/@Id=* -Original Message- From: Adam Connelly [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 08, 2008 06:24 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding? The project I'm working on at the moment uses a build server to automatically build our installers, etc. As part of this, it provides the version number to the installer. Therefore, every publish we do (and in fact every checkin of source) is a different version of the product. This means that ideally I'd be able to take any published msi and install it, and it should have the correct install / upgrade behaviour without us having to manually alter the wxs files at all (fair enough it also means we have to distribute every file every time, but I'm not worried about that at the moment). The only way I've got this to work at the moment is by manually changing the Product Id and checking it in before doing a publish to avoid the annoying another version of this product is already installed... message. Otherwise it forces the user to uninstall the previous version before installing the new version - something that I've never had to do with any serious commercial package. Is what I'm doing wrong, and if so what alternatives do I have? Cheers, Adam -Original Message- From: polan [mailto:[EMAIL PROTECTED] Sent: 08 October 2008 11:39 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding? Thx for the answer Ian Elliott (Excell Data Corporation) wrote: For the minor upgrade and small update you don't make use of the Update tag at all. Ok - lets stick to minor upgrade. I don't insert the upgrade tag, I change the package guid, and version. I run the installation msiexec /i ExampleInstaller.msi REINSTALALL=ALL REINSTALLMODE=vomus And i get stuck at maintenance dialog instead of getting normal installation. What's possibly wrong? Or maybe it is just the way that minor upgrade works? (couldn't think of the good reason) The other question is - if I get through it, will the minor upgrade override the files with new versions? I enclose a file with the source (it is a very simple and short one) http://n2.nabble.com/file/n1306236/Product.wxs Product.wxs Ian Elliott (Excell Data Corporation) wrote: Also, you listed below that the package guid didn't change for one scenario. You should always have a different package guid for every package built. My mistake of course - it was supposed to be written like you say. I did it this way, just described it wrong. -- View this message in context: http://n2.nabble.com/How-Update---Upgrade-strategy-%28small%2C-minor%2C-major%29-affect-file-overriding--tp1304357p1306236.html Sent from the wix-users mailing list archive at Nabble.com. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding?
The only way I've got this to work at the moment is by manually changing the Product Id and checking it in before doing a publish to avoid the annoying another version of this product is already installed... message. Otherwise it forces the user to uninstall the previous version before installing the new version - something that I've never had to do with any serious commercial package. Is what I'm doing wrong, and if so what alternatives do I have? You could do minor upgrades for your nightly builds - this requires passing REINSTALLMODE=vomus on the msiexec commandline, so would probably require being wrapped in a bootstrapper. Regards, John - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding?
Your command line looks wrong: msiexec /i ExampleInstaller.msi REINSTALALL=ALL REINSTALLMODE=vomus should be msiexec /i ExampleInstaller.msi REINSTALL=ALL REINSTALLMODE=vomus (However, it may be another typo.) It is expected behavior to get the maintenance dialog during a minor upgrade. Once you click Install, any newer files should be installed over the old ones. Also, you don't actually need to remove the Upgrade tag. It just doesn't get used during a minor upgrade. It is used for major upgrades. -Original Message- From: polan [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 08, 2008 3:39 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding? Thx for the answer Ian Elliott (Excell Data Corporation) wrote: For the minor upgrade and small update you don't make use of the Update tag at all. Ok - lets stick to minor upgrade. I don't insert the upgrade tag, I change the package guid, and version. I run the installation msiexec /i ExampleInstaller.msi REINSTALALL=ALL REINSTALLMODE=vomus And i get stuck at maintenance dialog instead of getting normal installation. What's possibly wrong? Or maybe it is just the way that minor upgrade works? (couldn't think of the good reason) The other question is - if I get through it, will the minor upgrade override the files with new versions? I enclose a file with the source (it is a very simple and short one) http://n2.nabble.com/file/n1306236/Product.wxs Product.wxs Ian Elliott (Excell Data Corporation) wrote: Also, you listed below that the package guid didn't change for one scenario. You should always have a different package guid for every package built. My mistake of course - it was supposed to be written like you say. I did it this way, just described it wrong. -- View this message in context: http://n2.nabble.com/How-Update---Upgrade-strategy-%28small%2C-minor%2C-major%29-affect-file-overriding--tp1304357p1306236.html Sent from the wix-users mailing list archive at Nabble.com. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding?
Ian Elliott (Excell Data Corporation) wrote: Your command line looks wrong: msiexec /i ExampleInstaller.msi REINSTALALL=ALL REINSTALLMODE=vomus should be msiexec /i ExampleInstaller.msi REINSTALL=ALL REINSTALLMODE=vomus (However, it may be another typo.) Such a stupid mistake... sorry for wasting your time and thx for pointing this. I'll test everything once again with correct command. -- View this message in context: http://n2.nabble.com/How-Update---Upgrade-strategy-%28small%2C-minor%2C-major%29-affect-file-overriding--tp1304357p1307794.html Sent from the wix-users mailing list archive at Nabble.com. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding?
I believe it is also possible to bypass the maintenance screen by simply passing /qb to misexec. This should give you a progress bar and cancel button, but that's it -- the upgrade happens with no user intervention: msiexec /i ExampleInstaller.msi /qb REINSTALL=ALL REINSTALLMODE=vomus I could be wrong, though. Ian Elliott (Excell Data Corporation) wrote: Your command line looks wrong: msiexec /i ExampleInstaller.msi REINSTALALL=ALL REINSTALLMODE=vomus should be msiexec /i ExampleInstaller.msi REINSTALL=ALL REINSTALLMODE=vomus (However, it may be another typo.) It is expected behavior to get the maintenance dialog during a minor upgrade. Once you click Install, any newer files should be installed over the old ones. Also, you don't actually need to remove the Upgrade tag. It just doesn't get used during a minor upgrade. It is used for major upgrades. -Original Message- From: polan [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 08, 2008 3:39 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding? Thx for the answer Ian Elliott (Excell Data Corporation) wrote: For the minor upgrade and small update you don't make use of the Update tag at all. Ok - lets stick to minor upgrade. I don't insert the upgrade tag, I change the package guid, and version. I run the installation msiexec /i ExampleInstaller.msi REINSTALALL=ALL REINSTALLMODE=vomus And i get stuck at maintenance dialog instead of getting normal installation. What's possibly wrong? Or maybe it is just the way that minor upgrade works? (couldn't think of the good reason) The other question is - if I get through it, will the minor upgrade override the files with new versions? I enclose a file with the source (it is a very simple and short one) http://n2.nabble.com/file/n1306236/Product.wxs Product.wxs Ian Elliott (Excell Data Corporation) wrote: Also, you listed below that the package guid didn't change for one scenario. You should always have a different package guid for every package built. My mistake of course - it was supposed to be written like you say. I did it this way, just described it wrong. -- View this message in context: http://n2.nabble.com/How-Update---Upgrade-strategy-%28small%2C-minor%2C-major%29-affect-file-overriding--tp1304357p1306236.html Sent from the wix-users mailing list archive at Nabble.com. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Teleoperate a roving mobile robot from the web: http://www.swampgas.com/robotics/rover.html - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding?
I've been trying to develop some upgrade strategy for my program.
What I want to achieve is an installer which would be able to install lets
say version 1.0.3, but also upgrade the versions 1.0.0 or 1.0.1 to version
1.0.3.
To make the things simple lets say that installing is just copying some
files and upgrading is changing the old versions of files to the new ones.
I also wouldn't like to have multiple positions in add/remove windows dialog
(just one after every update/install/upgrade).
I've read the tutorial
http://www.tramontana.co.hu/wix/lesson4.php
It gives good information about when you have to use major upgrade, but it
doesn't realy says what is the difference between the way the updates work.
It seemed that small update or minor upgrade is well enough for me.
I kept on playing with them (and with the major upgrade also when I didn't
succeed)
In the small and minor (to avoid error of already installed app) I am
starting the msi like this:
msiexec /i ExampleInstaller.msi REINSTALALL=ALL REINSTALLMODE=vomus /L*v
c:\msilog.txt
Just to make things clear:
small updates: product guid not changed, package guid not changed, version
changed
minor upgrade: product guid not changed, package guid changed, version
changed
major upgrade: product guid changed, package guid changed, version changed
In all of this I was trying to update the application without uninstalling.
First I tried without Upgrade section at all, then I added also following:
Upgrade Id={0253FF1A-030B-4646-9540-7BBF890BA52C}
UpgradeVersion OnlyDetect=yes Property='PATCHFOUND'
IncludeMinimum='yes'
Minimum='1.0.0' /
/Upgrade
The installation goes on fine and is finished, but whatever the update
strategy is, the files don't get updated.
They are all the same after the installation as before.
It changes when I use the OnlyDetect attribute set to no:
Upgrade Id={0253FF1A-030B-4646-9540-7BBF890BA52C}
UpgradeVersion OnlyDetect=no Property='PATCHFOUND'
IncludeMinimum='yes' Minimum='1.0.0' /
/Upgrade
Then the previous installation gets uninstalled and the files are fresh.
But as I understood it is not needed to uninstall old version to change some
files.
How does it work finally? I couldn't find any specific information about
this in wix docu or on google.
Sorry for the long introduction...
These are my questions (I'll be grateful for the answer or pointing to some
documentation)
How does the installation strategy (small, minor, major) affect replacing
changed files?
When does the new position in the add/remove windows dialog is created and
when it is not?
I use the newest version of wix 3 and votive.
I generated initially the fragment with components using heat, and it stays
the same in every next version of installer
(the guids are not being changed). This is a sample of component that does
not get overriden:
Component Id=MyApp.exe Guid={F51AFCCC-97E0-4610-AB91-77A35C1DFF70}
File Id=MyApp.exe Name=MyApp.exe KeyPath=yes
Source=$(var.MyProject.TargetDir)MyApp.exe /
/Component
cheers
Przemek
--
View this message in context:
http://n2.nabble.com/How-Update---Upgrade-strategy-%28small%2C-minor%2C-major%29-affect-file-overriding--tp1304357p1304357.html
Sent from the wix-users mailing list archive at Nabble.com.
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding?
If you use the Upgrade tag, you are doing a major upgrade. In this case, the
old version is removed and the new version is installed. If the files change
between the versions then you will get the latest versions after the upgrade.
Setting the OnlyDetect parameter to yes means that you just want to detect an
older version and not actually upgrade it. Once you set it to no, the
expected behavior of updating took place. Any files with newer versions, etc,
will be replaced.
There is some very good info on Major Upgrades here:
http://blogs.technet.com/alexshev/archive/2008/02/15/from-msi-to-wix-part-8-major-upgrade.aspx
For the minor upgrade and small update you don't make use of the Update tag at
all.
Also, you listed below that the package guid didn't change for one scenario.
You should always have a different package guid for every package built.
-Original Message-
From: polan [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 07, 2008 11:17 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect
file overriding?
I've been trying to develop some upgrade strategy for my program.
What I want to achieve is an installer which would be able to install lets
say version 1.0.3, but also upgrade the versions 1.0.0 or 1.0.1 to version
1.0.3.
To make the things simple lets say that installing is just copying some
files and upgrading is changing the old versions of files to the new ones.
I also wouldn't like to have multiple positions in add/remove windows dialog
(just one after every update/install/upgrade).
I've read the tutorial
http://www.tramontana.co.hu/wix/lesson4.php
It gives good information about when you have to use major upgrade, but it
doesn't realy says what is the difference between the way the updates work.
It seemed that small update or minor upgrade is well enough for me.
I kept on playing with them (and with the major upgrade also when I didn't
succeed)
In the small and minor (to avoid error of already installed app) I am
starting the msi like this:
msiexec /i ExampleInstaller.msi REINSTALALL=ALL REINSTALLMODE=vomus /L*v
c:\msilog.txt
Just to make things clear:
small updates: product guid not changed, package guid not changed, version
changed
minor upgrade: product guid not changed, package guid changed, version
changed
major upgrade: product guid changed, package guid changed, version changed
In all of this I was trying to update the application without uninstalling.
First I tried without Upgrade section at all, then I added also following:
Upgrade Id={0253FF1A-030B-4646-9540-7BBF890BA52C}
UpgradeVersion OnlyDetect=yes Property='PATCHFOUND'
IncludeMinimum='yes'
Minimum='1.0.0' /
/Upgrade
The installation goes on fine and is finished, but whatever the update
strategy is, the files don't get updated.
They are all the same after the installation as before.
It changes when I use the OnlyDetect attribute set to no:
Upgrade Id={0253FF1A-030B-4646-9540-7BBF890BA52C}
UpgradeVersion OnlyDetect=no Property='PATCHFOUND'
IncludeMinimum='yes' Minimum='1.0.0' /
/Upgrade
Then the previous installation gets uninstalled and the files are fresh.
But as I understood it is not needed to uninstall old version to change some
files.
How does it work finally? I couldn't find any specific information about
this in wix docu or on google.
Sorry for the long introduction...
These are my questions (I'll be grateful for the answer or pointing to some
documentation)
How does the installation strategy (small, minor, major) affect replacing
changed files?
When does the new position in the add/remove windows dialog is created and
when it is not?
I use the newest version of wix 3 and votive.
I generated initially the fragment with components using heat, and it stays
the same in every next version of installer
(the guids are not being changed). This is a sample of component that does
not get overriden:
Component Id=MyApp.exe Guid={F51AFCCC-97E0-4610-AB91-77A35C1DFF70}
File Id=MyApp.exe Name=MyApp.exe KeyPath=yes
Source=$(var.MyProject.TargetDir)MyApp.exe /
/Component
cheers
Przemek
--
View this message in context:
http://n2.nabble.com/How-Update---Upgrade-strategy-%28small%2C-minor%2C-major%29-affect-file-overriding--tp1304357p1304357.html
Sent from the wix-users mailing list archive at Nabble.com.
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
This SF.Net email
