Another approach is to use named bindpaths like this: (which in VS IDE can be
edited in the project's properties page (or by unloading the project)
<LinkerAdditionalOptions>
$(LinkerAdditionalOptions)
-nologo
-b foo="$(MySourceRoot)\source_path\foo\\"
</LinkerAdditionalOptions>
For $(MySourceRoot) I define that in another .targets file that I load into
all projects, or sometime I don't use the targets file and use a relative
path as you indicated.
Rather than this:
"..\Protocol\bin\Release\"
you could use:
"..\Protocol\bin\$(Configuration)\"
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Including-files-to-installer-with-bindpath-best-practice-tp7599451p7599459.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
