I suspect I'm "stuck" but thought I'd ask.
I have two existing MSIs, call them "Base.msi" and "Dell.msi". They install
separate facets of my product - the base files, then additional files
needed to support particular Dell hardware.
I now want to create a new single MSI that replaces "Base.msi" a
;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
Do you need to include this " " in
each MSI if you wrap all of the MSI's in a burn bundle?
Thank you,
Michael Ogilvie
--
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't hav
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
Hi folks,
I have a few installers that I am writing in WIX 3.7
I was just using:
To handle upgrades (uninstall older version, install new version)
I saw a blog on upgrades and they recommended doing the below, my question
is, do I need to add all that??
NOT Installed AND N
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
let WiX do it.
Neil
-Original Message-
From: StevenOgilvie [mailto:sogil...@msn.com]
Sent: 20 December 2012 18:26
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Upgrades NOT working on a new install
Hi all,
I have implemented upgrades by doing the following (I have an includ
Hi all,
I have implemented upgrades by doing the following (I have an include file
that has the product/package properties which I define and include the
include file :)...
then:
where I have the following defined:
and have a productcode and upgradecode that I don't change...
c
uk]
Sent: 09 March 2009 13:37
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Upgrades
The code below clears out previous versions for me.
...
...
...
I ran a test where I went from Version 1.0.3.0 to 1.0.4.
The code below clears out previous versions for me.
...
...
...
I ran a test where I went from Version 1.0.3.0 to 1.0.4.0. In the
1.0.3.0 version the root directory contained 3 files Default.aspx,
Web.Config and TextFil
I've got a program that I need to upgrade. I saw a post here, which I
thought explained how to do it.
However, for every "upgrade" I perform, it shows up as a new entry in the
Add/Remove Programs.
I've included what I think is the relevant markup. Thanks in advance for
any insight.
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
Hey all,
I'm trying to implement handling for major upgrades for a web application
installation.
The use case I'm currently testing is:
1. User installs v1.0.0 of the application
- Install gathers information about the virtual
directory and database server
- App is inst
[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
Hi,
I have a known problem with major upgrades and just want to be sure that there
is really no solution for it.
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
30 matches
Mail list logo
