Package cache page
The Package cache page of the Control Panel lists the packages
Prism for AL has cached, with their size, and lets you remove them. The package cache holds what
Prism extracts from .app files, so a workspace loads faster the next time. It also lets Prism resolve
packages that are not in the workspace; see Search depth.
Prism writes to the cache while it loads a workspace, when it meets a new package or a new version of a known one.
The cache is in %LOCALAPPDATA%\Statical\PrismAL\PackageCache\v2 unless you change
Package cache path on the Settings page.
Opening it
- Select Package cache in the Control Panel's navigation rail.
- On the page, press F1 to open this manual page.
| # | Name | Description |
|---|---|---|
| 1 | Copy script to clipboard. | Copies a PowerShell script that excludes the package cache from Microsoft Defender scans. See Speed up the cache. |
| 2 | Refresh | Re-reads the package cache: packages other processes added or removed, and pin state. The time of the most recent refresh is shown after the wipe buttons, as Refreshed. |
| 3 | Show only pinned packages | Shows only the pinned packages. The tooltip says how many packages are pinned. |
| 4 | Wipe selected package | Removes the selected package from the cache. See Wipe packages. |
| 5 | Wipe all packages | Empties the cache, except packages in use. |
| 6 | Total size | The size on disk of the whole cache, including the packages the filter hides. |
| 7 | Filter packages... |
Filters by publisher, name, module id or version range. Here the range 23.0..24.0 keeps the
version 23 packages. The list changes as you type.
|
| 8 | Status | A check mark when the package is extracted and ready, dots while it is being extracted or deleted, and an error mark when extraction or a delete failed. Point at it for details, such as why a delete was refused. |
| 9 | Pin | A pin marks a package in use by a workspace open in this Prism; a second icon marks one held by another Prism process, such as another Prism window, an MCP server or a command. Pinned packages are shown in bold and cannot be wiped. |
| 10 | Publisher | The module's publisher. |
| 11 | Name | The module's name. |
| 12 | Version | The module's version. |
| 13 | Size | The package's size on disk, with a bar showing it against the largest package in the list. |
Package list
- Sort: the list starts sorted by size, largest first. Select a column header to sort by that column.
- Details: point at a row to see the package's publisher, name, version, id, path in the cache and
state; what pins or holds it; and when it was extracted, by which Prism version, from how large a
.appfile, and its signature. - Copy: press Ctrl+C to copy the selected row.
- Cache folder: when the cache is not in the default folder, the banner at the top shows where it is.
Wipe packages
Wiping saves disk space, but the next workspace that needs a wiped package loads more slowly, since Prism extracts the package again. A package in use by a workspace, an MCP server or a command stays in the cache.
- Select a package in the list, as Base Application is selected above.
- Select Wipe selected package. The row shows dots while the package is deleted, and disappears when it is gone.
- If the package is in use, the Packages in use window says what uses it. Close that, then select Try again.
Wipe all packages deletes every package without asking, in a window titled Wiping clean package cache that shows its progress. Packages in use are kept and listed in the Packages in use window afterwards. A package that cannot be deleted for another reason, such as a file another program holds, is reported as “Could not delete …” with the reason.
Packages in use window
The Packages in use window opens when a wipe leaves packages in the cache because something is using them. It lists what holds them, with the packages each one holds, the one holding the most first.
| # | Name | Description |
|---|---|---|
| 1 | Headline | “<package> could not be deleted because it is in use.”, or “<n> packages could not be deleted because they are in use.” |
| 2 | Advice | “Close the workspace, server or command shown below, then try again. A package stays in the cache while anything is using it.” |
| 3 | Holder | What holds the packages: a workspace open in this Prism, or another process, such as a Prism window, an MCP server or a command, marked This Prism or Another process. |
| 4 | Details | What Prism knows about the holder: Process, PID, Port, Workspace, Command and Running since, each when known. |
| 5 | Packages | Expand 1 package or <n> packages to list what the holder keeps in the cache. Point at a package to see its path in the cache. |
| 6 | Copy details | Copies the holders and their packages as text, for example for a support question. |
| 7 | Try again | Closes the window and deletes the package again. Shown after Wipe selected package. |
| 8 | Close | Closes the window. Enter and Esc do the same. |
Speed up the cache
Anti-virus scans can slow down writing to the cache considerably. If your security policy allows it, exclude the cache folder from scanning. If the cache is on a Microsoft Dev Drive, you can skip this.
- In the Speed up cache I/O banner, select Copy script to clipboard. Prism copies a PowerShell script that adds Microsoft Defender exclusions for Prism for AL's local data folder, which holds the cache, and for the cache folder if you moved it.
- Open PowerShell as an administrator, paste the script and run it.
Help › Optimize Prism Package Cache Performance in the Control Panel copies the same script. For other anti-virus programs, see their documentation.