Hi Daniel, We had the exactly same problem. What we did to solve is, we created a second bootstrapper project called PrereqBootstrapper with the following content in Bundle.wxs (most of it is copied from the Wix NetFxExtension):
<Wix xmlns="http://schemas.microsoft.com/wix/2006/wi";> <Bundle Name="PrereqBootstrapper" Version="1.0.0.0" Manufacturer="Microsoft?" UpgradeCode="put your upgradecode here"> <BootstrapperApplicationRef Id="WixStandardBootstrapperApplication.RtfLicense" /> <?define NetFx40WebLink = http://go.microsoft.com/fwlink/?linkid=182805 ?> <?define NetFx40RedistLink = http://go.microsoft.com/fwlink/?LinkId=247729 ?> <?define NetFx40ClientWebLink = http://go.microsoft.com/fwlink/?linkid=182804 ?> <?define NetFx40ClientRedistLink = http://go.microsoft.com/fwlink/?LinkId=247730 ?> <?define NetFx40EulaLink = http://go.microsoft.com/fwlink/?LinkID=188993 ?> <Chain> <ExePackage InstallCommand="/q /norestart" PerMachine="yes" Id="WIC" Vital="yes" Permanent="yes" SourceFile="..\windows_imaging_component\wic_x86_deu.exe" /> <ExePackage InstallCommand="/q /norestart" RepairCommand="/q /norestart" UninstallCommand="/uninstall" PerMachine="yes" DetectCondition="NETFRAMEWORK40" Id="NetFx40ClientWeb" Vital="yes" Permanent="yes" Protocol="netfx4" DownloadUrl="$(var.NetFx40ClientWebLink)" Compressed="no" Name="redist\dotNetFx40_Client_setup.exe" After="WIC"> <RemotePayload Size="889416" Version="4.0.30319.1" ProductName="Microsoft .NET Framework 4 Client Profile" Description="Microsoft .NET Framework 4 Client Profile Setup" CertificatePublicKey="672605E36DD71EC6B8325B91C5FE6971390CB6B6" CertificateThumbprint="9617094A1CFB59AE7C1F7DFDB6739E4E7C40508F" Hash="06BECADB92A5FCCA2529C0B93687C2A0C6D0D610"/> </ExePackage> </Chain> </Bundle> </Wix> Afterwards we added this to our main bootstrapper: <Chain> <PackageGroupRef Id='Prereq' /> <your packages here/> </Chain> </Bundle> <Fragment> <WixVariable Id="WixMbaPrereqPackageId" Value="Prereq" /> <WixVariable Id="WixMbaPrereqLicenseUrl" Value="$(var.NetFx40EulaLink)" /> <PackageGroup Id="Prereq"> <ExePackage InstallCommand="/q /norestart /ChainingPackage "[WixBundleName]"" RepairCommand="/q /norestart /repair /ChainingPackage "[WixBundleName]"" UninstallCommand="/uninstall /q /norestart /ChainingPackage "[WixBundleName]"" DetectCondition="NETFRAMEWORK40" PerMachine="yes" Id="Prereq" Vital="yes" Permanent="yes" SourceFile="..\PrereqBootstrapper.exe"/> </PackageGroup> </Fragment> I have tested this in a Windows Server 2003 R2 environment and it installed both, WIC and .NET4. It still has a problem, though: The progress isn't shown correctly in UI. Maybe you can figure this out yourself and let me know if you find the solution. Best regards, Sabine Frauenhoffer Release Engineer -------------------------------------------------------------- Haufe-Lexware GmbH & Co. KG Munzinger Str. 9, D-79111 Freiburg Tel: +49 761 898-5385 E-Mail: sabine.frauenhof...@haufe-lexware.com Internet: http://www.haufe-lexware.com -------------------------------------------------------------------- Kommanditgesellschaft, Sitz und Registergericht Freiburg, HRA 4408 Komplementäre: Haufe-Lexware Verwaltungs GmbH, Sitz und Registergericht Freiburg, HRB 5557; Martin Laqua Geschäftsführung: Isabel Blank, Jörg Frey, Birte Hackenjos, Jens Köhler, Matthias Mühe, Markus Reithwiesner, Joachim Rotzinger, Dr. Carsten Thies Beiratsvorsitzende: Andrea Haufe -------------------------------------------------------------- » http://www.haufe.de/shop « -------------------------------------------------------------- -----Ursprüngliche Nachricht----- Von: Daniel Bruce [mailto:daniel.br...@prediktor.no] Gesendet: Montag, 8. Oktober 2012 09:31 An: General discussion for Windows Installer XML toolset.(wix-users@lists.sourceforge.net) Betreff: [WiX-users] WIC as a prereq before .NET 4.0 in Burn with custom BA Hello, We are attempting to roll out a managed bootstrapper that depends on .NET 4.0. On some platforms this requires WIC (Windows Imaging Component) to be installed prior to running the .NET 4.0 installer, which is giving us some issues. We have tried to solve this issue in a few ways, but none have worked, so I posted to stack overflow about it. Nobody has responded so far, so I'm crossposting here to see if anybody has any input. If so, it would be nice if you could take a look at the SO question, which has all the details, and perhaps shoot me an answer either there or here. http://stackoverflow.com/questions/12727583/adding-wic-as-a-requirement-before-net-4-0-in-wix-burn-custom-managed-bootstrap Daniel E. Bruce Software Developer, +47 91918893 Prediktor AS Habornveien 48B, N-1630 Gamle Fredrikstad, Norway ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
