在使用Windows PowerShell时，您可能遇到了cmdlet这个术语，并发现自己有些困惑。cmdlet是否与命令完全不同，或者只是它们的PowerShell名称？今天的超级用户问答帖子回答了一位好奇的读者的问题。

今天的问答环节是由SuperUser提供的，SuperUser是Stack Exchange的一个分支，是一个由社区驱动的问答网站分组。

问题

超级用户读者RBT想知道为什么Windows PowerShell命令被称为cmdlet：

I have been trying to figure out the nomenclature for why commands are called command-lets (cmdlets) in PowerShell. Why they are not simply called commands instead? What is the difference?

I could only guess based on this Wikipedia article about PowerShell that it might somehow be an abbreviation of the command line interface to interact with commands written in .Net.

为什么Windows PowerShell命令称为cmdlet？

答案

超级用户贡献者LotPings为我们提供了答案：

According to Microsoft:

A cmdlet is a lightweight command that is used in the Windows PowerShell environment. The Windows PowerShell runtime invokes these cmdlets within the context of automation scripts that are provided at the command line. The Windows PowerShell runtime also invokes them programmatically through Windows PowerShell APIs.

How Cmdlets Differ from Commands

Cmdlets differ from commands in other command-shell environments in the following ways:

• Cmdlets are instances of .NET Framework classes; they are not stand-alone executables.
• Cmdlets can be created from as few as a dozen lines of code.
• Cmdlets do not generally do their own parsing, error presentation, or output formatting. Parsing, error presentation, and output formatting are handled by the Windows PowerShell runtime.
• Cmdlets process input objects from the pipeline rather than from streams of text, and cmdlets typically deliver objects as output to the pipeline.
• Cmdlets are record-oriented because they process a single object at a time.

Source: Cmdlet Overview [Microsoft]

有什么要补充的解释吗？在评论中发出声音。想从其他精通技术的Stack Exchange用户那里了解更多答案吗？在这里查看完整的讨论主题。