Unfortunately I don't have a TFS install handy to look at this directly :( I did some quick searches on-line and it looks like depending on the version of Team Build you're using that you might need to modify some targets files to make this work. I would suggest asking your question over at the Team Build fourm (http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=481&SiteID=1), someone there likely can tell you how to do this.
Neil ________________________________ From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Joe Pub [EMAIL PROTECTED] Sent: Saturday, August 02, 2008 3:12 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Overriding DefaultConstants or sending variables to candle using TFSBuild But my problem is that I need some of the properties that are created in the tfsbuild.proj. I am trying to get the version number that is generated in the tfsbuild.proj into the .wixproj. So there is no way to get them into the .wixproj? Thanks 2008/8/1 Neil Enns <[EMAIL PROTECTED]>: > Joe, > > Simply setting properties in the tfsbuild.proj file won't get them passed > down into the .wixproj. I wasn't sure about this and had to look it up. Is it > an option to just include those changes directly in the .wixproj file instead? > > Neil > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Joe Pub > Sent: Friday, August 01, 2008 9:19 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Overriding DefaultConstants or sending variables to > candle using TFSBuild > > I have tried both CreateProperty and PropertyGroup, and neither seem > to work. I have placed mine inside Project element inside the > TFSBuild.proj file which looks like this > > <PropertyGroup> > <TestProp>TestString</TestProp> > </PropertyGroup> > > <PropertyGroup> > <DefineConstants>Test=$(TestProp)</DefineConstants> > </PropertyGroup> > > So based off my understanding, the DefineConstants should be totally > replaced using the above code, but when checking the build log, it has > all the defines that have been specified using votive. > > Any ideas? > > 2008/8/1 Neil Enns <[EMAIL PROTECTED]>: >> 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: wix-users@lists.sourceforge.net >> 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 >> WiX-users@lists.sourceforge.net >> 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 >> WiX-users@lists.sourceforge.net >> 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 > WiX-users@lists.sourceforge.net > 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 > WiX-users@lists.sourceforge.net > 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 WiX-users@lists.sourceforge.net 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 WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
