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-Burn-chain-td7585020.html As I understand it the idea of ExePackage is to launch a setup package (and not just any exe). At the time the Bundle chain is compiled, certain signatures are created for each package in the chain (MSI or Exe setup), in part, to prevent malware from being inserted into the chain at runtime. So in my experience there is a one-to-one relationship between a build of the bundle and each build (version) of each package in the chain, as detected by Burn at build time. Maybe someone else can provide more details or correct my understanding. -- 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-tp7598962p7599006.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
