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: Storing a varible in the vpd for use by other products
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
‎Apr 11, 2006
04:34 PM
Storing a varible in the vpd for use by other products
Hello,
Is it possible to store a variable in the vpd registry that is not bound to any particular product? We have multiple products using the same installer framework and we want the first one that is installed to set a global "HOME" variable in the registry for use by other products that may be installed afterwards.
Thanks in advance.
Is it possible to store a variable in the vpd registry that is not bound to any particular product? We have multiple products using the same installer framework and we want the first one that is installed to set a global "HOME" variable in the registry for use by other products that may be installed afterwards.
Thanks in advance.
(5) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 01, 2006
04:43 PM
rmackay wrote:
Hello,
Is it possible to store a variable in the vpd registry that is not bound to any particular product? We have multiple products using the same installer framework and we want the first one that is installed to set a global "HOME" variable in the registry for use by other products that may be installed afterwards.
Thanks in advance.
Global persisted variable setting.
I guess they want to encourage people to figure things out on their own.
This must be the crappiest user forum ever. Most at least have support guys answering the easy questions.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 08, 2006
05:17 AM
The problem with Global Persistent variables is that they get uninstalled alongside the product they are associated with... so you cannot rely on the variable staying there forever (if you uninstall the first product then the others will no longer have access to the variable).
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 08, 2006
09:13 AM
from what I have seen, the global persistant variable, if defined across all the products that use it, will stick around until the last of those products have been removed.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 09, 2006
05:04 AM
But if you defined it in all the products, when you launch the installer the variable would be updated with the value defined in that product installer, or wouldn't it?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 09, 2006
01:14 PM
In our case, we do not update the variable with every installation. The first installation creates it when it is not there and the other installations access it.
![](/skins/images/CC38E504FC9E1309DC48ACFEB4925670/responsive_peak/images/icon_anonymous_message.png)