Earlier this week I exchanged a few tweets with @jonhtyler about coming up with a proper name for a PowerShell function he was developing. The suggested best practice is to use the Verb-Noun naming convention, using an accepted verb. You can see the verbs with the Get-Verb cmdlet. So I figured why not automate this a bit. After all, sometimes it can be tricky finding the proper verb. Sometimes it helps to actually see the name first. So I put together this simple function called Test-CommandName.<\/p>\n
Function Test-CommandName {\r\n\r\n#comment help is here\r\n\r\nParam(\r\n[Parameter(Position=0,Mandatory=$True,\r\nHelpMessage=\"What is the noun for your command?\")]\r\n[ValidateNotNullorEmpty()]\r\n[string]$Noun,\r\n[ValidateSet(\"All\",\"Common\",\"Data\",\"Lifecycle\",\"Diagnostic\",\"Communications\",\"Security\",\"Other\")]\r\n[string]$Category=\"All\"\r\n\r\n)\r\n\r\nif ($Category -eq \"All\") {\r\n#get all verb names and add to an array\r\n$verbs = Get-Verb | Select -ExpandProperty Verb\r\n}\r\nelse {\r\n#get verbs that belong to the given category and add to an array of verb names\r\n$verbs = Get-Verb | Where {$_.Group -eq $Category} | Select -ExpandProperty Verb\r\n}\r\n\r\nforeach ($verb in $verbs) {\r\n<#\r\ngo through each verb and display a string that\r\nrepresents a potential Verb-Noun name for\r\nyour command\r\n#>\r\n\r\n\"{0}-{1}\" -f $verb,$noun\r\n}\r\n\r\n} #end Test-CommandName function<\/pre>\n