Vista - Get-Format/Get-View command to return views, view defs?

Anyone interested in the idea of a Get-View cmdlet that will return views as
currently defined in a PowerShell instance?

I'm not sure how universally valuable it would be, but it would certainly
complement Get-Command and Get-Member fairly well.

This Cmdlet didn't make it to the current version. Please file a feature
request.
In the meantime, you can use our tracing capability to determine what view
is applied to an object. Please check out this blog entry:
http://blogs.msdn.com/powershell/arc...25/583263.aspx for details.

--
Kevin Loo [MSFT]
Windows PowerShell Development
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.

"Alex K. Angelopoulos [MVP]" <a k a @ m v p s . o r g> ¼¶¼g©ó¶l¥ó·s»D:%23oWSms3eGHA.3468@TK2MSFTNGP03.phx.gbl...
> Anyone interested in the idea of a Get-View cmdlet that will return views
> as currently defined in a PowerShell instance?
>
> I'm not sure how universally valuable it would be, but it would certainly
> complement Get-Command and Get-Member fairly well.
>

On Fri, 19 May 2006 15:32:38 -0400, "Alex K. Angelopoulos [MVP]" <a k
a @ m v p s . o r g> wrote:

>Anyone interested in the idea of a Get-View cmdlet that will return views as
>currently defined in a PowerShell instance?
>
>I'm not sure how universally valuable it would be, but it would certainly
>complement Get-Command and Get-Member fairly well.

Alex,

Care to elaborate on what you see as the greatest benefits? And
precisely what you would like it to do?

Andrew Watt MVP

"Andrew Watt [MVP]" <SVGDeveloper@aol.com> wrote in message
news:ic8s621albv5dcqnu32ula8dntgqphq7fl@4ax.com...
> On Fri, 19 May 2006 15:32:38 -0400, "Alex K. Angelopoulos [MVP]" <a k
> a @ m v p s . o r g> wrote:
>
>>Anyone interested in the idea of a Get-View cmdlet that will return views
>>as
>>currently defined in a PowerShell instance?
>>
>>I'm not sure how universally valuable it would be, but it would certainly
>>complement Get-Command and Get-Member fairly well.
>
> Alex,
>
> Care to elaborate on what you see as the greatest benefits? And
> precisely what you would like it to do?

I'm not at all certain about either, but here are some guesses about some
possible interesting things with it.

First, the correct noun would probably be PSView. Get-PSView would return
data about the structure of the view in different situations, generally
which parameters would be displayed and how wide columns are for tabular
views, etc. There might be a corresponding Set-PSView to change the view of
a data type dynamically. Get-PSView should take either actual command output
or typenames as arguments/input.

I would also probably like to see some matching cmdlets for
exporting/importing views (Export-PSView/Import-PSView) so they can be
shared/saved. There might be room for a distinct set of commands for
installing/uninstalling views persistently and checkpointing/restoring
views.

I just love PowerShell's beauty and extensibility.
And I can't even imagine what fantastic new extensions v2 and v3 will bring
to us...

--
greetings
dreeschkind


"Alex K. Angelopoulos [MVP]" wrote:

> "Andrew Watt [MVP]" <SVGDeveloper@aol.com> wrote in message
> news:ic8s621albv5dcqnu32ula8dntgqphq7fl@4ax.com...
> > On Fri, 19 May 2006 15:32:38 -0400, "Alex K. Angelopoulos [MVP]" <a k
> > a @ m v p s . o r g> wrote:
> >
> >>Anyone interested in the idea of a Get-View cmdlet that will return views
> >>as
> >>currently defined in a PowerShell instance?
> >>
> >>I'm not sure how universally valuable it would be, but it would certainly
> >>complement Get-Command and Get-Member fairly well.
> >
> > Alex,
> >
> > Care to elaborate on what you see as the greatest benefits? And
> > precisely what you would like it to do?
>
> I'm not at all certain about either, but here are some guesses about some
> possible interesting things with it.
>
> First, the correct noun would probably be PSView. Get-PSView would return
> data about the structure of the view in different situations, generally
> which parameters would be displayed and how wide columns are for tabular
> views, etc. There might be a corresponding Set-PSView to change the view of
> a data type dynamically. Get-PSView should take either actual command output
> or typenames as arguments/input.
>
> I would also probably like to see some matching cmdlets for
> exporting/importing views (Export-PSView/Import-PSView) so they can be
> shared/saved. There might be room for a distinct set of commands for
> installing/uninstalling views persistently and checkpointing/restoring
> views.
>
>
>
>