Some properties are not available until the linker is about to generate, or bind, the final output. These variables are called binder variables and supported binder variables are listed below.
The following standard binder variables are available for all versioned binaries.
Variable name |
Example usage |
Example value |
1033 |
||
1.0.0.0 |
The following standard binder variables are available for all managed and native assemblies (except where noted), where the File/@Assembly attribute is set to ".net" or "win32".
Variable name |
Example usage |
Example value |
|
neutral |
|
1.0.0.0 |
||
|
MyAssembly, version=1.0.0.0, culture=neutral, publicKeyToken=0123456789abcdef, processorArchitecture=MSIL |
|
MyAssembly |
||
MSIL |
||
0123456789abcdef |
||
|
win32 |
|
1.0.0.0 |
Variables can be passed in before binding the output file from a WiX localization file, or .wxl file. This process allows the developer to link one or more .wixobj files together with diferent .wxl files to produce different localized packages.
Localization variables are in the following format:
!(loc.VariableName)
Read more about localization for how to create and link .wxl files.
You can create your own binder variables using the WixVariable element or by simply typing your own variable name in the following format:
!(bind.VariableName)
Custom binder variables allow you to use the same .wixobj files but specify different values when linking, similar to how localization variables are used. You might use binder variables for different builds, like varying the target processor architecture.