wixtoolset / issues

WiX Toolset Issues Tracker
http://wixtoolset.org/
130 stars 24 forks source link

Unnamed bindpath not respected #8585

Open Emdot opened 5 months ago

Emdot commented 5 months ago

WiX Version

5.0.0

.NET or MSBuild or Visual Studio Version

.NET 8.0.300

HeatWave Version

1.0.4.5

Windows Version

Win10 21H2

Repro Repo

No response

Repro Steps

  1. In a wxs file, use Files with Include="**". Example:
    <Wix xmlns="http://wixtoolset.org/schemas/v4/wxs">
    <Package Name="MyProduct" Version="1.0.0.0" Manufacturer="Example Corporation" UpgradeCode="{ABCDEFF7-BC0C-4393-ACD8-B2396B5C3564}"     >
                <Files Include="**" />
    </Package>
    </Wix>
  2. wix build -bindPath ..\data test.wxs
  3. wix msi decompile test.msi -o test.decompiled.wxs
  4. View the decompiled results

Actual Result

The MSI included files from the source directory

Expected Result

The MSI included files from the directory specified by the -bindpath argument.

The documentation for Files says of **: "If an unnamed bind path was specified, all files in that directory and its subdirectories."

Possibly related:

Acknowledgements

Emdot commented 5 months ago

Named bindpaths work for me in wixproj files. I don't know what's different about that vs. the command line.