Re: [WiX-users] Chaining MSPs

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.

Re: [WiX-users] Chaining MSPs

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 have

Re: [WiX-users] Chaining MSPs

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 have

[WiX-users] Shortcut Icon Disappears in XP

I'm having a strange issue with an installer (using WiX and Burn). We've put out about 15 updates (all major upgrades) without any problems. Now the latest update is causing the icon on the desktop shortcut to disappear on XP (leaving us with the default windows shortcut icon). The icon is fine

Re: [WiX-users] Chaining MSPs

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 foun

[WiX-users] Chaining MSPs

I asked this question previously in an older, slightly unrelated thread but I'm thinking it might be more appropriate as its own thread. I have a bundle (lets call it Bundle 1.0) with 3 MSIs (lets say A, B, and C; also all version 1.0). Some of the content in B and C has changed, so I produced an

Re: [WiX-users] Patching strategy

We've decided to go with the approach you've suggested, and I will look into delta patches to reduce the patch size (although since most of our changed files will be videos, I would guess deltas wouldn't help much). As far as each patch superseding the last, is this something we need to specify in

Re: [WiX-users] Patching strategy

This sounds like a good way to start at least. My one concern is what happens when the accumulated patches start to get large enough to make size a concern? Lets say the original data is 2GB, and every month we need to release a patch that changes 5% of it. After 5 months we're up to a 500MB acc

[WiX-users] Patching strategy

I am implementing a new installer for a product that needs to include several GB of data. I'm planning on having a single MSI for the application, several MSIs for the data, and using burn to chain everything together. The data will change periodically and updates will be delivered online, so pat

Re: [WiX-users] Force Update of Corrupt KeyPath File

Forgot to mention, I am using WiX 3.7. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Force-Update-of-Corrupt-KeyPath-File-tp7587628p7587636.html Sent from the wix-users mailing list archive at Nabble.com.