Hi Bob, no I'm saying $(env.var) does work when running MSBuild from the Razzle
window, but only from the Razzle window. If you run msbuild anywhere else, or
launch Visual Studio from outside of Razzle and try to build they it fails.
The 'you still need to get the variables from somewhere' was the issue. I was
wondering if I could set the same pathing that I do in setenv.cmd for the
Razzle environment in the wixproj file somehow.
If not then when I check in my current code (MSbuilding with the $(env.var) in
Razzle) I'll have to make sure all devs going forward launch VS within the
context of Razzle, otherwise the msbuild will fail.
Thanks,
DC
From: Bob Arnson [mailto:[email protected]]
Sent: Wednesday, January 28, 2009 6:26 PM
To: Windows Installer XML toolset developer mailing list
Subject: Re: [WiX-devs] Passing Environment Variables
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
