Comments on: Cmdlet clashes

By: alex

alex — Fri, 13 Apr 2007 20:54:12 +0000

hi nice site.

By: adrian

adrian — Fri, 09 Mar 2007 15:19:26 +0000

Unfortunately not. If there is a conflict, PowerShell throws a terminating error, eg:

The term ‘out-banner’ resolved to a cmdlet name that is ambiguous. Pos
sible matches include: Soapyfrog.Grrr\Out-Banner soapyfrog.conflict\Ou
t-Banner.
At line:1 char:11
+ out-banner <<<< hello

So without qualification, having duplicates will break a script.

By: Lance Robinson

Lance Robinson — Fri, 09 Mar 2007 15:08:15 +0000

Well I suppose add-pssnapin sets its own precedence level, so if I add your snap-in most recently, it will be the default used in case of a conflict (I think). Anything more fine-tuned than that would probably just be annoying.

By: Keith Hill

Keith Hill — Fri, 09 Mar 2007 05:29:40 +0000

You make a good point. It is something the PowerShell is probably going to need to address in a future release as more and more vendors provide PowerShell snapins.

By: adrian

adrian — Tue, 06 Mar 2007 15:16:36 +0000

I suppose you could resolve it like this:

New-Alias out-banner soapyfrog.grrr\out-banner

If you have lots of cmdlets, you might try this:

gcm -PSSnapin soapyfrog.grrr |% {$n=$_.name;$s=$_.pssnapin; new-alias -name “$n” -value “$s\$n” }

But that’s a bit of a hack.

I notice that default tab completion in the shell does alternate between different same-named cmdlets, so the PowerShell team did at least think about this.

By: Lance Robinson

Lance Robinson — Tue, 06 Mar 2007 14:44:50 +0000

I wonder if there is a way to define a permanent (in your profile) precedence for such ambiguous terms, so that if I use “out-banner” in my scripts, it will automatically assume that I am talking about the SoapyFrom.Grrr\out-banner.