Parsing command line arguments

I m pretty new to powershell and exploring its capabilities. One of the
things i m trying to experiment is creating a custom cmdlets. This is what i
m thinking of so please let me know if it is possible.

I have a custom cmdlet ParseCommandline, basically this will parse and
execute the input passed as a command line argument for eg.

ParseCommandLine | dir | sort -desc length | select -first 3

In above example ParseCommandline shud execute the dir then sort the data in
a descending order and finally select first 3 rows. How can i
programmatically access and execute this commands under ProcessRecord method.

Tks for your help.

In this case, your not passing any parameters to your cmdlet. You cmdlet is
just part of the pipeline and its output with be passed to next cmdlet in
pipeline (i.e. dir). If you want to execute that script from inside your
cmdlet for some reason then pass it as a scriptblock or string (i.e. mycmd
{dir|dothis|dothat} )

--
William Stacey [C# MVP]
Crypt your script
www.powerlocker.com


"Yogesh S" <YogeshS@discussions.microsoft.com> wrote in message
news:74D48EB8-74FB-46A2-8A40-1308E295A62E@microsoft.com...
|I m pretty new to powershell and exploring its capabilities. One of the
| things i m trying to experiment is creating a custom cmdlets. This is what
i
| m thinking of so please let me know if it is possible.
|
| I have a custom cmdlet ParseCommandline, basically this will parse and
| execute the input passed as a command line argument for eg.
|
| ParseCommandLine | dir | sort -desc length | select -first 3
|
| In above example ParseCommandline shud execute the dir then sort the data
in
| a descending order and finally select first 3 rows. How can i
| programmatically access and execute this commands under ProcessRecord
method.
|
| Tks for your help.
|
|

"William Stacey [C# MVP]" <william.stacey@gmail.com> wrote in message
news:uWWZnimoHHA.5032@TK2MSFTNGP02.phx.gbl...
> In this case, your not passing any parameters to your cmdlet. You cmdlet
> is
> just part of the pipeline and its output with be passed to next cmdlet in
> pipeline (i.e. dir). If you want to execute that script from inside your
> cmdlet for some reason then pass it as a scriptblock or string (i.e. mycmd
> {dir|dothis|dothat} )

You should also be aware that one of the values of the PowerShell
environment is that it provides the command parsing facility for each
cmdlet. This provides the benefit of consistent approach to argument
delimiters, support for both named and positional parameters and partial
name matching for named parameters. When creating a cmdlet, all you need to
do is declare properties that correspond to your parameters and decorate
them with the appropriate attributes e.g.:

[AllowNull]
[Parameter(Position = 0, Mandatory=true, ValueFromPipeline = true,
HelpMessage = "Accepts an object as input to the cmdlet. Enter a
variable that contains the objects or type a command or expression that gets
the objects.")]
public PSObject InputObject
{
get { return _input; }
set { _input = value; }
}

If you want to take a look at the source of a number of implemented cmdlets
download the source for the PowerShell Community Extensions:

http://www.codeplex.com/PowerShellCX...leCommits.aspx

--
Keith

Thanks Keith. I assume you wanted to reply to OP. On a related front, it
would be cool if partial name matching and wildcards worked for enum names
as well.

--
William Stacey [C# MVP]
Crypt your script
www.powerlocker.com


"Keith Hill [MVP]" <r_keith_hill@mailhot.nospamIdotcom> wrote in message
news:BF5F8974-CCF3-48DE-A885-03110C49675B@microsoft.com...
| "William Stacey [C# MVP]" <william.stacey@gmail.com> wrote in message
| news:uWWZnimoHHA.5032@TK2MSFTNGP02.phx.gbl...
| > In this case, your not passing any parameters to your cmdlet. You
cmdlet
| > is
| > just part of the pipeline and its output with be passed to next cmdlet
in
| > pipeline (i.e. dir). If you want to execute that script from inside
your
| > cmdlet for some reason then pass it as a scriptblock or string (i.e.
mycmd
| > {dir|dothis|dothat} )
|
| You should also be aware that one of the values of the PowerShell
| environment is that it provides the command parsing facility for each
| cmdlet. This provides the benefit of consistent approach to argument
| delimiters, support for both named and positional parameters and partial
| name matching for named parameters. When creating a cmdlet, all you need
to
| do is declare properties that correspond to your parameters and decorate
| them with the appropriate attributes e.g.:
|
| [AllowNull]
| [Parameter(Position = 0, Mandatory=true, ValueFromPipeline = true,
| HelpMessage = "Accepts an object as input to the cmdlet. Enter a
| variable that contains the objects or type a command or expression that
gets
| the objects.")]
| public PSObject InputObject
| {
| get { return _input; }
| set { _input = value; }
| }
|
| If you want to take a look at the source of a number of implemented
cmdlets
| download the source for the PowerShell Community Extensions:
|
|
http://www.codeplex.com/PowerShellCX...leCommits.aspx
|
| --
| Keith
|

"William Stacey [C# MVP]" <william.stacey@gmail.com> wrote in message
news:%23KTMLKnoHHA.4120@TK2MSFTNGP06.phx.gbl...
> Thanks Keith. I assume you wanted to reply to OP.

Yes, I was just trying to build on what you had said.

> On a related front, it
> would be cool if partial name matching and wildcards worked for enum names
> as well.

Partial name matching would be nice but I'm not sure how wildcards for enums
would work 'cept maybe for flags style enums.

--
Keith

Just as a lazy helper to disambig. For example
mycmd -color "bl???" #black
mycmd -color "r?d" #red
mycmd -color "g" # Error: gray or green
mycmd -color "g*n" # green

--
William Stacey [C# MVP]
PowerPad, PowerLocker
www.powerlocker.com


"Keith Hill [MVP]" <r_keith_hill@mailhot.nospamIdotcom> wrote in message
newsF87E0C7-6279-481E-B2F4-3508DD01221E@microsoft.com...
| "William Stacey [C# MVP]" <william.stacey@gmail.com> wrote in message
| news:%23KTMLKnoHHA.4120@TK2MSFTNGP06.phx.gbl...
| > Thanks Keith. I assume you wanted to reply to OP.
|
| Yes, I was just trying to build on what you had said.
|
| > On a related front, it
| > would be cool if partial name matching and wildcards worked for enum
names
| > as well.
|
| Partial name matching would be nice but I'm not sure how wildcards for
enums
| would work 'cept maybe for flags style enums.
|
| --
| Keith
|