Hi there. When I issue this:
get-command -commandtype filter
then what I get is filters and functions altogether.
What's wrong? This happens with the Pscx extensions
enabled as well as without it.
Thanks for your time.
Hi there. When I issue this:
get-command -commandtype filter
then what I get is filters and functions altogether.
What's wrong? This happens with the Pscx extensions
enabled as well as without it.
Thanks for your time.
"Darlove" <Darlove@xxxxxx> wrote in message
news:9858A993-9E4E-467C-9FA7-8AC6ACF31642@xxxxxx
> Hi there. When I issue this:
>
> get-command -commandtype filter
>
> then what I get is filters and functions altogether.
> What's wrong? This happens with the Pscx extensions
> enabled as well as without it.
>
> Thanks for your time.
Yep, that is confusing. It says in the documentation for get-command that in
that context
' "Filter" and "Function" represent all Windows PowerShell functions. '
but this is what I use anyhow .....
dir function: | where {$_.CommandType -eq 'Filter'}
--
Jon
| Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Run command problem in vbs | Tcs | VB Script | 5 | 08 Feb 2009 |
| Command prompt problem | bcwinch | General Discussion | 11 | 25 Sep 2008 |
| Re: Problem with Command Interpreter | the wharf rat | Vista General | 0 | 21 May 2008 |
| Re: Problem with Command Interpreter | propman | Vista General | 0 | 21 May 2008 |
| Command completion problem. | ymail | PowerShell | 2 | 23 Jan 2008 |