Mike Dimmick wrote:
As a workaround -- as WiX is likely to be more reactive than the SDK
team -- perhaps WiX could only generate these fields if they're used?
On the other hand, their presence doesn't appear to do any harm when
actually installing on operating systems before Windows Vista, so the
ICE can be ignored. Adapting WiX to generate variable schema could be
difficult as at present the schema is fixed (it all comes from
src\wix\Data\tables.xml).
MSI is explicitly backward-compatible so the "extra" columns (from MSI
3.1's point of view) are just ignored.
I suppose the ICE would have to change from currently just reporting
based on the presence of the new fields, to reporting based on whether
the contents of the field in any row is non-null.
That was my bug report to the MSI team. However, I have a workaround out
for review that does the equivalent of ICE66's checks, plus the non-null
column values, in the linker. Then I suppress ICE66 by default.
--
sig://boB
http://joyofsetup.com/
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
