DetentShell The PowerShell 7 ISE we should have been delivered 8 years ago*

A PowerShell editor that behaves like the ISE

Looking for an editor application for writing PowerShell, not a way to edit a file from inside a console session. DetentShell is that: ISE-style, built for PowerShell 7.

DetentShell logo
01 Two different questions

“PowerShell editor” means two different things. One is a console question: how do I edit a text file from inside a PowerShell session, without leaving the shell. This page isn’t that: if that’s what you need, the answer is a console-native command, not a separate application.

The other is an application question: what editor application do I open to write and run PowerShell scripts. That’s this page. If you want the ISE’s script-and-console layout on PowerShell 7, that’s DetentShell.

02 What an ISE-style editor gives you
03 Free-form text editors vs. this

A general-purpose text editor with a PowerShell syntax file will highlight your code. It won’t run it, debug it, or generate a test for it without an extension you install and a workspace you configure yourself first. In DetentShell the console, the debugger, and the test generator ship in the same window from the first launch.

See how it stacks up against VS Code, the ISE, and PowerShell Studio →

04 Where this stands today

You can’t install this application yet. The build itself works: 944 automated tests pass today across the editor, console, debugger, and analyzer. What’s left is getting a signed installer out the door, since every release ships signed under Detent Point LLC and nothing unsigned goes out ahead of that.

Read the full DetentShell overview →

Get DetentShell
PS> Start-Process "https://detentpoint.com/detentshell/download"
# Coming soon — ships once the installer is code-signed

Coming 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.

Follow progress on the changelog →