Probably, except that there were some reasons why I decided against dotNetInstaller. In the end, given that I had only one prereq (DOTNETFX 2.0), I used the VS2008 bootstrapper because it's supported by Microsoft; seems to work well at what it does. Also works with MSBuild. If I replace this with something I'm guessing it might be something like Burn, since that has the backing and expertise of Microsoft employees; if Burn is anything like the quality of WiX itself I expect it to be top-notch.
-----Original Message----- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Friday, December 03, 2010 16:40 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] cabbing for both 32-64-bit files Wouldn't it be simpler to have 1 executable that does all the work for you rather than this chain of executables ending in MSI's? dotnetinstaller (http://dotnetinstaller.codeplex.com/) for example could simplify that whole convoluted process to 1 executable containing both your MSI's & all your cab files. Palbinder Sandher Software Deployment & IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the <Virtual Environment>** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -----Original Message----- From: James Johnston [mailto:johnst...@inn-soft.com] Sent: 03 December 2010 16:06 To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] cabbing for both 32-64-bit files Right; it comes in a self-extracting EXE that then launching the VS2008 bootstrapper. The generated VS2008 bootstrapper EXEs have the MSI name embedded in them so there are two VS2008 bootstrapper EXEs: one for each MSI. I wrote a custom program in C that the self-extracting EXE launches. This app determines which VS2008 bootstrapper EXE to start based on the platform. Also it moves the setup files to a different temp directory to avoid trying to delete setup files that are still in use (see issue where VS2008 bootstrapper returns immediately instead of waiting for the app to finish installing). -----Original Message----- From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk] Sent: Friday, December 03, 2010 05:20 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] cabbing for both 32-64-bit files Hi James: Thanks for this, I'm assuming you then used a bundle to deal with the extraction/running the msi? Cheers Sean. -----Original Message----- From: James Johnston [mailto:johnst...@inn-soft.com] Sent: 02 December 2010 22:01 To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] cabbing for both 32-64-bit files I wanted a unified self-extracting EXE for both 32- and 64-bit versions. What I wound up doing was this: 1. The build script combined with WiX conditional compilation / preprocessor was used to compile to two different MSI files: one 32-bit and one 64-bit. Each was compiled individually. (For example, 32-bit MSI has a launch condition preventing use on 64-bit Windows). 2. Files that are shared go into a common external cabinet file. Because they are shared, each variation of the build script compile/link should produce the same CAB file. I use a diff command just to make sure this is the case before merging the 32-bit and 64-bit build output directories. 3. Files that are not shared go into two cabinets: one for 32-bit files to go with 32-bit MSI, and one for 64-bit files to go with 64-bit MSI. Again, the preprocessor is used to make this happen. The final layout looks something like: MyApp.cab MyApp_x64.cab MyApp_x86.cab MyApp_x64.msi MyApp_x86.msi In my case, the application is 32-bit but I had to split the install like this due to driver-related reasons. -----Original Message----- From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk] Sent: Thursday, December 02, 2010 19:02 To: wix-users@lists.sourceforge.net Subject: [WiX-users] cabbing for both 32-64-bit files Hi: I'm currently building an instasllation that will eventually go on to 32 and 64 bit machines.How would people handle the fact that I have some files only referenced by either the 32-bit/64-bit install (mainly com servers) and then other files referenced by both. Should I use separate cab files? Cheers Sean. ------------------------------------------------------------------------ ---- -- Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------ ---- -- Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------ ---- -- Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------ ------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
