/build/static/layout/Breadcrumb_cap_w.png

Launch condition not working

I want ot put launch condition in my msi. At 1st I am searching file, through system search, property sets to APP_TEST. Now I want to put launch condition, by using system search. I put launch conditions like APP_TEST=0, I tried a lot, but not working: Please suggest

0 Comments   [ + ] Show comments

Answers (13)

Posted by: anonymous_9363 14 years ago
Red Belt
2
Given the above log extract, the test in Launch Conditions should be 'APP_TEST<>1' or 'NOT APP_TEST=1'.
Posted by: zipsantro 14 years ago
Purple Belt
0
Is APP_TEST defined in property table?
If not then you need to validate as "NOT APP_TEST"

Jeeoo!
Santro
Posted by: abking99 14 years ago
Second Degree Blue Belt
0
Previously it was defined: but now i deleted it, and put a launch condition
NOT APP_TEST
but it is installing in both the scenarios.
Posted by: cygan 14 years ago
Fifth Degree Brown Belt
0
are you using wise or installshield
Posted by: abking99 14 years ago
Second Degree Blue Belt
0
Wise
Posted by: zipsantro 14 years ago
Purple Belt
0
Check your log file and identify the value of APP_TEST based on system search scenarios.

Jeeoo!
Santro
Posted by: abking99 14 years ago
Second Degree Blue Belt
0

MSI (c) (58:C4) [23:47:50:790]: Note: 1: 2262 2: CompLocator 3: -2147287038
MSI (c) (58:C4) [23:47:50:790]: Note: 1: 2262 2: RegLocator 3: -2147287038
MSI (c) (58:C4) [23:47:50:790]: Note: 1: 2262 2: IniLocator 3: -2147287038
MSI (c) (58:C4) [23:47:50:790]: PROPERTY CHANGE: Modifying APP_TEST property. Its current value is '1'. Its new value: 'C:\Program Files\Test\myapp.exe'.
Action ended 23:47:50: AppSearch. Return value 1.
MSI (c) (58:C4) [23:47:50:790]: Skipping action: CCPSearch (condition is false)
MSI (c) (58:C4) [23:47:50:790]: Skipping action: CCPDialog (condition is false)
MSI (c) (58:C4) [23:47:50:790]: Skipping action: RMCCPSearch (condition is false)
MSI (c) (58:C4) [23:47:50:790]: Doing action: LaunchConditions
Action 23:47:50: LaunchConditions. Evaluating launch conditions...
Action start 23:47:50: LaunchConditions.


here it gives error.
Posted by: abking99 14 years ago
Second Degree Blue Belt
0
I tried putting it
APP_TEST=1
but, it aborts the installation, in both the conditions
Posted by: abking99 14 years ago
Second Degree Blue Belt
0
Thanks to all, for putting efforts for me. Thanks to VBScab, it worked with NOT APP_TEST=1
Posted by: anonymous_9363 14 years ago
Red Belt
0
It's not hard. WPS tells you in the 'Launch Condition Details' dialog to enter the condition which must be met in order for the installation to continue.
Posted by: bob_msi 14 years ago
Orange Belt
0
in that case go to the property table and create a property

<PROPERTYNAME>.= [ProgramFilesFolder]foldername\filename.txt

in the launch condition table enter

NOT APP_TEST = <PROPERTYNAME>

description field ("enter description")
Posted by: abking99 14 years ago
Second Degree Blue Belt
0
but NOT APP_TEST=1 is similar to APP_TEST=0 am i right?
Posted by: anonymous_9363 14 years ago
Red Belt
0
No. Think about what the 'equals' sign means.

NOT APP_TEST=1
means 'Accept any scenario where APPTEST is not equal to 1'

APP_TEST=0
means 'Accept any scenario where APPTEST=0'

In your search, APP_TEST gets populated with the filename, if it's present, 'C:\Program Files\Test\myapp.exe'

In the first test, clearly APP_TEST no longer equals 1, passing the test. In the second test, it does not equal 0, thus failing the test.

Lastly, from what I can gather from the log extract, at no point does APP_TEST=0. I imagine you have it set to 1 in the 'Property' table.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