Hi Uwe,
actually, my solution is really only a cheat that uses positional binding to emulate this behavior. If you use this with multiple parameters, order becomes important!
So no, usually it's not that awesome in PowerShell to try a 1-1 emulation of an old commandline .exe. You will indeed have to parse text in this scenario (which they also did) and it's not the way you really want to go.
Here's another example with a slightly different usage than what you'd prefer:
function Get-Test
{
[CmdletBinding(PositionalBinding = $false)]
Param (
[ValidateNotNullOrEmpty()]
[string]
$ComputerName = $env:ComputerName,
[Alias('p')]
[switch]
$pRun,
[Parameter(Position = 0)]
[Alias('pc')]
[int[]]
$pCount,
[Alias('d')]
[switch]
$dRun,
[Parameter(Position = 1)]
[Alias('dc')]
[int[]]
$dCount,
[Alias('b')]
[switch]
$bRun,
[Parameter(Position = 2)]
[Alias('bc')]
[int[]]
$bCount
) #end param
$PSBoundParameters
}
This allows you to run it like this:
Get-Test -p 10 -d 20 -b 30
However NOT like this:
Get-Test -p 10 -b 20 -d 30
But ... now you can do something like this:
Get-Test -p -dc 10 -bc 20,42
Which will set -p, so you can know to use the defaults, explicitly bind the value 10 to $dCount and the values 20,42 to $bCount. Not neat, but the closest I think you can get to what you want (specifying a parameter without binding any
value to it, but also being able to do so at a will) in a multi-parameter scenario.
Cheers,
Friedrich "Fred" Weinmann
PS: Please don't use single-letter parameter-names. Give them a meaningful name which later helps anybody read your script. Uses Parameter-Aliases, if you want the usability for the user. For example, instead of "i" call it "InputPath",
instead of "o" call it "OutputPath"
There's no place like 127.0.0.1
