Naming conventions
Naming conventions are not rocket science and they are certainly not unique to PowerShell. They are also not concrete rules that will cause your code to stop working if they are ignored. On the other hand, the designers of PowerShell began the language with a strong foundation of consistent naming which is one of the keys to its success. In the following sections, we will discuss several instances where naming conventions will improve your PowerShell experience.
Cmdlet and function naming
As discussed in Chapter 1, PowerShell Primer, built-in cmdlets are named with a verb-noun format using a verb from a predefined list of approved verbs. This format is not required for user-defined cmdlets, functions, advanced functions, or scripts, but is highly recommended. The only place where not having properly named functions will cause any kind of programmatic issue is when a module, including the code, is imported into a PowerShell session. A module exporting functions that are...
