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
- :
- install file A.config or file B.config, depending on TYPE of PC
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
Dec 14, 2015
04:47 PM
install file A.config or file B.config, depending on TYPE of PC
I have two config files, A.config and B.config, only one of which should be installed. If installing on a regular PC, then A.config should be installed. If installing on an embedded PC, then B.config should be installed.
InstallShield itself cannot determine the type of device that I'm installing on - while it can deduce the O/S, this isn't sufficient as we can run any O/S from XP to Win 10 on the embedded PC as well as the desktop PC.
For other reasons, we detect the platform within the IS script itself by looking for the presence of a driver that is only installed on the embedded PC, thus, we know in the script which file we need to install from media.
What is my best option for implementing this using IS 2014?
InstallShield itself cannot determine the type of device that I'm installing on - while it can deduce the O/S, this isn't sufficient as we can run any O/S from XP to Win 10 on the embedded PC as well as the desktop PC.
For other reasons, we detect the platform within the IS script itself by looking for the presence of a driver that is only installed on the embedded PC, thus, we know in the script which file we need to install from media.
What is my best option for implementing this using IS 2014?
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Dec 15, 2015
09:23 AM
I think you headed in the right direction already buy detecting a known driver on the embedded PC. You could also use the dependency scanner to look for the driver and then set a property based off that?