| Groups | Blog | Home |
dotnet setup : Paging Phil Wilson -- Launch Condition problem in VS 2005.
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.
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] [quoted text, click to view] "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. > > > > >
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. [quoted text, click to view] "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. >> >> >> >> >> > >
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] ---- [quoted text, click to view] "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. >>> >>> >>> >>> >>> >> >> > >
That is what I would have thought also -- but that wouldn't explain why the
same property reference in a condition statement for creating a registry entry would work correclty. Are Launch Conditions evaluated before registry searches ?? This is the only conclusion I can come to. [quoted text, click to view] "Phil Wilson" <Phil.Wilson@unisys.spamcom> wrote in message news:ejBNingeGHA.2172@TK2MSFTNGP04.phx.gbl... > 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. >>>> >>>> >>>> >>>> >>>> >>> >>> >> >> > >
The registry searches (and the other searches) take place before the launch
conditions. That blank in the Welcome text bothers me - it should show a value. If you do the install with a log it will show property values too. I just think it's not being set. msiexec /i <path to msi> /l*v <path to some text log file> -- Phil Wilson [Microsoft MVP-Windows Installer] [quoted text, click to view] "Rob R. Ainscough" <robains@pacbell.net> wrote in message news:OWvZRJreGHA.1880@TK2MSFTNGP02.phx.gbl... > That is what I would have thought also -- but that wouldn't explain why > the same property reference in a condition statement for creating a > registry entry would work correclty. > > Are Launch Conditions evaluated before registry searches ?? This is the > only conclusion I can come to. > > > "Phil Wilson" <Phil.Wilson@unisys.spamcom> wrote in message > news:ejBNingeGHA.2172@TK2MSFTNGP04.phx.gbl... >> 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. >>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |