just put 32-bit components in the 32-bit file system.
Fortunately in this case that is an option. Are there any
recommendations on exactly where these components should go?
We give the user a choice of install location for our 64-bit
components, which defaults to Program Files\Product Name.
ALLUSERS=2 is a valid setting.
Yes, ALLUSERS=2 is valid in general, but I'm interested to know why my
installer was perfectly happy with it - even when the source file
contained:
Condition Message=...ALLUSERS=1/Condition
As Thorsten said on his reply, don't worry too much about locking that
I have set the Package/@InstallScope attribute in my WiX source file
to perMachine. As I understand things, this sets the ALLUSERS
property to 1. This effectively causes my MSI to default to a
per-machine installation, but does not entirely prevent per-user
installs since ALLUSERS can be
Is there a recommended way to install [COM registration]
information into the 32-bit part of the registry from a 64-bit
(Win64=yes) component?
We're now thinking of registering our COM server using RegistryValue
elements, where RegistryValue/@Key contains Wow6432Node. Does anyone
know of any
We're currently building an MSI targeting the x64 platform. Most of
our binaries are 64-bit, so we have placed each one into a 64-bit
component under the ProgramFiles64Folder directory. However, we also
need to install a 32-bit COM in-process server DLL. We're having
issues because we'd ideally
I'm using the version of WixCop which shipped with the final build of
WiX v3.0, passing it a single settings file and a single source file.
If the settings file is not found, WixCop displays an error and exits
returning 1, fatal error, as expected. However, if the source file
is not found, WixCop
6 matches
Mail list logo
