What do you want in a vNext for PowerShell?

This topic contains 0 replies, has 1 voice, and was last updated by Profile photo of Forums Archives Forums Archives 5 years, 5 months ago.

  • Author
    Posts
  • #5098

    by willsteele at 2012-09-11 07:48:28

    Ed Wilson posted this morning the PowerShell team is in the early stages of working on the next set of development priorities for v4. I know v3 literally just came out, but, if there is something you are really wanting to see out there but doesn't seem like it'll happen without someone raising their hand and asking, this is your chance to get a word in edgewise:

    http://blogs.technet.com/b/heyscriptingguy/archive/2012/09/11/bespoke-scripting-what-do-you-want-in-powershell.aspx

    Connect is the official feedback mechanism and is very easy to use. If you have a bug, a documentation bug or even a suggestion create an account, put your details and see what the team has to say. Visit the connect site here: http://connect.microsoft.com/. Once you are logged in you can search by product (it's not just PowerShell but all active development efforts) and put down your thoughts and suggestions. It's a great opportunity to try and get something you have been looking for included in PowerShell in a couple of years (if not sooner).

    by DonJ at 2012-09-11 07:53:08

    I'll back Will (and Ed) up on this. The PowerShell team truly does read their Connect feedback. If you happened to grab the first CTP of v3, the sample that came with it were the ones they'd shown us at the MVP Summit earlier that year. Most of the scripts had a comment at the start, with the Connect ticket ID# and the name of the person who suggested the feature that the script was demonstrating.

    They really do listen.

You must be logged in to reply to this topic.