Hi, I have written a ManagedBootstrapperApplication that requires .net 4.0.
On Windows 2003 and XP, this requires the Windows Imaging Component, so I've used another Burn bootstrapper to install the appropriate prerequisites as per this post: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WIC-as-a-prereq-before-NET-4-0-in-Burn-with-custom-BA-td7581202.html. The ExePackage with the prerequisite in is: <ExePackage Id="netfx40full" DisplayName=".NET Framework 4.0 Full Profile" Description="Installs .NET Framework 4.0" SourceFile="$(var.InstallNetFx40.TargetDir)InstallNetFx40.exe" Name="InstallNetFx40.exe" DetectCondition="netfx40full_Version >= v4.0.30129" InstallCommand="/q /norestart /ChainingPackage "[WixBundleName]"" Protocol="burn" Permanent="yes"> <Payload Id="netfx40wicx86" Name="Windows Imaging Component\wic_x86_enu.exe" SourceFile="$(var.InstallNetFx40.TargetDir)Windows Imaging Component\wic_x86_enu.exe"/> <Payload Id="netfx40wicx64" Name="Windows Imaging Component\wic_x64_enu.exe" SourceFile="$(var.InstallNetFx40.TargetDir)Windows Imaging Component\wic_x64_enu.exe"/> <Payload Id="netfx40netfx40" Name="net Framework\dotNetFx40_Full_x86_x64.exe" SourceFile="$(var.InstallNetFx40.TargetDir)net Framework\dotNetFx40_Full_x86_x64.exe"/> </ExePackage> On Windows 7, installing .net 4.0 requires a reboot. The .net 4.0 installer returns an exit code of 3010, which the prerequisite bootstrapper correctly interprets as requiring a reboot as per this log: [06C0:0680][2012-11-23T12:19:14]: Applying execute package: netfx40full, action: Install, path: C:\ProgramData\Package Cache\58DA3D74DB353AAD03588CBB5CEA8234166D8B99\net Framework\dotNetFx40_Full_x86_x64.exe, arguments: '"C:\ProgramData\Package Cache\58DA3D74DB353AAD03588CBB5CEA8234166D8B99\net Framework\dotNetFx40_Full_x86_x64.exe" /q /norestart /ChainingPackage "InstallNetFx40"' [05E8:06A0][2012-11-23T12:22:06]: Applied execute package: netfx40full, result: 0x0, restart: Required [05E8:06A0][2012-11-23T12:22:06]: Apply complete, result: 0x0, restart: Required, ba requested restart: No But then exits with an exit code of 0: [05E8:06A0][2012-11-23T12:22:06]: Shutting down, exit code: 0x0 This apparent success is then picked up by the parent bootstrapper, which doesn't schedule a reboot: [09EC:09F0][2012-11-23T12:19:06]: Applying execute package: netfx40full, action: Install, path: C:\ProgramData\Package Cache\E6325500A0345B428E5575D89844DF58E23D4BA8\InstallNetFx40.exe, arguments: '"C:\ProgramData\Package Cache\E6325500A0345B428E5575D89844DF58E23D4BA8\InstallNetFx40.exe" /q /norestart /ChainingPackage "Permasense Package 11"' [0938:093C][2012-11-23T12:22:06]: Applied execute package: netfx40full, result: 0x0, restart: None [0938:093C][2012-11-23T12:22:06]: Apply complete, result: 0x0, restart: None, ba requested restart: No Is this expected behaviour, or is it something that's fixed in 3.7? I don't particularly want to write an unmanaged BA... Nicholas ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
