You can definitely do this. My first question is why are you using
CreateProperty instead of setting a property directly using <PropertyGroup>
elements? You should only have to use CreateProperty if the value is something
computed on the fly by the build.
Here's what our project file looks like:
<!-- This group contains properties we use to indicate the location of
various files on disk -->
<PropertyGroup>
<!-- Location of the redistributables that get built into setup. -->
<RedistPath>$(EXTPATH)\BootstrapFiles</RedistPath>
<!-- Where the source files are for the installation package. -->
<SourceFileLocation>$(INETROOT)\target\$(Configuration)\i386</SourceFileLocation>
<PropertyGroup>
<!-- Override the defined constants from the Wix Targets to pass in
appropriate constants from the environment. -->
<PropertyGroup>
<DefineConstants>$(DefineConstants);SourceFileLocation=$(SourceFileLocation);RedistPath=$(RedistPath)</DefineConstants>
</PropertyGroup>
The values for $(DefineConstants), $(SourceFileLocation), etc. can come from
anywhere, including from your TFSBuild.proj file I believe. In our case they
happen to be in the same .wixproj as the <DefineConstants> element.
Neil
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Joe Pub
Sent: Friday, August 01, 2008 9:03 AM
To: [email protected]
Subject: [WiX-users] Overriding DefaultConstants or sending variables to candle
using TFSBuild
Hi,
I am using Wix 3.0.4318.0. I have created a Wix project using Votive
and have added it to TFS. I am attempting to either customise the
whole DefaultConstants property inside my TFSBuild.proj file or create
a property which is referenced in the DefaultsConstants property at no
avail.
I have created a property insode the BeforeCompile target inside
TFSBuild.proj like this
<CreateProperty Value="TestString">
<Output TaskParameter="Value" PropertyName="TestProp"/>
</CreateProperty>
and then Votive has a reference to using the Define preprocessor
Test=$(TestProp).
When checking the Build log, the candle command line lists the Test
var as empty.
I have also tried another approach of attempting to override the whole
DefaultsConstants property inside TFSBuild.proj. Is there a way to
get variables to the candle compiler?
Thanks
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
