e-
> From: John Cooper [mailto:
> JoCooper@
> ]
> Sent: Friday, April 10, 2015 2:45 PM
> To: General discussion about the WiX toolset.
> Subject: Re: [WiX-users] Burn and chaining multiple MSIs and detecting
> proper states for each MSI
>
> Is A' a major or minor
Sorry Rob, I was getting confused with my question and my testing of other
solutions.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-and-chaining-multiple-MSIs-and-detecting-proper-states-for-each-MSI-tp7599891p7599951.html
Sent from the wix-
http://www.firegiant.com/
-Original Message-
From: victorwhiskey [mailto:victorhwhis...@yahoo.com]
Sent: Monday, April 13, 2015 9:24 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Burn and chaining multiple MSIs and detecting proper
states for each MSI
I'm not s
I'm not sure either. Just gasping...
Can I manually check for Version numbers and such to determine if I should
upgrade or not in the BA? Maybe from DetectPackageComplete?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-and-chaining-multipl
: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Burn and chaining multiple MSIs and detecting proper
states for each MSI
Or can I set the REINSTALLMODE MSI property to vmous or vamus of A on upgrade?
Thanks
Or can I set the REINSTALLMODE MSI property to vmous or vamus of A on
upgrade?
Thanks
victorwhiskey wrote
> Rob,
>
> The structure is similar to plugins where A is the main app and B and C
> are "plugins". We don't want to have the user have to install A
> separately, so I'm trying to bundle A
Rob,
The structure is similar to plugins where A is the main app and B and C are
"plugins". We don't want to have the user have to install A separately, so
I'm trying to bundle A (or A') with B and C. This is where I'm running into
problems where if B and C are out there, and they don't install in
...@yahoo.com]
Sent: Sunday, April 12, 2015 9:05 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Burn and chaining multiple MSIs and detecting proper
states for each MSI
John and Rob, thanks for the reply.
All MSIs are using Major Upgrades. The only relationship between B and C is
only the
John and Rob, thanks for the reply.
All MSIs are using Major Upgrades. The only relationship between B and C is
only the shared components in A or A'. And the product code is different
between A and A'.
Would using a wixlib work or be better than an MSI?
Thanks!
--
View this message in contex
---
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: Friday, April 10, 2015 2:45 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Burn and chaining multiple MSIs and detecting proper
states for each MSI
Is A' a major or minor upgrade of A?
Is the ProductCode t
sers] Burn and chaining multiple MSIs and detecting proper
states for each MSI
This is my scenario, I have 2 different bundles, B and C. They each have 2 MSIs
chained with a common MSI A or A' (a newer version of A). If I installed bundle
B which has A then I install C which has A', I&
This is my scenario, I have 2 different bundles, B and C. They each have 2
MSIs chained with a common MSI A or A' (a newer version of A). If I
installed bundle B which has A then I install C which has A', I'm expecting
B to install B and A, then C to install and upgrade A to A'. I am getting
this a
12 matches
Mail list logo
