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 4 and 2 and type the answer here:
  • Post
  • Thanks for the DateTime explanation Lee. I've put some more comments on your blog entry.

  • * Can you please ISE be more extensible, for example it would be nice to allow scripts add WinForms controls on ISE tabs. Or create its own kind of tabs.

    *can you please make ISE perform all interface function as in console powerShell.exe, history of command for example (with search)

    *can you please made ISE embeddable in winforms applications

  • Creating a new object from an assembly in a certain folder (C:\Users\Eric\someassm.dll) fails if there are dependent assemblies in that same folder (C:\Users\Eric\dependassm.dll) UNLESS you specifically include those assemblies too. I know this is due to Code Access Security in .NET but it really takes away a potential use of PS: quickly testing objects you just created in Visual Studio. Right now I have to rebuild simple command line programs in order to manually test a rebuilt assembly. It'd be much easier to just open a new PS window, load the main assembly and work with the new object there.

  • What is up on connect.microsoft.com?  It looks like someone went through all the old cases and closed most of them. Many were set to "Closed (Won't Fix)".  They also didn't have explanations as to why they won't be fixed.  Some appear to have been fixed, but were still set the same. These were all closed on or around 1/6/2009.  Since there are less than 300 closed cases for Powershell and about 147 of those were closed around 1/6/2009, either you were very, very, very busy or they were just closed to make room for V2.

    I really hope this is a mistake and not just a way to get rid of cases.  Yes, many of them were old, some even from V1 RCX, but many were still valid bugs from after V1 was released.  It's a sad thing if they were just thrown away.  It does not encourage your users to give you new feedback if the old feedback was ignored.

  • I observed that ISE does't change between the tabs when a greater number of files are loaded ( for example 7). Are there any config files or log files to look for. I can't yet tell whether this depends on my ISE Extensions. Closing tabs works, afterwards normal behaviour. No data lost till now.

    Bernd Kriszio -- http://pauerschell.blogspot.com/

  • Cool.  It looks like the cases being closed on connect.microsoft.com was an accident.  I just looked again and all the cases that were closed are open again.

    Thanks

  • get-help get-* returns a list of commands that start with the word get

    get-help about-* triggers an error.

    That doesn't seem very consistent especially since the get-help command suggests that syntax for getting help on a command.

  • @Mark

    Strange, I don't see any error for get-help about-*, it just returns nothing. You need to type get-help about_* or just get-help about* to get the list of about topics.

    In PowerShell V2 CTP3 we made it even more friendly, now it is doing full-text search of the content of help topics in case if no matching help titles are found.

    For example, try get-help customize in PowerShell V2 CTP3. In the output, you will get all help topics that contain word 'customize' in their content.

    Hope this helps,

    Vladimir Averkin

    Windows PowerShell Team

  • The latest CHM file download for V2 CTP3 shows 'Cannot display page' for every single page. I've tried it on 3 machines, XP, Server 2003, and Vista and it doesn't work on any of them.

  • @ Kevin

    The contents of CHM file are 'blocked' because it was downloaded from internet. To be able to use it, right click on a file in Windows Explorer, click Properties and click on the 'Unblock' button in the bottom of the 'General' tab.

    Hope this helps,

    Vladimir Averin

    Windows PowerShell Team

  • I'd be interested to know what type of scalability testing has been done on the winrm service itself. Specifically I am looking for data on scenarios where a small number of central servers (1-5), either via runspaces, icm, etc. are using winrm to send commands (to exec PS scripts, collect data, etc.) to large numbers (10000-50000) of clients, on a continuous basis, 24x7. I'd like to see stats on resource usage, memory leaks, other resource exhaustion within winrm. I'd like to be able to say that after a whole day of running commands against 1000's of clients, that my central servers won't need to have win-rm restarted or be rebooted.

    I'd also like to know at some point how to tune the winrm service config for different workloads, and I'd also like to know what instrumentation will be in place for win-rm so that we can know when it is not healthy, either via SCOM or whatever.

    What happens when there is a failure in the winrm service on the central server, are commands currently in-flight on remote clients going to block/fail/hang and possibly impact the client? Data please.

    Functionality is great, and you guys have clearly done a good job on that, but if you are positioning this product as a next-gen sysadmin, tool, it has to scale.

  • I encounter some behaviour I think is a bug:

    $items = "item0", "item1", "item2"

    $part = ($items | select-string "item0")

    $items | where {$part -notcontains $_}

    what do you think that $items be at the end of the script?

    I was expecting "item1", "item2" but instead the value of $items is: "item0", "item1", "item2".

  • @Shay

    Select-String is returning MatchInfo objects, not string objects, therefore -notcontains does not work as you expect.

    Last line can be fixed as

    $items | where {$part.tostring() -notcontains $_}

    A much simpler solution is

    $items = "item0", "item1", "item2"

    $items -ne 'item0'

    Hope this helps,

    Vladimir Averkin

    Windows PowerShell team

  • @Vladimir

    I understand why it doesn't work (as a C# developer), but don't you think that the code SHOULD work (as a PowerShell user)?

    The script look decent and the the whole purpose of PS was not to think about this sort of stuff (especially in the dynamic lang world).

    It can be fixed by adding -asString to select-string (confusing) or by returning string objects from select-string or that "where" script will be able to deal with MatchInfo.

  • For what it's worth, the E-mail address gPSfback@microsoft.com gets a 554 Access Denied bounce.

    It's mentioned in both the release notes, and if you click the "Feedback" button in the Graphical PowerShell.

    Just my $.02 - It would be super if there were a way to change the default text size in the Graphical PowerShell.  the console version inherits this capability from the console it runs in, but I couldn't figure out how to do this with the graphical one.

    Thanks for a great piece of technology!

    -Chris

Page 2 of 3 (39 items) 123