On Jul 16, 8:15*am, Larry__Weiss <l...@xxxxxx> wrote:

> After reading your post, I started looking at Get-Member last night.
> It certainly opens your eyes to the world of .Net objects.
>
> * - Larry
>
>
>
> tojo2000 wrote:

> > The three things that I really liked when I first started were
> > 1. Objects and the pipeline. *Being able to pass objects down the
> > pipeline rather than text.
> > 2. Introspection. *Being able to take the output of the pipeline and
> > pipe it to Get-Member so that I can tell exactly which methods and
> > properties an object has.
> > 3. PSDrives. *The first time I loaded up the registry using a PSDrive,
> > that was really cool.- Hide quoted text -

>
> - Show quoted text -

Get-Member makes it really easy to see what your script is doing and
what it can do.

I frequently start a script and test it by doing a get-member on each
line, just to see where I am
and how to go forward.

I don't understand. Can you show an example?

- Larry


OldDog wrote:

> Get-Member makes it really easy to see what your script is doing and
> what it can do.
>
> I frequently start a script and test it by doing a get-member on each
> line, just to see where I am
> and how to go forward.

Bob Landau wrote:

> 5) While Get-ChildItem is the best tool I can think of for dealing with
> resources on a generic provider. I find common file querys such as
>
> dir /a-d
> dir /0e
>
> are far to complicated.

Agreed -- in fact, I wrote my own "dir" script in PowerShell -- gci is
just too much typing from what I was used to in cmd.exe
(http://windowsitpro.com/article/articleid/101900/).

--
Bill Stewart