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
- :
- Always Install
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
‎Feb 08, 2012
01:58 PM
Always Install
Hi,
I have a question regarding "Features/Always Install". I am uncertain if this title means "ALWAYS install".
At the moment this is populated with various dll's (all Microsoft) which were automatically imported from a VB project. What I really want is these to only be installed if they are more recent than any existing version on the users computer. Is there a way to do this?
Thanks
Ian
I have a question regarding "Features/Always Install". I am uncertain if this title means "ALWAYS install".
At the moment this is populated with various dll's (all Microsoft) which were automatically imported from a VB project. What I really want is these to only be installed if they are more recent than any existing version on the users computer. Is there a way to do this?
Thanks
Ian
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 12, 2012
01:53 PM
Does anybody have a answer to this question, it's very important to me.
If there is no-one who knows, is there anywhere I can get an answer?
Many thanks
Ian
If there is no-one who knows, is there anywhere I can get an answer?
Many thanks
Ian
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 13, 2012
10:33 AM
It's just a name, but typically this feature is not shown to the end-user, so there is no chance for it to be unselected manually. You can write system searches, feature conditions, custom actions, etc., each of which influence this feature's likelihood to install in other ways.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 14, 2012
07:34 PM
Michael,
Thank you VERY much for your reply.
Sorry, I'm very new to this! I think you are saying that the "always install" only means that the end-user has no option to deny installation of these files which is fine.
I'm still unsure what happens if any of the files is already installed on their system, or if a more recent version is already installed. I do understand the standard MSI "file overwrite" rules but have no idea if these apply to these files.
I don't really understand your 2nd sentence, is there an example anywhere explaining- how to "influence this feature's likelihood to install"?
Thanks again
Ian
Thank you VERY much for your reply.
Sorry, I'm very new to this! I think you are saying that the "always install" only means that the end-user has no option to deny installation of these files which is fine.
I'm still unsure what happens if any of the files is already installed on their system, or if a more recent version is already installed. I do understand the standard MSI "file overwrite" rules but have no idea if these apply to these files.
I don't really understand your 2nd sentence, is there an example anywhere explaining- how to "influence this feature's likelihood to install"?
Thanks again
Ian
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 15, 2012
08:58 AM
Windows Installer's file versioning rules apply to all files it installs as part of a feature>component>file relationship. (Other rules apply to DuplicateFile and such tables.)
As far as influencing a feature's likelihood to install, there are a multitude of approaches here. There are installlevels and feature conditions. There's the feature selection tree and control events such as AddLocal. There's properties including ADDLOCAL, and API calls such as MsiSetFeatureState. That's why I said influence - there's an ordering to how these are evaluated, and any later one can reverse the decision of an earlier one.
As far as influencing a feature's likelihood to install, there are a multitude of approaches here. There are installlevels and feature conditions. There's the feature selection tree and control events such as AddLocal. There's properties including ADDLOCAL, and API calls such as MsiSetFeatureState. That's why I said influence - there's an ordering to how these are evaluated, and any later one can reverse the decision of an earlier one.