Hi Matt, First of all I never developed a .Net 4. Bootstrapper. But actually I use the InstallShield Environment with a configuration for such a bootstrapper. So in total they use the downloaded version of the client profile dotNetFx40_Client_x86_x64.exe (http://download.microsoft.com/download/5/6/2/562A10F9-C9F4-4313-A044-9C94E0A8FAC8/dotNetFx40_Client_x86_x64.exe) . This is called during bootstrapper run with parameters "/q /norestart". A reboot after installing the package is done if it returns an exit code 1641 or 3010. Windows Installer 3.1 is a prerequisite for the package installation.
As normally their configurations are good and well tested I assume this configuration should not run into the "Windows Imaging Component" issue Regards Tobias 2010/9/8 Matt Sullivan <msulli...@zaptechnology.com>: > 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-6307-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
