Re: [WiX-users] Uninstall an installed product.
In the integration with WiX and Visual Studio I notice that a file with the extension .wixpdb is created. The documentation at http://wix.sourceforge.net/manual-wix3/files.htm indicates that this file is A .wixpdb file is created by the linker for each final output. It contains the debugging information.. How is this file used? Or for now should I just ignore it? Kevin -- What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Uninstall an installed product.
The ICE61 message is pretty clear to me.
This product should remove only older versions of itself. The Maximum version
is not less than the current product.
UpgradeVersion/@Maximum *must* be less than Product/@Version.
Notice I said less than and *not* less than or equal. This is very
important.
You could set UpgradeVersion/@Maximum = Product/@Version _if and only if_
UpgradeVersion/@IncludeMaximum = no.
Of course, the MajorUpgrade element handles all this for you very well.
Product ... Version=2.10 ... UpgradeCode=...
Package ... /
MajorUpgrade DowngradeErrorMessage=A later version of [ProductName] is
already installed. Setup will now exit. /
...
/Product
Can't really get much easier than that.
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
Please consider the environment before printing this e-mail
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Wednesday, March 02, 2011 6:23 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
I am sorry but now I am getting:
\Product.wxs(16,0): warning LGHT1076: ICE61: This product should remove
only older versions of itself. The Maximum version is not less than the
current product. (2.1.0 2.1.0)
\Product.wxs(21,0): warning LGHT1076: ICE61: This product should remove
only older versions of itself. The Maximum version is not less than the
current product. (3.0.0 2.1.0)
The wxs code is:
Product Version=2.1.0
UpgradeCode=529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B
Upgrade Id=529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B
UpgradeVersion OnlyDetect='no' Property='PREVIOUSFOUND'
Minimum='1.0.0' IncludeMinimum='yes'
Maximum='3.0.0' IncludeMaximum='no' /
/Upgrade
What is this telling me?
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Wednesday, March 02, 2011 4:00 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
The Product/@Id is of type AutogenGuid according to
http://wix.sourceforge.net/manual-wix3/wix_xsd_product.htm. The
AutogenGuid description says:
Values of this type will look like: 01234567-89AB-CDEF-0123-456789ABCDEF
or {01234567-89AB-CDEF-0123-456789ABCDEF}. A GUID can be auto-
generated by setting the value to *. Also allows PUT-GUID-HERE for use
in examples.
Package/@Id is also of type AutogenGuid according to
http://wix.sourceforge.net/manual-wix3/wix_xsd_package.htm.
The compiler becomes responsible for generating a new GUID on each build.
Windows Installer requires that each and every package has a different
Package/@Id. Explicitly setting Package/@Id to * is the same functionality
as just not specifying the attribute at all as it is not required. As the
compiler
generates a new GUID on each build we meet the requirements set by
Windows Installer.
As mentioned earlier, Windows Installer defines a major upgrade as a
package that has a different Package/@Id (by definition), a different
Product/@Id, a different Product/@Version, and the SAME
Product/@UpgradeCode as a currently installed product. The
Product/@UpgradeCode is what ties together products that belong to the
same product family.
The Upgrade table is used to detect previously installed products that should
be upgraded and schedules them to be uninstalled. The MajorUpgrade
element makes it really easy to author the Upgrade table correctly. See
http://wix.sourceforge.net/manual-wix3/wix_xsd_majorupgrade.htm.
If you always want to generate major upgrades then you'll want to do the
following:
* Use the MajorUpgrade element.
* Set Product/@Id to *.
* Do not set Package/@Id as the default value results in the correct behavior.
* Guarantee that your build process results in a different Product/@Version
on every build.
* Do NOT change Product/@UpgradeCode between builds.
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail
-Original Message-
From: Chris Lord [mailto:chris.l...@atterotech.com]
Sent: Wednesday, March 02, 2011 1:29 PM
To: wix-users
Subject: Re: [WiX-users] Uninstall an installed product.
Kevin
You dont need to change it. Setting the package ID to * ensures the
package in your installer is automatically regenerated with a new GUID
each time you build it. This means when uninstalling, the MSI wont be
confused by identical package GUID's.
For each version you release, assuming you are doing major upgrades,
the Product GUID and Package GUID must change BUT the Upgrade GUID
must remain the same for EVERY version of that product.
Chris
Re: [WiX-users] Uninstall an installed product.
The message is clear to you but you are the expert. I doesn't make sense to me.
Let me just try to explain my thought process and you can tell me where I am
misunderstanding. As can be seen from the WiX code below, the version that I am
trying to set my product to is 2.1. The minimum and maximum versions are
minimum of 1.0 and maximum of 3.0. 2.1 seems to fall between these so it is
valid. Older versions of the product would be less than 2.1 (which I am
declaring as the current version)). My thinking is older versions (less or
equal to 2.1) should be removed to make way for the new. This is what I want.
In order to achieve this I set the Upgrade Minimum to be 1.0 and set
IncludeMinimum to 'yes' so that versions less than or equal to the minimum will
be removed (any version that is less than or equal to the current version). As
I understood the 'Maximum' it said that maximum version was 3.0 and if the
product version was greater than the current version but less than the maximum
it was considered a downgrade (again IncludeMaximum is 'no' so it is greater
than the current version and less than the maximum). So when I release a new
version and bump the version number to 2.2 it is still greater than the minimum
and less than the maximum.
Right?
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Thursday, March 03, 2011 12:14 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
The ICE61 message is pretty clear to me.
This product should remove only older versions of itself. The Maximum version
is not less than the current product.
UpgradeVersion/@Maximum *must* be less than Product/@Version.
Notice I said less than and *not* less than or equal. This is very
important.
You could set UpgradeVersion/@Maximum = Product/@Version _if and only if_
UpgradeVersion/@IncludeMaximum = no.
Of course, the MajorUpgrade element handles all this for you very well.
Product ... Version=2.10 ... UpgradeCode=...
Package ... /
MajorUpgrade DowngradeErrorMessage=A later version of [ProductName] is
already installed. Setup will now exit. /
...
/Product
Can't really get much easier than that.
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Wednesday, March 02, 2011 6:23 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
I am sorry but now I am getting:
\Product.wxs(16,0): warning LGHT1076: ICE61: This product should
remove only older versions of itself. The Maximum version is not less
than the current product. (2.1.0 2.1.0)
\Product.wxs(21,0): warning LGHT1076: ICE61: This product should
remove only older versions of itself. The Maximum version is not less
than the current product. (3.0.0 2.1.0)
The wxs code is:
Product Version=2.1.0
UpgradeCode=529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B
Upgrade Id=529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B
UpgradeVersion OnlyDetect='no' Property='PREVIOUSFOUND'
Minimum='1.0.0' IncludeMinimum='yes'
Maximum='3.0.0' IncludeMaximum='no' /
/Upgrade
What is this telling me?
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Wednesday, March 02, 2011 4:00 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
The Product/@Id is of type AutogenGuid according to
http://wix.sourceforge.net/manual-wix3/wix_xsd_product.htm. The
AutogenGuid description says:
Values of this type will look like: 01234567-89AB-CDEF-0123-456789ABCDEF
or {01234567-89AB-CDEF-0123-456789ABCDEF}. A GUID can be auto-
generated by setting the value to *. Also allows PUT-GUID-HERE for
use in examples.
Package/@Id is also of type AutogenGuid according to
http://wix.sourceforge.net/manual-wix3/wix_xsd_package.htm.
The compiler becomes responsible for generating a new GUID on each build.
Windows Installer requires that each and every package has a different
Package/@Id. Explicitly setting Package/@Id to * is the same
functionality as just not specifying the attribute at all as it is not
required. As the compiler generates a new GUID on each build we meet
the requirements set by Windows Installer.
As mentioned earlier, Windows Installer defines a major upgrade as a
package that has a different Package/@Id (by definition), a different
Product/@Id, a different Product/@Version, and the SAME
Product/@UpgradeCode as a currently installed product. The
Product/@UpgradeCode is what ties together products that belong to the
same product family.
The Upgrade table is used
Re: [WiX-users] Uninstall an installed product.
Can you reference any source that justifies your thinking? If you can't then you are only guessing and have not performed the appropriate level of due diligence I would expect from any responsible engineer. Upgrade Table - http://msdn.microsoft.com/en-us/library/aa372379.aspx Upgrade Element - http://wix.sourceforge.net/manual-wix3/wix_xsd_upgrade.htm UpgradeVersion Element - http://wix.sourceforge.net/manual-wix3/wix_xsd_upgradeversion.htm None of those references mention anything about downgrades. Those references do mention multiple times product versions detected by FindRelatedProducts. FindRelatedProducts Action - http://msdn.microsoft.com/en-us/library/aa368600.aspx The FindRelatedProducts action runs through each record of the Upgrade table in sequence and compares the upgrade code, product version, and language in each row to products installed on the system. When FindRelatedProducts detects a correspondence between the upgrade information and an installed product, it appends the product code to the property specified in the ActionProperty column of the UpgradeTable. The property specified in the UpgradeVersion/@Property gets set when products matching the conditions expressed by the UpgradeVersion element are met. The ICE61 message is telling you what you need to do. If the ICE61 message does not match your expectations then I would trust the ICE61 message and do what it's telling you to do because it is trying to steer you into a correct implementation. The FindRelatedProducts action is responsible for finding installed products matching the conditions specified by the Upgrade table setting one or more properties when it finds matching installed products. You need to schedule FindRelatedProducts for this search to occur otherwise nothing happens. FindRelatedProducts will not uninstall any installed products it finds. That is the job of the RemoveExistingProducts action. To detect products that you want to upgrade you need to specify the minimum and maximum versions you want to detect. You do not want to detect the version of the current product because you don't want to upgrade yourself. To detect newer products you'll need to have a second UpgradeVersion element with a minimum version equal to your current version. This second UpgradeVersion element will set a second property so you can determine that a newer version is installed. Here's some more information that my research assistant (Google) found for me: How To: Implement a Major Upgrade In Your Installer - http://wix.sourceforge.net/manual-wix3/major_upgrade.htm WiX Script for Major Upgrades - http://neilsleightholm.blogspot.com/2009/01/wix-script-for-major-upgrades.html Major Upgrades Now Easier Than Ever - http://www.joyofsetup.com/2010/01/16/major-upgrades-now-easier-than-ever/ I don't mind providing help but I get quite irritated when I'm translating error and warning messages that are extremely clear. That tells me that the other party is just not trying very hard to learn the domain or the tools. Windows Installer is horribly complex and I understand that... but there is actually a good amount of information out there if you just try to look for it. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Thursday, March 03, 2011 11:11 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. The message is clear to you but you are the expert. I doesn't make sense to me. Let me just try to explain my thought process and you can tell me where I am misunderstanding. As can be seen from the WiX code below, the version that I am trying to set my product to is 2.1. The minimum and maximum versions are minimum of 1.0 and maximum of 3.0. 2.1 seems to fall between these so it is valid. Older versions of the product would be less than 2.1 (which I am declaring as the current version)). My thinking is older versions (less or equal to 2.1) should be removed to make way for the new. This is what I want. In order to achieve this I set the Upgrade Minimum to be 1.0 and set IncludeMinimum to 'yes' so that versions less than or equal to the minimum will be removed (any version that is less than or equal to the current version). As I understood the 'Maximum' it said that maximum version was 3.0 and if the product version was greater than the current version but less than the maximum it was considered a downgrade (again IncludeMaximum is 'no' so it is greater than the current version and less than the maximum). So when I release a new version and bump the version number to 2.2 it is still greater than the minimum and less than the maximum. Right? -Original Message- From: Castro, Edwin G
Re: [WiX-users] Uninstall an installed product.
Sorry I was looking at http://www.tramontana.co.hu/wix/lesson4.php#4.2 Some quotes, Minimum and Maximum specify the range of versions we are supposed to update with this upgrade. IncludeMaximum and IncludeMinimum specify whether the bound value is actually included in the range or not. This is where I had the idea that the version specified in the product element had to be in between the Minimum and Maximum. If our intention is a major upgrade, that is, complete and automatic removal of the previous version when a new one arrives, we just need to set OnlyDetect to no and to set the version numbers accordingly. Minimum will then specify the first version we allow to replace with the current one (and we include this minimum version in the range) while Maximum can be set to the current version number (but not included in the range). Then, any version between the first and the previous one before the current version will be removed automatically during the installation of the current version. 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. This is where I got the idea that the removed versions are from the Minimum to the current (nothing is mentioned about Maximum being less than current). The downgrade idea came as a result of various emails exchanged and the fact that if the version installed is greater than the current version that is replacing it this is by definition a downgrade. Is this out of date? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Thursday, March 03, 2011 1:54 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Can you reference any source that justifies your thinking? If you can't then you are only guessing and have not performed the appropriate level of due diligence I would expect from any responsible engineer. Upgrade Table - http://msdn.microsoft.com/en-us/library/aa372379.aspx Upgrade Element - http://wix.sourceforge.net/manual-wix3/wix_xsd_upgrade.htm UpgradeVersion Element - http://wix.sourceforge.net/manual-wix3/wix_xsd_upgradeversion.htm None of those references mention anything about downgrades. Those references do mention multiple times product versions detected by FindRelatedProducts. FindRelatedProducts Action - http://msdn.microsoft.com/en-us/library/aa368600.aspx The FindRelatedProducts action runs through each record of the Upgrade table in sequence and compares the upgrade code, product version, and language in each row to products installed on the system. When FindRelatedProducts detects a correspondence between the upgrade information and an installed product, it appends the product code to the property specified in the ActionProperty column of the UpgradeTable. The property specified in the UpgradeVersion/@Property gets set when products matching the conditions expressed by the UpgradeVersion element are met. The ICE61 message is telling you what you need to do. If the ICE61 message does not match your expectations then I would trust the ICE61 message and do what it's telling you to do because it is trying to steer you into a correct implementation. The FindRelatedProducts action is responsible for finding installed products matching the conditions specified by the Upgrade table setting one or more properties when it finds matching installed products. You need to schedule FindRelatedProducts for this search to occur otherwise nothing happens. FindRelatedProducts will not uninstall any installed products it finds. That is the job of the RemoveExistingProducts action. To detect products that you want to upgrade you need to specify the minimum and maximum versions you want to detect. You do not want to detect the version of the current product because you don't want to upgrade yourself. To detect newer products you'll need to have a second UpgradeVersion element with a minimum version equal to your current version. This second UpgradeVersion element will set a second property so you can determine that a newer version is installed. Here's some more information that my research assistant (Google) found for me: How To: Implement a Major Upgrade In Your Installer - http://wix.sourceforge.net/manual-wix3/major_upgrade.htm WiX Script for Major Upgrades - http://neilsleightholm.blogspot.com/2009/01/wix-script-for-major-upgrades.html Major Upgrades Now Easier Than Ever - http://www.joyofsetup.com/2010/01/16/major-upgrades-now-easier-than-ever/ I don't mind providing help but I get quite irritated when I'm translating error
Re: [WiX-users] Uninstall an installed product.
I am sorry you feel you are translating error messages but the message is not clear in telling me what to do. I reiterate: \Product.wxs(16,0): warning LGHT1076: ICE61: This product should remove only older versions of itself. The Maximum version is not less than the current product. (2.1.0 2.1.0) \Product.wxs(21,0): warning LGHT1076: ICE61: This product should remove only older versions of itself. The Maximum version is not less than the current product. (3.0.0 2.1.0) First the statement, this product should remove only older versions of itself.. I agree with that. Why is it a warning? Then it says, The Maximum version is not less than the current product. This is also true but I am not sure why it is a warning. Why are there two warning messages? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Thursday, March 03, 2011 1:54 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Can you reference any source that justifies your thinking? If you can't then you are only guessing and have not performed the appropriate level of due diligence I would expect from any responsible engineer. Upgrade Table - http://msdn.microsoft.com/en-us/library/aa372379.aspx Upgrade Element - http://wix.sourceforge.net/manual-wix3/wix_xsd_upgrade.htm UpgradeVersion Element - http://wix.sourceforge.net/manual-wix3/wix_xsd_upgradeversion.htm None of those references mention anything about downgrades. Those references do mention multiple times product versions detected by FindRelatedProducts. FindRelatedProducts Action - http://msdn.microsoft.com/en-us/library/aa368600.aspx The FindRelatedProducts action runs through each record of the Upgrade table in sequence and compares the upgrade code, product version, and language in each row to products installed on the system. When FindRelatedProducts detects a correspondence between the upgrade information and an installed product, it appends the product code to the property specified in the ActionProperty column of the UpgradeTable. The property specified in the UpgradeVersion/@Property gets set when products matching the conditions expressed by the UpgradeVersion element are met. The ICE61 message is telling you what you need to do. If the ICE61 message does not match your expectations then I would trust the ICE61 message and do what it's telling you to do because it is trying to steer you into a correct implementation. The FindRelatedProducts action is responsible for finding installed products matching the conditions specified by the Upgrade table setting one or more properties when it finds matching installed products. You need to schedule FindRelatedProducts for this search to occur otherwise nothing happens. FindRelatedProducts will not uninstall any installed products it finds. That is the job of the RemoveExistingProducts action. To detect products that you want to upgrade you need to specify the minimum and maximum versions you want to detect. You do not want to detect the version of the current product because you don't want to upgrade yourself. To detect newer products you'll need to have a second UpgradeVersion element with a minimum version equal to your current version. This second UpgradeVersion element will set a second property so you can determine that a newer version is installed. Here's some more information that my research assistant (Google) found for me: How To: Implement a Major Upgrade In Your Installer - http://wix.sourceforge.net/manual-wix3/major_upgrade.htm WiX Script for Major Upgrades - http://neilsleightholm.blogspot.com/2009/01/wix-script-for-major-upgrades.html Major Upgrades Now Easier Than Ever - http://www.joyofsetup.com/2010/01/16/major-upgrades-now-easier-than-ever/ I don't mind providing help but I get quite irritated when I'm translating error and warning messages that are extremely clear. That tells me that the other party is just not trying very hard to learn the domain or the tools. Windows Installer is horribly complex and I understand that... but there is actually a good amount of information out there if you just try to look for it. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Thursday, March 03, 2011 11:11 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. The message is clear to you but you are the expert. I doesn't make sense to me. Let me just try to explain my thought process and you can tell me where I am misunderstanding. As can be seen from
Re: [WiX-users] Uninstall an installed product.
Courtesy of Google: ICE61 - http://msdn.microsoft.com/en-us/library/aa369005.aspx The message clearly tells you to make Maximum less than the current product version. You say you understand that. Fix it. Your email essentially said here are some warnings... what do I do... To that I say read the warnings and do what they tell you to make them go away. You want to understand why Maximum needs to be less than the current product version. That is different than what do I do to make the messages go away. I've already provided a bunch of information so I'll let you learn on your own. I hate to say it but RTFM. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Thursday, March 03, 2011 1:23 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. I am sorry you feel you are translating error messages but the message is not clear in telling me what to do. I reiterate: \Product.wxs(16,0): warning LGHT1076: ICE61: This product should remove only older versions of itself. The Maximum version is not less than the current product. (2.1.0 2.1.0) \Product.wxs(21,0): warning LGHT1076: ICE61: This product should remove only older versions of itself. The Maximum version is not less than the current product. (3.0.0 2.1.0) First the statement, this product should remove only older versions of itself.. I agree with that. Why is it a warning? Then it says, The Maximum version is not less than the current product. This is also true but I am not sure why it is a warning. Why are there two warning messages? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Thursday, March 03, 2011 1:54 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Can you reference any source that justifies your thinking? If you can't then you are only guessing and have not performed the appropriate level of due diligence I would expect from any responsible engineer. Upgrade Table - http://msdn.microsoft.com/en-us/library/aa372379.aspx Upgrade Element - http://wix.sourceforge.net/manual- wix3/wix_xsd_upgrade.htm UpgradeVersion Element - http://wix.sourceforge.net/manual- wix3/wix_xsd_upgradeversion.htm None of those references mention anything about downgrades. Those references do mention multiple times product versions detected by FindRelatedProducts. FindRelatedProducts Action - http://msdn.microsoft.com/en- us/library/aa368600.aspx The FindRelatedProducts action runs through each record of the Upgrade table in sequence and compares the upgrade code, product version, and language in each row to products installed on the system. When FindRelatedProducts detects a correspondence between the upgrade information and an installed product, it appends the product code to the property specified in the ActionProperty column of the UpgradeTable. The property specified in the UpgradeVersion/@Property gets set when products matching the conditions expressed by the UpgradeVersion element are met. The ICE61 message is telling you what you need to do. If the ICE61 message does not match your expectations then I would trust the ICE61 message and do what it's telling you to do because it is trying to steer you into a correct implementation. The FindRelatedProducts action is responsible for finding installed products matching the conditions specified by the Upgrade table setting one or more properties when it finds matching installed products. You need to schedule FindRelatedProducts for this search to occur otherwise nothing happens. FindRelatedProducts will not uninstall any installed products it finds. That is the job of the RemoveExistingProducts action. To detect products that you want to upgrade you need to specify the minimum and maximum versions you want to detect. You do not want to detect the version of the current product because you don't want to upgrade yourself. To detect newer products you'll need to have a second UpgradeVersion element with a minimum version equal to your current version. This second UpgradeVersion element will set a second property so you can determine that a newer version is installed. Here's some more information that my research assistant (Google) found for me: How To: Implement a Major Upgrade In Your Installer - http://wix.sourceforge.net/manual-wix3/major_upgrade.htm WiX Script for Major Upgrades - http://neilsleightholm.blogspot.com/2009/01/wix-script-for-major- upgrades.html Major Upgrades Now Easier Than
Re: [WiX-users] Uninstall an installed product.
Minimum and Maximum specify the range of versions we are supposed to update with this upgrade. Why would Maximum be greater than the current product version? Anything larger than the current version would make the current version obsolete and thus we don't want to upgrade. I'm going to ignore the other stuff about downgrades... I don't have experience to measure how safe and/or complex they are. I generally disallow downgrades, in other words, I use UpgradeVersion to detect a downgrade situation and use a LaunchCondition to prohibit installation. Or more accurately, I let the MajorUpgrade element do it for me since it does a great job in this regard. Use the MajorUpgrade element and let it get it right! Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Thursday, March 03, 2011 1:16 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Sorry I was looking at http://www.tramontana.co.hu/wix/lesson4.php#4.2 Some quotes, Minimum and Maximum specify the range of versions we are supposed to update with this upgrade. IncludeMaximum and IncludeMinimum specify whether the bound value is actually included in the range or not. This is where I had the idea that the version specified in the product element had to be in between the Minimum and Maximum. If our intention is a major upgrade, that is, complete and automatic removal of the previous version when a new one arrives, we just need to set OnlyDetect to no and to set the version numbers accordingly. Minimum will then specify the first version we allow to replace with the current one (and we include this minimum version in the range) while Maximum can be set to the current version number (but not included in the range). Then, any version between the first and the previous one before the current version will be removed automatically during the installation of the current version. 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. This is where I got the idea that the removed versions are from the Minimum to the current (nothing is mentioned about Maximum being less than current). The downgrade idea came as a result of various emails exchanged and the fact that if the version installed is greater than the current version that is replacing it this is by definition a downgrade. Is this out of date? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Thursday, March 03, 2011 1:54 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Can you reference any source that justifies your thinking? If you can't then you are only guessing and have not performed the appropriate level of due diligence I would expect from any responsible engineer. Upgrade Table - http://msdn.microsoft.com/en-us/library/aa372379.aspx Upgrade Element - http://wix.sourceforge.net/manual- wix3/wix_xsd_upgrade.htm UpgradeVersion Element - http://wix.sourceforge.net/manual- wix3/wix_xsd_upgradeversion.htm None of those references mention anything about downgrades. Those references do mention multiple times product versions detected by FindRelatedProducts. FindRelatedProducts Action - http://msdn.microsoft.com/en- us/library/aa368600.aspx The FindRelatedProducts action runs through each record of the Upgrade table in sequence and compares the upgrade code, product version, and language in each row to products installed on the system. When FindRelatedProducts detects a correspondence between the upgrade information and an installed product, it appends the product code to the property specified in the ActionProperty column of the UpgradeTable. The property specified in the UpgradeVersion/@Property gets set when products matching the conditions expressed by the UpgradeVersion element are met. The ICE61 message is telling you what you need to do. If the ICE61 message does not match your expectations then I would trust the ICE61 message and do what it's telling you to do because it is trying to steer you into a correct implementation. The FindRelatedProducts action is responsible for finding installed products matching the conditions specified by the Upgrade table setting one or more properties when it finds matching installed products. You
Re: [WiX-users] Uninstall an installed product.
Again I am just reading the tutorial the only explanation that I came up with to reconcile what I was reading with the arguments for the element was the concept of downgrade. I also would like to disallow downgrades. So since I am a little slow. If I always want to do a major upgrade then with each build I change the version on the product element AND also change Maximum on the upgrade element to be less than the current version? Right? So the code would look like: Product Version=2.1.0 UpgradeCode=529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B Upgrade Id=529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B UpgradeVersion OnlyDetect='no' Property='PREVIOUSFOUND' Minimum='1.0.0' IncludeMinimum='no' Maximum='2.1.0' IncludeMaximum='yes' / /Upgrade Do I finally have it? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Thursday, March 03, 2011 3:44 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Minimum and Maximum specify the range of versions we are supposed to update with this upgrade. Why would Maximum be greater than the current product version? Anything larger than the current version would make the current version obsolete and thus we don't want to upgrade. I'm going to ignore the other stuff about downgrades... I don't have experience to measure how safe and/or complex they are. I generally disallow downgrades, in other words, I use UpgradeVersion to detect a downgrade situation and use a LaunchCondition to prohibit installation. Or more accurately, I let the MajorUpgrade element do it for me since it does a great job in this regard. Use the MajorUpgrade element and let it get it right! Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Thursday, March 03, 2011 1:16 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Sorry I was looking at http://www.tramontana.co.hu/wix/lesson4.php#4.2 Some quotes, Minimum and Maximum specify the range of versions we are supposed to update with this upgrade. IncludeMaximum and IncludeMinimum specify whether the bound value is actually included in the range or not. This is where I had the idea that the version specified in the product element had to be in between the Minimum and Maximum. If our intention is a major upgrade, that is, complete and automatic removal of the previous version when a new one arrives, we just need to set OnlyDetect to no and to set the version numbers accordingly. Minimum will then specify the first version we allow to replace with the current one (and we include this minimum version in the range) while Maximum can be set to the current version number (but not included in the range). Then, any version between the first and the previous one before the current version will be removed automatically during the installation of the current version. 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. This is where I got the idea that the removed versions are from the Minimum to the current (nothing is mentioned about Maximum being less than current). The downgrade idea came as a result of various emails exchanged and the fact that if the version installed is greater than the current version that is replacing it this is by definition a downgrade. Is this out of date? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Thursday, March 03, 2011 1:54 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Can you reference any source that justifies your thinking? If you can't then you are only guessing and have not performed the appropriate level of due diligence I would expect from any responsible engineer. Upgrade Table - http://msdn.microsoft.com/en-us/library/aa372379.aspx Upgrade Element - http://wix.sourceforge.net/manual- wix3/wix_xsd_upgrade.htm UpgradeVersion Element - http://wix.sourceforge.net/manual- wix3/wix_xsd_upgradeversion.htm None of those references mention anything about downgrades. Those
Re: [WiX-users] Uninstall an installed product.
Thank you. To avoid changing the version to different values in two different places, is the some way to set the 'Maximum' to the equivalent of current version - 1 so it will always work? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Thursday, March 03, 2011 4:39 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Almost. You want: UpgradeVersion/@IncludeMinimum=yes UpgradeVersion/@IncludeMaximum=no Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Thursday, March 03, 2011 2:23 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Again I am just reading the tutorial the only explanation that I came up with to reconcile what I was reading with the arguments for the element was the concept of downgrade. I also would like to disallow downgrades. So since I am a little slow. If I always want to do a major upgrade then with each build I change the version on the product element AND also change Maximum on the upgrade element to be less than the current version? Right? So the code would look like: Product Version=2.1.0 UpgradeCode=529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B Upgrade Id=529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B UpgradeVersion OnlyDetect='no' Property='PREVIOUSFOUND' Minimum='1.0.0' IncludeMinimum='no' Maximum='2.1.0' IncludeMaximum='yes' / /Upgrade Do I finally have it? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Thursday, March 03, 2011 3:44 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Minimum and Maximum specify the range of versions we are supposed to update with this upgrade. Why would Maximum be greater than the current product version? Anything larger than the current version would make the current version obsolete and thus we don't want to upgrade. I'm going to ignore the other stuff about downgrades... I don't have experience to measure how safe and/or complex they are. I generally disallow downgrades, in other words, I use UpgradeVersion to detect a downgrade situation and use a LaunchCondition to prohibit installation. Or more accurately, I let the MajorUpgrade element do it for me since it does a great job in this regard. Use the MajorUpgrade element and let it get it right! Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Thursday, March 03, 2011 1:16 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Sorry I was looking at http://www.tramontana.co.hu/wix/lesson4.php#4.2 Some quotes, Minimum and Maximum specify the range of versions we are supposed to update with this upgrade. IncludeMaximum and IncludeMinimum specify whether the bound value is actually included in the range or not. This is where I had the idea that the version specified in the product element had to be in between the Minimum and Maximum. If our intention is a major upgrade, that is, complete and automatic removal of the previous version when a new one arrives, we just need to set OnlyDetect to no and to set the version numbers accordingly. Minimum will then specify the first version we allow to replace with the current one (and we include this minimum version in the range) while Maximum can be set to the current version number (but not included in the range). Then, any version between the first and the previous one before the current version will be removed automatically during the installation of the current version. 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. This is where I got the idea that the removed versions are from the Minimum to the current (nothing is mentioned about Maximum
Re: [WiX-users] Uninstall an installed product.
Now the code looks like: Product ... Id=* UpgradeCode=529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B Package... / MajorUpgrade AllowDowngrades=no AllowSameVersionUpgrades=yes DowngradeErrorMessage=Downgrading the brain Schedule=afterInstallInitialize/ Upgrade Id=529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B UpgradeVersion OnlyDetect='no' Property='PREVIOUSFOUND' Minimum='1.0.0' IncludeMinimum='no' Maximum='2.0.9' IncludeMaximum='yes' / /Upgrade So 2.0.9 is less than 2.1 now I get only one ICE warning C:\... \Product.wxs(16,0): warning LGHT1076: ICE61: This product should remove only older versions of itself. The Maximum version is not less than the current product. (2.1.0 2.1.0) It looks like it thinks the Maximum is 2.1 when as you can see the Maximum is 2.0.9. -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Thursday, March 03, 2011 4:39 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Almost. You want: UpgradeVersion/@IncludeMinimum=yes UpgradeVersion/@IncludeMaximum=no Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Thursday, March 03, 2011 2:23 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Again I am just reading the tutorial the only explanation that I came up with to reconcile what I was reading with the arguments for the element was the concept of downgrade. I also would like to disallow downgrades. So since I am a little slow. If I always want to do a major upgrade then with each build I change the version on the product element AND also change Maximum on the upgrade element to be less than the current version? Right? So the code would look like: Product Version=2.1.0 UpgradeCode=529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B Upgrade Id=529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B UpgradeVersion OnlyDetect='no' Property='PREVIOUSFOUND' Minimum='1.0.0' IncludeMinimum='no' Maximum='2.1.0' IncludeMaximum='yes' / /Upgrade Do I finally have it? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Thursday, March 03, 2011 3:44 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Minimum and Maximum specify the range of versions we are supposed to update with this upgrade. Why would Maximum be greater than the current product version? Anything larger than the current version would make the current version obsolete and thus we don't want to upgrade. I'm going to ignore the other stuff about downgrades... I don't have experience to measure how safe and/or complex they are. I generally disallow downgrades, in other words, I use UpgradeVersion to detect a downgrade situation and use a LaunchCondition to prohibit installation. Or more accurately, I let the MajorUpgrade element do it for me since it does a great job in this regard. Use the MajorUpgrade element and let it get it right! Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Thursday, March 03, 2011 1:16 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Sorry I was looking at http://www.tramontana.co.hu/wix/lesson4.php#4.2 Some quotes, Minimum and Maximum specify the range of versions we are supposed to update with this upgrade. IncludeMaximum and IncludeMinimum specify whether the bound value is actually included in the range or not. This is where I had the idea that the version specified in the product element had to be in between the Minimum and Maximum. If our intention is a major upgrade, that is, complete and automatic removal of the previous version when a new one arrives, we just need to set OnlyDetect to no and to set the version numbers accordingly. Minimum will then specify the first version we allow to replace with the current one (and we include this minimum version in the range) while Maximum can be set to the current version number (but not included in the range). Then, any version between
Re: [WiX-users] Uninstall an installed product.
Thank you that sounds much easier. Now I have: Product ... Id=* Version=2.1.0 UpgradeCode=529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B Package / MajorUpgrade AllowDowngrades=no AllowSameVersionUpgrades=yes DowngradeErrorMessage=A later version of [ProductName] is already installed. Schedule=afterInstallInitialize/ But I still get the message: C:\...\Product.wxs(16,0): warning LGHT1076: ICE61: This product should remove only older versions of itself. The Maximum version is not less than the current product. (2.1.0 2.1.0) I am not sure where it is picking up Maximum from. I tried changing the version to make sure I was using the right .wxs file and then the error message is the same but with 2.2.0 substituted for the version so changes in this .wxs are reflected in the error messages. -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Thursday, March 03, 2011 5:51 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. You do not want to include your own Upgrade element (and UpgradeVersion element) if you are using the MajorUpgrade element. The MajorUpgrade element takes care of authoring the Upgrade table for you. Product Id=* UpgradeCode=529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B ... Package ... / MajorUpgrade ... / !-- Upgrade and UpgradeVersion elements no longer needed -- ... /Product I also want to make another comment. 2.0.9 is indeed less than 2.1.0. 2.0.10 is also less than 2.1.0. The ranges for ProductVersion are 0-255.0-255.0-65535 See http://msdn.microsoft.com/en-us/library/aa370859.aspx *IF* you want to keep your Upgrade and UpgradeVersion elements then I recommend that you set UpgradeVersion/@Maximum to Product/@Version and UpgradeVersion/@IncludeMaximum to no. I recommend that you remove the Upgrade and UpgradeVersion elements all together and keep only the MajorUpgrade element letting it take care of everything for you. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Thursday, March 03, 2011 3:31 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Now the code looks like: Product ... Id=* UpgradeCode=529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B Package... / MajorUpgrade AllowDowngrades=no AllowSameVersionUpgrades=yes DowngradeErrorMessage=Downgrading the brain Schedule=afterInstallInitialize/ Upgrade Id=529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B UpgradeVersion OnlyDetect='no' Property='PREVIOUSFOUND' Minimum='1.0.0' IncludeMinimum='no' Maximum='2.0.9' IncludeMaximum='yes' / /Upgrade So 2.0.9 is less than 2.1 now I get only one ICE warning C:\... \Product.wxs(16,0): warning LGHT1076: ICE61: This product should remove only older versions of itself. The Maximum version is not less than the current product. (2.1.0 2.1.0) It looks like it thinks the Maximum is 2.1 when as you can see the Maximum is 2.0.9. -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Thursday, March 03, 2011 4:39 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Almost. You want: UpgradeVersion/@IncludeMinimum=yes UpgradeVersion/@IncludeMaximum=no Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Thursday, March 03, 2011 2:23 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Again I am just reading the tutorial the only explanation that I came up with to reconcile what I was reading with the arguments for the element was the concept of downgrade. I also would like to disallow downgrades. So since I am a little slow. If I always want to do a major upgrade then with each build I change the version on the product element AND also change Maximum on the upgrade element to be less than the current version? Right? So the code would look like: Product Version=2.1.0 UpgradeCode
Re: [WiX-users] Uninstall an installed product.
When I set it to * I get an error that it is not a GUID format. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Tuesday, March 01, 2011 2:07 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. I would personally leave of Package/@Id and and set Product/@Id to *. Or if you really want to set Package/@Id then set it to *. Product Id=* ... Package Id=* ... / /Product Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Friday, February 25, 2011 10:48 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. The product id and package id are: Product Id=9F6D788B-7A58-4750-BFEF-169FF18EE1C6... Package Id=---- .../ Since the package id is all '?' I assume that you mean I need to change the product id? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Wilson, Phil [mailto:phil.wil...@invensys.com] Sent: Friday, February 25, 2011 12:28 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Your new MSI has a new ProductCode? From that message it looks like it hasn't. Another possibility is that the PackageCode hasn't changed. Phil Wilson -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Friday, February 25, 2011 9:28 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Right now it is not automatically uninstalling the product. I am met with the dialog instructing me to go to Add/Remove Panel. Currently I am using an earlier version of WiX so I guess I am reading the right stuff in the tutorial. I am looking to try to migrate my WiX code to WiX 3.5 so I would also be interested in learning how this is done with the newer version. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Chris Lord [mailto:chris.l...@atterotech.com] Sent: Friday, February 25, 2011 11:21 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Kevin, Lesson 4 is/was based on Wix V3. Rob's reply refers to an addition to Wix3.5 though I would expect lesson 4 code probably still applies in V3.5. Depending on which version of WiX you use will determine what options you have for writing upgrades. Now, the key is where you place the RemoveExistingProducts function as this directly affects exactly what happens. If you schedule it early in the sequence then any existing product is uninstalled in its entirety before your new version is installed. If, as you have, schedule it late in the sequence then basically what will happen is that the initial install will remain with only files that have changed being affected/changed/removed. A quick search for RemoveExistingProducts should you the location to schedule it early or late (I don't remember the location off the top of my head). Note, there are advantages and disadvantages of using it either way so you may also want to look into that and decide which suits you best. If you are having specific issues with upgrading, can you be more specific about what is, or isn't working? Creating a verbose log when you run the installer may also help you diagnose what's happening. Chris On 02/25/2011 11:05 AM, Kevin Burton wrote: What is the syntactic sugar? I thought I was following http://www.tramontana.co.hu/wix/lesson4.php#4.2 So the question is why doesn't this work (what am I missing)? And, is there a better way? For reference here is the WiX code that I am using: Property Id=PREVIOUSVERSIONSINSTALLED Secure=yes / Upgrade Id='529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B' UpgradeVersion Minimum=1.0.0.0 Maximum=3.0.0.0 OnlyDetect='no' Property=PREVIOUSVERSIONSINSTALLED IncludeMinimum=yes IncludeMaximum=no / /Upgrade . . . . . InstallExecuteSequence RemoveExistingProducts After=InstallFinalize/RemoveExistingProducts /InstallExecuteSequence Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent
Re: [WiX-users] Uninstall an installed product.
What is it? I usually set Product\@Id=* and do not set Package\@Id at all. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Wednesday, March 02, 2011 6:27 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. When I set it to * I get an error that it is not a GUID format. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Tuesday, March 01, 2011 2:07 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. I would personally leave of Package/@Id and and set Product/@Id to *. Or if you really want to set Package/@Id then set it to *. Product Id=* ... Package Id=* ... / /Product Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Friday, February 25, 2011 10:48 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. The product id and package id are: Product Id=9F6D788B-7A58-4750-BFEF-169FF18EE1C6... Package Id=---- .../ Since the package id is all '?' I assume that you mean I need to change the product id? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Wilson, Phil [mailto:phil.wil...@invensys.com] Sent: Friday, February 25, 2011 12:28 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Your new MSI has a new ProductCode? From that message it looks like it hasn't. Another possibility is that the PackageCode hasn't changed. Phil Wilson -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Friday, February 25, 2011 9:28 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Right now it is not automatically uninstalling the product. I am met with the dialog instructing me to go to Add/Remove Panel. Currently I am using an earlier version of WiX so I guess I am reading the right stuff in the tutorial. I am looking to try to migrate my WiX code to WiX 3.5 so I would also be interested in learning how this is done with the newer version. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Chris Lord [mailto:chris.l...@atterotech.com] Sent: Friday, February 25, 2011 11:21 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Kevin, Lesson 4 is/was based on Wix V3. Rob's reply refers to an addition to Wix3.5 though I would expect lesson 4 code probably still applies in V3.5. Depending on which version of WiX you use will determine what options you have for writing upgrades. Now, the key is where you place the RemoveExistingProducts function as this directly affects exactly what happens. If you schedule it early in the sequence then any existing product is uninstalled in its entirety before your new version is installed. If, as you have, schedule it late in the sequence then basically what will happen is that the initial install will remain with only files that have changed being affected/changed/removed. A quick search for RemoveExistingProducts should you the location to schedule it early or late (I don't remember the location off the top of my head). Note, there are advantages and disadvantages of using it either way so you may also want to look into that and decide which suits you best. If you are having specific issues with upgrading, can you be more specific about what is, or isn't working? Creating a verbose log when you run the installer may also help you diagnose what's happening. Chris On 02/25/2011 11:05 AM, Kevin Burton wrote: What is the syntactic sugar? I thought I was following http://www.tramontana.co.hu/wix/lesson4.php#4.2 So the question is why doesn't this work (what am I missing)? And, is there a better way? For reference here is the WiX code that I am using: Property Id=PREVIOUSVERSIONSINSTALLED Secure
Re: [WiX-users] Uninstall an installed product.
'it' is the Package/@id that this thread is about. If I set the Product/@Id to * then how do I change it so that the previous version is uninstalled? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Wednesday, March 02, 2011 12:43 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. What is it? I usually set Product\@Id=* and do not set Package\@Id at all. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Wednesday, March 02, 2011 6:27 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. When I set it to * I get an error that it is not a GUID format. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Tuesday, March 01, 2011 2:07 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. I would personally leave of Package/@Id and and set Product/@Id to *. Or if you really want to set Package/@Id then set it to *. Product Id=* ... Package Id=* ... / /Product Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Friday, February 25, 2011 10:48 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. The product id and package id are: Product Id=9F6D788B-7A58-4750-BFEF-169FF18EE1C6... Package Id=---- .../ Since the package id is all '?' I assume that you mean I need to change the product id? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Wilson, Phil [mailto:phil.wil...@invensys.com] Sent: Friday, February 25, 2011 12:28 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Your new MSI has a new ProductCode? From that message it looks like it hasn't. Another possibility is that the PackageCode hasn't changed. Phil Wilson -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Friday, February 25, 2011 9:28 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Right now it is not automatically uninstalling the product. I am met with the dialog instructing me to go to Add/Remove Panel. Currently I am using an earlier version of WiX so I guess I am reading the right stuff in the tutorial. I am looking to try to migrate my WiX code to WiX 3.5 so I would also be interested in learning how this is done with the newer version. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Chris Lord [mailto:chris.l...@atterotech.com] Sent: Friday, February 25, 2011 11:21 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Kevin, Lesson 4 is/was based on Wix V3. Rob's reply refers to an addition to Wix3.5 though I would expect lesson 4 code probably still applies in V3.5. Depending on which version of WiX you use will determine what options you have for writing upgrades. Now, the key is where you place the RemoveExistingProducts function as this directly affects exactly what happens. If you schedule it early in the sequence then any existing product is uninstalled in its entirety before your new version is installed. If, as you have, schedule it late in the sequence then basically what will happen is that the initial install will remain with only files that have changed being affected/changed/removed. A quick search for RemoveExistingProducts should you the location to schedule it early or late (I don't remember the location off the top of my head). Note, there are advantages and disadvantages of using it either way so you may also want to look into that and decide which suits you best. If you are having specific issues with upgrading, can you
Re: [WiX-users] Uninstall an installed product.
Kevin You dont need to change it. Setting the package ID to * ensures the package in your installer is automatically regenerated with a new GUID each time you build it. This means when uninstalling, the MSI wont be confused by identical package GUID's. For each version you release, assuming you are doing major upgrades, the Product GUID and Package GUID must change BUT the Upgrade GUID must remain the same for EVERY version of that product. Chris -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Wednesday, March 02, 2011 2:58 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. 'it' is the Package/@id that this thread is about. If I set the Product/@Id to * then how do I change it so that the previous version is uninstalled? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Wednesday, March 02, 2011 12:43 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. What is it? I usually set Product\@Id=* and do not set Package\@Id at all. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Wednesday, March 02, 2011 6:27 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. When I set it to * I get an error that it is not a GUID format. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Tuesday, March 01, 2011 2:07 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. I would personally leave of Package/@Id and and set Product/@Id to *. Or if you really want to set Package/@Id then set it to *. Product Id=* ... Package Id=* ... / /Product Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Friday, February 25, 2011 10:48 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. The product id and package id are: Product Id=9F6D788B-7A58-4750-BFEF-169FF18EE1C6... Package Id=---- .../ Since the package id is all '?' I assume that you mean I need to change the product id? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Wilson, Phil [mailto:phil.wil...@invensys.com] Sent: Friday, February 25, 2011 12:28 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Your new MSI has a new ProductCode? From that message it looks like it hasn't. Another possibility is that the PackageCode hasn't changed. Phil Wilson -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Friday, February 25, 2011 9:28 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Right now it is not automatically uninstalling the product. I am met with the dialog instructing me to go to Add/Remove Panel. Currently I am using an earlier version of WiX so I guess I am reading the right stuff in the tutorial. I am looking to try to migrate my WiX code to WiX 3.5 so I would also be interested in learning how this is done with the newer version. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Chris Lord [mailto:chris.l...@atterotech.com] Sent: Friday, February 25, 2011 11:21 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Kevin, Lesson 4 is/was based on Wix V3. Rob's reply refers to an addition to Wix3.5 though I would expect lesson 4 code probably still applies in V3.5. Depending on which version of WiX you use will determine what options you have for writing upgrades. Now, the key is where you place the RemoveExistingProducts function as this directly affects exactly what happens. If you
Re: [WiX-users] Uninstall an installed product.
The Product/@Id is of type AutogenGuid according to
http://wix.sourceforge.net/manual-wix3/wix_xsd_product.htm. The AutogenGuid
description says:
Values of this type will look like: 01234567-89AB-CDEF-0123-456789ABCDEF or
{01234567-89AB-CDEF-0123-456789ABCDEF}. A GUID can be auto-generated by
setting the value to *. Also allows PUT-GUID-HERE for use in examples.
Package/@Id is also of type AutogenGuid according to
http://wix.sourceforge.net/manual-wix3/wix_xsd_package.htm.
The compiler becomes responsible for generating a new GUID on each build.
Windows Installer requires that each and every package has a different
Package/@Id. Explicitly setting Package/@Id to * is the same functionality as
just not specifying the attribute at all as it is not required. As the compiler
generates a new GUID on each build we meet the requirements set by Windows
Installer.
As mentioned earlier, Windows Installer defines a major upgrade as a package
that has a different Package/@Id (by definition), a different Product/@Id, a
different Product/@Version, and the SAME Product/@UpgradeCode as a currently
installed product. The Product/@UpgradeCode is what ties together products that
belong to the same product family.
The Upgrade table is used to detect previously installed products that should
be upgraded and schedules them to be uninstalled. The MajorUpgrade element
makes it really easy to author the Upgrade table correctly. See
http://wix.sourceforge.net/manual-wix3/wix_xsd_majorupgrade.htm.
If you always want to generate major upgrades then you'll want to do the
following:
* Use the MajorUpgrade element.
* Set Product/@Id to *.
* Do not set Package/@Id as the default value results in the correct behavior.
* Guarantee that your build process results in a different Product/@Version on
every build.
* Do NOT change Product/@UpgradeCode between builds.
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
Please consider the environment before printing this e-mail
-Original Message-
From: Chris Lord [mailto:chris.l...@atterotech.com]
Sent: Wednesday, March 02, 2011 1:29 PM
To: wix-users
Subject: Re: [WiX-users] Uninstall an installed product.
Kevin
You dont need to change it. Setting the package ID to * ensures the
package in your installer is automatically regenerated with a new GUID each
time you build it. This means when uninstalling, the MSI wont be confused
by identical package GUID's.
For each version you release, assuming you are doing major upgrades, the
Product GUID and Package GUID must change BUT the Upgrade GUID must
remain the same for EVERY version of that product.
Chris
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Wednesday, March 02, 2011 2:58 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
'it' is the Package/@id that this thread is about. If I set the Product/@Id to
* then how do I change it so that the previous version is uninstalled?
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Wednesday, March 02, 2011 12:43 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
What is it? I usually set Product\@Id=* and do not set Package\@Id at all.
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Wednesday, March 02, 2011 6:27 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
When I set it to * I get an error that it is not a GUID format.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Tuesday, March 01, 2011 2:07 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
I would personally leave of Package/@Id and and set Product/@Id to
*. Or if you really want to set Package/@Id then set it to *.
Product Id=* ...
Package Id=* ... /
/Product
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Friday, February 25
Re: [WiX-users] Uninstall an installed product.
I get a squigly blue line (error) when I include the MajorUpgrade.. element
below the Product. I have the namespace for the schema set to
http://schemas.microsoft.com/wix/2006/wi;.
I get the error:
Error 2 Schema validation failed with the following error at line 1,
column 565: The element 'Product' in namespace
'http://schemas.microsoft.com/wix/2006/wi' has invalid child element
'MajorUpgrade' in namespace 'http://schemas.microsoft.com/wix/2006/wi'. List of
possible elements expected: 'Package'.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Wednesday, March 02, 2011 4:00 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
The Product/@Id is of type AutogenGuid according to
http://wix.sourceforge.net/manual-wix3/wix_xsd_product.htm. The AutogenGuid
description says:
Values of this type will look like: 01234567-89AB-CDEF-0123-456789ABCDEF or
{01234567-89AB-CDEF-0123-456789ABCDEF}. A GUID can be auto-generated by
setting the value to *. Also allows PUT-GUID-HERE for use in examples.
Package/@Id is also of type AutogenGuid according to
http://wix.sourceforge.net/manual-wix3/wix_xsd_package.htm.
The compiler becomes responsible for generating a new GUID on each build.
Windows Installer requires that each and every package has a different
Package/@Id. Explicitly setting Package/@Id to * is the same functionality as
just not specifying the attribute at all as it is not required. As the compiler
generates a new GUID on each build we meet the requirements set by Windows
Installer.
As mentioned earlier, Windows Installer defines a major upgrade as a package
that has a different Package/@Id (by definition), a different Product/@Id, a
different Product/@Version, and the SAME Product/@UpgradeCode as a currently
installed product. The Product/@UpgradeCode is what ties together products that
belong to the same product family.
The Upgrade table is used to detect previously installed products that should
be upgraded and schedules them to be uninstalled. The MajorUpgrade element
makes it really easy to author the Upgrade table correctly. See
http://wix.sourceforge.net/manual-wix3/wix_xsd_majorupgrade.htm.
If you always want to generate major upgrades then you'll want to do the
following:
* Use the MajorUpgrade element.
* Set Product/@Id to *.
* Do not set Package/@Id as the default value results in the correct behavior.
* Guarantee that your build process results in a different Product/@Version on
every build.
* Do NOT change Product/@UpgradeCode between builds.
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail
-Original Message-
From: Chris Lord [mailto:chris.l...@atterotech.com]
Sent: Wednesday, March 02, 2011 1:29 PM
To: wix-users
Subject: Re: [WiX-users] Uninstall an installed product.
Kevin
You dont need to change it. Setting the package ID to * ensures the
package in your installer is automatically regenerated with a new GUID
each time you build it. This means when uninstalling, the MSI wont be
confused by identical package GUID's.
For each version you release, assuming you are doing major upgrades,
the Product GUID and Package GUID must change BUT the Upgrade GUID
must remain the same for EVERY version of that product.
Chris
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Wednesday, March 02, 2011 2:58 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
'it' is the Package/@id that this thread is about. If I set the
Product/@Id to * then how do I change it so that the previous version is
uninstalled?
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Wednesday, March 02, 2011 12:43 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
What is it? I usually set Product\@Id=* and do not set Package\@Id at all.
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Wednesday, March 02, 2011 6:27 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
When I set it to * I get an error that it is not a GUID format.
Kevin Burton
Re: [WiX-users] Uninstall an installed product.
What version of WiX do you have?
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
Please consider the environment before printing this e-mail
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Wednesday, March 02, 2011 3:08 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
I get a squigly blue line (error) when I include the MajorUpgrade.. element
below the Product. I have the namespace for the schema set to
http://schemas.microsoft.com/wix/2006/wi;.
I get the error:
Error 2 Schema validation failed with the following error at line 1,
column
565: The element 'Product' in namespace
'http://schemas.microsoft.com/wix/2006/wi' has invalid child element
'MajorUpgrade' in namespace 'http://schemas.microsoft.com/wix/2006/wi'.
List of possible elements expected: 'Package'.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Wednesday, March 02, 2011 4:00 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
The Product/@Id is of type AutogenGuid according to
http://wix.sourceforge.net/manual-wix3/wix_xsd_product.htm. The
AutogenGuid description says:
Values of this type will look like: 01234567-89AB-CDEF-0123-456789ABCDEF
or {01234567-89AB-CDEF-0123-456789ABCDEF}. A GUID can be auto-
generated by setting the value to *. Also allows PUT-GUID-HERE for use
in examples.
Package/@Id is also of type AutogenGuid according to
http://wix.sourceforge.net/manual-wix3/wix_xsd_package.htm.
The compiler becomes responsible for generating a new GUID on each build.
Windows Installer requires that each and every package has a different
Package/@Id. Explicitly setting Package/@Id to * is the same functionality
as just not specifying the attribute at all as it is not required. As the
compiler
generates a new GUID on each build we meet the requirements set by
Windows Installer.
As mentioned earlier, Windows Installer defines a major upgrade as a
package that has a different Package/@Id (by definition), a different
Product/@Id, a different Product/@Version, and the SAME
Product/@UpgradeCode as a currently installed product. The
Product/@UpgradeCode is what ties together products that belong to the
same product family.
The Upgrade table is used to detect previously installed products that should
be upgraded and schedules them to be uninstalled. The MajorUpgrade
element makes it really easy to author the Upgrade table correctly. See
http://wix.sourceforge.net/manual-wix3/wix_xsd_majorupgrade.htm.
If you always want to generate major upgrades then you'll want to do the
following:
* Use the MajorUpgrade element.
* Set Product/@Id to *.
* Do not set Package/@Id as the default value results in the correct behavior.
* Guarantee that your build process results in a different Product/@Version
on every build.
* Do NOT change Product/@UpgradeCode between builds.
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail
-Original Message-
From: Chris Lord [mailto:chris.l...@atterotech.com]
Sent: Wednesday, March 02, 2011 1:29 PM
To: wix-users
Subject: Re: [WiX-users] Uninstall an installed product.
Kevin
You dont need to change it. Setting the package ID to * ensures the
package in your installer is automatically regenerated with a new GUID
each time you build it. This means when uninstalling, the MSI wont be
confused by identical package GUID's.
For each version you release, assuming you are doing major upgrades,
the Product GUID and Package GUID must change BUT the Upgrade GUID
must remain the same for EVERY version of that product.
Chris
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Wednesday, March 02, 2011 2:58 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
'it' is the Package/@id that this thread is about. If I set the
Product/@Id to * then how do I change it so that the previous version is
uninstalled?
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Wednesday, March 02, 2011 12:43 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
What is it? I usually set Product\@Id=* and do not set
Re: [WiX-users] Uninstall an installed product.
Assuming you are using WiX 3.5.2519.0, then you need to put the MajorUpgrade
element after the Package element. The Package element must be the first child
of Product. See http://wix.sourceforge.net/manual-wix3/wix_xsd_product.htm.
Wix xmlns=
Product ...
Package ... /
...
MajorUpgrade ... /
...
/Product
/Wix
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
Please consider the environment before printing this e-mail
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Wednesday, March 02, 2011 3:14 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
What version of WiX do you have?
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Wednesday, March 02, 2011 3:08 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
I get a squigly blue line (error) when I include the MajorUpgrade..
element below the Product. I have the namespace for the schema set
to http://schemas.microsoft.com/wix/2006/wi;.
I get the error:
Error 2 Schema validation failed with the following error at line 1,
column
565: The element 'Product' in namespace
'http://schemas.microsoft.com/wix/2006/wi' has invalid child element
'MajorUpgrade' in namespace
'http://schemas.microsoft.com/wix/2006/wi'.
List of possible elements expected: 'Package'.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Wednesday, March 02, 2011 4:00 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
The Product/@Id is of type AutogenGuid according to
http://wix.sourceforge.net/manual-wix3/wix_xsd_product.htm. The
AutogenGuid description says:
Values of this type will look like: 01234567-89AB-CDEF-0123-
456789ABCDEF
or {01234567-89AB-CDEF-0123-456789ABCDEF}. A GUID can be auto-
generated by setting the value to *. Also allows PUT-GUID-HERE for
use in examples.
Package/@Id is also of type AutogenGuid according to
http://wix.sourceforge.net/manual-wix3/wix_xsd_package.htm.
The compiler becomes responsible for generating a new GUID on each
build.
Windows Installer requires that each and every package has a different
Package/@Id. Explicitly setting Package/@Id to * is the same
functionality as just not specifying the attribute at all as it is not
required. As the compiler generates a new GUID on each build we meet
the requirements set by Windows Installer.
As mentioned earlier, Windows Installer defines a major upgrade as a
package that has a different Package/@Id (by definition), a different
Product/@Id, a different Product/@Version, and the SAME
Product/@UpgradeCode as a currently installed product. The
Product/@UpgradeCode is what ties together products that belong to the
same product family.
The Upgrade table is used to detect previously installed products that
should be upgraded and schedules them to be uninstalled. The
MajorUpgrade element makes it really easy to author the Upgrade table
correctly. See http://wix.sourceforge.net/manual-
wix3/wix_xsd_majorupgrade.htm.
If you always want to generate major upgrades then you'll want to do
the
following:
* Use the MajorUpgrade element.
* Set Product/@Id to *.
* Do not set Package/@Id as the default value results in the correct
behavior.
* Guarantee that your build process results in a different
Product/@Version on every build.
* Do NOT change Product/@UpgradeCode between builds.
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail
-Original Message-
From: Chris Lord [mailto:chris.l...@atterotech.com]
Sent: Wednesday, March 02, 2011 1:29 PM
To: wix-users
Subject: Re: [WiX-users] Uninstall an installed product.
Kevin
You dont need to change it. Setting the package ID to * ensures
the package in your installer is automatically regenerated with a
new GUID each time you build it. This means when uninstalling, the
MSI wont be confused by identical package GUID's.
For each version you release, assuming you are doing major upgrades,
the Product GUID and Package GUID must change BUT the Upgrade
Re: [WiX-users] Uninstall an installed product.
Thank you.
http://wix.sourceforge.net/manual-wix3/wix_xsd_majorupgrade.htm
lists Product as the parent.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Wednesday, March 02, 2011 5:43 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
Assuming you are using WiX 3.5.2519.0, then you need to put the MajorUpgrade
element after the Package element. The Package element must be the first child
of Product. See http://wix.sourceforge.net/manual-wix3/wix_xsd_product.htm.
Wix xmlns=
Product ...
Package ... /
...
MajorUpgrade ... /
...
/Product
/Wix
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Wednesday, March 02, 2011 3:14 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
What version of WiX do you have?
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Wednesday, March 02, 2011 3:08 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
I get a squigly blue line (error) when I include the
MajorUpgrade.. element below the Product. I have the namespace
for the schema set to http://schemas.microsoft.com/wix/2006/wi;.
I get the error:
Error 2 Schema validation failed with the following error at line 1,
column
565: The element 'Product' in namespace
'http://schemas.microsoft.com/wix/2006/wi' has invalid child element
'MajorUpgrade' in namespace
'http://schemas.microsoft.com/wix/2006/wi'.
List of possible elements expected: 'Package'.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Wednesday, March 02, 2011 4:00 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
The Product/@Id is of type AutogenGuid according to
http://wix.sourceforge.net/manual-wix3/wix_xsd_product.htm. The
AutogenGuid description says:
Values of this type will look like: 01234567-89AB-CDEF-0123-
456789ABCDEF
or {01234567-89AB-CDEF-0123-456789ABCDEF}. A GUID can be auto-
generated by setting the value to *. Also allows PUT-GUID-HERE
for use in examples.
Package/@Id is also of type AutogenGuid according to
http://wix.sourceforge.net/manual-wix3/wix_xsd_package.htm.
The compiler becomes responsible for generating a new GUID on each
build.
Windows Installer requires that each and every package has a
different Package/@Id. Explicitly setting Package/@Id to * is the
same functionality as just not specifying the attribute at all as it
is not required. As the compiler generates a new GUID on each build
we meet the requirements set by Windows Installer.
As mentioned earlier, Windows Installer defines a major upgrade as a
package that has a different Package/@Id (by definition), a
different Product/@Id, a different Product/@Version, and the SAME
Product/@UpgradeCode as a currently installed product. The
Product/@UpgradeCode is what ties together products that belong to
the same product family.
The Upgrade table is used to detect previously installed products
that should be upgraded and schedules them to be uninstalled. The
MajorUpgrade element makes it really easy to author the Upgrade
table correctly. See http://wix.sourceforge.net/manual-
wix3/wix_xsd_majorupgrade.htm.
If you always want to generate major upgrades then you'll want to do
the
following:
* Use the MajorUpgrade element.
* Set Product/@Id to *.
* Do not set Package/@Id as the default value results in the correct
behavior.
* Guarantee that your build process results in a different
Product/@Version on every build.
* Do NOT change Product/@UpgradeCode between builds.
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail
-Original Message-
From: Chris Lord [mailto:chris.l...@atterotech.com]
Sent: Wednesday, March 02, 2011 1:29 PM
To: wix-users
Subject
Re: [WiX-users] Uninstall an installed product.
The error occurs with 'light'
H:\light -?
Microsoft (R) Windows Installer Xml Linker version 3.5.2519.0
Copyright (C) Microsoft Corporation. All rights reserved.
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Wednesday, March 02, 2011 5:14 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
What version of WiX do you have?
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Wednesday, March 02, 2011 3:08 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
I get a squigly blue line (error) when I include the MajorUpgrade..
element below the Product. I have the namespace for the schema set
to http://schemas.microsoft.com/wix/2006/wi;.
I get the error:
Error 2 Schema validation failed with the following error at line 1,
column
565: The element 'Product' in namespace
'http://schemas.microsoft.com/wix/2006/wi' has invalid child element
'MajorUpgrade' in namespace 'http://schemas.microsoft.com/wix/2006/wi'.
List of possible elements expected: 'Package'.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Wednesday, March 02, 2011 4:00 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
The Product/@Id is of type AutogenGuid according to
http://wix.sourceforge.net/manual-wix3/wix_xsd_product.htm. The
AutogenGuid description says:
Values of this type will look like: 01234567-89AB-CDEF-0123-456789ABCDEF
or {01234567-89AB-CDEF-0123-456789ABCDEF}. A GUID can be auto-
generated by setting the value to *. Also allows PUT-GUID-HERE for
use in examples.
Package/@Id is also of type AutogenGuid according to
http://wix.sourceforge.net/manual-wix3/wix_xsd_package.htm.
The compiler becomes responsible for generating a new GUID on each build.
Windows Installer requires that each and every package has a different
Package/@Id. Explicitly setting Package/@Id to * is the same
functionality as just not specifying the attribute at all as it is not
required. As the compiler generates a new GUID on each build we meet
the requirements set by Windows Installer.
As mentioned earlier, Windows Installer defines a major upgrade as a
package that has a different Package/@Id (by definition), a different
Product/@Id, a different Product/@Version, and the SAME
Product/@UpgradeCode as a currently installed product. The
Product/@UpgradeCode is what ties together products that belong to the
same product family.
The Upgrade table is used to detect previously installed products that
should be upgraded and schedules them to be uninstalled. The
MajorUpgrade element makes it really easy to author the Upgrade table
correctly. See
http://wix.sourceforge.net/manual-wix3/wix_xsd_majorupgrade.htm.
If you always want to generate major upgrades then you'll want to do
the
following:
* Use the MajorUpgrade element.
* Set Product/@Id to *.
* Do not set Package/@Id as the default value results in the correct behavior.
* Guarantee that your build process results in a different
Product/@Version on every build.
* Do NOT change Product/@UpgradeCode between builds.
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail
-Original Message-
From: Chris Lord [mailto:chris.l...@atterotech.com]
Sent: Wednesday, March 02, 2011 1:29 PM
To: wix-users
Subject: Re: [WiX-users] Uninstall an installed product.
Kevin
You dont need to change it. Setting the package ID to * ensures
the package in your installer is automatically regenerated with a
new GUID each time you build it. This means when uninstalling, the
MSI wont be confused by identical package GUID's.
For each version you release, assuming you are doing major upgrades,
the Product GUID and Package GUID must change BUT the Upgrade GUID
must remain the same for EVERY version of that product.
Chris
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Wednesday, March 02, 2011 2:58 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
'it' is the Package/@id that this thread is about. If I set the
Product/@Id to * then how do I change it so that the previous
version is
uninstalled?
Kevin Burton
Senior
Re: [WiX-users] Uninstall an installed product.
I am sorry but now I am getting:
\Product.wxs(16,0): warning LGHT1076: ICE61: This product should remove only
older versions of itself. The Maximum version is not less than the current
product. (2.1.0 2.1.0)
\Product.wxs(21,0): warning LGHT1076: ICE61: This product should remove only
older versions of itself. The Maximum version is not less than the current
product. (3.0.0 2.1.0)
The wxs code is:
Product Version=2.1.0
UpgradeCode=529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B
Upgrade Id=529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B
UpgradeVersion OnlyDetect='no' Property='PREVIOUSFOUND'
Minimum='1.0.0' IncludeMinimum='yes'
Maximum='3.0.0' IncludeMaximum='no' /
/Upgrade
What is this telling me?
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Wednesday, March 02, 2011 4:00 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
The Product/@Id is of type AutogenGuid according to
http://wix.sourceforge.net/manual-wix3/wix_xsd_product.htm. The AutogenGuid
description says:
Values of this type will look like: 01234567-89AB-CDEF-0123-456789ABCDEF or
{01234567-89AB-CDEF-0123-456789ABCDEF}. A GUID can be auto-generated by
setting the value to *. Also allows PUT-GUID-HERE for use in examples.
Package/@Id is also of type AutogenGuid according to
http://wix.sourceforge.net/manual-wix3/wix_xsd_package.htm.
The compiler becomes responsible for generating a new GUID on each build.
Windows Installer requires that each and every package has a different
Package/@Id. Explicitly setting Package/@Id to * is the same functionality as
just not specifying the attribute at all as it is not required. As the compiler
generates a new GUID on each build we meet the requirements set by Windows
Installer.
As mentioned earlier, Windows Installer defines a major upgrade as a package
that has a different Package/@Id (by definition), a different Product/@Id, a
different Product/@Version, and the SAME Product/@UpgradeCode as a currently
installed product. The Product/@UpgradeCode is what ties together products that
belong to the same product family.
The Upgrade table is used to detect previously installed products that should
be upgraded and schedules them to be uninstalled. The MajorUpgrade element
makes it really easy to author the Upgrade table correctly. See
http://wix.sourceforge.net/manual-wix3/wix_xsd_majorupgrade.htm.
If you always want to generate major upgrades then you'll want to do the
following:
* Use the MajorUpgrade element.
* Set Product/@Id to *.
* Do not set Package/@Id as the default value results in the correct behavior.
* Guarantee that your build process results in a different Product/@Version on
every build.
* Do NOT change Product/@UpgradeCode between builds.
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail
-Original Message-
From: Chris Lord [mailto:chris.l...@atterotech.com]
Sent: Wednesday, March 02, 2011 1:29 PM
To: wix-users
Subject: Re: [WiX-users] Uninstall an installed product.
Kevin
You dont need to change it. Setting the package ID to * ensures the
package in your installer is automatically regenerated with a new GUID
each time you build it. This means when uninstalling, the MSI wont be
confused by identical package GUID's.
For each version you release, assuming you are doing major upgrades,
the Product GUID and Package GUID must change BUT the Upgrade GUID
must remain the same for EVERY version of that product.
Chris
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Wednesday, March 02, 2011 2:58 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
'it' is the Package/@id that this thread is about. If I set the
Product/@Id to * then how do I change it so that the previous version is
uninstalled?
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Wednesday, March 02, 2011 12:43 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall an installed product.
What is it? I usually set Product\@Id=* and do not set Package\@Id at all.
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
P Please consider the environment before printing this e-mail
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Wednesday, March 02, 2011 6:27 AM
To: General discussion for Windows Installer XML toolset
Re: [WiX-users] Uninstall an installed product.
I would personally leave of Package/@Id and and set Product/@Id to *. Or if you really want to set Package/@Id then set it to *. Product Id=* ... Package Id=* ... / /Product Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Friday, February 25, 2011 10:48 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. The product id and package id are: Product Id=9F6D788B-7A58-4750-BFEF-169FF18EE1C6... Package Id=---- .../ Since the package id is all '?' I assume that you mean I need to change the product id? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Wilson, Phil [mailto:phil.wil...@invensys.com] Sent: Friday, February 25, 2011 12:28 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Your new MSI has a new ProductCode? From that message it looks like it hasn't. Another possibility is that the PackageCode hasn't changed. Phil Wilson -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Friday, February 25, 2011 9:28 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Right now it is not automatically uninstalling the product. I am met with the dialog instructing me to go to Add/Remove Panel. Currently I am using an earlier version of WiX so I guess I am reading the right stuff in the tutorial. I am looking to try to migrate my WiX code to WiX 3.5 so I would also be interested in learning how this is done with the newer version. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Chris Lord [mailto:chris.l...@atterotech.com] Sent: Friday, February 25, 2011 11:21 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Kevin, Lesson 4 is/was based on Wix V3. Rob's reply refers to an addition to Wix3.5 though I would expect lesson 4 code probably still applies in V3.5. Depending on which version of WiX you use will determine what options you have for writing upgrades. Now, the key is where you place the RemoveExistingProducts function as this directly affects exactly what happens. If you schedule it early in the sequence then any existing product is uninstalled in its entirety before your new version is installed. If, as you have, schedule it late in the sequence then basically what will happen is that the initial install will remain with only files that have changed being affected/changed/removed. A quick search for RemoveExistingProducts should you the location to schedule it early or late (I don't remember the location off the top of my head). Note, there are advantages and disadvantages of using it either way so you may also want to look into that and decide which suits you best. If you are having specific issues with upgrading, can you be more specific about what is, or isn't working? Creating a verbose log when you run the installer may also help you diagnose what's happening. Chris On 02/25/2011 11:05 AM, Kevin Burton wrote: What is the syntactic sugar? I thought I was following http://www.tramontana.co.hu/wix/lesson4.php#4.2 So the question is why doesn't this work (what am I missing)? And, is there a better way? For reference here is the WiX code that I am using: Property Id=PREVIOUSVERSIONSINSTALLED Secure=yes / Upgrade Id='529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B' UpgradeVersion Minimum=1.0.0.0 Maximum=3.0.0.0 OnlyDetect='no' Property=PREVIOUSVERSIONSINSTALLED IncludeMinimum=yes IncludeMaximum=no / /Upgrade . . . . . InstallExecuteSequence RemoveExistingProducts After=InstallFinalize/RemoveExistingProducts /InstallExecuteSequence Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Thursday, February 24, 2011 10:34 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. In WiX v3.5, MajorUpgrade element provides nice syntactic sugar. Otherwise, you want to look at the Upgrade element. On Thu, Feb 24, 2011 at 10:22 AM, Kevin Burtonkev...@buyseasons.comwrote: I know this is an old question but I don't know the WiX syntax for automatically
Re: [WiX-users] Uninstall an installed product.
What is the syntactic sugar? I thought I was following http://www.tramontana.co.hu/wix/lesson4.php#4.2 So the question is why doesn't this work (what am I missing)? And, is there a better way? For reference here is the WiX code that I am using: Property Id=PREVIOUSVERSIONSINSTALLED Secure=yes / Upgrade Id='529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B' UpgradeVersion Minimum=1.0.0.0 Maximum=3.0.0.0 OnlyDetect='no' Property=PREVIOUSVERSIONSINSTALLED IncludeMinimum=yes IncludeMaximum=no / /Upgrade . . . . . InstallExecuteSequence RemoveExistingProducts After=InstallFinalize/RemoveExistingProducts /InstallExecuteSequence Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Thursday, February 24, 2011 10:34 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. In WiX v3.5, MajorUpgrade element provides nice syntactic sugar. Otherwise, you want to look at the Upgrade element. On Thu, Feb 24, 2011 at 10:22 AM, Kevin Burton kev...@buyseasons.comwrote: I know this is an old question but I don't know the WiX syntax for automatically uninstalling an installed product. I looked at the documentation and I got confused with Major/Minor updates/upgrades. In my case if the product is install I *always* want to uninstall it before proceeding with the installation. Any hints? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Uninstall an installed product.
Kevin, Lesson 4 is/was based on Wix V3. Rob's reply refers to an addition to Wix3.5 though I would expect lesson 4 code probably still applies in V3.5. Depending on which version of WiX you use will determine what options you have for writing upgrades. Now, the key is where you place the RemoveExistingProducts function as this directly affects exactly what happens. If you schedule it early in the sequence then any existing product is uninstalled in its entirety before your new version is installed. If, as you have, schedule it late in the sequence then basically what will happen is that the initial install will remain with only files that have changed being affected/changed/removed. A quick search for RemoveExistingProducts should you the location to schedule it early or late (I don't remember the location off the top of my head). Note, there are advantages and disadvantages of using it either way so you may also want to look into that and decide which suits you best. If you are having specific issues with upgrading, can you be more specific about what is, or isn't working? Creating a verbose log when you run the installer may also help you diagnose what's happening. Chris On 02/25/2011 11:05 AM, Kevin Burton wrote: What is the syntactic sugar? I thought I was following http://www.tramontana.co.hu/wix/lesson4.php#4.2 So the question is why doesn't this work (what am I missing)? And, is there a better way? For reference here is the WiX code that I am using: Property Id=PREVIOUSVERSIONSINSTALLED Secure=yes / Upgrade Id='529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B' UpgradeVersion Minimum=1.0.0.0 Maximum=3.0.0.0 OnlyDetect='no' Property=PREVIOUSVERSIONSINSTALLED IncludeMinimum=yes IncludeMaximum=no / /Upgrade . . . . . InstallExecuteSequence RemoveExistingProducts After=InstallFinalize/RemoveExistingProducts /InstallExecuteSequence Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Thursday, February 24, 2011 10:34 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. In WiX v3.5, MajorUpgrade element provides nice syntactic sugar. Otherwise, you want to look at the Upgrade element. On Thu, Feb 24, 2011 at 10:22 AM, Kevin Burtonkev...@buyseasons.comwrote: I know this is an old question but I don't know the WiX syntax for automatically uninstalling an installed product. I looked at the documentation and I got confused with Major/Minor updates/upgrades. In my case if the product is install I *always* want to uninstall it before proceeding with the installation. Any hints? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Uninstall an installed product.
Right now it is not automatically uninstalling the product. I am met with the dialog instructing me to go to Add/Remove Panel. Currently I am using an earlier version of WiX so I guess I am reading the right stuff in the tutorial. I am looking to try to migrate my WiX code to WiX 3.5 so I would also be interested in learning how this is done with the newer version. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Chris Lord [mailto:chris.l...@atterotech.com] Sent: Friday, February 25, 2011 11:21 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Kevin, Lesson 4 is/was based on Wix V3. Rob's reply refers to an addition to Wix3.5 though I would expect lesson 4 code probably still applies in V3.5. Depending on which version of WiX you use will determine what options you have for writing upgrades. Now, the key is where you place the RemoveExistingProducts function as this directly affects exactly what happens. If you schedule it early in the sequence then any existing product is uninstalled in its entirety before your new version is installed. If, as you have, schedule it late in the sequence then basically what will happen is that the initial install will remain with only files that have changed being affected/changed/removed. A quick search for RemoveExistingProducts should you the location to schedule it early or late (I don't remember the location off the top of my head). Note, there are advantages and disadvantages of using it either way so you may also want to look into that and decide which suits you best. If you are having specific issues with upgrading, can you be more specific about what is, or isn't working? Creating a verbose log when you run the installer may also help you diagnose what's happening. Chris On 02/25/2011 11:05 AM, Kevin Burton wrote: What is the syntactic sugar? I thought I was following http://www.tramontana.co.hu/wix/lesson4.php#4.2 So the question is why doesn't this work (what am I missing)? And, is there a better way? For reference here is the WiX code that I am using: Property Id=PREVIOUSVERSIONSINSTALLED Secure=yes / Upgrade Id='529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B' UpgradeVersion Minimum=1.0.0.0 Maximum=3.0.0.0 OnlyDetect='no' Property=PREVIOUSVERSIONSINSTALLED IncludeMinimum=yes IncludeMaximum=no / /Upgrade . . . . . InstallExecuteSequence RemoveExistingProducts After=InstallFinalize/RemoveExistingProducts /InstallExecuteSequence Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Thursday, February 24, 2011 10:34 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. In WiX v3.5, MajorUpgrade element provides nice syntactic sugar. Otherwise, you want to look at the Upgrade element. On Thu, Feb 24, 2011 at 10:22 AM, Kevin Burtonkev...@buyseasons.comwrote: I know this is an old question but I don't know the WiX syntax for automatically uninstalling an installed product. I looked at the documentation and I got confused with Major/Minor updates/upgrades. In my case if the product is install I *always* want to uninstall it before proceeding with the installation. Any hints? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Software Download: Index, Search Analyze Logs
Re: [WiX-users] Uninstall an installed product.
Your new MSI has a new ProductCode? From that message it looks like it hasn't. Another possibility is that the PackageCode hasn't changed. Phil Wilson -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Friday, February 25, 2011 9:28 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Right now it is not automatically uninstalling the product. I am met with the dialog instructing me to go to Add/Remove Panel. Currently I am using an earlier version of WiX so I guess I am reading the right stuff in the tutorial. I am looking to try to migrate my WiX code to WiX 3.5 so I would also be interested in learning how this is done with the newer version. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Chris Lord [mailto:chris.l...@atterotech.com] Sent: Friday, February 25, 2011 11:21 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Kevin, Lesson 4 is/was based on Wix V3. Rob's reply refers to an addition to Wix3.5 though I would expect lesson 4 code probably still applies in V3.5. Depending on which version of WiX you use will determine what options you have for writing upgrades. Now, the key is where you place the RemoveExistingProducts function as this directly affects exactly what happens. If you schedule it early in the sequence then any existing product is uninstalled in its entirety before your new version is installed. If, as you have, schedule it late in the sequence then basically what will happen is that the initial install will remain with only files that have changed being affected/changed/removed. A quick search for RemoveExistingProducts should you the location to schedule it early or late (I don't remember the location off the top of my head). Note, there are advantages and disadvantages of using it either way so you may also want to look into that and decide which suits you best. If you are having specific issues with upgrading, can you be more specific about what is, or isn't working? Creating a verbose log when you run the installer may also help you diagnose what's happening. Chris On 02/25/2011 11:05 AM, Kevin Burton wrote: What is the syntactic sugar? I thought I was following http://www.tramontana.co.hu/wix/lesson4.php#4.2 So the question is why doesn't this work (what am I missing)? And, is there a better way? For reference here is the WiX code that I am using: Property Id=PREVIOUSVERSIONSINSTALLED Secure=yes / Upgrade Id='529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B' UpgradeVersion Minimum=1.0.0.0 Maximum=3.0.0.0 OnlyDetect='no' Property=PREVIOUSVERSIONSINSTALLED IncludeMinimum=yes IncludeMaximum=no / /Upgrade . . . . . InstallExecuteSequence RemoveExistingProducts After=InstallFinalize/RemoveExistingProducts /InstallExecuteSequence Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Thursday, February 24, 2011 10:34 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. In WiX v3.5, MajorUpgrade element provides nice syntactic sugar. Otherwise, you want to look at the Upgrade element. On Thu, Feb 24, 2011 at 10:22 AM, Kevin Burtonkev...@buyseasons.comwrote: I know this is an old question but I don't know the WiX syntax for automatically uninstalling an installed product. I looked at the documentation and I got confused with Major/Minor updates/upgrades. In my case if the product is install I *always* want to uninstall it before proceeding with the installation. Any hints? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver
Re: [WiX-users] Uninstall an installed product.
The product id and package id are: Product Id=9F6D788B-7A58-4750-BFEF-169FF18EE1C6... Package Id=---- .../ Since the package id is all '?' I assume that you mean I need to change the product id? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Wilson, Phil [mailto:phil.wil...@invensys.com] Sent: Friday, February 25, 2011 12:28 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Your new MSI has a new ProductCode? From that message it looks like it hasn't. Another possibility is that the PackageCode hasn't changed. Phil Wilson -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Friday, February 25, 2011 9:28 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Right now it is not automatically uninstalling the product. I am met with the dialog instructing me to go to Add/Remove Panel. Currently I am using an earlier version of WiX so I guess I am reading the right stuff in the tutorial. I am looking to try to migrate my WiX code to WiX 3.5 so I would also be interested in learning how this is done with the newer version. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Chris Lord [mailto:chris.l...@atterotech.com] Sent: Friday, February 25, 2011 11:21 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Kevin, Lesson 4 is/was based on Wix V3. Rob's reply refers to an addition to Wix3.5 though I would expect lesson 4 code probably still applies in V3.5. Depending on which version of WiX you use will determine what options you have for writing upgrades. Now, the key is where you place the RemoveExistingProducts function as this directly affects exactly what happens. If you schedule it early in the sequence then any existing product is uninstalled in its entirety before your new version is installed. If, as you have, schedule it late in the sequence then basically what will happen is that the initial install will remain with only files that have changed being affected/changed/removed. A quick search for RemoveExistingProducts should you the location to schedule it early or late (I don't remember the location off the top of my head). Note, there are advantages and disadvantages of using it either way so you may also want to look into that and decide which suits you best. If you are having specific issues with upgrading, can you be more specific about what is, or isn't working? Creating a verbose log when you run the installer may also help you diagnose what's happening. Chris On 02/25/2011 11:05 AM, Kevin Burton wrote: What is the syntactic sugar? I thought I was following http://www.tramontana.co.hu/wix/lesson4.php#4.2 So the question is why doesn't this work (what am I missing)? And, is there a better way? For reference here is the WiX code that I am using: Property Id=PREVIOUSVERSIONSINSTALLED Secure=yes / Upgrade Id='529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B' UpgradeVersion Minimum=1.0.0.0 Maximum=3.0.0.0 OnlyDetect='no' Property=PREVIOUSVERSIONSINSTALLED IncludeMinimum=yes IncludeMaximum=no / /Upgrade . . . . . InstallExecuteSequence RemoveExistingProducts After=InstallFinalize/RemoveExistingProducts /InstallExecuteSequence Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Thursday, February 24, 2011 10:34 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. In WiX v3.5, MajorUpgrade element provides nice syntactic sugar. Otherwise, you want to look at the Upgrade element. On Thu, Feb 24, 2011 at 10:22 AM, Kevin Burtonkev...@buyseasons.comwrote: I know this is an old question but I don't know the WiX syntax for automatically uninstalling an installed product. I looked at the documentation and I got confused with Major/Minor updates/upgrades. In my case if the product is install I *always* want to uninstall it before proceeding with the installation. Any hints? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance
Re: [WiX-users] Uninstall an installed product.
Kevin, If you are doing Major upgrades, your product ID must for change whilst your Upgrade ID must remain the same. Chris On 02/25/2011 01:48 PM, Kevin Burton wrote: The product id and package id are: Product Id=9F6D788B-7A58-4750-BFEF-169FF18EE1C6... Package Id=---- .../ Since the package id is all '?' I assume that you mean I need to change the product id? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Wilson, Phil [mailto:phil.wil...@invensys.com] Sent: Friday, February 25, 2011 12:28 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Your new MSI has a new ProductCode? From that message it looks like it hasn't. Another possibility is that the PackageCode hasn't changed. Phil Wilson -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Friday, February 25, 2011 9:28 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Right now it is not automatically uninstalling the product. I am met with the dialog instructing me to go to Add/Remove Panel. Currently I am using an earlier version of WiX so I guess I am reading the right stuff in the tutorial. I am looking to try to migrate my WiX code to WiX 3.5 so I would also be interested in learning how this is done with the newer version. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Chris Lord [mailto:chris.l...@atterotech.com] Sent: Friday, February 25, 2011 11:21 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. Kevin, Lesson 4 is/was based on Wix V3. Rob's reply refers to an addition to Wix3.5 though I would expect lesson 4 code probably still applies in V3.5. Depending on which version of WiX you use will determine what options you have for writing upgrades. Now, the key is where you place the RemoveExistingProducts function as this directly affects exactly what happens. If you schedule it early in the sequence then any existing product is uninstalled in its entirety before your new version is installed. If, as you have, schedule it late in the sequence then basically what will happen is that the initial install will remain with only files that have changed being affected/changed/removed. A quick search for RemoveExistingProducts should you the location to schedule it early or late (I don't remember the location off the top of my head). Note, there are advantages and disadvantages of using it either way so you may also want to look into that and decide which suits you best. If you are having specific issues with upgrading, can you be more specific about what is, or isn't working? Creating a verbose log when you run the installer may also help you diagnose what's happening. Chris On 02/25/2011 11:05 AM, Kevin Burton wrote: What is the syntactic sugar? I thought I was following http://www.tramontana.co.hu/wix/lesson4.php#4.2 So the question is why doesn't this work (what am I missing)? And, is there a better way? For reference here is the WiX code that I am using: Property Id=PREVIOUSVERSIONSINSTALLED Secure=yes / Upgrade Id='529189FE-FD0E-44ff-8DA6-B4FB5CC7A78B' UpgradeVersion Minimum=1.0.0.0 Maximum=3.0.0.0 OnlyDetect='no' Property=PREVIOUSVERSIONSINSTALLED IncludeMinimum=yes IncludeMaximum=no / /Upgrade . . . . . InstallExecuteSequence RemoveExistingProducts After=InstallFinalize/RemoveExistingProducts /InstallExecuteSequence Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Thursday, February 24, 2011 10:34 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall an installed product. In WiX v3.5, MajorUpgrade element provides nice syntactic sugar. Otherwise, you want to look at the Upgrade element. On Thu, Feb 24, 2011 at 10:22 AM, Kevin Burtonkev...@buyseasons.comwrote: I know this is an old question but I don't know the WiX syntax for automatically uninstalling an installed product. I looked at the documentation and I got confused with Major/Minor updates/upgrades. In my case if the product is install I *always* want to uninstall it before proceeding with the installation. Any hints? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -- Free Software Download: Index, Search
Re: [WiX-users] Uninstall an installed product.
In WiX v3.5, MajorUpgrade element provides nice syntactic sugar. Otherwise, you want to look at the Upgrade element. On Thu, Feb 24, 2011 at 10:22 AM, Kevin Burton kev...@buyseasons.comwrote: I know this is an old question but I don't know the WiX syntax for automatically uninstalling an installed product. I looked at the documentation and I got confused with Major/Minor updates/upgrades. In my case if the product is install I *always* want to uninstall it before proceeding with the installation. Any hints? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: David Watson [mailto:dwat...@sdl.com] Sent: Wednesday, February 23, 2011 11:28 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Command line installation? Hi, To set a property from the command line you simply just set the property to be equal to the required value. e.g. Msiexec /i installer.msi FULLYQUALIFIEDCOMPUTERNAME= Kevinspc.buyseasons.com SERVICEUSER=bob etc. Remember to make all your properties public my making them all CAPS to and you may need to set them to be secure, set any password properties to hidden to remove them from logs. You should be able to condition the display of your dialogue based on the properties that you have stated but it is also possible to run the msi without any ui at all by altering the command line with /qn. dave -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: 23 February 2011 15:08 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Command line installation? I would like to know what strategies are best to use if I optionally don't want a UI. Right now I have a custom dialog that appears and it sets a number of properties. If any of these properties are set on the command line I would like to skip the dialog. That is one question. The second question is how do I set the properties on the command line? If it helps the dialog is defined as ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Fragment UI Property Id=FULLYQUALIFIEDCOMPUTERNAME Hidden=yesdevbrain03/Property Property Id=SERVICEUSER Hidden=yesuser/Property Property Id=SERVICEPASSWORD Hidden=yestesting/Property Property Id=SQLSERVER Hidden=yescomputer/Property Property Id=TRANSACTIONSSQLSERVER Hidden=yescomputer/Property Property Id=REPLICATEDTRANSACTIONSERVER Hidden=yescomputer/Property Property Id=INVENTORYSERVER Hidden=yescomputer/Property Property Id=SHIPPINGSERVER Hidden=yescomputer/Property Property Id=COMMERCESERVERSITENAME Hidden=yessite/Property Property Id=SMTPSERVERNAME Hidden=yesmail.company.com /Property Property Id=LYRISSQLSERVER Hidden=yesserver/Property Property Id=LYRISUSER Hidden=yesuser/Property Property Id=LYRISPASSWORD Hidden=yestesting/Property Property Id=CYBERSOURCEURL Hidden=yeshttps://myco.ic3.com/ /Property Dialog Id=PropertiesDlg Width=290 Height=390 Title=[ProductName] [ProductVersion] $(var.Configuration) NoMinimize=yes Control Id=Title Type=Text X=15 Y=6 Width=200 Height=15 Transparent=yes NoPrefix=yes Text=Ready to Install / Control Id=ComputerNameLabel Type=Text X=15 Y=26 Width=80 Height=15 Transparent=yes NoPrefix=yes Text=Computer Name / Control Id=ComputerNameEdit Type=Edit X=114 Y=22 Width=150 Height=18 Property=FULLYQUALIFIEDCOMPUTERNAME / Control Id=UserLabel Type=Text X=15 Y=46 Width=80 Height=15 Transparent=yes NoPrefix=yes Text=User / Control Id=UserEdit Type=Edit X=114 Y=42 Width=150 Height=18 Property=SERVICEUSER / Control Id=PasswordLabel Type=Text X=15 Y=66 Width=80 Height=15 Transparent=yes NoPrefix=yes Text=Password / Control Id=PasswordEdit Type=Edit X=114 Y=62 Width=150 Height=18 Property=SERVICEPASSWORD Password=yes / Control Id=SqlServerLabel Type=Text X=15 Y=86 Width=100 Height=15 Transparent=yes NoPrefix=yes Text=BuySeasons Sql Server / Control Id=SqlServerEdit Type=Edit X=114 Y=82 Width=150 Height=18 Property=SQLSERVER / Control Id=TransactionsSqlServerLabel Type=Text X=15 Y=106 Width=100 Height=15 Transparent=yes NoPrefix=yes Text=Transactions Sql Server / Control Id=TransactionsSqlServerEdit Type=Edit X=114 Y=102 Width=150 Height=18 Property=TRANSACTIONSSQLSERVER / Control Id=ShippingSqlServerLabel Type=Text X=15 Y=126 Width=100 Height=15 Transparent=yes NoPrefix=yes Text=Shipping Sql Server / Control Id=ShippingSqlServerEdit Type=Edit X=114 Y=122 Width=150 Height=18 Property=SHIPPINGSERVER / Control Id=ReplicatedTransactionsSqlServerLabel Type=Text X=15 Y=146 Width=100 Height=15 Transparent=yes NoPrefix=yes Text=Replicated Sql Server / Control Id=ReplicatedTransactionsSqlServerEdit
