{"id":10080,"date":"2015-10-23T06:00:00","date_gmt":"2015-10-23T13:00:00","guid":{"rendered":"https:\/\/www.sapien.com\/blog\/?p=10080"},"modified":"2015-10-18T11:46:55","modified_gmt":"2015-10-18T18:46:55","slug":"using-module-qualified-cmdlet-names","status":"publish","type":"post","link":"https:\/\/dev.sapien.com\/blog\/2015\/10\/23\/using-module-qualified-cmdlet-names\/","title":{"rendered":"Using Module-Qualified Cmdlet Names"},"content":{"rendered":"

Open-source projects and new methods of distributing modules, such as PowerShellGet and the PowerShell Gallery, have significantly increased the availability of Windows PowerShell modules. While we once relied on modules from Microsoft, we now can select from hundreds of new modules developed in the community.<\/p>\n

The upside of having so many modules is vastly increased utility. But, all of those new modules make cmdlet and function name conflicts more likely. Many modules use prefixes, but some are likely to slip through.<\/p>\n

To be sure that you’re using the cmdlet or function that you selected, and not a different one with the same name, use a module-qualified cmdlet name. This is valuable if you write scripts and modules, and critical if you share them, where they might run on a system with a module set that you cannot anticipate.<\/p>\n

PowerShell Studio has a new feature that qualifies all of the command names in your script. You can turn it on before you share a script and, if you choose, turn it off. PowerShell Studio also recognizes module-qualified names and uses syntax coloring to indicate when a command is correctly qualified.<\/p>\n

Module-qualified names were introduced in Windows PowerShell 3.0.<\/p>\n

Module-Qualified Cmdlet Names<\/h3>\n

To specify the module of a function or cmdlet, use the following syntax:<\/p>\n

[ModuleName]\\[Cmdlet_or_Function_Name]<\/pre>\n
For example, to specify the Get-Process cmdlet in Microsoft.PowerShell.Management, type:<\/p>\n
Microsoft.PowerShell.Management\\Get-Process<\/pre>\n
The module prefix is valid in any command. For example:<\/p>\n
Microsoft.PowerShell.Core\\Invoke-Command -Session $s -ScriptBlock {Microsoft.PowerShellCore\\Save-Help -Path D:\\HelpFiles}<\/pre>\n
You can also use module-qualified commands in splatted parameters. For example:<\/p>\n
$s = Microsoft.PowerShell.Core\\New-PSSession -ComputerName VMSvr01\r\n\r\n$Params = @{Session=$s; ScriptBlock={Microsoft.PowerShell.Management\\Get-Process}}\r\n\r\nMicrosoft.PowerShell.Core\\Invoke-Command @Params<\/pre>\n
PowerShell Studio Support for Module-Qualified Commands<\/h3>\n
Beginning in Version 4.2.90, PowerShell Studio recognizes and supports module-qualified commands.<\/p>\n
\u00b7 To qualify all of the commands in your script, type Ctrl + Shift + H<\/b>.<\/p>\n
\"image\"<\/a><\/p>\n
\u00b7 To remove the module qualification from all commands in your script, type Ctrl + Alt + H<\/b>.<\/p>\n
\"image\"<\/a><\/p>\n
Also, if you type a module qualified name for a particular cmdlet, and that module does not have a cmdlet with that name, such as a Get-Command command in the Microsoft.PowerShell.Utility module, PowerShell Studio labels it as “unknown.”<\/p>\n
\"image\"<\/a><\/p>\n
If you type a correct module qualification, PowerShell Studio recognizes it and colors it blue (or the color specified for cmdlets names in your Option settings).<\/p>\n
\"image\"<\/a><\/p>\n
Name Conflicts in Windows PowerShell<\/h3>\n
When two commands have the same name (and neither is module-qualified), the Windows Powershell command precedence rules determine which command runs. The precedence rules are documented in about_Command_Precedence<\/a>, but, in short, the precedence order is:<\/p>\n
1\u00b7 Alias
\n2\u00b7 Function
\n3\u00b7 Cmdlet
\n4\u00b7 Native Windows command<\/p>\n
When commands with the same name have the same type, Windows PowerShell runs the command that was added to the session last. Because that is arbitrary and not predictable, it’s best to qualify the command name.<\/p>\n
In Windows PowerShell 5.0, you can also install different versions of the same module in the same or different directories (and scope) on the same computer. It would be very useful to be able to qualify the version, as well as the module, of a command, but that’s a subject for a different blog post.<\/p>\n
June Blender is a technology evangelist at SAPIEN Technologies, Inc and a Windows PowerShell MVP. You can reach her at <\/i>juneb@sapien.com<\/i><\/a>\u00a0and follow her on Twitter at <\/i>@juneb_get_help<\/i><\/a>.<\/i><\/p>\n","protected":false},"excerpt":{"rendered":"
Open-source projects and new methods of distributing modules, such as PowerShellGet and the PowerShell Gallery, have significantly increased the availability of Windows PowerShell modules. While we once relied on modules from Microsoft, we now can select from hundreds of new modules developed in the community. The upside of having so many modules is vastly increased […]<\/p>\n","protected":false},"author":31,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[1034,703,25],"tags":[28,1016,997],"class_list":["post-10080","post","type-post","status-publish","format-standard","hentry","category-best-practices","category-powershell-studio","category-windows-powershell","tag-powershell","tag-powershell-studio","tag-windows-powershell"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t