Cmdlet Naming

suggest change

Introduction

CmdLets should be named using a <verb>-<noun> naming scheme in order to improve discoverability.

Found a mistake? Have a question or improvement idea? Let me know.

Cmdlet naming:

*Cmdlet Naming

*Verbs

*Nouns

Table Of Contents

0Getting started

1Loops

2Operators

3Using ShouldProcess

4PowerShell classes

5Switch statement

6Working with objects

7Using existing static classes

8Basic set operations

9PowerShell functions

10Sending email

11Handling secrets and credentials

12PowerShell Remoting

13PowerShell Streams, debug, verbose, warning, error output

14Variables in PowerShell

15Communicating with RESTful APIs

16Working with the PowerShell pipeline

17PowerShell Background Jobs

18Return behavior in PowerShell

19XML

20Introduction to psake

21Progress bar

22Strings

23TCP communication

24SharePoint module

25Aliases

26Automatic variables

27Environment variables

28PowerShell profiles

29Enforcing script pre-requisites

30Using the help system

31Splatting

32Desired state configuration

33Signing scripts

34Security and cryptography

35CSV parsing

36Introduction to Pester

37Modules scripts and functions

38PowerShell.exe command-line

39Common parameters

40Parameter sets

41Regular Expressions

42PowerShell dynamic parameters

43WMI and CIM

44GUI in PowerShell

45Conditional logic

46URL encode/decode

47MongoDB

48Running executables

49Error handling

50HashTables

51ActiveDirectory module

52SQL queries

53Automatic variables #2

54Package management

55Cmdlet naming

56Built-in variables

57Creating DSC class-based resources

58PowerShell modules

59PowerShell workflows

60How to downloaded latest artifact from artifactory

61Calculated properties

62Special operators

63Anonymize IP v4 and v6

64Comment-based help

65AWS S3

66AWS Rekognition

67PSScriptAnalyzer

68Naming conventions

69Embedding managed code (C#, VB)

70Archive module

71Infrastructure automation

72Scheduled tasks module

73ISE module

74Recipies

75Contributors