WiXHeat misleading signature- no mode operates on file list
See original GitHub issueThere are currently WiXHeat(IEnumerable<FilePath>, ...)
signatures. heat.exe
ignores all but the first file, so this is misleading.
What we need, as per http://wixtoolset.org/documentation/manual/v3/overview/heat.html:
Mode | Signature |
---|---|
dir |
WiXHeat(DirectoryPath, ...) |
file , project , reg |
WiXHeat(FilePath, ...) |
perf , website |
WiXHeat(string, ...) |
Via command line experimentation, I can confirm that file
, project
, and reg
all ignore subsequent files.
Willing to PR.
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
WIX Heat not harvesting a reg file properly - outputting the ...
Now, if I try to build the reg.wxs file (using candle.exe - candle.exe -v *.wxs), I get the following error: error CNDL0025 :...
Read more >(Wix) heat.exe could not be loaded with msbuild
I get this error message: Unhandled Exception: System.BadImageFormatException: Could not load file or assembly 'file:///C:\Program Files (x86)\ ...
Read more >Heat harvesting
To use Heat to harvest directories, files, or projects: ... Whether to create Directory entries for empty directories when harvesting. The default is...
Read more >Frequently asked questions
Heatmaps (or heat maps); ML Insights. Why should I use Clarity? Clarity offers many unique features that help you understand user behavior:.
Read more >Introduction to Windows Installer XML (WiX) toolset
WiX is a set of tools that allows you to create Windows Installer-based deployment packages for your application. The WiX toolset is based...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think it is ok to base the second feature branch off the first, and then once merged, rebase one last time on develop branch.
However, for the second PR, mark it as
[WIP]
in the title of the PR, so we know not to do anything with it.This is no longer waiting for issuer feedback.