Thanks for your reply!
For this I've to think about my different constellations and maybe I'll ask you againThis should not be a problem for you because even if both searches are true, only the "Visio2013 x86" version can be installed on a 32-bit machine. So, if the machine is a 32-bit one (condition NOT VersionNT64), you will be sure that the "x86" version of the Visio product is installed.
Ok. I'm a little bit unsure because I set the "Installation Behavior" for the invisible features to "Not installed" (I want handle if it should be installed) and set always a condition for "Install if" (my condition) and "Disabled if" (I set a condition for that, because I see at "More Options" the setting "When all conditions are false, use the following level"=4(complete); I'm not able to set it to 0, because I already set it to "Not installed").If a feature is invisible, then it will have the same behavior for the typical and custom installation because the user will not be able to change its state from the UI as long as it is not displayed.
Which setting has the higher priority? "Not installed" or "When all conditions are false, use the following level"?
What would be the best way for me? Set only a condition for "Install if" or for "Disabled if" too?
As you can see at the pictures, there is the option for "Mark components in this feature as '64-bit component'" (for the whole feature or single component);--- "64-bit component", because they should installed dependent on the installed Visio version
I'm afraid I do not fully understand this requirement, can you please give me more details?
should I set this option for my components that are only for Visio-x64 or for the registry keys?
If possible I don't want to use this method, please see my post before.You can search for the "Outlook Bitness" registry key to determine the Office version and for a registry entry or a file related to Visio to determine its version.
Thanks in advance