tylerjenningsw 4aea350f2a Packaging: the installer's Repair puts back a damaged effectcraft-cli.exe (#466) ...

Cause: Repair used REINSTALLMODE=ecmus. effectcraft-cli.exe has no version
resource, so Windows Installer treats it as unversioned: a changed copy
with a later write time counts as a user edit and is kept, and "c" only
checks files that carry an MSI checksum, which these don't.

Fix: Repair uses "amus", which puts back every file whatever its version
or date.

Tests: test-msi.ps1's stand-in CLI is unversioned like the real one; the
test damages it in place and repairs with the REINSTALLMODE read from
installer-ui.wxs (no longer msiexec /fa after deleting it), then compares
contents. It fails with ecmus (the damaged file stays) and passes now.

2026-10-09 14:49:19 -04:00

..

effectcraft.wxs

Packaging: upgrading a custom-folder install from 0.6.0 or earlier keeps its folder (#466)

2026-10-09 14:45:47 -04:00

installer-ui.wxs

Packaging: the installer's Repair puts back a damaged effectcraft-cli.exe (#466)

2026-10-09 14:49:19 -04:00

package.ps1

Packaging: the Windows installer asks where to install EffectCraft (#466)

2026-10-09 13:58:35 -04:00

sign.ps1

Signed release pipeline (macOS/Windows/Linux/Web); README community note

2026-10-02 12:06:24 -04:00

test-msi.ps1

Packaging: the installer's Repair puts back a damaged effectcraft-cli.exe (#466)

2026-10-09 14:49:19 -04:00