;m missing...)
> Date: Thu, 28 Nov 2013 13:39:39 -0500
> From: michael.ogil...@pixelink.com
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Upgrades
>
> Hello Phil,
>
> Thanks for the info.
>
> >From the log files it looks like it uninstalls the stuff tw
gilvie
-Original Message-
From: Phill Hogland [mailto:phogl...@rimage.com]
Sent: Wednesday, November 27, 2013 10:54 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Upgrades
Generally yes, although you might not specify all of those attributes.
Each
MSI needs some infor
Generally yes, although you might not specify all of those attributes. Each
MSI needs some information instructing it how to process upgrades, which is
independent of how the MSI is launched, as part of a bundle chain or
directly.
--
View this message in context:
http://windows-installer-xml-w
Thanks Rob Thought so...
Steve Ogilvie “Our lives begin to end the day we become silent about
things that matter.”, Dr. Martin Luther King Jr. Sent from my Black
That's just setting a bunch of properties. If you don't use the properties,
you don't need all that. MajorUpgrade element is all you need (plus change
Product/@Id and do not change Product/@UpgradeCode).
On Tue, Apr 2, 2013 at 6:01 AM, StevenOgilvie wrote:
> Hi folks,
>
> I have a few installer
Windows Installer XML toolset.
Subject: Re: [WiX-users] Upgrades NOT working on a new install
Not sure what you mean by extra code, this is what an upgrade looks like. Using
afterInstallValidate will uninstall and then install, using afterInstallExecute
will replace files (not a good
/ and
http://www.joyofsetup.com/2010/01/16/major-upgrades-now-easier-than-ever/ )
Neil
-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
Sent: 20 December 2012 21:53
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Upgrades NOT
I am not sure why you would need this, it is not something I have needed.
-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
Sent: 20 December 2012 21:39
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Upgrades NOT working on a
s code for sure :)
Steve
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: December-20-12 4:08 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Upgrades NOT working on a new install
Correction - use it will be
simpler.
What about the
CA: Setting REINSTALLMODE to
amus...
Is that required?
Steve
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: December-20-12 4:08 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Upgrades
Correction - use it will be
simpler.
-Original Message-
From: Neil Sleightholm
Sent: 20 December 2012 21:06
To: General discussion for Windows Installer XML toolset.
Subject: RE: [WiX-users] Upgrades NOT working on a new install
Use
- Product/@Id="*"
- Remove the Id fr
r to debug.
Neil
-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
Sent: 20 December 2012 19:26
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Upgrades NOT working on a new install
Okay,
I now have:
Whe
>> From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
>> Sent: Thursday, December 20, 2012 12:13 PM
>> To: General discussion for Windows Installer XML toolset.
>> Subject: Re: [WiX-users] Upgrades NOT working on a new install
>>
>> Okay I changed the
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Upgrades NOT working on a new install
>
> Okay I changed the ProductCode to be "*" as well as the Package Id="*"
> First MSI had a version number of 4.0.1.25 second MSI has
ndows Installer XML toolset.
> Subject: Re: [WiX-users] Upgrades NOT working on a new install
>
> Okay I changed the ProductCode to be "*" as well as the Package Id="*"
> First MSI had a version number of 4.0.1.25 second MSI has a version number
> of 4.1.2
newer MSI has a different version number
(higher) and the ProductCode is different...
Steve
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: December-20-12 2:55 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users]
x: 503-617-0291
www.fiserv.com
> -Original Message-
> From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
> Sent: Thursday, December 20, 2012 11:26 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Upgrades NOT working on a new ins
[mailto:n...@x2systems.com]
Sent: December-20-12 1:47 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Upgrades NOT working on a new install
You seem to have the MajorUpgrade element and also the Upgrade element,
MajorUpgrade replaces the need for manually aut
You seem to have the MajorUpgrade element and also the Upgrade element,
MajorUpgrade replaces the need for manually authoring the upgrade table. Also,
I wouldn't hard code Product/@Id just use "*" and have WiX generate it for you,
likewise Package/@Id isn't required just let WiX do it.
Neil
--
Changing the GUID of your component makes no difference to anything in
your example. Your code is telling the Windows Installer to uninstall
any old version of your software before it installs the current version.
If this is the only way your installers will work then your GUIDs can be
the same or
Two thoughts that I have.
1. Your SetCAP_RestoreWebConfig custom action is sequenced at 265. Has the TargetDir property been determined by Windows Installer at this point? If it hasn't, then you're going to be getting a blank TargetDir value. I"m not real sure of when that happens, but that
[EMAIL PROTECTED] wrote:
> I have an MSI file with a user-interface that gives the choice to install for
> all users or only for current user. When the user installs a new version of
> the product there should be the choice to remove the older version or to
> continue with installation and insta
22 matches
Mail list logo
