I might recommend an easier bug to start with than that. <smile/>

The solution to that bug is to redo the handling of file transfers in the 
Binder such that we can tell the difference between generated and non-generated 
input files. We also need to move all of the temporarily generated files to a 
new location under the intermediate folder (which also means we need to provide 
the intermediate folder to the Binder). At the same time want to handle the 
.wixlib and merge modules that break incremental build as well.

Basically, it's a large refactoring/rewrite feature to massively clean up the 
Binder and solve a bunch of core bugs. I wouldn't start there. <smile/>

How about one of the following:

2301
2299
2298
2281
2246
2155
2133

Those are (IIRC) easy bugs and will allow you to walk through the WiX processes 
(which have a bit of learning curve) without getting too buried in the actual 
fix.


From: Rob Winningham [mailto:[email protected]]
Sent: Sunday, February 9, 2014 1:15 PM
To: [email protected]
Subject: [WiX-devs] Issue 4049 - Tag Extension breaks Incremental Build

I'd like to work on Issue 4049<http://wixtoolset.org/issues/4049/>.

The problem:

Use of ISO/IEC 19770-2 SWID Tag in authoring causes temporary file containing 
SWID regid to be produced in %TEMP%. This file is used as input to Link target 
in MSBuilld. Because new temporary file is generated every time the build 
occurs and this file is always newer then build output, the build of Link 
target is triggered.

Observation


  *   The file written to %TEMP% is not deleted by WiX.

Potential solution:


  *   Give the file a predictable name (such as the "File_" column from the 
SoftwareIdentificationTag table.)
  *   At compile time, only create or update the file if necessary.

Additional ideas:


  *   Treat the file as Intermediate Output

     *   Write the file to the IntermediateOutputPath (obj) folder instead of 
%TEMP%
     *   Add the file to FileWrites so that it can be cleaned

Thoughts:

If the file is treated as Intermediate Output, I'm not certain where/how to add 
the file to FileWrites.  Since the file is created by the binder, I'm not 
certain there's a simple way to tell MSBuild to add it to FileWrites.  I'm 
hoping someone smarter than me can point me in the right direction.
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
WiX-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-devs

Reply via email to