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
- :
- InstallAnywhere
- :
- InstallAnywhere Forum
- :
- Installing only selected files from rules variable
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
‎Nov 29, 2007
08:58 AM
Installing only selected files from rules variable
In the Visual tree, there are files mapped to Product Featues, which is correct behavior. The question is how can I stop a file from installing although it is listed in the product features. I have tried using a variable in the rule for the file but it will still install the file. Any sugestions? Thanks
6 Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 29, 2007
09:12 AM
Well, if you do not want the file installed, why don't you simply remove it?
Or have you tried setting a rule like "true matches false"? This should guarantee that the respective file is never installed!
Or have you tried setting a rule like "true matches false"? This should guarantee that the respective file is never installed!
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 29, 2007
09:26 AM
Thanks, this is a special upgrade and the requirement is to update the database with content only and not re-install files because some of the files could be a war or jar file that might have a newer patch release version, in this case we dont want to write over some of these files because we could write over newer with older files.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 29, 2007
10:03 AM
For the future you can do something like adding an installation rule
$IS_UPDATE$ matches true
and you can launch your installer like this
setup.exe -DIS_UPDATE=true
in case you want to do an update.
But I guess now you're in position of modifying your existing installer in order to make an updater out of it, right? In this case what I suggest is to modify in Project/File Settings from the default Always Overwrite to Never Overwrite, I guess this should do the trick.
$IS_UPDATE$ matches true
and you can launch your installer like this
setup.exe -DIS_UPDATE=true
in case you want to do an update.
But I guess now you're in position of modifying your existing installer in order to make an updater out of it, right? In this case what I suggest is to modify in Project/File Settings from the default Always Overwrite to Never Overwrite, I guess this should do the trick.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 29, 2007
10:54 AM
Thanks.
In regards to "make an updater out of it, right?" yes, however this installer currently does a New Install, Upgrade Install(both content and all files), and we are now adding the third option to install only content, without files. The user can select which of the 3 install types. All 3 installer types share the product features.
The Never Overwite would work if this was only an updater(content only) installer.
In regards to "make an updater out of it, right?" yes, however this installer currently does a New Install, Upgrade Install(both content and all files), and we are now adding the third option to install only content, without files. The user can select which of the 3 install types. All 3 installer types share the product features.
The Never Overwite would work if this was only an updater(content only) installer.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 29, 2007
10:58 AM
Then I guess the previous suggestion should work if you set the the variable based on the user choice (i.e. by default the variable, let's name it $DO_INSTALL$ is set to true, and in case the user selects Upgrade only you would set it to false, so the rule $DO_INSTALL$ matches true will fail and the files won't be installed.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 29, 2007
12:29 PM
I resolved this problem.
I will create a new Feature and map the files required appropriately.
I will create a new Feature and map the files required appropriately.
