Mise

For managed mise deployments, treat it as a developer toolchain manager rather than a normal MSI product. The official install docs show profile activation for PowerShell with (&mise activate pwsh) | Out-String | Invoke-Expression; deploy that profile change intentionally, because without shell activation users may have the binary installed but not get automatic tool-version switching.

When building shared images, CI runners, or locked-down workstations, pin the mise storage paths instead of relying on per-user defaults: the docs expose MISE_DATA_DIR, MISE_CONFIG_DIR, MISE_CACHE_DIR, and MISE_INSTALL_PATH, and the shim directory must be on PATH. After placing the binary and configuration, run mise install for configured tools; use mise use -g only when you deliberately want a global default tool version. Source: official mise installation docs.