Binder variables are only provided for all versioned binaries (only fileversion and filelanguage) and only for assembly attributes for files attributed with File/@Assembly set to ".net" or "win32". There are cases where assembly binder variables are helpful, like when registering a type to a private assembly location in the registry, XML file, etc.
There is a workaround, by setting File/@AssemblyApplication to its own File/@Id, but this is not intuitive.
A solution, if any, should not hinder performance (or at least optionally hinder performance) by checking every possible file for an assembly identity.
Binder variables are only provided for all versioned binaries (only fileversion and filelanguage) and only for assembly attributes for files attributed with File/@Assembly set to ".net" or "win32". There are cases where assembly binder variables are helpful, like when registering a type to a private assembly location in the registry, XML file, etc.
There is a workaround, by setting File/@AssemblyApplication to its own File/@Id, but this is not intuitive.
A solution, if any, should not hinder performance (or at least optionally hinder performance) by checking every possible file for an assembly identity.
bq. Originally opened by @heaths@ from "http://sourceforge.net/p/wix/feature-requests/358/":http://sourceforge.net/p/wix/feature-requests/358/