Comments on: An apology to the PowerShell Community http://veeammeup.com/2009/03/an-apology-to-the-powershell-community.html The Veeam Team Tue, 22 Jun 2010 14:09:43 +0000 hourly 1 http://wordpress.org/?v=3.0 By: halr9000 http://veeammeup.com/2009/03/an-apology-to-the-powershell-community.html/comment-page-1#comment-19 halr9000 Wed, 25 Mar 2009 17:32:00 +0000 http://veeammeup.com/2009/03/an-apology-to-the-powershell-community/#comment-19 Look for a blog post from the PowerShell team in the near future, they intend to address this issue in a big way by highlighting some upcoming V2 features. Look for a blog post from the PowerShell team in the near future, they intend to address this issue in a big way by highlighting some upcoming V2 features.

]]> By: chamdor http://veeammeup.com/2009/03/an-apology-to-the-powershell-community.html/comment-page-1#comment-18 chamdor Wed, 25 Mar 2009 00:26:00 +0000 http://veeammeup.com/2009/03/an-apology-to-the-powershell-community/#comment-18 I second the design by cshanklin. I second the design by cshanklin.

]]> By: cshanklin http://veeammeup.com/2009/03/an-apology-to-the-powershell-community.html/comment-page-1#comment-17 cshanklin Tue, 24 Mar 2009 20:26:00 +0000 http://veeammeup.com/2009/03/an-apology-to-the-powershell-community/#comment-17 In the VI Toolkit Community Extensions we prefix all nouns with Tke to eliminate possible confusion.<br/><br/>Example: Get-TkeSnapshotExtended returns snapshots with an extra property (the size of the property). Your approach certainly works, but I like this one better. In the VI Toolkit Community Extensions we prefix all nouns with Tke to eliminate possible confusion.

Example: Get-TkeSnapshotExtended returns snapshots with an extra property (the size of the property). Your approach certainly works, but I like this one better.

]]> By: jefferyhicks http://veeammeup.com/2009/03/an-apology-to-the-powershell-community.html/comment-page-1#comment-16 jefferyhicks Tue, 24 Mar 2009 19:52:00 +0000 http://veeammeup.com/2009/03/an-apology-to-the-powershell-community/#comment-16 Personally, I'm a big fan of custom nouns. When I run PowerShell classes I tell students about the naming conventions, the risks of name collisions and what most vendors are doing. I think a custom noun removes all ambiguity, plus it makes it easy for users to discover your cmdlets using help:<br/><br/>help VR*<br/><br/>Jeffery Hicks<br/>Microsoft PowerShell MVP<br/>http://blog.sapien.com<br/>follow me: http://www.twitter.com/JeffHicks<br/><br/>"Those who forget to script are doomed to repeat their work."<br/><br/>Now Available: Managing Active Directory With Windows PowerShell: TFM Personally, I’m a big fan of custom nouns. When I run PowerShell classes I tell students about the naming conventions, the risks of name collisions and what most vendors are doing. I think a custom noun removes all ambiguity, plus it makes it easy for users to discover your cmdlets using help:

help VR*

Jeffery Hicks
Microsoft PowerShell MVP
http://blog.sapien.com
follow me: http://www.twitter.com/JeffHicks

“Those who forget to script are doomed to repeat their work.”

Now Available: Managing Active Directory With Windows PowerShell: TFM

]]>