Thank you for the replies! Let's see... ----------
> Date: Thu, 19 Feb 2009 15:46:00 -0800 > From: "John Cooper (Volt)" <a-jc...@microsoft.com> > > I think what you want to do could be done with a: > > 1) Launch condition dependent on a property; > 2) The property is set based on a Registry Search, File Search, or > Component Search. > > -- > John M. Cooper ---------- Thank you, John. All I have for now is the Upgrade Code of the whole application, but I can try to find out the PID of its components. I'll try something in this direction. Registry and File search don't seem to be straightforward in my case... ---------- > Date: Thu, 19 Feb 2009 17:18:28 -0800 > From: Bob Arnson <b...@joyofsetup.com> > > I think you have your logic reversed: You want the error message to be > shown if the property *isn't* set (meaning the other product wasn't > found). Try "NOT NOTFOUND" instead. > > -- > sig://boB > http://joyofsetup.com/ > ---------- You are correct, Bob; I've right the wrong code here. But unfortunately it's not the main problem. Man, I've tried millions of variants of this code, including your suggestion. That's why I think the way I'm doing the thing may be wrong... But thanks anyway! Cheers, Volnei ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
