The transition to NetApp MS Azure AD B2C is complete. If you missed the pre-registration, you will be invited to reigister at next log in.
Please note that access to your NetApp data may take up to 1 hour.
To learn more, read the FAQ and watch the video.
Need assistance? Complete this form and select “Registration Issue” as the Feedback Category.

Microsoft Virtualization Discussions

Naming Conventions for Cmdlets


One quick piece of feedback for the cmdlets is the naming scheme. There are quite a few cmdlets with verbs that do not adhere to the standard verb list that is published by Microsoft which can be found here. One example would be rather than "Perform-Failback" the proper name would be "Invoke-Failback."  Likewise, rather than "Abort-DRMirrors" the proper name would be "Stop-DRMirror"  All nouns should be singular. This is another best practice that the PowerShell team has encouraged developers to use. Using plural nouns can get very confusing, especially if you ever plan to release your products for other lanuages. Just as an example, the PS team has a cmdlet called "Get-ChildItem" - would the plural be "Get-Children" ? Stick to singular nouns.

This is a subtle but important detail. As a powershell user, I can go from VMM to exchange to OnTap PowerShell Toolkit and always have the same set of verbs and understandable nouns. It makes it much easier for us as powershell users to discover the capabilities you have provided in your cmdlets.

One other note is the idea of a noun prefix. The ONTap PowerShell Toolkit use Na for everything. i.e "Get-NaLun" or "Set-NaVol" I would suggest adopting a prefix for your cmdlets as well.. perhaps OC for OnCommand ?



Great feedback!  Thanks Andy.

NetApp on Discord Image

We're on Discord, are you?

Live Chat, Watch Parties, and More!

Explore Banner

Meet Explore, NetApp’s digital sales platform

Engage digitally throughout the sales process, from product discovery to configuration, and handle all your post-purchase needs.

NetApp Insights to Action
I2A Banner