Please Give Us Feedback

Please Give Us Feedback

  • Comments 39

With the release of Win7/WS08R2 beta, we are officially in the end game of PowerShell V2.  This is the phase were we can only respond to customer feedback and we rely upon customer feedback to tell us whether and when we are ready to ship.  In other words - now is when we need to hear from you the most. 

  • Please use PowerShell V2
    • You can use the CTP3 bits or the bits that come with Win7/WS08R2 (they are essentially the same bits).
  • Please use all aspects of the product - experiment with the new features as well as verify your old favorites
  • Please report backward compatibility issues.  This is SUPER SUPER important to us so if anything USED to work and no longer does - it goes to the front of the fix queue.
  • Please file bugs and suggestions.  Let us know what you hate, what doesn't work for you, how you think things should work.  We love reading your feedback so please - turn the fire hose on.
  • Please share.  Blog, Post, twit (tweet?), talk, demo, present - you pick your favorite mode of sharing but share.  PowerShell is a community effort.  I learn from you, you learn from me, others learn from us.  The more sharing there is, the better our community is and the faster we learn.
  • Please encourage your friends, your peers, your fellow Internet surfers to join the party and use the V2 bits.

I'm very excited about what we are delivering in PowerShell V2.  As a community, we are going to be using these bits for many many years so let's work together to ensure that they are the best possible.

 

Experiment! Enjoy! Engage!

Jeffrey Snover [MSFT]
Windows Management Partner Architect
Visit the Windows PowerShell Team blog at:    http://blogs.msdn.com/PowerShell
Visit the Windows PowerShell ScriptCenter at:  http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx

