Hi, In theory (productive usage not yet) I did some similar for an installer. The huge asset is e.g. for a wow64 application only containing device drivers for x86 and x64 the saving e.g. for a CD shipping both versions is enormous here. When a bundling technique is used the customers can download only one package and start the needed version of the installation. In fact our technical support is also confronted with issues from customers where they download e.g. the x86 version but actually need the x86 package.
Here I think a bootstrapper or also a CD browser might offer the needed functionality for extracting and running the needed package (x86 or x64). Possible bootstrapper solutions might be DotNetInstaller, the upcoming BURN, SharpSetup, MSI Factory bootstrapper creator or some self created things e.g. using NSIS. Such a solution was also implemented using an internal Burn version for .Net Framework 4.0. Regards Tobias 2010/12/3 Sean Farrow <sean.far...@seanfarrow.co.uk>: > 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
