Darren Cormier wrote:
Yes I have, but in order to take advantage of that you
must launch Visual Studio from your Razzle window. By doing this VS
has the context of all environmental variables that are defined in
source depot's setenv.cmd. That's currently the only way I'm able to
msbuild. I could enforce this process to the rest of my team as a
solution but I was curious if there was another way to pass them.
Perhaps through the .wixproj file like preprocessor variables are defined?
You can pass whatever you want as additional preprocessor variables
(using the DefineConstants property) but you still need to get the
values from somewhere. Are you saying $(env.var) doesn't work when
running MSBuild from a razzle window (outside loading the .wixproj in VS)?
--
sig://boB
http://joyofsetup.com/
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
WiX-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-devs
