leifiyo
Posted on Nov 15
AI-assisted
Shipping a desktop app to Windows tends to end the same way: you pick NSIS, Inno Setup or WiX, and then you learn a scripting language or an XML schema to get a setup file out of the door.
I built Bach because making a Windows installer shouldn't need a script language or a compiler. It covers the common case, an app that installs for one user, with settings instead of code.
What it looks like
This is the whole config for a Rust app:
[app] name = "Hello" version = "1.0.0" publisher = "Hello Inc." executable = "hello.exe"
[files] source = "target/release" exclude = [ "*.pdb" , "deps/**" , "build/**" ]
Enter fullscreen mode
Exit fullscreen mode
$ bach build Wrote dist\Hello-Setup-1.0.0.exe ( 9.7 MB ) Packed 101.8 KB of 216.5 KB ( 47% ) , in 0.9s
Enter fullscreen mode
Exit fullscreen mode
source is the folder your build writes to. Bach packs it, plus the config, into one Setup.exe .
What the setup file does
No admin prompt.…