get-command and *.txt "applications"

Has anyone else noticed that the get-command cmdlet identifies some of
the PowerShell .txt Help files as "applications". It also does that
for other non-PowerShell .txt files under C:\Windows and subfolders.

Run

get-command *.txt -commandType application | more

and see what I mean.

What's the rationale?

Andrew Watt MVP

On Thu, 11 Jan 2007 17:38:35 +0000, "Andrew Watt [MVP]"
<SVGDeveloper@aol.com> wrote:

>Has anyone else noticed that the get-command cmdlet identifies some of
>the PowerShell .txt Help files as "applications". It also does that
>for other non-PowerShell .txt files under C:\Windows and subfolders.
>
>Run
>
>get-command *.txt -commandType application | more
>
>and see what I mean.
>
>What's the rationale?
>
>Andrew Watt MVP

Just to add to the quirk.

Try

get-command *.bmp -commandType Application | more

Unexpected. At least by me.

Andrew Watt MVP

"Andrew Watt [MVP]" wrote:
> Unexpected. At least by me.
"get-command *.bmp -commandType Application | more"
That seemed surprising in the beginning but after reading through
Get-Command documentation on "CommandType" parameter,

"Application" represents all non-PowerShell files on the system that you can
run within PowerShell, including .txt, .exe. and .dll files in the Windows
PowerShell path.

Displaying *.bmp file just by specifying the BMP file name seems to fall
into the category of "Application" since "BMP" files are
1. "non-PowerShell files"
2. "You can run within PowerShell"
3. "files in the Windows PowerShell path"

But stil.. it is a bit unexpected ;p