I used the information from the following link to configure a project to
build either a 32 bit or 64 bit installer.
http://alekdavis.blogspot.com/2011/05/build-32-and-64-bit-installers-using.html
My projects are for drivers and I need to install the full driver tree
regardless of which platform is being targeted to preserve the code signing
signature. I do not use the Win64 flag (which is deprecated) but in my
project file I added the MSBuild property InstallerPlatform to each
Configuration which can be built. This sets the -arch flag for the compiler
and linker (and marks all components either 32 bit in the 32 bit package or
64 bit in the 64 bit package).
In almost all cases the Component Guid is auto-generated ('*'). The
Bootstrapper only allows the 32 bit package to be installed on a true 32 bit
platform (not on WoW64, preventing a side-by-side installation). If a
specific Component GUID is needed then I set a literal string in my wxi <?if
$(var.Platform) = x64 ?> block.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Component-GUID-rules-clarification-tp7593971p7593975.html
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees_APR
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
