It's so weird, we have MSBuild message tasks, outputting the environment variable, and pre-build events outputting the variable, each correctly displaying the value in the build log. If we place the hard-coded path in the pre-processor args list instead of a redirection to the environment var, it works - so yes, the env var is evaluating to empty, why would MSBuild NOT tokenize this argument and replace env vars? It was working for almost a year....
sooo sooo bizarre. Adam Langley Senior Developer +64 9 486 9010 alang...@winscribe.com www.winscribe.com Please consider the environment before printing this email! -----Original Message----- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Wednesday, 9 June 2010 3:43 p.m. To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Candle is ignoring preprocessor arguments The value must be evaluating to blank because it would be failing if the variable was not defined at all. On Tue, Jun 8, 2010 at 3:22 PM, Adam Langley <alang...@winscribe.com> wrote: > Argh! > > We had a fully functional build server (TFS 2008), creating our installers, > then on Friday the builds just started turning red. > The problem seems to be, we pass variables to candle, which defines the > root folder for all content file locations: > > e.g. (truncated) > C:\Program Files\Windows Installer XML v3\bin\candle.exe > -d"Tasks=D:\TFSBuild\Temp\Product\Installers_v1.0_Trunk\Sources\Tasks\" > > This is then used in the source files like this > <File Name="NLog.dll" > Source="$(var.Tasks)\_PublishedWebsites\EmailRelay\bin\NLog.dll" Vital="yes" > /> > > And we're getting "file with path, > \_PublishedWebsites\EmailRelay\bin\NLog.dll, not found" from light.exe. > > I looked at the .obj file generated by candle.exe, and it turns out that > the Source of the file has failed to embed the value of $(var.Tasks) (it has > evaluated to empty string), meaning that of course light.exe isnt going to > be able to find the source files - the problem lies in candle.exe. > > Why would candle.exe just start doing this all of a sudden? We havent > changed anything in the source files, nor updated our WiX installation. > We can SEE that candle is being passed the value on the command-line, but > it just FAILS to put it into Source paths! > > Help! > > Thanks > > Adam Langley > Senior Developer > +64 9 486 9010 > alang...@winscribe.com > www.winscribe.com > > > > Please consider the environment before printing this email! > > > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- virtually, Rob Mensching - http://RobMensching.com LLC ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
