PowerShell 7 Scripting with the PowerShell ISE

Posted on

By now, everyone should have gotten the memo that with the move to PowerShell 7, the PowerShell ISE should be considered deprecated. When it comes to PowerShell script and module development for PowerShell 7, the recommended tool is Visual Studio Code. It is free and offers so much more than the PowerShell ISE ever could.

Manage and Report Active Directory, Exchange and Microsoft 365 with
ManageEngine ADManager Plus - Download Free Trial

Exclusive offer on ADManager Plus for US and UK regions. Claim now!

But.....

As much as some people may want to use VS Code., they can't. The reasons don't really matter and in the long run hopefully will be moot. The bottom line is that today some of you are using PowerShell 7 but are stuck with the PowerShell ISE. Fortunately, there is an easy solution. Open up the PowerShell ISE and run this command:

Enter-PSSession -ConfigurationName powershell.7 -ComputerName localhost

Congratulations. You've entered into a PowerShell 7 remoting session on your computer. The PowerShell ISE will now pick up syntax and Intellisense.  In the script editor, I can start typing a Foreach-Object command and the ISE detects the PowerShell 7 syntax.

ise-ps7

I haven't testing this technique extensively and because you are in a remote session I can't guarantee everything will run, but you should at least be able to script it.

Don't get me wrong,  You should be fighting to get Visual Studio code or other editors into your environment. But in the short term, this might be enough to keep you going.

Behind the PowerShell Pipeline

10 thoughts on “PowerShell 7 Scripting with the PowerShell ISE”

  2. Has anyone come up with a solution to viewing a Progress Bar within VS Code?

    1. Write-Progress works for my in the PowerShell terminals within VSCode. If you are looking for something like how Write-Progress worked in the PowerShell ISE, that I have not seen. Nor would I expect it.

  3. When I try your suggestion of Enter-PSSession in the PowerShell ISE, it stalls for about 30 seconds and them emits the error shown below. What am I doing wrong? I’m using a fully patched Windows 10 Pro 64-bit operating system.

    Enter-PSSession : Connecting to remote server localhost failed with the following error message : The
    client cannot connect to the destination specified in the request. Verify that the service on the
    destination is running and is accepting requests. Consult the logs and documentation for the WS-Management
    service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service,
    run the following command on the destination to analyze and configure the WinRM service: “winrm
    quickconfig”. For more information, see the about_Remote_Troubleshooting Help topic.

    1. You should try running Test-WSMan against the remote computer first to verify remoting is enabled on the other end. Sounds like remoting is not enabled. If you are still stuck, I encourage you to use the forums at PowerShell.org.

  4. I am getting the same error as fmorrison. Test-WSMan produces the following:

    wsmid : http://schemas.dmtf.org/wbem/wsman/identity/1/wsmanidentity.xsd
    ProtocolVersion : http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd
    ProductVendor : Microsoft Corporation
    ProductVersion : OS: 0.0.0 SP: 0.0 Stack: 3.0

    Is there something to do to register the configuration name first or should the install of PowerShell 7 do that automatically?

    1. In a PowerShell 7 session, did you run Enable-PSRemoting? You need to do that to enable the PS7 endpoints..

      1. Yes sir, PS Remoting was already configured. Maybe that is the problem? Perhaps PowerShell 7 fails to create those endpoints when installed when remoting is already configured? Thanks for your reply, your follow up is greatly appreciated.

      2. You need to run it again in PowerShell 7 or have select the option to enable remoting when you installed it. If you run Get-PSSessionConfiguration in the ISE and don’t see the PS7 endpoints, my trick isn’t going to work. It won’t hurt to run Enable-PSRemoting again in PowerShell 7.

  5. A little follow up. I ran the following in PowerShell 7:
    Get-PSSessionConfiguration | Format-List -Property Name, Permission

    Returns no data. Seems we are maybe missing something to register that session name.

Comments are closed.