Just so my comment reads a bit more clearly I'm going to label the products. In your situation you have Product B that depends on Product A being installed. If you are also the author of Product A you can add AppSearch item to search for a specific component from Product B, use an Upgrade table entry to detect the existence of Product B or write a custom action to check for whatever criteria you want to base the detection on.
I wouldn't implement a launch condition on the uninstall. In fact, it's generally a good idea to condition the LaunchCondition action with "NOT Installed" so that once the MSI is installed the launch conditions will never prevent a repair or uninstallation. Otherwise if you ever get a bad condition the MSI can be orphaned on the machine which is very frustrating for users. If you want to just display a warning message that Product B needs Product A and they may not want to uninstall it, I would just condition a text control on one of your dialogs in the maintenance sequence so they are informed but can then choose to remove Product A if it they want. -- View this message in context: http://n2.nabble.com/Enforcing-installation-dependencies-tp4682311p4682371.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
