Bind variables *might* work because they might be processed after the .wxl files. Preprocessor variables definitely won't because they are run before the Compiler which doesn't even reference the .wxl files.
Jacques Eloff wrote: > Hi > > Is it possible to refer to variables inside your .wxl file? > > I have a situation where a value is defined inside an environment variable > that is used throughout various parts of a project (msbuild, custom cmd > scripts and WiX). This value is passed to candle using the -d commandline > switch, so it works fine for my .wxs file. I would also like to refer to > this inside a <String> element inside my wxl file, but if you write > something like <String Id='foo'>$(var.foo)</String> and then reference > !(loc.foo) inside your .wxi/.wxs file, then the MSI contains the string > literal of $(var.foo). > > Can custom bind variables be used to work around this problem when I run > Light? > > Thanks, > Jacques > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
