No, we didn't package up the imaging component. I think this issue only arises on Windows XP 64 bit (and Server 2003, I believe) which are a small percentage of our target installs, so for those few we just wanted a better error message than the one given by the visual studio bootstrapper. I've never liked the way it bundles up all the eulas and then kicks of a passive install much anyway. I think it is possible to change some of that (as shown previously) but we just decided to switch to an alternative.
I don't think that Burn is ready for prime time yet, although looking at Rob's blog I am pleasantly surprised! Particularly the WPF UI:) :) But a Wix 3.5 release is more important (with VS2010). -Nick -----Original Message----- From: Matt Sullivan [mailto:msulli...@zaptechnology.com] Sent: 09 September 2010 08:40 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] .Net 4 bootstrapper with Windows Imaging Component Nick, How exactly did switching to the DotNetInstaller bootstrapper help you out with this? Did you manage to package the windows imaging component so the bootstrapper will install it before .Net? If so, do you have any configuration packages etc. that might be useful to share. (Sorry for the vagueness, I know next to nothing about it.) Alternately did you change the .net installer command line options so that it will show a prerequisite error? If I was going to consider switching bootstrapper it'd be tempting to try out wix's burn, but I haven't been following where it's up to, or how it compares feature wise to the DotNetInstaller. -- Matt -----Original Message----- From: Nick Ball [mailto:nick.b...@grantadesign.com] Sent: Wednesday, 8 September 2010 6:56 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] .Net 4 bootstrapper with Windows Imaging Component Hi Matt, We ran into this problem recently too. Installs were failing on XP 64 bit (no SP3, just SP2 and no windows imaging component). I felt the problem was exactly as you mentioned - we just want to launch the .Net installer with the full UI, where it reports the prerequisite error 'gracefully' rather than the unfriendly error the bootstrapper gives. We ended up switching to DotNetInstaller for bootstrapping .Net 4.0 http://dotnetinstaller.codeplex.com/ -Nick -----Original Message----- From: Matt Sullivan [mailto:msulli...@zaptechnology.com] Sent: 08 September 2010 08:20 To: General discussion for Windows Installer XML toolset.(wix-users@lists.sourceforge.net) Subject: [WiX-users] .Net 4 bootstrapper with Windows Imaging Component Hi All, I'm trying to create a bootstrapper to install .Net 4. It works fine in general, but fails with an error code 5100 on machines that don't have the "Windows Imaging Component" already installed. If you run the .Net installer separately it shows an error dialog that windows imaging is missing, however when run from the bootstrapper I presume it passes command line options that make it fail silently. I understand most machines will already have this installed, but for the sake of a few extra MB I'd like to include that in my bootstrapper/installer, however I'm running into two problems: 1. I don't have a standard windows imaging package to include. 2. I can't see any way to specify ordering in the bootstrapper prerequisites. So: * Has anyone successfully done this? * Has anyone found or written a bootstrapper manifest (product.xml, package.xml etc.) for the windows imaging component * What files should a bootstrapper manifest even include? The language specific redistributables from here http://www.microsoft.com/downloads/en/details.aspx?FamilyID=8e011506-630 7-445b-b950-215def45ddd8&displaylang=en or something closer to WIC_x86_enu.exe from the .Net 3.5 SP1 installer? * Is there any way to specify the order that bootstrapper prerequisites are installed? (I'm using wix 3.0, but looking to upgrade as soon as 3.5 is officially released.) * Failing that, is there any way to have the bootstrapper test for the dependency and fail gracefully if it's not installed? Or run the .Net installer without the command line flags that cause it to fail without an error dialog? Cheers, Matt ------------------------------------------------------------------------ ------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
