Several of us seem to be having difficulty regarding conditions. I know there are numerous articles and posts on this topic and I have been there... read those, but just have not gotten my brain wrapped around this concept. Perhaps it needs to be explained from another perspective or the explanation expanded in some way.
Johannes: what happens in your scenario and what do you expect (or desire) instead? Does the verbose log indicate the states of the packages that you expect? Do the command lines do what you want if you run them manually?
rguggisberg: which parts are still confusing? Is it the logic tree aspect with the condition groups, the conditions themselves (how do I check a registry key for something), and/or the way you use them in various locations (eligibility, detection, feature, exit)?
The EXE, where the version is checked and the EXE, which is part of the installation, which I'm starting, are not the same. The EXE in the Install Operation is started, when the check EXE doesn't exist. But the EXE in the Build Operation isn't startet, if a check EXE with a file version less than 2... exists. I hope the help text to Modify Operation ( Chapter 1, sentence 2: "The Modify Operation is applicable...installed.") is correct.
If your hint to "verbose log" belongs to the suite runtime, I need help, where to control the logging.
If I understand what you're describing correctly, you've set up your package to be eligible only if a given exe is on the machine with a version less than 2.0.0.1. However it is detected as present on the machine if that exe is present at any version. I'm not quite sure what you want this to do, but I think you may have it reversed. Instead detection should require a version match (or a version range match); eligibile should be either the file's missing or it has a low enough version (a range including what you will install).
This might look like Detection: All File Exists: Path=xxx.exe File Comparison: Path=xxx.exe, Conversion=Version, Comparison=GreaterEqual, Value=1.0.0.0
