Automating the world one-liner at a time…
First, I want to say thanks to everyone who posted suggestions for the verb list on the blog post at http://blogs.msdn.com/powershell/archive/2009/04/22/soliciting-new-verbs.aspx. In addition to the blog comments, we received a lot of feedback from our MVPs and internal partners.
I wanted to loop back with everyone on the outcome of the verb list update and post the final approved verb list for Windows PowerShell 2.0. I also wanted to give visibility into what some of the verbs were that we considered but ultimately did not approve and what we feel are the best matches for those on the approved list. In total, we received nearly 80 proposals for new verbs - a partial list is below. Of the roughly 80, we added 20 new verbs, 4 of which were added in RC.
We'll be working to update the MSDN documentation with this list in the coming weeks. In the meantime, feel free to use the list below as the official list for PowerShell 2.0. As mentioned previously, you can also use the Get-Verb function in PowerShell to retrieve the list of approved verbs.
Final List of Approved Verbs for Windows PowerShell 2.0
Partial List of Verbs Considered (these were not approved)
Dan HarmanProgram ManagerWindows PowerShell
when is the next CTP or beta being released for PowerShell 2.0
I am curious to learn why some of those were not approved? I don't know if you can share?
Bill, I am guessing PowerShell 2.0 will not be released prior to Windows 7 or Windows 2008 release date.
When I first encountered PowerShell, the concept of a list of approved verbs struck me as strange - why do I have to use a list of verbs MS decided on? They will always be some actions in my product that do not fit into any of these verbs, and my existing customers will have to relearn what the commands mean. However, after a while I came to believe that perhaps a small set of verbs does make sense, in that it provides a uniform way to address actions. E.g., Instead of "Assign-User" I can use "Add-UserAssignment". Fine.
But now there are 96 verbs. The list of "approved" verbs is well on its way to complete dilution. What is point of having 96 approved verbs? It's not like users are going to understand or care about the difference between GET or SELECT or FIND or REQUEST. They want whatever is easy and fits the product. I'm sure PS3 will have 134 approved verbs. I see my example "assign" has been [arbitrarily] rejected for PS2.
Seriously, is there a point to these anymore? Why not just suggest the best-practice of using the verb-noun syntax for your cmdlets and forget the whole approved-verbs thing?
Will you be updating the Microsoft Command Line Standard also?