2 big benefits I can think of:
1) Machine maintenance
If you have 5 build machines, you don't have to update WiX on all 5 of
the build machines. The synch process pulls down the appropriate WiX version
during the build process.
2) Large projects that share Build machines don't need to all share the same
version of WiX.
Individual projects within a greater product build process could use
different /specific versions of WiX. If 1 of your 50 projects needs to move to
a later version of WiX (bug fixes, feature enhancements, etc...) it can do so
without wondering what side effects might be introduced to the other projects
should they all have moved to the later version of WiX.
Etc...
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher
Karper
Sent: Monday, July 07, 2008 3:25 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Integration of WiX v3 on team build server
How would you expect the build server to be able to use the WiX tools
without them being installed?
I mean, strictly speaking you don't need to install them, just make them
available. But what would be the benefit?
Chris
On Mon, Jul 7, 2008 at 4:01 PM, Dmitry Berkovich <[EMAIL PROTECTED]> wrote:
> Hi,
> I want compile WiX projects on team build server, but I don't want
> install WiX on build server, so I am planning add all needed files to
> source control.
> I have some problem when I am compile wixproj file. wixproj file
> contains those 2 lines:
> <WixTargetsPath Condition=" '$(WixTargetsPath)' == ''
> ">$(MSBuildExtensionsPath)\Microsoft\WiX\v3.0\Wix.targets</WixTargetsPath>
> <Import Project="$(WixTargetsPath)" />
>
> Since WiX not installed on build machine I override CoreCompile target
> of Microsoft.TeamFoundation.Build.targets in my TFSBuild.proj file, so
> I can transfer WixTargetsPath to MSBuild task. The problems that build
> failed since I have error:
> Solution file warning MSB4122: Scanning project dependencies for
> project "MyProj.wixProj" failed. Blablabla since "WixTargetsPath" not
> exist.
>
> What I need to do to resolve this problem?
>
> Thanks in advance,
>
> Dima
>
> -------------------------------------------------------------------------
> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
> Studies have shown that voting for your favorite open source project,
> along with a healthy diet, reduces your potential for chronic lameness
> and boredom. Vote Now at http://www.sourceforge.net/community/cca08
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
