Regarding the initial question for me WOW64 deployment frequently was
a choice where x86 or x64 assemblies are deployed based on VersionNT64
or (Not VersionNT64).

But in daily work I also tend to do the splitting of one solution into
2 MSI packages as in my experience this got frequently needed at later
stages of deployment projects. Possible configurations to simplify
customeers' life could be:

- BootstrapperEXE for chosing x86 or x64 MSI
- BootstrapperEXE for applying an x64 MST on a x86 MSI if running on
x64 (as described by mistoll)

For optimizing disk space possible optimization is: 3 cab files, one
with shared files one with x64 and one with x86 files:
See e.g.
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/cabbing-for-both-32-64-bit-files-td5797219.html
or
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/using-trhe-same-cab-between-two-different-configurations-td5594268.html



2011/5/13 mistoll <unwicht...@mistoll.de>:
> As already pointed out MSI does not support mixed x86 and x64 installers. If
> you need a x64 installation explicitely, you can
> Daniel Madill wrote:
>> make a 32-bit and 64-bit installation from the same installer source. But
>> that gives you two files.
>
> In addition to that you can use torch to create a transform file and use a
> bootstrapper like burn to call the msi according to OS.
>
> Here's a fragment to clearify the idea. Please note that the ProductSearch
> is required in order to have a correct behavior.
>
>
> <Fragment>
>    <util:ProductSearch Guid="$(var.ProductCode)" Variable="Installed"/>
>    <PackageGroup Id="MyPackage">
>      <MsiPackage Id="MyPackage_32"
>                  SourceFile="Setup_x86.msi"
>                  Vital="yes"
>                  InstallCondition="Installed OR NOT VersionNT64"/>
>      <MsiPackage Id="MyPackage_64"
>                 SourceFile="Setup_x86.msi"
>                 Vital="yes"
>                 InstallCondition="Installed OR VersionNT64">
>        <MsiProperty Name="TRANSFORMS" Value="Setup_x64.mst" />
>        <Payload Name="Setup_x64.mst"/>
>      </MsiPackage>
>    </PackageGroup>
> </Fragment>
>
>
>
> Michael
>
>
> --
> View this message in context: 
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/single-msi-for-32-bit-and-64-bit-tp6358749p6360058.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Achieve unprecedented app performance and reliability
> What every C/C++ and Fortran developer should know.
> Learn how Intel has extended the reach of its next-generation tools
> to help boost performance applications - inlcuding clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>

------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to