This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: System search property in feature condition
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 25, 2008
12:23 PM
System search property in feature condition
Hi
I have another issue that is bothering me.
My goal is to let the installer check for a certain file or registry and if that is found, certain features should be installed. I've read the installshield manual and I created in the system search a search for a file and the result is stored in a property (which i created in property manager). I also checked the statement "Store the value in the property and use the property in an install condition" (i wonder what value is used).
Then i went to my feature view and in the feature condition builder i wanted to use my created property. But in the drop down list of property's there's only a list starting with Adminuser, Alpha until Windowsbuild, but not my property that i created.
So my questions are, is it possible to use the self created property's in that condition builder?
If not, how do i have to do the trick with the conditions on the features for installed apps (files or reg keys)?
Thanks for the help.
I have another issue that is bothering me.
My goal is to let the installer check for a certain file or registry and if that is found, certain features should be installed. I've read the installshield manual and I created in the system search a search for a file and the result is stored in a property (which i created in property manager). I also checked the statement "Store the value in the property and use the property in an install condition" (i wonder what value is used).
Then i went to my feature view and in the feature condition builder i wanted to use my created property. But in the drop down list of property's there's only a list starting with Adminuser, Alpha until Windowsbuild, but not my property that i created.
So my questions are, is it possible to use the self created property's in that condition builder?
If not, how do i have to do the trick with the conditions on the features for installed apps (files or reg keys)?
Thanks for the help.
(9) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 25, 2008
12:31 PM
Yes, you can use custom properties in a feature condition (or a component condition, custom action condition, dialog-control condition, and so on); I think the condition builder shows only built-in properties.
P.S. To test the value contained in the system search condition, you can create an MSI log file, or use [PROP_NAME] in a dialog box, or many other things...
P.S. To test the value contained in the system search condition, you can create an MSI log file, or use [PROP_NAME] in a dialog box, or many other things...
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 25, 2008
02:53 PM
So i just check the contents of the property (probably 1 or 0) and i can use it in the condition even if it doesn't show it in the builder?
I'll try it tomorrow.
I'll try it tomorrow.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 26, 2008
12:14 PM
I tried today, but it didn't work.
I'm able to show a string, or the contents of a variable declared within the script in a message box, but the contents of a private property is not shown ( gives me errors when i compile the script). So i'm still not sure what value a property receives when a system search has found it's goal.
I tried with a feature condition PROPERTY < 1 while it's value was set to 0 in the property table.
I did a systemsearch on a file (which was present) and the result of the search should've been placed in PROPERTY. After which my feature with the condition on should not have been installed. But unfortunatly it wasn't ... 😞
Can anyone describe me exactly what to do? Or point me to a working example?
Thanks in advance
I'm able to show a string, or the contents of a variable declared within the script in a message box, but the contents of a private property is not shown ( gives me errors when i compile the script). So i'm still not sure what value a property receives when a system search has found it's goal.
I tried with a feature condition PROPERTY < 1 while it's value was set to 0 in the property table.
I did a systemsearch on a file (which was present) and the result of the search should've been placed in PROPERTY. After which my feature with the condition on should not have been installed. But unfortunatly it wasn't ... 😞
Can anyone describe me exactly what to do? Or point me to a working example?
Thanks in advance
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 26, 2008
12:45 PM
For a start, to test the value contained in the system search condition, you can create an MSI log file, or use [PROP_NAME] in a dialog box, or many other things...
(If your search property is already in the Property Manager view with value 0, perhaps delete from there, too.)
(If your search property is already in the Property Manager view with value 0, perhaps delete from there, too.)
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 26, 2008
02:06 PM
Funny that you mention the log. Logging with installshield is not working properly, i added the logging via menu Build/Settings and in tab MSI log file i added the location (root) and Verbose logging. But when i tested the condition, i searched for a log but nothing was found ...
I tried the MSI separatly (to use parameter /Lv) but since it is an installshield project i cannot run it without the setup.exe.
I still have to find the commandline parameters for the setup.exe logging thing, couldn't find one in the installshield PDF ...
I'm used to work with Wise package studio and to be honest, i had far less trouble with these kind of small things. I must admit that this package is more difficult then the things i've done with Wise package studio.
I tried the MSI separatly (to use parameter /Lv) but since it is an installshield project i cannot run it without the setup.exe.
I still have to find the commandline parameters for the setup.exe logging thing, couldn't find one in the installshield PDF ...
I'm used to work with Wise package studio and to be honest, i had far less trouble with these kind of small things. I must admit that this package is more difficult then the things i've done with Wise package studio.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 26, 2008
04:26 PM
Perhaps pass the msiexec /L switch through the /V switch, as in:
setup.exe /V"/L*v C:\everything.log"
setup.exe /V"/L*v C:\everything.log"
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 27, 2008
12:48 AM
Robert
Thanks for helping me out, you seem to be the one of the few members that actually try to help other people out.
I'll try your suggestions today.
Regards
Thanks for helping me out, you seem to be the one of the few members that actually try to help other people out.
I'll try your suggestions today.
Regards
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 28, 2008
02:59 AM
The system search is working. When i do a search for a registry key, it stores the value data in the property that i wanted to use.
When i entered this system search, it was immediatly used as een Launch condition, which i don't want to, so i deleted this entry in the launchCondition table.
I wanted to use this Property as a Feature condition. So i added following condition on a feature: Level: 200 Condition: TESTRESULT="test"
So it should raise the installlevel to 200 when the regkey is found.
After the install, i examined the log, and the registry key was found, the property had the value 'test', but my feature was still installed.
The installlevel was set to '1', the condition should've been triggered and the installlevel of my feature should've been raised to 200. But it didn't.
The whole installlevel story doesn't seem work either. Normal behaviour should be that every component with an installlevel lower or equal then the installlevel of the product should be installed. But because i'm struggling so hard now, i manually changed the feature installlevel to 200. Recompiled and tested it and the feature was still installed 😞
In the past i used ADDLOCAL property to play with feature installs, you can specify on the commandline what features are installed, but this install should be a mix of users choice (which works pefectly with the standard dialoge) and an automatic search and disable. This last item seems to be a pain in the ass and i just can't get it right (if it's technically possible).
When i entered this system search, it was immediatly used as een Launch condition, which i don't want to, so i deleted this entry in the launchCondition table.
I wanted to use this Property as a Feature condition. So i added following condition on a feature: Level: 200 Condition: TESTRESULT="test"
So it should raise the installlevel to 200 when the regkey is found.
After the install, i examined the log, and the registry key was found, the property had the value 'test', but my feature was still installed.
The installlevel was set to '1', the condition should've been triggered and the installlevel of my feature should've been raised to 200. But it didn't.
The whole installlevel story doesn't seem work either. Normal behaviour should be that every component with an installlevel lower or equal then the installlevel of the product should be installed. But because i'm struggling so hard now, i manually changed the feature installlevel to 200. Recompiled and tested it and the feature was still installed 😞
In the past i used ADDLOCAL property to play with feature installs, you can specify on the commandline what features are installed, but this install should be a mix of users choice (which works pefectly with the standard dialoge) and an automatic search and disable. This last item seems to be a pain in the ass and i just can't get it right (if it's technically possible).
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 29, 2008
01:17 PM
Is it possible that it has to do with the CostFinalize that is already been done by the time my condition is checked?