Bind paths vs. Visual Studio project references (e.g. $(var.MyProject.TargetDir))...the latter doesn't require passing custom parameters to light. Why make the specifying of a source file more arcane with a bind paths binder variable? Especially when the use case is a patch file in the unseen future? IMHO, better to just let us use a -bf flag when we need it.
I personally like being able to bind the binary data into the wixout so that it can be moved and used later. Such a useful feature to throw away. Especially when the binder variable is not a great replacement. What's melt got to do with it? Isn't that for merge modules? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Creating-patches-using-wixout-bf-flag-deprecated-tp7598765p7598779.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
