FAQ
Frequently asked questions about BSIS, its current status and planned features.
What does BSIS stand for?
Better NSIS. It is an independent project exploring a modern, design-first Windows installer framework. Its goal is not to repackage NSIS under another name.
Can I download BSIS?
Not yet. The Rust core is private and the current proof of concept is not a public release. The documentation is public so design decisions and implemented capabilities can be followed as the project develops.
Is there a graphical installer?
Yes, as an experimental, opt-in Windows WebView2 preview. A packaged setup can launch the fixed offline install wizard with Setup.exe gui. The installed Uninstall.exe gui opens a separate receipt-verified removal window. The default double-click/zero-argument flow is still console mode. Developer-provided custom Svelte/React screens and a stable UI API are not available yet. See Installer UI.
Which languages can I use?
The current engine is written in Rust and accepts JSON build configurations. TypeScript, JavaScript, Svelte and other languages are future developer experience options, not supported source plugins today.
Which compression algorithms work?
Zstandard is implemented for embedded offline payloads. Developers can select compression levels 1–19 with bsis build --compression-level; the default is 3. LZMA2 and LZ4 remain proposed, not available. See Packaging.
Does --yes make it a silent installer?
It skips the confirmation prompt for the prototype commands, but full unattended deployment, exit-code contracts and silent GUI behavior need further work.
Is BSIS safe for production distribution?
No. The proof of concept is explicitly experimental. Publisher signing, upgrade safety, UAC, platform compatibility and security hardening are incomplete. See Security model.
Does it support updating an existing installation?
Not yet. Installation requires a new target directory. Updating, repairing, rollback and Windows application registration are on the roadmap.
Why does the site have documentation before a public release?
To document verified behavior, track architectural decisions and help avoid confusing future proposals with current capabilities. The site is updated independently of the private engine.
Where can I find exact commands?
Use CLI reference for the implemented commands or Getting started for a complete test workflow.