I am also learning these details, but I have seen this come up previously in
the forum.
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-config-file-Answer-file-td7593918.html#a7593920
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Runtime-configurable-Bur
Hi Phill,
Thanks for your answer.
what do you mean by 'custom action' type behavior?
the only thing I'm trying to do is run an exe, and the exe's path depends on
2 variables (windows folder, and versionNT).
Why can't I do this in Burn? why does the path have to be predefined?
I don't understand th
It looks like you are trying to do 'custom action' type behavior in the
bundle chain, which is not really what the ExePackage is for. The
ExePackage must be available at build time, so that a thumb print of the
package can be embedded in the bundle for security reasons, as I understand
it. Custom
any ideas someone?
shouldn't this be relatively simple?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-ExePackage-SourceFile-How-to-set-to-a-dynamic-path-tp7598962p7599001.html
Sent from the wix-users mailing list archive at Nabble.com.
Hi,
I need to set a path to an exe dynamically (depending on .Net version), and
I don't know how (tried using wix/burn variables).
I'm also trying to use burn built-in variables ([WindowsFolder] and
[VersionNT]). no success.
my code:
I keep getting errors where
5 matches
Mail list logo
