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
- :
- How to a access with a CA to data installed via a chained package
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
Jul 20, 2014
03:20 AM
How to a access with a CA to data installed via a chained package
I prepare an installer (Basic MSI with installshield 2013) that needs to install, if not already installed, a third party application as a chained package.
My own installer has to copy one of its files in a directory whom location is defined in a registry entry created by the chained package.
I plan to use a deferred CA to copy this file, but I don’t know how to get the value of the registry entry when my installer will need to run the chained package. In fact I am not sure that an immediate CA is able to access a registry entry installed via a chained package…
In other words, my problem comes from a lack of knowledge about the accurate execution sequence of CA in a transaction embedding a chained package.
My own installer has to copy one of its files in a directory whom location is defined in a registry entry created by the chained package.
I plan to use a deferred CA to copy this file, but I don’t know how to get the value of the registry entry when my installer will need to run the chained package. In fact I am not sure that an immediate CA is able to access a registry entry installed via a chained package…
In other words, my problem comes from a lack of knowledge about the accurate execution sequence of CA in a transaction embedding a chained package.
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jul 22, 2014
01:42 AM
A deferred installscript action should do just fine for getting a registry value created by your chained MSI.
First check if the key exists:
http://helpnet.installshield.com/installshield18helplib/mergedProjects/installshield18langref/LangrefRegDBKeyExist.htm
Then get the value you want:
http://helpnet.installshield.com/installshield18helplib/mergedProjects/installshield18langref/LangrefRegDBGetKeyValueEx.htm
Then store the value in an MSI property:
MsiSetProperty("SOMEMSIPROPERTY", svValue);
Sequence it after ISChainPackageCommit but before InstallFinalize
Then do whatever you want with the value.
First check if the key exists:
http://helpnet.installshield.com/installshield18helplib/mergedProjects/installshield18langref/LangrefRegDBKeyExist.htm
Then get the value you want:
http://helpnet.installshield.com/installshield18helplib/mergedProjects/installshield18langref/LangrefRegDBGetKeyValueEx.htm
Then store the value in an MSI property:
MsiSetProperty("SOMEMSIPROPERTY", svValue);
Sequence it after ISChainPackageCommit but before InstallFinalize
Then do whatever you want with the value.
