You should then use the property [INSTALL_USERNAME] in your control. Edit: To schedule the custom action use the Before or After attribute, if you are unsure where to schedule it use a tool like orca to see what order things are happening in, here's an example of the custom action running after...
This method uses the values of properties stored in the Session object passed as a parameter to the method and determines the path of the current version's executable file.
Thanks Jamie. -----Original Message----- From: Pally Sandher Sent: 07 February 2011 18:27 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Using a <Property> Value inside <File Name=???>
If you're using WiX v3.0 you'll have to type more stuff. line 10: This is the Property that we'll remember.
The value will be overwritten if the Property is used for a search. Any Attribute (namespace='##other' processContents='lax') Extensibility point in the WiX XML Schema. Schema extensions can register additional attributes at this point in the schema.
The safest approach would be to wrap everything (this is what the WiX decompiler, Dark, does) but---at least in my humble opinion---this makes the source
I gathered these tricks after creating installers using WiX. For each problem, a solution was found after long experimenting or searching deep in the web.
Property Id="WixShellExecTarget" Value="[#IESLink.pdf]" />. I get no warnings at all when building that product's project. However I am using WiX v3.0.5217.0 while it appears from the original post that Riyaz is using WiX...
WIX property value substitution and CAQuietExec. So far, I'm NOT finding WIX to be my favorite most intuitive, easy-to-use, language/system. I created a custom dialog, entered data, and see the values in the install log.