Skip to main content
bach import reads an Inno Setup script (.iss) or an NSIS script (.nsi) and writes a first bach.toml next to it. Both are programming languages, so it reads only what has a setting in Bach, and lists what it left out. It runs on Windows, macOS and Linux.

What comes across

  • The app’s name, version, publisher, website and icon, the license file and the install folder’s name.
  • The folder the files come from ([files] source, the folder most Source: or File lines take from) and what they exclude.
  • Whether the install is machine-wide (PrivilegesRequired, RequestExecutionLevel, a Program Files folder), the desktop shortcut, extra Start menu shortcuts, and programs the script runs from the install folder ([[run]]).
  • #define constants ({#Name}) and !define constants (${NAME}) are filled in.

What is listed instead

Registry writes, custom pages and code ([Code], NSIS functions), components, {tmp} and system programs, files that go to other folders, and an #include file. A setting the script doesn’t give is marked in the file (# name = ""), and bach check reports it.
Inno Setup asks for administrator rights unless the script says PrivilegesRequired=lowest, so such a script becomes scope = "machine" and the command says so. Delete that line if the app can live in one user’s folder. Read the file before you build: it is a starting point, not a copy of what the old installer did.
See also Migrate from another installer, which removes the old installer’s install from computers that have it.