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 action behavior really should be in a msi.
-- 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-tp7598962p7599003.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
