PowerShell naming design guidelines

A must see for anyone writing code for PowerShell:

http://blogs.msdn.com/powershell/archive/2009/04/16/increasing-visibility-of-cmdlet-design-guidelines.aspx

 

S4Matic is currently using custom function names (technology\verb-noun), however one of reasons is that in future we want to easily migrate to Posh V2.

So situation is that naming convention applied now is NOT according to standards, but once Posh V2 will get adopted, it will be immediately following new naming convention. That allows us to easily migrate without changing any code at customer sites.

Martin