New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extract Icon Resources from PE Files #4340
Comments
Hello
What I'm expecting is adding exe once to msi, but it is added twice, because of Icon Table.
|
|
@robmen @barnson any chance we can do this in v5? I'd suggest an optional attribute like IconIndex that tells wix to extract that resource and place it in the table instead of the actual file. This would be very helpful for IsWiX as I could author a browse/preview in the designer and then author the XML accordingly. |
No, I'm full up for WiX v5. |
I'm you actively against such a feature? Assign it to me and I could give it a try. This is a high value feature to me so I'd be willing to fund it if someone wante to give me a price. |
No, but there's overlap with the ARP feature that would need to be address in the WIP. |
What/where is the ARP feature? Is that basically the same type of situation but instead of referenced by a shortcut its referenced by ARPPRODUCTICON? If so I can imagine a couple possible paths:
|
Strongly-typed authoring for product registration. |
A recent question on stack overflow centered around MSI bloat as an EXE was being included twice when the developer expected it only once (smartcabbing). The bloat was from the Icon table. It would be nice if the Icon element had an optional IconIndex attribute that if present would cause WiX to extract the icon resource during the build and use that as it's source path instead of the primary source path. FWIW, InstallShield does this as it's icon table is Name, Data, ISBuildSourcePath and ISIconIndex where the last two columns are removed from the final MSI.
The text was updated successfully, but these errors were encountered: