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 pass Installer property from server to client side?
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
‎May 21, 2013
04:47 AM
How to pass Installer property from server to client side?
Hi,
I'm trying to set an installer property on server side and want to access it back in client side. No matter what I do it does not pass the property to client side. For client to server we have securecustomproperty but do we have something similar from server to client?
I do not want to set a registry just to access properties from one mode to other.
Thanks.
I'm trying to set an installer property on server side and want to access it back in client side. No matter what I do it does not pass the property to client side. For client to server we have securecustomproperty but do we have something similar from server to client?
I do not want to set a registry just to access properties from one mode to other.
Thanks.
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 21, 2013
08:23 AM
I think serializing the value to the registry or a file which can be accessed by the client is the only approach available.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 21, 2013
09:44 AM
Hi Phil,
I've about 20 properties to pass. I'll have to write all of them to registry via a custom action. Then I'll have to schedule a custom action to read those properties back and delete registry. I just wanted to avoid custom actions for petty jobs.
I've about 20 properties to pass. I'll have to write all of them to registry via a custom action. Then I'll have to schedule a custom action to read those properties back and delete registry. I just wanted to avoid custom actions for petty jobs.