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 haven't been releasing patches for A (since it's fairly small it's easier to just do major upgrades). We've released several updates and are now on version 1.0.5. 1.0.5 was a fairly large change, so we released it as a major update. We now want to release a fix to A (to bring it up to 1.0.6), and leave B and C alone. B and C add up to over 1GB of data (hence the reason for the patches to being with), so we obviously don't want our users to have to re-download a full update. I've tried both removing the B.msp and C.msp, and generating actual empty patches for them, but in both cases A gets updated and B and C get removed. Here is a pared down version of my wxs file: Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; ?define ProductVersion=1.0.6 ? ?define ProductName=Product ? ?define UpgradeCode=UPGRADE_GUID ? ?define Manufacturer=Company ? Bundle Name=$(var.ProductName) Version=$(var.ProductVersion) Manufacturer=$(var.Manufacturer) UpgradeCode=$(var.UpgradeCode) BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.RtfLicense bal:WixStandardBootstrapperApplication LicenseFile=$(var.AssetsPath)\License.rtf SuppressOptionsUI=yes / /BootstrapperApplicationRef Chain MsiPackage SourceFile=A.msi DisplayInternalUI=no MsiProperty Name=INSTALLFOLDER Value=[InstallFolder] / /MsiPackage MsiPackage SourceFile=B.msi DisplayInternalUI=no Compressed=no SlipstreamMsp Id=B_Patch / /MsiPackage MsiPackage SourceFile=C.msi DisplayInternalUI=no Compressed=no SlipstreamMsp Id=C_Patch / /MsiPackage MspPackage Id=B_Patch SourceFile=B_Patch.msp DisplayInternalUI=no Compressed=yes / MspPackage Id=C_Patch SourceFile=C_Patch.msp DisplayInternalUI=no Compressed=yes / /Chain /Bundle /Wix -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Chaining-MSPs-tp7591695p7594241.html Sent from the wix-users mailing list archive at Nabble.com. -- Start Your Social Network Today - Download eXo Platform Build your Enterprise Intranet with eXo Platform Software Java Based Open Source Intranet - Social, Extensible, Cloud Ready Get Started Now And Turn Your Intranet Into A Collaboration Platform http://p.sf.net/sfu/ExoPlatform ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
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 haven't been releasing patches for A (since it's fairly small it's easier to just do major upgrades). We've released several updates and are now on version 1.0.5. 1.0.5 was a fairly large change, so we released it as a major update. We now want to release a small patch to A (to bring it up to 1.0.6), and leave B and C alone. B and C add up to over 1GB of data (hence the reason for the patches to being with), so we obviously don't want our users to have to re-download a full update. Everything I've tried to do has resulted in A being updated, and B and C getting uninstalled. Here is a pared down version of my wxs file: Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; xmlns:bal=http://schemas.microsoft.com/wix/BalExtension; xmlns:util=http://schemas.microsoft.com/wix/UtilExtension; ?define ProductVersion=1.0.6 ? ?define ProductName=Product ? ?define UpgradeCode=UPGRADE_GUID ? ?define Manufacturer=Company ? Bundle Name=$(var.ProductName) Version=$(var.ProductVersion) Manufacturer=$(var.Manufacturer) UpgradeCode=$(var.UpgradeCode) BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.RtfLicense bal:WixStandardBootstrapperApplication LicenseFile=$(var.AssetsPath)\License.rtf SuppressOptionsUI=yes / /BootstrapperApplicationRef Chain MsiPackage SourceFile=$(var.MsiPath) DisplayInternalUI=no MsiProperty Name=INSTALLFOLDER Value=[InstallFolder] / /MsiPackage MsiPackage SourceFile=A.msi DisplayInternalUI=no Compressed=no SlipstreamMsp Id=A_Patch / /MsiPackage MsiPackage SourceFile=B.msi DisplayInternalUI=no Compressed=no SlipstreamMsp Id=B_Patch / /MsiPackage MspPackage Id=A_Patch SourceFile=A_Patch.msp DisplayInternalUI=no Compressed=yes / MspPackage Id=B_Patch SourceFile=B_Patch.msp DisplayInternalUI=no Compressed=yes / /Chain /Bundle /Wix -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Chaining-MSPs-tp7591695p7594240.html Sent from the wix-users mailing list archive at Nabble.com. -- Start Your Social Network Today - Download eXo Platform Build your Enterprise Intranet with eXo Platform Software Java Based Open Source Intranet - Social, Extensible, Cloud Ready Get Started Now And Turn Your Intranet Into A Collaboration Platform http://p.sf.net/sfu/ExoPlatform ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
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. -- Start Your Social Network Today - Download eXo Platform Build your Enterprise Intranet with eXo Platform Software Java Based Open Source Intranet - Social, Extensible, Cloud Ready Get Started Now And Turn Your Intranet Into A Collaboration Platform http://p.sf.net/sfu/ExoPlatform ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Chaining MSPs
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- From: KG [mailto:kelly.gr...@toltech.net] Sent: Friday, January 10, 2014 11:46 AM To: wix-users@lists.sourceforge.net Subject: [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 updated 1.0.1 MSI for B and C, and also a MSP for each. I then create Bundle 1.0.1 (a major update to Bundle 1.0 with all three updated MSIs) and BundlePatch 1.0.1 with just the patches for B and C. The behavior I would like to see would be for it not to matter if the user installs Bundle 1.0 followed by BundlePatch 1.0.1, or just Bundle 1.0.1 (i.e., new users can download and install the latest full version while current users only need the much smaller patch version). The closest I've been able to come to this is to give BundlePatch 1.0.1 a different UpgradeCode, and add in a RelatedBundle tag with Bundle's upgrade code and Patch as the action. This installs the two patches and leaves everything else the same, however, it doesn't update the version number in the Programs and Features control panel (we still see Bundle 1.0). In the Installed Updates control panel we do see BundlePatch 1.0.1 listed as an update. Most other things I have tried result in the patches getting installed, and then MSI A being uninstalled. Does anyone know if what I'm trying to do is even possible? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Chaining-MSPs-tp7591695.html Sent from the wix-users mailing list archive at Nabble.com. -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
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 found this: Bundle Version and patching http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bundle-Version-and-patching-td7579655.html#a7584962 which references Feature Request 725 http://sourceforge.net/p/wix/feature-requests/725/ . That is pretty much the problem I was having. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Chaining-MSPs-tp7591695p7591702.html Sent from the wix-users mailing list archive at Nabble.com. -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Chaining MSPs
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* 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 this: Bundle Version and patching http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bundle-Version-and-patching-td7579655.html#a7584962 which references Feature Request 725 http://sourceforge.net/p/wix/feature-requests/725/ . That is pretty much the problem I was having. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Chaining-MSPs-tp7591695p7591702.html Sent from the wix-users mailing list archive at Nabble.com. -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
