Vista - Suggestion: Cmdlet PSProvider

https://connect.microsoft.com/feedba...8563&SiteID=99

I believe a Cmdlet PSProvider is a valuable potential addition to the
PowerShell core product. Implementation should support invocation by path
and use of Get-Item and Get-ItemProperty. This would give us the following
benefits:
(1) It would be possible to explicitly invoke a cmdlet by path,
short-circuiting spurious aliasing or clashing function names. If the
standard cmdlet drive is named 'cmdlet', you could use
cmdlet:\Get-Command
and guarantee you are getting the Get-Command cmdlet and not an alias or a
function which has been given that name.

(2) The technique is intuitive, extending explicit path specification from
the FileSystem.

(3) The Item treatment provides a possible avenue for constructing cmdlet
invocations programmatically in an intuitive way, by getting the item,
setting property values, and then executing it.

(4) If cmdlets ever change significantly in different versions, it allows a
logical way for providing access to legacy versions in distinct cmdlet
provider containers.

Hi Alex,

I posted quite similar suggestions and some other (lengthy) thoughts about
PowerShell providers/drives some time ago in the old NG.
I don't know if you missed them (you have been in that thread too), so here
are the links again:

http://www.microsoft.com/communities...c6e&sloc=en-us

http://www.microsoft.com/communities...2af&sloc=en-us

I don't know whether MS or anyone else noticed or liked my ideas, because
none posted feedback on my suggestions. Unfortunately, I didn't have the time
yet to transform all my thoughts into feature suggestions for the connect
site. So, please feel free to file new feature requests on things you like as
well, as I'm quite bussy at the moment. I will then vote for them of course.


--
greetings
dreeschkind


"Alex K. Angelopoulos [MVP]" wrote:

> https://connect.microsoft.com/feedba...8563&SiteID=99
>
> I believe a Cmdlet PSProvider is a valuable potential addition to the
> PowerShell core product. Implementation should support invocation by path
> and use of Get-Item and Get-ItemProperty. This would give us the following
> benefits:
> (1) It would be possible to explicitly invoke a cmdlet by path,
> short-circuiting spurious aliasing or clashing function names. If the
> standard cmdlet drive is named 'cmdlet', you could use
> cmdlet:\Get-Command
> and guarantee you are getting the Get-Command cmdlet and not an alias or a
> function which has been given that name.
>
> (2) The technique is intuitive, extending explicit path specification from
> the FileSystem.
>
> (3) The Item treatment provides a possible avenue for constructing cmdlet
> invocations programmatically in an intuitive way, by getting the item,
> setting property values, and then executing it.
>
> (4) If cmdlets ever change significantly in different versions, it allows a
> logical way for providing access to legacy versions in distinct cmdlet
> provider containers.
>
>
>

I've got a list of about 20 bugs/features/etc. that I haven't cross-checked
in Connect myself. When I get the chance - probably next week at earliest -
I may just toss them out here in a single mega-post to see if anyone else
has raised them before I post to Connect.

"dreeschkind" <dreeschkind@discussions.microsoft.com> wrote in message
news:B1F30824-C72E-431D-A5AB-3729C17A2A7F@microsoft.com...
> Hi Alex,
>
> I posted quite similar suggestions and some other (lengthy) thoughts about
> PowerShell providers/drives some time ago in the old NG.
> I don't know if you missed them (you have been in that thread too), so
> here
> are the links again:
>
> http://www.microsoft.com/communities...c6e&sloc=en-us
>
> http://www.microsoft.com/communities...2af&sloc=en-us
>
> I don't know whether MS or anyone else noticed or liked my ideas, because
> none posted feedback on my suggestions. Unfortunately, I didn't have the
> time
> yet to transform all my thoughts into feature suggestions for the connect
> site. So, please feel free to file new feature requests on things you like
> as
> well, as I'm quite bussy at the moment. I will then vote for them of
> course.
>
>
> --
> greetings
> dreeschkind
>
>
> "Alex K. Angelopoulos [MVP]" wrote:
>
>> https://connect.microsoft.com/feedba...8563&SiteID=99
>>
>> I believe a Cmdlet PSProvider is a valuable potential addition to the
>> PowerShell core product. Implementation should support invocation by path
>> and use of Get-Item and Get-ItemProperty. This would give us the
>> following
>> benefits:
>> (1) It would be possible to explicitly invoke a cmdlet by path,
>> short-circuiting spurious aliasing or clashing function names. If the
>> standard cmdlet drive is named 'cmdlet', you could use
>> cmdlet:\Get-Command
>> and guarantee you are getting the Get-Command cmdlet and not an alias or
>> a
>> function which has been given that name.
>>
>> (2) The technique is intuitive, extending explicit path specification
>> from
>> the FileSystem.
>>
>> (3) The Item treatment provides a possible avenue for constructing cmdlet
>> invocations programmatically in an intuitive way, by getting the item,
>> setting property values, and then executing it.
>>
>> (4) If cmdlets ever change significantly in different versions, it allows
>> a
>> logical way for providing access to legacy versions in distinct cmdlet
>> provider containers.
>>
>>
>>