Sorry to revive such an old thread, but I'm having some troubles with a very
similar situation as the one I previously described.
I ended up going with Rob's first suggestion - the Bundle has A.msi, B.msi,
C.msi, B.msp, and C.msp (B.msi and C.msi are not embedded and not included).
So far we
Sorry to open a such an old thread, but I'm having some troubles with a very
similar situation as the one I previously described.
I ended up going with Rob's first suggestion - the Bundle has A.msi, B.msi,
C.msi, B.msp, and C.msp (B.msi and C.msi are not embedded and not included).
So far we
Of course, as soon as I write this I figure it out. Ignore please...
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Chaining-MSPs-tp7591695p7594242.html
Sent from the wix-users mailing list archive at Nabble.com.
There are a couple options.
1. One include the original B and C MSIs *plus* the new B and C MSPs in the
updated Burn. Burn will only download the B and C MSIs if they are missing and
Burn will slipstream the MSPs when possible.
2. Make the new Bundle a patch bundle.
-Original Message-
robmen wrote
1. One include the original B and C MSIs *plus* the new B and C MSPs in
the updated Burn. Burn will only download the B and C MSIs if they are
missing and Burn will slipstream the MSPs when possible.
This seems to work and give me the desired behavior. Thanks!
I also just found
FYI: That feature request on SF now lives at http://wixtoolset.org/issues/3962/.
Date: Fri, 10 Jan 2014 13:35:30 -0800
From: kelly.gr...@toltech.net
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Chaining MSPs
robmen wrote
1. One include the original B and C MSIs *plus
6 matches
Mail list logo