Willsatroyd

My feedback

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

    We’ll send you updates on this idea

    2 comments  ·  PowerShell » PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
    Willsatroyd commented  · 

    Understood. Thank you.

    Willsatroyd shared this idea  · 
  2. 153 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    9 comments  ·  PowerShell » ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
    Willsatroyd commented  · 

    Due to no reason but my observation that nothing has changed here in years, I suspect all dev on the ISE preview / future ISE has ceased. I suspect because of VS Code. Would be nice to get confirmation though. MS has stated that PS is 'finished', so that's another bit of evidence.

    Willsatroyd supported this idea  · 
  3. 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  ·  PowerShell » ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
    Willsatroyd supported this idea  · 
  4. 5 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PowerShell » ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
    Willsatroyd shared this idea  · 
  5. 200 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    19 comments  ·  PowerShell » PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →

    After much discussion with Aaron Nelson and Chrissy LeMaire, and thanks to the enormous amount of support for this item, we’ve recognized that this is something we need to accomplish, one way or another.

    We don’t want to offer an ETA on this as the work is not well understood by our team yet, and no one currently has immediate bandwidth on starting that investigation. But I want to stress the fact that is an important ask that we’re taking seriously as a priority.

    In the meantime, it would be immensely useful if someone with expertise in the DataTable space could submit an RFC (basically a brief spec) to our PowerShell-RFC repository on GitHub. That way, we can have a discussion about what the design of a ConvertTo-DataTable cmdlet might look like before we dive in on an implementation. The process for doing so is located here: https://github.com/PowerShell/PowerShell-RFC/blob/master/RFC0000-RFC-Process.md#draft

    I…

    Willsatroyd supported this idea  · 
  6. 9 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PowerShell » ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
    Willsatroyd commented  · 

    I would love the expand/collapse functionality

    Willsatroyd supported this idea  · 
  7. 8 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PowerShell » ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
    Willsatroyd supported this idea  · 
  8. 19 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PowerShell » ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
    Willsatroyd supported this idea  · 
  9. 49 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    Thank you for the suggestion. Given the number of requests, we cannot field all recommendations, so for now we’ll be monitoring this to see if there is broad support.

    Willsatroyd commented  · 

    I'd like to see any source repository supported with an extensible system where Git would be one option; TFS online and local TFS instances would be great too.

    Willsatroyd supported this idea  · 
  10. 177 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  PowerShell » PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
    Willsatroyd supported this idea  · 
  11. 166 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  General Feedback » Licensing, SKU, & Edition  ·  Flag idea as inappropriate…  ·  Admin →
    Willsatroyd commented  · 

    KMS should definitely be a role. You'd want to ensure that a KMS server didn't accept authorisation attempts before having the keys configured so maybe the servers could be authorised like DHCP servers.
    Perhaps there could be the option for the keys to be stored in AD in those environments.
    However it is done, get rid of that VBS script! A good starting point for me would be to replace it with PowerShell CmdLets

    Willsatroyd supported this idea  · 
  12. 250 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    11 comments  ·  General Feedback » Shell, GUI, & Explorer  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for the feedback. This is something that has been suggested frequently, and we are hearing you. At this time no decision has been made either way.

    Willsatroyd supported this idea  · 
  13. 9 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PowerShell » Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
    Willsatroyd supported this idea  · 
  14. 222 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    22 comments  ·  PowerShell » Documentation  ·  Flag idea as inappropriate…  ·  Admin →
    Willsatroyd supported this idea  · 
  15. 47 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  PowerShell » ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
    Willsatroyd commented  · 

    I would like to see the whole variable highlighted too, rather than just the text after the $. That way if I want a quick copy & paste of a variable, I don't have to type the $.

    Willsatroyd supported this idea  · 
  16. 57 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    This is a very difficult thing to implement, it could potentially break many of the add-ons, and could introduce some very confusing UI elements.

    That said, we’re interested to get more ideas from you for how something like this might work. Feel free to post your comments below.

    Thanks,
    Joey

    Willsatroyd commented  · 

    Perhaps the best example I know of is the lamented lost PowerGUI Pro script editor.

    Willsatroyd supported this idea  · 
  17. 170 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    15 comments  ·  PowerShell » Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
    Willsatroyd commented  · 

    Sync with mirror option are the most important.

    Willsatroyd supported this idea  · 
  18. 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  ·  PowerShell » ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
    Willsatroyd shared this idea  · 
  19. 119 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    10 comments  ·  PowerShell » PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →

    Hi everyone,

    With PowerShell 6.0, we’ve already begun updating our versioning system to be more descriptive. Right now, PSVersion returns 6.0.0-alpha as a System.Management.Automation.SemanticVersion object (with Major, Minor, Patch, and Label properties), and we’ve also added a GitCommitId property to PSVersionTable that matches perfectly with tags on GitHub: https://github.com/powershell/powershell/tags

    Still, we can definitely continue to improve the semantic version implementation. You can track (and contribute to!) the discussion on these improvements here: https://github.com/PowerShell/PowerShell/issues/2354

    Thanks,
    Joey

    Willsatroyd supported this idea  · 
  20. 25 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PowerShell » ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
    Willsatroyd supported this idea  · 
← Previous 1

Feedback and Knowledge Base