Detent Point
PowerShell 7 didn’t have an ISE. Now it does. Here’s what’s actually in it, in plain terms, not a spec sheet.
Syntax highlighting knows PowerShell 7’s cmdlets, parameters, and operators, plus a highlight set for common dbatools cmdlets. Everything below is checked against your actual file, not a snapshot.
- IntelliSense on
Ctrl+Space, in the editor and in the console - Function navigator: jump to any function in the open file
- Comment/uncomment on
Ctrl+/ - Folding for
{ }blocks and#regionsections that understands PowerShell, so a brace inside a string or comment never folds by mistake - Find and replace (
Ctrl+F/Ctrl+H,F3to repeat,Ctrl+Ggo to line) that matches$Nameand-Pathas whole tokens, not fragments - Multi-file work: new tab (
Ctrl+N), open (Ctrl+O), cycle (Ctrl+Tab), close (Ctrl+W) - Snippet insertion on
Ctrl+J
DetentShell keeps the ISE’s two-level tab model: PowerShell session tabs, each holding its own script files and its own isolated PowerShell 7 session (Ctrl+T opens a new one). Debugging runs on the same function keys the ISE used, over PowerShell’s own debugging engine.
- Per-tab isolation: what you define in one session stays in that session, and the test suite checks this directly
- Your
promptfunction runs for real; a broken one falls back to the default instead of freezing the console F9toggles a breakpoint,F5runs or continues,F8runs just the selectionF10steps over,F11steps into,Shift+F11steps out- Call stack and Watch/Locals panels, re-evaluated at every stop so nothing goes stale while you step
- Break-on-entry: start debugging with no breakpoints and execution pauses at the first statement
Four checks run against your buffer as you type, on background workers that never freeze the editor:
- Parse errors squiggle where they sit, before you save or run anything
- PSScriptAnalyzer lint squiggles inline, using your own installed PSScriptAnalyzer. Not installed? One quiet nudge, and the linter just sits out; nothing breaks
- 5.1-to-7 compatibility, both directions: one check flags 5.1-isms that break on PowerShell 7; another flags 7-only syntax that would break if the script later runs on 5.1
- Quick Fix: five hardening fixes (try/catch wrapping, strict mode, parameter validation, a dangerous-cmdlet guard, a secure failure mode), each previewed before anything touches your script
F1 on a symbol opens a real help pane fed by Get-Help, on its own background thread so a slow lookup never stalls your session. Seven built-in themes, four of them dark: Light, Dark, Sage, Terminal Green, Classic Console, Amber Glow, and High Contrast. Every color pair, including syntax highlighting, passes an automated contrast check before a build can ship.
Windows PowerShell 5.1 execution is batch-only: a 5.1 script runs out of process and its output comes back as serialized data, not a live console. No 5.1 prompt, no 5.1 debugger, no line numbers on 5.1 output. The live console and debugger above are PowerShell 7 only. Per-token color and font customization, an ISE Colors & Fonts equivalent, is not in v1; you choose from the seven built-in themes.
Everything on this page traces to code and tests in the app itself. Most recent clean full-suite run: 944 tests passing, 0 failing (2026-07-13).
Pester test generation has its own page → · A Format/Indent button is coming →
PS> Start-Process "https://detentpoint.com/detentshell/download"
# Coming soon — ships once the installer is code-signedComing soon. DetentShell launches at $29.99 in the Microsoft Store for its first two weeks. The regular price that follows is not final yet and will be published here first; volume licensing for teams is handled separately.