SAPIEN Technologies

I was asking for the product's version information.

Hard to tell without any information or actual access to compare things.
I mean is you would try the console suggestion and post the actual powershell error message in full, maybe we would see something.
[Edit: Apologies, it already was in the PowerShell section]

This is a pretty simple task, but the devil is usually in the details. You say "I've spent a couple of hours trying to get this going without any luck". That is a little to vague to determine where you might get hung up. Nor does it allow us to determine how far you got until you got stuck. I would ...

Please provide all the requested information.
Product, version and build:

If it works with the ISE it works in PowerShell Studio, it is the same PowerShell. Usually this happens because a different platform, version or bitness is selected in PowerShell Studio. Maybe you run the ISE elvated? Try to turn STA on if you not have yet. Try to use "Run in console" in PowerShell ...

From what I see in the original picture you are more looking for what is generally referred to as snippets. Both PrimalScript and PowerShellStudio have a snippets browser that shows a number of pre-fabricated snippets and can be customized to show your own alongside.

You can launch any script elevated by using the elevation button on the ribbon. There is no need to run PowerShell Studio itself elevated at all times.

[Topic moved by moderator]

Send screenshots. Without knowing what you see and what you resolution is, its hard to tell.

It has something to do with re-setting $PSScriptRoot. It seems Powershell in some instances does not like that. Using a different variable name solves the problem. function Get-ScriptDirectory { [OutputType([string])] param () if ($host.Name -eq 'PrimalScriptHostImplementation') { if ($null -ne $hos...