|
I’m going to check in a breaking change which will
affect anyone with a compiler extension. The change is basically to add a new
SourceLineNumberCollection argument to CompilerCore.AddValidReference. This
will allow WiX to display unresolved reference errors with source line
information. The reason I made this change is because as the references
feature in WiX is used more predominantly, it’s become more and more
difficult to tell why certain references are created. For example, if you
author a bitmap control, it creates a reference to the Binary element
containing the bitmap file. If the binary isn’t found during
linking, you might be a little confused because there is no explicit BinaryRef
that references the element. Hopefully, the additional source line
information will be a good prompt for figuring out what’s going on.
This should also help in the scenario in which an extension adds a reference to
a custom action dll which needs to be provided at link time. Previously
you might just see an error like “CustomAction:ConfigureIIs
unresolved”. But now, there will be source line information of the
WebSite element which pulled in that custom action. Derek |
