Many people who use the PSEdit function aren’t even worried about a runspace. Commands that run in the same Debug session also share a persistent runspace.Ī PSEdit to Open a Script in PowerShell Studioīut, that’s probably too literal. Run the script from the console or use the Run in Console or Run Selection in Console commands. If you need a persistent runspace to share content, like variables, use the PowerShell Studio Console Pane.

And, that runspace never includes PowerShell profiles, so you don’t need to hide, move, or disable them. It creates a new runspace each time you use Run, Run Selection, or Debug, even if you run them repeatedly on the same script. It not only creates a new runspace for every script. A new runspace is an improvement, even though the new runspace still includes your personal PowerShell profiles and anything that they import or auto-load.Īs a best practice test environment, by default, PowerShell Studio runs every script in a new runspace every time. That’s obviously not the best test environment. In ISE, you need to create a new runspace because, by default, everything that you run in ISE runs in the same runspace in its console. The PSEdit function, which is defined in and works only in PowerShell ISE (not in the ISE module), opens a script that you specify in a new PowerShell Tab, that is, a new runspace. Um, you don’t need itīeing very literal, you don’t need the PSEdit function in PowerShell Studio.

“How do I use PSEdit in PowerShell Studio?,” Thom asked on Twitter.

Like many of us, he came to PowerShell Studio from PowerShell ISE, so he looks for the “ISE way” to do things in PowerShell Studio. My friend, Thom Schumacher, who has been leading the Arizona PowerShell User Group for the past few months, is getting to know PowerShell Studio.

Sapien powershell studio disable tab