Non-standard filenames in the zip

[rhoot]

It looks like the script to package this is using PowerShell's Compress-Archive to create the zip files. Up until 2019 that command produced non-standard filenames inside the zip-files. It looks like whatever version being used to package this is older than that.

The result when you try to open the zip-file on a non-Windows system is this. The backslashes are embedded as part of the filename of the DLL, and the parent folder appears as its own entry:

Thankfully this zip file only has one file in it so it's not particularly hard to fix manually, but it'd be nice either using a newer version of PowerShell that doesn't have this problem, or using something else to create the zip files so it doesn't have to be fixed up manually. 🙂