PowerShell

The PowerShell forum accepts bug reports as well as feedback and suggestions. For more information, check out the PowerShell Homepage

The following is a list of the states we use to track items.

status meaning
survey We saw this and we are considering it. Please upvote if it’s important to you.
needs more information We don’t understand the issue and need additional details.
investigating We are looking at this internally to understand things like: scenario, reproduction of issue, costing, or other technical details.
in queue The issue is understood and in our unprioritized backlog. Your votes will be used to drive prioritization of this work.
  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Export-ISEState options

    Export-ISEState should have the ability to 'Save current tab', 'Save specific tabs' and 'Save all tabs'

    Default should remain 'Save all tabs'

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    survey  ·  0 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  2. Add proxy configuration on PowerShell ISE

    PowerShell ISE needs to have a proxy configuration!

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  3. Add a "Comment these lines" action to the right-click context menu of PowerShell ISE

    Much like how other IDEs provide similar functionality, an ability to quickly comment/uncomment chunks of code through the context menu would be a valuable addition to future iterations of the already fantastic ISE.

    With one line selected by the user a # is fine, with multiple lines selected, a <# #> would be preferred.

    I understand there is a...very unusual (quite frankly) keyboard shortcut to accomplish something similar, but I believe there is significant value in having an easy to access method of accomplishing this.

    6 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  4. ISE Bracket Shading

    I think that the ISE should have some user-customizable options - such as bracket shading. The grey isn't quite dark enough to spot. PowerGUI's shading is significantly darker, making it easier to detect the correlating bracket.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  5. Remember last command output eg PSLastItem - forgot to assign object to variable

    When you type in and run a cmdlet (especially one with side-effects) and forget to assign the output to a varialbe, it would be nice to be able to pick up the last output still stored in object form, from an automatic PS variable (eg PSLastItem) to feed into another command.
    Example: running Start-Process with -PassThru, then wanting the ExitCode of the result which I forgot to assign. Maybe even re-use $_ as shorthand, because we're not in the pipeline?

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  6. ISE Run in isolated console

    PowerGUI has a Run in External PowerShell Window feature, which executes the code externally, allowing parameters to be passed in, and eliminating some of the ISE quirks when testing code.
    I think have this option (along with customizable bracket shading) would be a great ISE feature.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  7. GUI change for ISE

    Currently powershell ISE is split into 3 horizontal panels with the following sections:script, results, and single commands.
    It makes more sense to do 3 panels where there are 2 horizontal panels; the top for single commands, bottom for script, and the results of the scripts or commands be on a 3rd full screen panel to the right, similar to an IDE.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    survey  ·  0 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  8. Format-Table

    "Get-WmiObject win32_operatingsystem | Format-Table -AutoSize"
    In the PowerShell ISE the AutoSize parameter didn't effects SerialNumber Column .

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →

    Either I’m unable to repro this, or I am missing the issue. I get consistent output between the ISE and standard PS shell.

    Can you provide the following, please, so I can understand it better:
    > Copy & paste the output of the standard shell & the ISE for this command. Don’t worry that it doesn’t look right in this editor, I’ll convert it to a non-proportional font to understand it.
    > In one of the windows, run $psversiontable, and include that in the output.

    One last request – can you try replacing Get-WMIObject with Get-CimInstance & see if it does the same thing? The -WMI cmdlets have been replaced with the largely equivalent -Cim cmdlets for a while, and you should really be using the newer cmdlets.

  9. 1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    survey  ·  0 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  10. ISE Excape Caracters Bug

    Steps to reproduce

    Open ISE and Run the following code:
    Write-Host "Text1" -NoNewline;Write-Host $("`rText2");
    Now open Powershell (not ISE) and do the same, it has a different behavior

    Expected behavior

    The following output

    Text2
    Actual behavior

    The following output

    Text1Text2

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  11. PowerShellISE Command AddOn should show combobox when parameter type is enum

    When a parameter definition in cmdlet is of an enum type, the Command Add On just shows a string field instead of a combo box. It will only show a combobox when the parameter has the ValidateSet attribute defined

    A sample code to help

    Add-Type -TypeDefinition @"
    // very simple enum type
    public enum SimpleEnumType
    {

      Value1,
    
    Value2,
    Value3

    }
    "@

    function Test-ISEEnum {

    param(
    
    [Parameter(Mandatory=$true)]
    [SimpleEnumType]$WithoutValidateSet,
    [Parameter(Mandatory=$true)]
    [ValidateSet(&quot;Value1&quot;,&quot;Value2&quot;)]
    [SimpleEnumType]$WithValidateSet
    )

    }

    In command line tab-key auto completion uses all enum values for both parameters.
    ISE command add-on shows a combo box for only $WithValidateSet parameter and provided only the…

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  12. Use the type of variables in the same way as OutputTypeAttribute when doing tab completion

    Use the type of variables in the same way as OutputTypeAttribute

    Get-Process | % <tab> #completes members of [Diagnostics.Process].

    [Diagnostics.Process[]] $proc = Get-Process

    $proc | % <tab> # does not complete members of [Diagnostics.Process] although the type is known.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    survey  ·  0 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  13. Allow closing tabs by middle-clicking

    Closing tabs by middle-clicking is supported in Visual Studio and all web browsers. Please add support for it in ISE, as well.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  14. [type] should use type completion rather than directory completion

    It's strange that this uses type completion:

    New-Object -TypeName l

    <tab> completes to "long"

    but this uses directory completion:

    Update-TypeData -TypeConverter l

    <tab> completes to ".\Links&quot;

    Even though the former takes a [string] and the latter takes a [type]

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    survey  ·  0 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  15. Support large PowerShell projects

    My dayjob revolves mostly around PowerShell. The largest PowerShell project I've worked on has over 50 000 lines of PowerShell code, the second largest has nearly 20 000. As you can imagine, supporting projects that large is simply impossible with PowerShell ISE. The company I work for bought licenses for PowerShell Studio from Sapien, which made working on the projects tolerable.

    By far the biggest problem with the projects were exhaustingly numerous runtime errors. This was long before the era of PSScriptAnalyzer and Visual Studio Code.

    Even with recent improvements to PowerShell tooling, I still feel like PowerShell is lacking…

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  16. Certain PowerShell ISE windows screws up alt+tabbing

    It looks like certain windows are screwed up in Windows 10 w.r.t. to it's alt+tab handling.


    1. The modal:

    a. Open PowerShell ISE
    b. Go to Tools | Options...

    Now try to alt+tab away from the "Options" window.

    The first alt+tab entry is the "main PowerShell ISE" window which if you alt+tab to that, takes you right back into the "Options" window. So it takes 2 alt+tabs to escape from the "Options" window rather than the expected 1 alt+tab.


    1. The non-modal "Edit | Find in Script..." suffers from the above problem as well.


    2. The modal "Edit | Go To Line..." seems…

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    investigating  ·  0 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  17. Please add a way to programmatically collapse 1 region (ONLY ONE!) in a PowerShell script.

    Please add a way to programmatically collapse 1 region (ONLY ONE!) in a PowerShell script. I'd like to deliver a script with a region of dependencies collapsed. I can use dot sourcing to save someone from viewing the script from having to scroll through the function dependencies but it would be nice to be able to deliver the script in 1 file.

    An example of my use case can be found here: http://stackoverflow.com/questions/37835140/collapse-or-toggle-1-region-in-the-powershell-ise?sfb=2

    4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    survey  ·  1 comment  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  18. history

    History that works with the ISE. I would like to find this simple bash type history to work beyond the current session and reboots.

    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  19. ise color bug:inlinescript

    【Cause of the bug】
    "inlinescript" is a keyword, but color wrong in ise,color as same as a command.

    【bug with powershell version】
    ise in win7 + powershell 2.0: not support PSWorkflow.
    ise in win7 + powershell 5.0: yes have this bug,tested.
    ise in win8 + powershell 3.0: unknown
    ise in win8.1 + powershell 4.0: yes have this bug,tested.
    ise in win10 10586:yes have this bug,tested.
    ise in win2016 tp5 :yes have this bug,tested.

    【test code】
    at first let font bigest,then test.
    workflow aaa
    {

    inlinescript #&lt;----color wrong
    
    {
    &quot;bbb&quot;
    }

    }

    【how to fix】
    unknown

    【reporter】
    By the chinese powershell…

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    survey  ·  1 comment  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  20. Allow for building front ends for power shell front ends within Visual Studio

    What would be great is to have a way to build a front end for power shell scripts, there is a way to build windows forms with the other object oriented languages VB.NET, C#, etc. Albeit they are programming languages not scripting languages. The best tool out there so far for this is sapien's power shell studio. It's nice but it's no visual studio :)

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base