Increasing visibility of cmdlet design guidelines

Increasing visibility of cmdlet design guidelines | ASP NET Hosting

Increasing visibility of cmdlet design guidelines | ASP NET Hosting — Thu, 16 Apr 2009 03:56:20 GMT

PingBack from http://asp-net-hosting.simplynetdev.com/increasing-visibility-of-cmdlet-design-guidelines/

re: Increasing visibility of cmdlet design guidelines

Confused — Thu, 16 Apr 2009 19:00:23 GMT

Your list prohibited characters includes '-' .. does this mean I can not export Module functions with Verb-Noun syntax?

re: Increasing visibility of cmdlet design guidelines

Carter Shanklin — Fri, 17 Apr 2009 10:58:16 GMT

It would be easier to take these recommendations seriously if groups within Microsoft followed them.

re: Increasing visibility of cmdlet design guidelines

PowerShellTeam — Fri, 17 Apr 2009 15:26:12 GMT

@Carter

Absolutely. That was one of the key arguments for having CODE instead of merely documentation to back up the standards.

Jeffrey Snover [MSFT]

Distinguished Engineer

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

re: Increasing visibility of cmdlet design guidelines

Marco Shaw — Sun, 19 Apr 2009 19:33:34 GMT

@Confused,

My interpretation here is that you cannot use a 2nd hyphen anywhere in your funtion name.

So this will work:

My-Function

But this won't:

My-Custom-Function

Soliciting New Verbs

Windows PowerShell Blog — Thu, 23 Apr 2009 02:17:53 GMT

With the recent changes in v2 to increase the visibility of the cmdlet design guidelines , we want to

Soliciting New Verbs

PowerShell Team Blog (external) — Thu, 23 Apr 2009 16:14:39 GMT

With the recent changes in v2 to increase the visibility of the cmdlet design guidelines , we want to

re: Increasing visibility of cmdlet design guidelines

Thomas Lee — Fri, 24 Apr 2009 11:52:27 GMT

This is a most sensible idea. I agree with Carter that the PowerShell team needs to start inside Microsoft, but Jeffrey's reply makes sense.

I think there might be some mileage in classifying nouns too, but with less importance. Could there be an official set of nouns that customers could add to (say stored in nouns.xml in $PSHOME??).

Also, there should be a GPO value to disable the strict name checking (or to always turn it on explicitly). Just because my firm develops a "bad" set of cmdlets, there's not much point in constantly warning me (ie the user) as I can't do anything about it. Displaying an error message that I can't do anything about seems poor practice.