Build & Run vs export only

Goal: Choose between testing instantly in Live (desktop) and shipping an installable package (web or desktop).

Time: ~5 minutes

Steps

  1. While designing, use Build & Run on the desktop app when Live is open — fastest loop for hearing and seeing changes.
  2. Confirm Extension Host is set via toolbar Host… before your first Build & Run (see Set up Extension Host).
  3. Set Extension name and Author on the toolbar before either build type — Live shows these in the menu.
  4. When you need an installable package to deploy directly into Live on desktop, click Export .ablx (desktop only, visible when a compatible Live install is detected) — this reveals the .ablx in Finder and brings Live to focus, completing the install workflow. To produce a portable file for sharing or CI handoff without triggering the install workflow, click Build .ablx instead.
  5. Build .ablx produces an installable extension package without requiring Live to be connected at build time — ideal for web Patchwright or CI handoff.
  6. After Build .ablx, install the package through Live’s extension workflow and enable it in preferences.
  7. Re-run Build & Run (desktop) whenever you change the graph and want immediate refresh in the open Set.

Expected result

Build & Run updates the extension in your current Live session. Build .ablx gives you a portable package you can install on another machine or share.

If something goes wrong

Problem What to do
Build & Run does nothing Set up Extension Host; keep Live open with a Set
.ablx missing Check build status and log; fix graph errors first
Live shows old behavior Build again; confirm you saved the project
Web cannot Run Expected — use Build .ablx and install in Live
Name wrong in menu Change toolbar Extension name before rebuild

See also