Is there support for variables within the MSI? I can't find documentation on it, but I'd think it would be supported.

Specifically, I am defining packaging standards for a locked-down corporate environment. We are using Wise Enterprise 4.62. I want to add a custom registry key in HKLM\Software\CompanyName to hold as much detail as possible about the each installation of the company's packaged software, including install date/time, source MSI location, etc.

Can I simply create a registry entry in the MSI and put a variable in the Value field? Is anyone else adding such a registry key? Any other suggestions?
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


To my knowledge, you cant use variables in msi's. However, Wise had their own set of "variables", called properties (I know version 5.1 only, hopefully yours are the same). I dont think its possible to use properties in registry though.

I can imagine 3 possible solutions
1. Use regedit to export the reg keys you want, modify it to use variables, then make a VB script that imports it into the registry. Use Wise script to run the VB script.
2. If #1 doesnt work, use VB script to insert the values you need in the reg file, then have the VB script import it to the registry. A bit more difficult, but hey...
3. Add the key to the MSI manually... And right-click&select-properties on the program files folder to see date created if you have to know.
Answered 04/27/2004 by: lokbjo
Senior Yellow Belt

Please log in to comment
Yes, in Windows Installer terms Properties are basically variables and you can add your own in the properties table. To use the value in something like a registry value, just use the name of the property in brackets.

So if you added your own property to identify the author of the MSI, you could place it in the registry by adding a value with [Author] as the data:

Subkey: HKLM\Software\Corporate
Value: Author
Data: [Author]

Remember, properties are case sensitive. All capitals means it is a public property which can have its value set on the command line.
Answered 04/27/2004 by: bkelly
Red Belt

Please log in to comment
Ah ha! A terminology issue. Thanks bkelly!

Wow, looking over the Properties documentation on MSDE opens up a WORLD of possibilities. Passable from the command line, accessable via VBScript.... A lot can be done there. I knew it had to be possible, and wow is it robust.

For the lurkers, Windows Installer properties documentation can be found at
Answered 04/28/2004 by: VikingLoki
Second Degree Brown Belt

Please log in to comment