This much less a WiX issue and more of a MSBuild issue as that's what is used 
to perform a build in Visual Studio 2010.

MSBuild has the concept of Target Inputs and Outputs which it uses to determine 
whether a target need to be executed in incremental build scenarios.

The wix2010.targets file imported by your .wixproj project will need to be 
customized to make this work as you expect. The changes will likely need to 
completely replace some of the targets defined in wix2010.targets with versions 
that make use of Target Inputs and Outputs in a fashion that is consistent with 
your expectations.

Edwin G. Castro
Software Developer - Staff
Digital Channels
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
Please consider the environment before printing this e-mail


> -----Original Message-----
> From: Sean Leonard [mailto:lists+sourcefo...@seantek.com]
> Sent: Wednesday, May 18, 2011 10:48 PM
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Developer with WiX experience needed; proper
> incremental build support
> 
> Hi WiX users:
> 
> I'm working on a WiX installer that installs a native Windows application. The
> application itself is not too complex--just three files. But, we need to do
> several things in WiX and with a supporting native bootstrapper setup
> executable that seems to have eluded other developers that have worked
> on the project.
> 
> As a developer myself I could do it, but, WiX is a skillset that I am trying 
> not to
> learn (not becaue I dislike WiX, but because I am needed on other aspects of
> the product).
> 
> Anyway, the specific question (so that this is not just a naked job
> post) is: how can the WiX files be setup so that they have proper incremental
> build support in Visual Studio 2010 with multiple language source files? The
> process is:
> 
> Take 3 input files (DLLs, EXEs) ->
> Take 10 localizations (en-us, ja-jp, fr-fr, etc.) -> Create master msi Create 
> 10
> transforms stash the transforms somewhere Use EmbedTransform to create
> one final msi file with the 10 transforms, so the software can ship as one MSI
> 
> When an incremental build happens:
> * If zero input files have changed and the final msi has not changed, NO build
> should occur. We're done.
> * If one of the 3 input files have changed, create the initial msi, and use
> embedtransform to create one file msi from the stashed transforms.
>   (This sounds implausible, but, I have looked at the transforms and they are
> for all intents and purposes the same. There seems to be no reason to
> constantly rebuild the transforms.)
> * Only if one of the localizations has changed, for example, one of the 
> strings
> has changed, then the 10 transforms should be regenerated.
> 
> 
> I have tried to post this job to elance but no developer has actually been
> successful at finishing the job, which is very frustrating. If anybody wants 
> to
> work on this, I have a job for you. :) I am also looking for a developer who 
> can
> help work on the native Win32 bootstrapper which still has a ways to go.
> 
> Thanks,
> 
> Sean
> 
> ------------------------------------------------------------------------------
> What Every C/C++ and Fortran developer Should Know!
> Read this article and learn how Intel has extended the reach of its next-
> generation tools to help Windows* and Linux* C/C++ and Fortran developers
> boost performance applications - including clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its 
next-generation tools to help Windows* and Linux* C/C++ and Fortran 
developers boost performance applications - including clusters. 
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to