discussion about the WiX toolset.
Subject: Re: [WiX-users] MajorUpgrade element problems
FYI there is not an attachment.
This is how I used to do it before my requirements changed...
will upgrade 1.1.1.1 to 1.1.2.1 and not allow a downgrade.
keep the Upgradecode static and the product/Package Ids
change the upgrade guid.
-Original Message-
From: Przemyslaw Galera [mailto:p.gal...@indigovision.com]
Sent: 04 June 2014 10:02
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] MajorUpgrade element problems
Hello,
Thank you very much for your response.
What hasn't
...@indigovision.com]
Sent: 04 June 2014 10:02
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] MajorUpgrade element problems
Hello,
Thank you very much for your response.
What hasn't been asked explicitly is: Can I use a MajorUpgrade element and
prevent the Software from upgrading
Solutions
-Original Message-
From: David Watson [mailto:dwat...@sdl.com]
Sent: 04 June 2014 10:39
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] MajorUpgrade element problems
If you want to block the installation you can use the upgradeVersion element
with OnlyDetect
I am new 2 wix.
I tried using burn but it is not generating the wixobj file. Below is the
bundle I am trying to create. Is there anything wrong in this. I already have
my two .msi's in sourcefile path. In the upgrade code I created a new GUID.
?xml version=1.0?
Wix
...@indigovision.com
www.indigovision.com
Complete IP Video Security Solutions
-Original Message-
From: David Watson [mailto:dwat...@sdl.com]
Sent: 04 June 2014 10:39
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] MajorUpgrade element problems
If you want
discussion about the WiX toolset.
Subject: Re: [WiX-users] MajorUpgrade element problems
You may not realize that you can have multiple Upgrade elements. So you can
forget the MajorUpgrade and do something like this, off the top of my head:
Property Id=PREVIOUSVERSIONSINSTALLED Secure=yes / Upgrade
Id
...@gmail.com]
Sent: 04 June 2014 15:20
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] MajorUpgrade element problems
You may not realize that you can have multiple Upgrade elements. So you can
forget the MajorUpgrade and do something like this, off the top of my head
: Phil Wilson [mailto:phildgwil...@gmail.com]
Sent: 04 June 2014 16:08
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] MajorUpgrade element problems
Ok, but I think somebody may have already mentioned that you can't upgrade from
2.0.0.1 to 2.0.0.5 because Windows Installer
: [WiX-users] MajorUpgrade element problems
Ok, but I think somebody may have already mentioned that you can't upgrade
from 2.0.0.1 to 2.0.0.5 because Windows Installer upgrades use only the first
3 fields of the version. You can't use upgrade elements or majorupgrade for
this reason
Message-
From: Phil Wilson [mailto:phildgwil...@gmail.com]
Sent: 04 June 2014 17:12
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] MajorUpgrade element problems
I'll repeat the part that says you can't do any kind of major upgrade unless
you change your version in the first
discussion about the WiX toolset.
Subject: Re: [WiX-users] MajorUpgrade element problems
There is one option, you can set AllowSameVersionUpgrades that will allow
1.0.0.0 to be upgraded to 1.0.0.1 but (and it is a big but) it will also make
1.0.0.1 upgrade to 1.0.0.0 which is dangerous
Hi there!
I have a terrible problem with using the MajorUpgrade element in the current
installer we have. We tended to use the Upgrade element having different error
messages for different versions by using UpgradeVersion property.
We wanted this behaviour to persist and to force the Major
FYI there is not an attachment.
This is how I used to do it before my requirements changed...
will upgrade 1.1.1.1 to 1.1.2.1 and not allow a downgrade.
keep the Upgradecode static and the product/Package Ids to *
I use a config.wxi file that I include into product.wxs then reference the
Meant maybe try to explain why you are getting downgrading between builds
with no errors - from 2.3.4.6 to 2.3.4.2 Got ahead of myself.
J
On Mon, Jun 2, 2014 at 3:15 PM, Jeremiahf jeremi...@gmail.com wrote:
FYI there is not an attachment.
This is how I used to do it before my
Meant maybe try to explain why you are getting downgrading between builds
with no errors - from 2.3.4.6 to 2.3.4.2 Got ahead of myself.
As far as MSI is concerned, those 2 version numbers are the same. MSI only
looks at the first 3 parts.
16 matches
Mail list logo
