I've been following this discussion for the last day or so because I'm attempting something very similar. I have multiple MSIs that I would like to be installed as a single user experience ... just as the documentation says. However, I haven't been able to even get a bundle project to run. I get an error message "This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package".
Here is a simple setup project right out of the documentation which does run on its own. <?xml version="1.0" encoding="UTF-8"?> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi";> <Product Id="*" Name="SetupProject1" Language="1033" Version="1.0.0.0" Manufacturer="Me" UpgradeCode="9568A4E8-36E0-4266-9266-4F4C8C5E889F"> <Package InstallerVersion="200" Compressed="yes" InstallScope="perMachine" /> <MajorUpgrade DowngradeErrorMessage="A newer version of [ProductName] is already installed." /> <MediaTemplate /> <Feature Id="ProductFeature" Title="SetupProject1" Level="1"> <ComponentGroupRef Id="ProductComponents" /> </Feature> </Product> <Fragment> <Directory Id="TARGETDIR" Name="SourceDir"> <Directory Id="ProgramFilesFolder"> <Directory Id="INSTALLFOLDER" Name="SetupProject1" /> </Directory> </Directory> </Fragment> <Fragment> <ComponentGroup Id="ProductComponents" Directory="INSTALLFOLDER"> <Component Id="ProductComponent"> <File Id="filLicense.rtf" Source="License.rtf" KeyPath="yes"/> </Component> </ComponentGroup> </Fragment> </Wix> Here is the bundle project which does not run. <?xml version="1.0" encoding="UTF-8"?> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi"; xmlns:bal="http://schemas.microsoft.com/wix/BalExtension";> <Bundle Version="1.0.0.0" UpgradeCode="{F6A26A26-F26B-44A8-A8D5-9A529815FBF1}"> <BootstrapperApplicationRef Id="WixStandardBootstrapperApplication.RtfLicense"> <bal:WixStandardBootstrapperApplication LicenseFile="License.rtf" /> </BootstrapperApplicationRef> <Chain> <PackageGroupRef Id="MyPackage"/> </Chain> </Bundle> <Fragment> <PackageGroup Id="MyPackage"> <MsiPackage SourceFile="$(var.SetupProject1.TargetPath)"> </MsiPackage> </PackageGroup> </Fragment> </Wix> Itrel Monroe Senior Software Engineer The information contained in this communication including any attachments is intended solely for the use of the individual(s) to whom it is addressed. This communication may contain information that is privileged, confidential and exempt from disclosure under applicable law. Any review, retransmission, dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this email in error, please notify the sender and delete the material from any computer. No printed copies should be made or retained. Thank you for your cooperation. -----Original Message----- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Wednesday, June 20, 2012 10:52 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Chaining 2 msi's An MSI cannot install another MSI. On Wed, Jun 20, 2012 at 7:33 AM, Dan Muller <dmuller...@comcast.net> wrote: > Yeah, I had found that link and it was not the most useful, I > eventually found some references and learned from them. > > I got a bundled exe, but I was wondering if there was a way to create > a bundled msi instead? > Also, can someone point me to a tutorial on changing the burn UI? > > > <?xml version="1.0" encoding="UTF-8"?> <Wix > xmlns="http://schemas.microsoft.com/wix/2006/wi";> > <Bundle Name="Bundle" Version="" Manufacturer="" UpgradeCode=""> > <BootstrapperApplicationRef > Id="WixStandardBootstrapperApplication.RtfLicense" /> > <Chain> > <MsiPackage > Id="INTELC_INSTALLER" > SourceFile="C:\path\to\Installer.msi" > Compressed="no" > EnableFeatureSelection="no" Vital="yes" > > <MsiProperty Name="ALLUSERS" Value="1"/> > </MsiPackage> > <MsiPackage > Id="INTELC_CODE" > SourceFile="C:\spath\to\Installer2.msi" > Compressed="no" > EnableFeatureSelection="no" Vital="yes" > > <MsiProperty Name="ALLUSERS" Value="1"/> > </MsiPackage> > </Chain> > </Bundle> > </Wix> > > > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Chaining > -2-msi-s-tp7578938p7578969.html Sent from the wix-users mailing list > archive at Nabble.com. > > > ---------------------------------------------------------------------- > -------- > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. > Discussions will include endpoint security, mobile security and the > latest in malware threats. > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- virtually, Rob Mensching - http://RobMensching.com LLC ---------------------------------------------------------------------------- -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
