Is it possible to use something other than a registry entry or an environment variable in a Path Variable? Can I use a Property? I want to embed a portion of the path that will vary with each build.
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Can I use a property in a Path Variable?
Started by
clachiusa
, Jul 08 2011 13:44
3 replies to this topic
MSIYER
-
- Full Members
- 90 posts
Posted 08 July 2011 - 14:24
Yes. Very much possible.
Just use MsiGetProperty MsiSetProperty functions to get or to set the property and use it in your CA to create the full path that you need.
Just use MsiGetProperty MsiSetProperty functions to get or to set the property and use it in your CA to create the full path that you need.
clachiusa
-
- Full Members
- 4 posts
Posted 08 July 2011 - 14:33
I need to use it in the Path Variables table and it doesn't resolve itself. The path where my built components reside changes with each build.
I can get the information I need into an MSI property, but I can't put that property into the Path Variable to be used by Dynamic File Linking in my Component.
I can get the information I need into an MSI property, but I can't put that property into the Path Variable to be used by Dynamic File Linking in my Component.
Stefan Krueger
-
- Administrators
- 13,269 posts
InstallSite.org
Posted 19 July 2011 - 13:36
Path variables are used a build time.
Properties are resolved at runtime (install time). So you can't use them during build.
Properties are resolved at runtime (install time). So you can't use them during build.
Stefan Krüger
InstallSite.org twitter facebook