Leave a Comment
  • Please add 6 and 1 and type the answer here:
  • Post
  • Is there a URL or something for your preferred means of feedback?  I'd like to post where I know it will be read, but here is my comment:

    The PS ISE is great, but I don't seem to see an option to print (and in color with line numbers).  Is this feature going to be available in the RTW? That along with the lack of intellisense is the only reasons I use other products, like PowerGUI, etc.  You guys are almost there...

  • The most biggest wall for me is that I need to read and write English for feedback.

  • I have trouble with this Command:

    (Example from Tobias Weltners Book "Scripting mit Windows Powershell")

    dir HKCU: -recurse -include *Powershell*

    In Version 1.0 it goes.....

    See Group:

    http://groups.google.com/group/microsoft.public.windows.powershell/browse_thread/thread/54baffd8ef7d718a#

  • It's a pity i can't test some of the new features at the moment because it doesn't run on Win XP.....

    But altogether a good and stable version - what i saw so far.

    Out-GridView is really smart.

    Are you planing to implement AD Cmdlets?

    The graphical Powershell made big improvements.

  • I would like to be able to create a new session in the PS ISE without closing and reopening the whole editor.  I was writing a WPF script last weekend and I was getting my session into a state where there was a variable or something that would not be reset between runs and when I would rerun the script it would generate errors and I had to completely close PS ISE and reopen the script to be able to run it again.  Something like the "clear output pane" that clears all my session variables and functions and such.

    Also it would be nice if it could highlight the complementing open/close bracket/parenthesis when your cursor is next to one.

    Also the example presented in about_functions_cmdletbindingattribute is misleading.  It needs to say:

    function MyVerb-MyNoun {

     [CmdletBinding(SupportsShouldProcess ... etc)]

     Param()

     Begin{}

     Process{}

     End{}

    }

  • @bj

    WS08/R2 Beta has the AD Cmdlets.

    jps

  • Hi Jeffrey

    Re: backwards compatibility, I have PoSh v2 CTP3 installed, and the PowerShell Community Extensions v1.1.1 installed.  These worked fine in CTP2, but now when I start PowerShell I get the following error:

    Attempting to perform the InitializeDefaultDrives operation on the 'DirectoryServices' provider failed.

    Set-Alias : Alias is not writeable because alias measure is read-only or constant and cannot be written to.

    At C:\Program Files (x86)\PowerShell Community Extensions\Profile\Profile.ps1:79 char:14

    +     Set-Alias <<<<  $name $value -Scope Global -Option AllScope -Force:$force -Description "PSCX $type alias"

       + CategoryInfo          : WriteError: (measure:String) [Set-Alias], SessionStateUnauthorizedAccessException

       + FullyQualifiedErrorId : AliasNotWritable,Microsoft.PowerShell.Commands.SetAliasCommand

    Set-Alias : Alias is not writeable because alias start is read-only or constant and cannot be written to.

    At C:\Program Files (x86)\PowerShell Community Extensions\Profile\Profile.ps1:79 char:14

    +     Set-Alias <<<<  $name $value -Scope Global -Option AllScope -Force:$force -Description "PSCX $type alias"

       + CategoryInfo          : WriteError: (start:String) [Set-Alias], SessionStateUnauthorizedAccessException

       + FullyQualifiedErrorId : AliasNotWritable,Microsoft.PowerShell.Commands.SetAliasCommand

    Is there something I've missed, maybe?

    Alastair

  • My latest in a series of the weekly, or more often, summary of interesting links I come across related to Visual Studio. Justin Etheredge wrote a nice overview of overflow checking in c# and explains how to enable this for certain statements and project

  • Casting to a DateTime object doesn't respect the current culture of the thread. For example:

    > [Threading.Thread]::CurrentThread.CurrentCulture

    LCID  Name

    ----  ----

    2057  en-GB

    > [DateTime] "01/02/03"

    02 January 2003

    > # Note US date interpretation.

    (alightly confusingly, there's also a CurrentUICulture property on the Thread object, but that always returns en-US, even though all my control panel settings are set to UK. When I try to set this to en-UK using Powershell, it has no effect.).

  • *) Please, show some respect to users and tell them about known issues in documentation, help, etc. Tell them about known workarounds and alternative solutions. Doing so, you will help them to stay with PowerShell even for real jobs.

    *) Please, improve the documentation: it should be up-to-date, with decent formatting and with working examples. Current documentation is often not easy to read, CHM version has no index – all this does not look like documentation of a mature product.

    Thank you all for the great job.

    Roman

  • Matthew: The DateTime issue is on purpose, and ensures that users can write these DateTime constants without having to pay special attention to their internationalization impacts. More info here: http://www.leeholmes.com/blog/DateTimeCastsAreLanguagePrimitives.aspx.

    Lee Holmes [MSFT]

    Windows PowerShell Development

  • @roman

    I got the "improve the documentation" point - that will definately get better before we ship.  

    I didn't quite follow the first point.  Is that a CTP3 issue or a general issue?  Were you saying that we should articulate what problems/shortcomings we know about when we release a CTP?

    Experiment! Enjoy! Engage!

    Jeffrey Snover [MSFT]

    Windows Management Partner Architect

    Visit the Windows PowerShell Team blog at:    http://blogs.msdn.com/PowerShell

    Visit the Windows PowerShell ScriptCenter at:  http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx

  • @Jeffrey

    There are a few V1 cmdlets with issues or bugs. See Connect. I afraid some of them will not be fixed or improved, because you are officially in the end game of PowerShell V2, so that you are presumably concentrated now mostly on V2\V1 regressions and CTPs new bugs. At least it sounds and looks so. Well, it’s fair enough. But it won’t be fair if you say nothing in documentation and users, especially newcomers will waste their time instead of reading “this is not working, if ..., do this instead”.

    Thanks,

    Roman

  • Alastair: We're investigating the alias issue. Thanks for reporting it. The DirectoryServices provider issue has been resolved in internal builds.

    Lee Holmes [MSFT]

    Windows PowerShell Development

  • I posted a list of notes for things I'd like to see in the ISE:

    http://dougfinke.com/blog/index.php/2009/01/12/powershell-integrated-scripting-environment-increases-your-velocity-for-code-development/

Page 1 of 3 (39 items) 123