Phil Wilson
5/17/2006 11:30:00 PM
If you're putting the property name in square brackets in the correct case
in the Welcome text and it's blank, that means you're not getting the value
into the property. If I do a registry search for [Property MDACVER RegKey
SOFTWARE\Microsoft\DataAccess Root vsdrrHKLM and Value Version] I definitely
see 2.82.1830.0 in the Welcome screen. Maybe you're not getting the value,
the property value is empty, and that might be making every comparison
evaluate to true.
--
Phil Wilson [MVP Windows Installer]
----
"Rob R. Ainscough" <robains@pacbell.net> wrote in message
news:uktBzPeeGHA.4040@TK2MSFTNGP05.phx.gbl...
> Hi Phil,
>
> The reg entries are being found (via Search for Registry Entry) and loaded
> into the property -- the "Conditions" evaluation on the creation of reg
> entries during the install are working correctly (registry editor
> section). Just the Launch Actions Condition statements don't appear to be
> working at all (Launch Conditions section). Has me baffled.
>
> The Welcome displays a blank space, and yes they are REG_SZ.
>
> Rob.
>
>
> "Phil Wilson" <pdjwilson@nospam.cox.net> wrote in message
> news:uyuPoWFeGHA.1320@TK2MSFTNGP04.phx.gbl...
>> What's the actual format of the data in the registry? Is it really
>> REG_SZ?
>>
>> If you go to the user interface sequence and put [MYENVMODE] at the start
>> of the WelcomeText string you'll see the actual value, just as a sanity
>> check.
>>
>> --
>> Phil Wilson
>> [Microsoft MVP-Windows Installer]
>>
>> "Rob R. Ainscough" <robains@pacbell.net> wrote in message
>> news:uAp5UyYdGHA.1208@TK2MSFTNGP02.phx.gbl...
>>> Or anyone that might know. Phil, I've read you book, it was very
>>> helpful, however this Search Registery and Condition problem I'm having
>>> is about to make me jump off the edge.
>>>
>>> I've created a deployment project and decided I wanted to use the
>>> Registry Search feature setup as follows:
>>>
>>> Search Target Machine
>>> Search for my Environment
>>> Property: MYENVMODE
>>> RegKey: SOFTWARE\MyApp
>>> Root: vsdrrHKLM
>>> Value: Version
>>>
>>> Launch Conditions
>>> MyCondition
>>> Condition: MYENVMODE >= "3.0.0.0"
>>> Message: "Condition True!"
>>>
>>> If I create a registry key: HKEY_LOCAL_MACHINE\SOFTWARE\MyApp
>>> then create a string value Version
>>>
>>> If do the following:
>>> set Version = "3.0.0.0", Message displays "Condition True!"
>>> set Version = "2.9.1.1", Message displays "Condition True!"
>>> set Version = "3.1.1.1", Message displays "Condition True!"
>>>
>>> If change Condition: MYENVMODE = "3.0.0.0"
>>> set Version = "3.0.0.0", Message displays "Condition True!"
>>> set Version = "2.9.1.1", Message displays "Condition True!"
>>> set Version = "3.1.1.1", Message displays "Condition True!"
>>>
>>> If change Condition: MYENVMODE < "3.0.0.0"
>>> set Version = "3.0.0.0", Message displays "Condition True!"
>>> set Version = "2.9.1.1", Message displays "Condition True!"
>>> set Version = "3.1.1.1", Message displays "Condition True!"
>>>
>>> If change Condition: MYENVMODE <> "3.0.0.0"
>>> set Version = "3.0.0.0", Message displays "Condition True!"
>>> set Version = "2.9.1.1", Message displays "Condition True!"
>>> set Version = "3.1.1.1", Message displays "Condition True!"
>>>
>>> As you can see, it doesn't matter what I do, this always evalutes to
>>> true and triggers the condition. Do conditions just NOT work? I've read
>>> several other people have the exact same problem. Just for reference,
>>> when testing, I right click on the deployment project in VS 2005 and
>>> select "Install".
>>>
>>> What the heck am I doing wrong? I'm stumped -- been working on this all
>>> day!
>>>
>>> Thanks, Rob.
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>