Re: [WiX-users] Loading Extensions
Thanks, that was it. I had a hunt round the documentation and I couldn't see that documented and I didn't think the command line help made it too clear either. I'm sure there is lots that need documenting but I think this would be useful to add. Neil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson Sent: 02 August 2008 21:43 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Loading Extensions Neil Sleightholm wrote: > That's odd, I tried it today before posting with v3.0.4401.0 and it > doesn't work. Just to confirm what I did, I put candle in the path and > got this error: > candle.exe : error CNDL0144 : The extension WixUIExtension.dll' > could not be loaded. > Drop the ".dll" extension. If you give a filename, it will try to load it as a path and it doesn't have enough information to do so. -- sig://boB http://joyofsetup.com/ - 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
Re: [WiX-users] Overriding DefaultConstants or sending variables to candle using TFSBuild
Hi Dmitry, That sounds like the way to go, so I basically copy the CoreCompile target from Microsoft.TeamFoundation.Build.targets and make my modifications as required? Thanks 2008/8/2 Dmitry Berkovich <[EMAIL PROTECTED]>: > Hi Joe, > First of all parameters that you are declare in the TFSBuild.proj not > passed to your solution that compiled. Its existing 2 way to pass them to > solution and all inner projects, but it depends when Team Build you are > using : 2008 or 2005. > > (*) 2008 its will be easy: > http://msdn.microsoft.com/en-us/library/bb399127.aspx ( i can confiirm that > it working, since I am using 2005) > (*) 2005 - its more complexity. You need redefine "CoreCompile" target. if > you will look in original "CoreCompile" target (declared in > Microsoft.TeamFoundation.Build.targets) you will find this row: > > Condition=" '@(SolutionToBuild)'!='' " > Projects="@(SolutionToBuild)" > > Properties="Configuration=%(ConfigurationToBuild.FlavorToBuild);Platform=%(ConfigurationToBuild.PlatformToBuild);SkipInvalidConfigurations=true;VCBuildOverride=$(MSBuildProjectDirectory)\TFSBuild.vsprops;FxCopDir=$(FxCopDir);OutDir=$(OutDir);ReferencePath=$(ReferencePath);TeamBuildConstants=$(TeamBuildConstants);$(CodeAnalysisOption)" > Targets="Build" /> > as you see here, it transfer only several predefined properties, so you need > little change this code, to make ability transfer your own properties. > > Dima. > > P.S - you can override this target in your TFSBuild.proj, you don't need > change original Microsoft.TeamFoundation.Build.targets file. > > > On Sat, Aug 2, 2008 at 1:12 PM, Joe Pub <[EMAIL PROTECTED]> wrote: > >> 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 >> > >> > >> >TestString >> > >> > >> > >> >Test=$(TestProp) >> > >> > >> > 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 >> 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: >> >> >> >> >> >> >> >> >> >>$(EXTPATH)\BootstrapFiles >> >> >> >> >> >> $(INETROOT)\target\$(Configuration)\i386 >> >> >> >> >> >> >> >> >> $(DefineConstants);SourceFileLocation=$(SourceFileLocation);RedistPath=$(RedistPath) >> >> >> >> >> >> 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 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 >> >> >> >> >> >> >> >> >> >> >> >> 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 t
Re: [WiX-users] Loading Extensions
Neil, Can you open a sourceforge bug on this requesting the clarified documentation? Thanks! Neil From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Neil Sleightholm [EMAIL PROTECTED] Sent: Sunday, August 03, 2008 2:38 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Loading Extensions Thanks, that was it. I had a hunt round the documentation and I couldn't see that documented and I didn't think the command line help made it too clear either. I'm sure there is lots that need documenting but I think this would be useful to add. Neil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson Sent: 02 August 2008 21:43 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Loading Extensions Neil Sleightholm wrote: > That's odd, I tried it today before posting with v3.0.4401.0 and it > doesn't work. Just to confirm what I did, I put candle in the path and > got this error: > candle.exe : error CNDL0144 : The extension WixUIExtension.dll' > could not be loaded. > Drop the ".dll" extension. If you give a filename, it will try to load it as a path and it doesn't have enough information to do so. -- sig://boB http://joyofsetup.com/ - 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
Re: [WiX-users] Wix and TFS
Thanks a lot. I will try it out. Neil Enns wrote: > > Here's the documentation I mentioned that should show up in the next > weekly WiX build: > > Integrating WiX Projects Into Daily Builds > > One of the most common reasons for using MSBuild with WiX project files is > to integrate the build of an installer into an existing daily build > process. This is often coupled with a need to build WiX projects without > having to pre-install any WiX tools on the daily build machine. WiX > projects and the WiX toolset to build them can be added to most daily > build processes that support MSBuild using a few simple steps. > > Step 1: Check in the WiX Toolset > > To avoid having to install WiX on build machines you can check all the > tools necessary to build WiX projects into your source code control > system. Here's how: > > 1. Install WiX on a developer machine using the standard WiX installer > 2. Create a directory in your source code control system to hold the WiX > tools > 3. Copy the contents of c:\Program Files\Windows Installer XML v3\bin into > the directory created in step 2 > 4. Copy the contents of c:\Program Files\MSBuild\Microsoft\WiX\v3.0 into > the directory created in step 2 > 5. Add and check in the files from steps 3 and 4 > > Step 2: Modify Your .wixproj File > > After checking the WiX tools into source code control the .wixproj file > must be modified to point to the location of the checked in tools. Open > the .wixproj file in any text editor, such as Visual Studio, and add the > following to the file anywhere between the element before the > element: > > > $(SourceCodeControlRoot)\wix\3.0.4311.0 > $(WixToolPath)\Wix.targets > $(WixToolPath)\wixtasks.dll > > > The WixToolPath must be set to point to the location of the WiX tools > directory created in Step 1. The method used to reference the location > will vary depending on your build system, but it can either be a relative > path to the directory (such as ..\..\tools), an MSBuild property that is > set via an environment variable (such as $(BinariesRoot) in a Team > Foundation Server build) or a custom property passed in on the > command-line or via an environment variable. > > The WixTargetsPath and WixTasksPath properties direct MSBuild to use the > WiX build process and WiX tasks from the tools directory. > -- View this message in context: http://www.nabble.com/Wix-and-TFS-tp18768809p18804264.html Sent from the wix-users mailing list archive at Nabble.com. - 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
