Hmm, sounds intriguing. Could you point me in the direction of some more
information about this approach and/or provide an example? The WiX docs
mention binder paths in "How To: Specify source files", but I wonder if
there is more thorough source of information.
Thanks again for your advice!
_
Something else to consider: instead if using loc variables, try organizing
your build location so that bind paths can be used. Then when building you
can provide the appropriate bindpath on the command-line. I do this to
minimize the File/@Source elements all the time. "Named base paths" can be
qui
I think that I may have caused some confusion by naming the File/@Id field
the way I did in my example. In reality, I am using "heat"-style ID's (for
example "filB75B712DC4A64A7882230FE0BCC0CC3E") for all of my files.
Regardless of the ID convention, though, I get the same errors.
However, I did j
Instead of specifying File/@Id, try specifying File/@Name. I think the
issue is that the File/@Name is defaulting to the value from File/@Source.
By specifying File/@Name you are telling the WiX toolset the explicit file
name to use for the install. File/@Id will default to File/@Name giving
you t
Thanks, I suppose that solution could work.
Nonetheless, I feel like this should be a fairly common scenario and that
there should be some way to support it using the built-in localization
features. I think that this would be easy if either all of the localized
source files (in my example, the Fil
You could try doing this with variables instead of localised strings.
If there are a lot of these variables then you could put the command
line arguments for defining them into a file and add "@filename.txt" to
your command line, with a different file for each language.
Rob
On 15/06/2012 17:4
6 matches
Mail list logo
