Skip to content

DiscWright 0.8.1

Choose a tag to compare

View all tags
@github-actions github-actions released this 27 Sep 21:57
· 14 commits to main since this release
v0.8.1
96e85dd
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

A bug-fix release, one fix, and it is about the installer rather than the disc. Project files and the on-disc layout are unchanged: a 0.8.0 project opens and rebuilds exactly as it did.

The Start menu shortcut did nothing on a Windows without VBScript

The installer pointed it at wscript.exe and DiscWright.vbs, the launcher whose whole job is starting the app with no console window flashing up first. vbscript.dll is not on a current Windows 11 image: VBScript became a Feature on Demand in 24H2, and Microsoft has said it will be disabled by default and then removed.

On such a machine the shortcut opened a Windows Script Host error box and nothing else, which is where DiscWright ended for anyone who installed it rather than unzipping it.

The installer now asks the machine and builds the shortcut to match:

  • VBScript there: nothing changes, wscript and the .vbs as before.
  • VBScript not there: powershell.exe with its window hidden, which costs a brief console flash. Worth accepting only where the quieter way cannot run at all, which is why it is decided per machine rather than for everybody.

All three places that start the app are covered: the Start menu shortcut, the optional desktop icon, and the tick box at the end of the install.

Why 0.8.0 shipped with it

Smart App Control blocks an unsigned installer on the machine DiscWright is developed on, so the installer had been going out having never been run. Windows Sandbox is a throwaway Windows without that policy, and packaging\sandbox\Test-Installer.ps1 now installs a release there, checks what Windows records, starts the app, uninstalls and checks it is gone. Running it against 0.8.0's own published installer is what found this, and it is a step in the release runbook from now on.

This release was tested that way before publishing, which 0.8.0 was not. Every check passed on a clean Windows 11 image.

What was never affected

  • The zip. Run DiscWright.cmd calls PowerShell directly and never touches VBScript. Checked here too: it unpacks and opens as 0.8.1.
  • Discs. The same sandbox run confirmed mshta, JScript and Scripting.FileSystemObject are all on that image, so a disc's menu has everything it uses.

Checksums

DiscWright-0.8.1-setup.exe  6300530B57241510EF20638E98FE2DDADF4C824042C3A8165181C0976D42F17B
DiscWright-0.8.1.zip        3572F96EBD228AD1ACC1119B2105EBF6138A17C8578F27691D04E2882DC25EE7

Tests: 478 logic, 92 window, plus the installer on a clean Windows.

Assets 4
Loading