By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,726 Members | 2,465 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,726 IT Pros & Developers. It's quick & easy.

Can't get Condition to evaluate correctly?

P: n/a
I'm pretty frustrated right now, but I'm unable to get a Launch Condition to
work at all in my Condition statement of a Registry entry.

(working on a Deployment Project)

1. In Launch Conditions editor
a. Add Registry Search (under Search Target Machine)
b. Set regKey, root, Value, Property name (i.e. LOCALENV)

2. In Registry Editor
a. Create Registry entry with Condition set to LOCALENV = "1"

3. Edit the real registry on my target machine and add the corresponding
registry entry that LOCALENV points to and set value to "1"

Install my deployment and it doesn't set LOCALENV -- so, to validate that
the Search Registry is working, I added a Launch Condition to -- the bizarre
part is that both of these conditions trigger a message:

LOCALENV = "1"
LOCALENV = "0"

How is it possible that both conditions can be true??

May 11 '06 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.