►
From YouTube: PowerShell Object Formatting (David Goldman)
Description
The thing that makes PowerShell such an exceptional language is that the data it returns are objects rather than just text output. Mastering the PowerShell language depends on having a solid foundation of formatting PowerShell outputs.
This video demonstration by David Goldman is a deep dive into how to massage your PowerShell output data to work better for you. David covers how PowerShell formats the output objects it creates, how formatting is determined and how you can create your own custom formatting views with little effort. He also covers core concepts like what a PowerShell object is, How objects are passed down the pipeline from start to finish, and how PowerShell generates views of objects it creates (Table, List, Wide, Custom objects)
Who is David Goldman?
David Goldman is a Microsoft PFE in the O365 space. David's career with Microsoft spans over 20 years and he has a long history of supporting Microsoft Exchange and now Office365. Simply put, David is a master of finding and manipulating data with PowerShell.
About the Research Triangle PowerShell User group (RTPSUG):
The Research Triangle PowerShell Users Group (RTPSUG) is the largest PowerShell group in the world! We meet twice a month to discuss all topics related to PowerShell and automation. Our topics cover beginner to advanced concepts and offer people a chance to learn new skills and ask questions. Our mission is to create a space for all attendees to feel welcome, ask questions and be part of a community.
For more information on our group, please visit any of following links:
WEB: https://rtpsug.com
MEETUP: https://www.meetup.com/Research-Triangle-PowerShell-Users-Group
LINKEDIN: https://www.linkedin.com/company/rtpsug/
TWITTER: https://twitter.com/rtpsug
GITHUB: https://github.com/rtpsug
A
A
This
evening
we
have
dave
goldman
who's,
going
to
talk
to
us
about
the
inner
workings
and
the
funny
playing
with
powershell
objects,
and
you
know
dave
I
want
to
you
know,
simply
ask
you,
you
know
how
you're
doing,
and
you
know
how
did
you
get
into
you
know
some
of
what
you've
been
playing
with
powershell.
Tell
me
a
little
about
yourself.
B
I
don't
know
I'm
doing
well.
Thank
you,
phil,
mike
for
having
me
speak
tonight,
I've
a
little
bit
about
myself.
I've
been
at
microsoft
for
20
years,
I've
held
the
various
different
roles
css
I
was
customer
facing,
went
to
the
escalation
side
of
the
house
and
then
went
to
the
development
group
and
then
recently,
about
seven
years
ago,
came
back
to
public
facing
and
I've
in
some
way
shape
or
form.
B
I've
been
involved
with
powershell
since
it
was
created,
but
you
know
I've
only
used
it
at
times
that
I've
needed
to
for
myself
in
the
last
two
years.
I
started
getting
very,
very
serious
about
it.
I
started
working
side
by
side
with
some
of
the
devs
as
mentors
working
on
checking
in
bugs
the
power
shell,
and
there
were
some
things
that
that
I
came
across
that
I
found
pretty
interesting.
B
B
How
do
we
cut
this
down
without
losing
any
information,
or
how
do
we
see
what
we
want
to
and
a
little
bit
about
myself,
I'm
a
tinkerer,
so
I
really
love
to
dig
into
stuff,
so
the
best
place
for
me
to
go
was
into
the
powershell
source
code
and
debug
it
and
see
how
it
works,
figure
it
out
and
that's
what
I
did
that's
what
I
kind
of
do
with
with
all
the
topics
that
you
know.
If
I
don't
know
something
I
want
to
know,
100.
A
B
You
can
a
little
now
a
lot
of
people
don't
realize
I
don't
actually
have
a
college
degree,
I'm
self-taught.
So
when
I
first
got
into
it.
25
years
ago
I
started
with
my
mcse.
I
started
taking
certification
exams
and
started
working
my
way
up
and
I
always
had
a
passion
for
creating
things
which
led
to
development.
B
There's,
always
I
think
people
find
in
it
or
cs
that
there's
a
million
programs,
but
they
never
do
what
exactly
what
you
want
them
to
do.
So
that
kind
of
sparked
my
interest
in
creating
things
that
that
I
needed
and
that
led
me
down
to
code
path
and
then
through
work
that
gave
me
a
greater
path
for
escalation
and
growth
and
learning.
B
So
I
started
working
towards
becoming
a
principal
escalation
engineer,
which
basically
meant
that
I
was
debugging
problems
for
a
living,
so
I'd
get
a
problem
and
I'm
in
the
code
and
debugging
it
all
day.
Looking
for
the
bug
and
working
with
the
product
group-
and
so
you
know
if
you
really
have
a
deep
passion
for
that,
there's
always
a
place
to
start,
and
and
you
can
do
it,
if
I
could
do
it,
anybody
could
do
it.
C
So
so
tonight
is
about
I'm
assuming,
since
I
don't
know
the
the
core
material
other
than
some
of
the
stuff
we
discussed.
This
is
people
are
probably
used
to
gathering
data
in
powershell
and
not
realizing
that
once
they
get
the
data,
they
can
manipulate
it
and
turn
it
around
into
other
things,
and
maybe
some
of
that
is
sort
of
unknown
to
people.
Is
that
a
sort
of
a
good
summary
of
of
what
tonight
is
about.
B
Actually
yeah
and
I'm
gonna
put
that
up
on
the
screen.
I
just
put
the
about
speaker
slide
up
here.
It
has
my
github
link.
It
has
my
linkedin
link
and
my
twitter.
So
if
anybody
wants
to
contact
me
through
the
group
or
after
to
talk
about
this,
or
maybe
like
you
know
my
career
because
you
have
aspirations
to
to
get
into
cs
or
you
know,
I
t
feel
free
to
reach
out
to
me,
but
moving
along
to
the
topic.
B
B
And
then
I
have
a
couple
demos
that
basically
show
you
extending
types,
because
powershell
is
an
extensive
type.
You
can
basically
take
an
object
and
convert
it
into
something
else.
By
adding
you
know,
properties
and
methods
and
so
forth
to
it.
So
we
do
a
little
bit
we'll
we'll
do
a
little
bit
of
that
and
then
I'll
show
you
how
to
do
this
on
the
fly.
B
But
then
I'll
also
show
you
how
to
do
it
as
if
you're,
if
you
create
your
own
module,
because
the
processes
are
a
little
bit
different
and
then
I've
got
the
the
source
code
breakpoints
for
you
guys.
So,
if
you're
adventurous
and
you
want
to
go
into
powershell
source
code
and
debug
it.
You
just
need
to
download
that
from
github,
and
you
can
set
these
to
break
points,
build
it
and
then
you
can
play
around
with
it
yourself.
C
B
Right
I'll
see
thanks
mike
and
and
guys
by
all
means.
I
want
a
second
what
what
mike
and
phil
were
saying.
I
know
how
to
do
stuff
on
how
I
do
it
internally.
I
would
love
to
see
if
you
guys,
you
know,
do
this
type
of
stuff
out
in
your
neck
of
the
woods.
So
if
you
do-
and
you
have-
you
know
something
to
add-
please
you
know
share
it
with
me.
B
We,
when
we
talk
about
objects,
powershell
works
on
objects
and
everything
is
an
object.
We
have
to
have
some
sort
of
tangible
component
to
work
with
these
objects
have
different
components
of
metadata.
They
have
methods,
they
have
properties,
events
and
metadata.
The
methods
allow
you
to
take
an
action
on
that
object.
The
properties
you
can
store
data.
Those
are
your
variables
you
can
subscribe
to
events
and
the
metadata
are.
You
know,
information
about
the
object,
types
and
and
so
forth.
D
B
Did
that
work
there
we
go.
I
had
to
control
shift
on
this
on
this
so
and-
and
if
you
can
see
here
like
everything
that
I
have
in
my
environment
is
automated,
I
have
various
different
connection
points
through
my
profile
that
I
connect
to
and,
as
mike
was
saying,
phil
were
saying
earlier,
with
justin
have
an
add-in
for
secret
vault.
If
you
don't
play
around
with
secret
vault,
it
is
very,
very
cool.
B
C
B
C
B
B
All
right
I'll
get
I'll
grab
it
from
his
from
his
page,
because
I
I
bookmarked
it
but
not
to
take
a
look
while
you
do
anything,
yeah,
pretty
cool,
so
all
right.
So
let
me
minimize
this
region.
So,
for
example,
if
I
run
git
process,
git
process
runs
and
it
spits
out
all
this
horrific
stuff
to
the
screen
and
you're.
Like
you
know.
What
is
this
so
by
default?
B
There
is
a
hierarchical
structure
within
powershell,
where
all
objects
start
their
manifestation
from
a.net
object
and
each
one
of
these
have
different
views
and
in
several
other
presentations.
I've
been
asked
to
show
this,
but
just
forget
process
for
an
example.
If
I
run
this
you'll
see
that
there's
92
items
that
are
on
that
object,
if
you
were
unfamiliar,
there's
a
switch
called
force.
B
I
use
this
all
the
time
and
you'll
notice
that
if
you
dunk
that
out,
you'll
notice,
there's
167
items
that
are
on
that
that
object,
that
you
typically
wouldn't
see
and
a
lot
of
them
start
with
the
underscores,
and
you
can
actually
see
the
methods
for
sets
the
sets
the
gets,
and
you
know
finally
static
members,
there's
only
10
of
those,
and
these
are
ones
that
are
inherited
from
the
dotnet
object
itself
that
you
can
see.
So
if
I
was
to
actually
go
on
to
this
process,
I
could
call
start
or
new.
B
So
this
is
what
powershell
does
for
every
object.
Now
these
are
different
when
you
make
remote
calls,
because
in
certain
situations
you
have
something
called
serialization
and
deserialization,
where
you're
taking
information
from
one
system
and
you're
passing
it
to
another,
and
you
have
to
reconstruct
that
metadata.
But
for
now
that's
that's
another
topic.
We're
just
going
to
stick
with
just
local
objects,
and-
and
the
reason
for
this
is
this-
is
where
the
formatting
comes
in.
B
B
The
two
that
we're
focusing
on
here
is
the
ps
type
names,
because
this
is
where
you
can
actually
see
the
birth
of
this
object
and
what
it
gets
converted
to
and
then
the
ps
standard
member
set.
This
is
a
default
display.
Property
set
it's
on
every
object,
and
this
is
what
the
powershell
formatting
engine
is
looking
for
when
it
wants
to
format
objects.
B
So
if
I
dump
out
the
type
names
you
can
see
that
this
object
originally
was
a
system
object,
it
was
marshalled
by
reference,
goes
through
the
component
model
and
ends
up
as
a
system.diagnostic
process.
So
this
kind
of
helps
you
understand
what
that
object
morphed
into
and
then
the
second
one
which
is
more
important
and
by
by
all
means
if,
if
you're
not
familiar
with
objects,
or
you
haven't
really
dug
into
them,
the
one
tip
that
I
could
give
you
is,
and
you
can
do
this
for
hours-
create
an
object.
A
B
B
Is
you
can
create
custom
objects
in
powershell
and
you
will
give
them
a
name
so
and
that's
where
the
ps
type
names
comes
from
that
custom,
name,
that
you
call
it
like
dave's
object
or
whatever
that's
what
gets
stamped
on
the
object
and
that's
what
powershell
is
actually
looking
for
as
well.
As
you
know,
basically,
okay,
what
type
names
are
on
this
object?
C
There
are
different
types
of
objects
and
one
of
the
wonderful
things
of
a
powershell
is
based
on
those
objects.
Powershell
will
make
some
suggestions
for
you,
based
on
the
type
of
object
that
something
is
oh,
I
see
you
have
object
a
you
probably
want
these
methods
in
these
properties
in
these
views.
So
what
I
think
you're
going
to
be
talking
about
is
how
to
get
away
from
some
of
those
default
things
later
on
to
do
what
you
want
to
get
away
from
some
of
the
preferences
that
powershell
sets
right,
correct.
C
Yeah,
so
powershell
is
trying
to
do
a
lot
of
work
for
us
and
help
us
out
by
saying
when
I
get
certain
objects,
I
already
know
I
have
to
present
certain
things
to
the
user.
Dave
is
going
to
show
us
later
on
about
how
we
can
take
that
even
farther
to
say.
Well,
maybe
you
don't
want
the
help
that
powershell
has
given
you.
Maybe
you
want
to
do
your
own
custom
stuff,
so
I
just
wanted
to
give
that
as
sort
of
like
a
lead
in
because
that
may
have
gone
over
some
people's
heads
there.
B
D
B
B
You
can
always
send
that
down
to
the
pipeline
to
get
member
and
get
member
will
always
give
you
a
display
like
this,
and
this
will
show
you
that
you
know
I
created
a
string
and
it's
showing
that
for
this
type,
it's
a
string,
it
will
show
you
all
of
the
methods
that
are
available
for
the
string
class.
All
of
these
can
be
looked
at
at
msdn.
B
B
B
Powershell
tries
to
do
all
the
work
for
you,
so
in
this
case
we
have
asked
powershell
to
give
us
a
process
object
and
by
default,
there's
a
view
associated
with
this,
and
what
that
view
is,
is
this
so
we,
the
powershell,
dev
team,
stated
that
when
we
at
creation,
we
want
to
show
these
five
properties
id
handle,
cpu
system,
information
and
name.
So
when
you
actually
dump
out
that
object.
B
A
Well,
I
think
it's
the
question
that
I
think
some
people
would
have
would
be
not
so
much
direct
is,
is
almost
I
think,
you're
going
to
get
to
it,
and
I
think
you
know
you'll
be
fine.
That's
why
I
don't
want
to
ask
the
question,
but
is
what
was
the
value
in
knowing
that
information?
Is
that
hey
here?
Here's
some
information
that
I
have
and
here's
where
I
can
get
the
default?
A
A
It
go
ahead,
so
what
I
guess,
what
you're
you're
saying
really
is,
that
is,
if
you're
trying
to
get
different
information
back
out
of
the
objects
you're
currently
looking
at,
is
that
there
may
be
an
opportunity
for
different
views
and
there
may
be
opportunities
for
to
create
custom
objects
or
convert
the
objects.
You're
given
into
your
own
custom
objects.
To
then
keep
it
into
the
views
you
want
and
then
also
the
the
the
typesets
and
some
magic
beyond
that
right.
That
would
change.
C
Okay,
I
think
one
of
the-
I
think
one
of
the
frustrating
things
for
me
from
time
to
time
is
when
I
pull
back
data
sometimes-
and
I
do
go,
look
at
get
member.
It
comes
back
as
a
different
object
than
I
expected.
Sometimes
so
I
have
an
active
directory
focus
and
sometimes
it'll
come
back
as
an
active
directory
object
and
sometimes
it'll
come
back
as
string
objects.
B
Zero
is
always
your
first
element,
but
if
you
strip
too
many
out
or
you
create
a
new
object,
that
scalar
object
is
still
going
to
be
put
in
a
collection.
So
you
could
end
up
returning
and
seeing
a
system.string
for
that
instead
of
an
80
user,
and
that
was
one
of
the
reasons
why
I
kind
of
went
down
this
road,
because
I
would
run
into
that
a
lot
in
the
past,
working
with
mailbox
objects
and
address.
B
A
Go
ahead,
no!
No,
I
was
just
going
to
say,
and
some
added
to
that
is
one
of
the
things
that
I
find
is
that
certain
commandlets
or
even
you
know
I
deal
with
a.d
stuff,
and
I
also
do
with
like
vmware
stuff
and
because
it
is
it,
the
commandlets
sometimes
request
a
different.
They
work
differently
based
upon
the
object
type
coming
in,
and
so,
if
it
is
like
a
vm
object
or
is
it
an
ad
object
itself?
It's
an
it's
an
ad
object.
A
You
know
the
actual
class
ad
object,
then
it
it
does
different
things,
and
so,
but
if
I
send
in
a
string
it
acts
differently
and
it
puts
the
properties
in
the
different
places,
and
so
that's
also
kind
of
the
magic
behind
the
of
what
powershell
does,
and
so
that's
sometimes
what
I'm
really
trying
to
focus
on
what
kind
of
objects
I'm
working
with
is
so
that
the
next
commandlet
down
the
line
can
automatically
you
know,
parse
the
information
I'm
looking
for.
Is
that
hey?
It's
expecting.
A
B
B
And
what
we're
doing
is
we're
asking
powershell
filter
this
so
where
the
object
has
handles
that
are
greater
than
50
filter
all
of
those
out
and
then
we're
going
to
pass
this
down
to
the
sort
command
and
we're
going
to
say
sort
them
in
the
value
of
name
and
handles,
and
then
we're
asking
powershell
to
format
this
in
a
table
display
for
us.
So
what
that
looks
like
in
powershell
just
so,
you
can
see.
B
B
And
then
you
can
see
the
table
that
was
split
out
so
what's
happening
here.
Is
I
asked
for
that?
This
information
and
we
ended
up
getting
this
back
in
return
now
for
the
fit
for
the
visual
representation
what's
happening?
Is
we
hit
enter
the
powershell
parser
takes
all
of
this
information
and
says:
what
are
you
as
the
user
asking
for
me?
B
It
will
run
git
process,
it
will
go
and
now
give
it
to
where
object
and
we
work
on
each
individual
request.
Now
this
is
where
the
magic
comes
in
out
default
and
out
host.
This
is
where
you,
as
the
end
user,
would
see
the
information
displayed
on
the
screen
now
going
back
to
the
questions
of
where
what
I
was
asked
earlier
is:
what
is
the
importance
and
relevance
of
the
type
names
and
the
property
sets?
This
is
where
it
comes
in
handy,
so
we
ran
a
command.
Get
process
created
a
diagnostic
process.
B
It
holds
the
information,
as
you
saw.
We
passed
it
down
the
pipeline
now,
at
the
very
end
before
it
gets
to
the
screen.
There's
a
command
called
out
default
in
the
background.
Powershell
adds
that
to
every
object
before
it's
outputted
and
there's
two
things
that
outdefault
does.
The
first
thing
is
it's
responsible
for
communicating
with
the
powershell
formatting
engine
to
look
up
views
and
then
it
will
send
the
out
the
output
to
the
to
the
host.
That's
the
console.
B
If
there
is
no
predefined
view,
then
what
powershell
is
going
to
do
is
look
up
to
see
if
there's
a
user
defined
view,
one
that
you
have
created
in
the
using
two
different
powershell
xml
files,
which
I'll
show
after
this
is
where
the
type
names
comes
in,
where
you're
tying
your
custom
object.
To
that
view,
this
tells
powershell
hey.
B
If
there's
not,
then
the
powershell
just
does
its
absolute
best
and
says:
hey,
I'm
gonna
give
you
a
table
and
if
there's
too
much
information,
it's
gonna
give
you
a
list,
and
it's
just
going
to
spit
the
list
out
to
the
screen,
which
is
what
you
saw
here
and
powershell
just
dumped
all
of
this
stuff
out
in
a
list
now
it
formatted
in
the
list
that
I
wanted,
but
this
is
kind
of
clunky
to
work
with
this.
Is
you
know
this
is
a
little
bit
difficult.
B
You
know
to
work
with
now.
There
is
one
more
thing
that
I
wanted
to
point
out
when
it
comes
to
formatting
lists
and
objects
that
have
a
lot
of
information
in
them.
This
is
a
property,
it's
a
preference
property
called
format
enumeration
limit,
and
what
I'm
going
to
do
is
I'm
going
to
open
up
this
text
file
here?
But
if
you
guys
want
to
see
the
link
for
that
that
anyone-
that's
not
familiar
with
this,
this
is
in
the
ps
home
enus
directory.
B
These
are
where
your
help
files
are
and
there's
one
called
about
preferences,
and
these
are
the
default
preferences
that
powershell
uses
when
you
start
up
a
powershell
session,
and
this
will
show
you
all
of
the
default
values,
this
format
for
enumerated
enumeration
is
by
default
set
to
four.
So
what
that
looks
like
is
earlier
when
I
started
my
lab.
I
ran
a
couple
commands
and,
for
example,
here
in
my
lab,
I
pulled
back
a
object
per
job.
This
is
for
mailboxes,
but
you'll
notice.
B
B
This
value
is
per
session,
so
every
time
you
start
up
a
new
session,
that's
the
default!
Unless
you
go
into
your
powershell
profile
and
you
decide
to
set
up
the
preferences
where
you
want
to
have
it
always
enumerate
15
or
more,
because
you
want
to
see
all
of
the
data
and
know
what
you're
working
with
and
then
you
can
start
to
cut
it
down
from
there.
C
Yeah,
I
was
just
going
to
say
that
I
think
this
is
awesome.
What
you're
doing
the
slide
that
you
had
up
prior?
I
think
one
of
the
the
one
of
the
awesome
things
about
powershell
is:
is
that
what
you're,
showing
here
is
what
so
many
people
struggle
to
sort
of
understand
how
things
get
passed
along
and,
as
you
get
more
experience
with
powershell,
we
understand
these
processes
better.
C
One
of
the
great
things
about
powershell
is
you
can
kind
of
get
started
on
day
one
without
knowing
any
of
this
crap
and
get
kind
of
far
that's
the
cool
thing
about
it,
but,
as
you
dig
in
more,
you
really
understand
how
these
pieces
work
together
and
really
start
to
understand.
There's
a
lot
more,
you
can
do
when
we
start
to
pick
apart
the
processes
that
was
an
excellent
representation
of
how
that
works
behind
the
scenes.
That
was
awesome.
B
Yeah
powershell,
if
you
ask
for
it,
it
will
give
it
to
you,
you
can
get.
You
can
get
overwhelmed
really
quickly.
So
now
are
there
any
other
questions
on
that,
because
what
I'm
going
to
do
next
is
I'm
actually
going
to
jump
into
the
views
like
how
the
views
are
constructed?
What
are
the
files
that
back
them?
I'm
going
to
show
you
an
example
of
the
system
process
which
we've
been
working
with.
B
B
B
B
Ps1Xml,
thank
you
all
right,
you're
welcome.
So
now
for
the
for
the
formats
there's
four
different
views
that
you
can
create,
you
can
create
a
table.
You
can
create
a
list,
it
could
be
wide
or
it
can
be
custom
now.
One
thing
to
note
about
this
is
that
the
types
file
allows
you
to
extend
it
with
additional
properties.
B
B
B
So
with
regards
to
the
example
before
we
said,
get
all
the
processes
and
we
asked
powershell
to
construct
us
of
you,
we
said
look
for
all
of
the
ones
that
are
greater
than
50
and
sort
them
by
name
and
by
handle
count
and
give
us
a
table.
We
didn't
throw
anything
away,
but
at
the
same
time
powershell
gave
us
everything
now.
One
thing
I
want
to
stress-
and
it's
really
important
to
do
this:
never
you
never
want
to
update
these
core
files.
They
are
signed.
They're
digitally
signed
and
they
will
destroy
your
powershell
environment.
B
If
you
make
any
changes
to
these
files
directly,
what
you
always
want
to
do
is
use
a
template
from
one
of
them
which
I'll
show
you
how
to
do,
and
it's
super
simple
and
with
beginning
of
powershell
6.
These
are
the
type
files
are
no
longer
shipped
with
powershell.
They
are
actually
compiled
into
powershell.
B
So
if
you're
using
you
know,
windows,
powershell
or
using
windows
terminal-
and
you
have
different
powershell
sessions-
just
be
aware
of
that,
where,
if
you
fire
up
5-1
and
you're
creating
a
custom
view,
but
you
can't
find
them
in
six
or
above
we
didn't
get
rid
of
them,
they're,
just
part
of
powershell.
Now
and
and
if
you
want
to
take
a
look
at
those
real,
quick
I'll,
just
give
you
guys
a
quick
second,
what
you
can
do
is,
let
me
put
my
environment
back
up.
B
B
So
the
powershell
team
was
gracious
enough
to
ship
different
formatting
views
for
certificate,
information,
diagnostics
types,
and
this
goes
all
the
way
down
and
if
I
look
for
the
type
files
you'll
see
that
there's
just
a
couple
here:
the
dot
net
types
get
event
which
is
just
generic
and
then
types,
and
what
I'm
going
to
do
is
I'm
going
to
crack
two
of
these
open
and
again
for
anyone?
That's
not
familiar
with
aliases
ii's
invoke
item.
D
B
B
So
in
this
case
I
have
the
name,
and
I
can
go
back
and
look
in
that
type
file
and
I
could
say:
hey:
I've
got
the
correct
object,
and
so
now
taking
a
look
at
this,
I
can
see
that
there
is
a
ps
standard
member
set
and
the
powershell
team
has
in
fact
created
a
custom
view
and
by
default,
we'll
always
show
the
id
handles.
Cpu
si
system,
information
and
name,
and
then,
if
I
look
over
at
the
format,
how
are
we
going
to
display
this
to
the
screen?
B
You
can
kind
of
see
here
from
the
xml
format
that
we
have
an
object.
It's
called
process,
and
you
want
to
view
selected
by
this-
is
the
if
you
remember
before
the
ps
type
names,
here's
the
type
name,
and
I'm
going
to
show
you
how
to
do
this
when
we
construct
our
own,
where
we're
actually
going
to
construct
it.
But
you
can
start
I'm
hoping
that
everyone
can
see
how
this
kind
of
fits
together
now
with
the
type
name
and
using
the
view
get
member
where
you
can
see.
B
Okay,
now
I
ran
get
process
and
I
did
find
a
default
display
property
set,
and
I
also
found
that
we
have
a
view,
and
so
for
this
view
you
can
see
that
we're
doing
a
table
control
and
for
the
labels
here's
handle.
We
want
that
column
to
be
seven
characters,
what
in
width
and
we're
aligning
it
to
the
right,
and
you
can
kind
of
see
what
this
table
looks
like
and
here's
all
the
elements
that
are
in
that
table
so
by
default.
B
A
So
you're
saying
so,
I
just
make
sure
that
I
kind
of
understand
that
concept.
There
is
because
they're
the
default
types
there
it
would
return
those
three
properties,
but
because
we're
also
requesting
a
view
of
it,
it's
actually
using
the
format
instead
of
the
type.
So
if
I
just
dump
that
out
to
a
file
like
out
file,
then
I
would
only
get
those
five
properties.
B
You
you
would
get
the
view
you
would
get
all
of
these,
because
those
are
what
is
in
and
contained
in
the
object.
Now.
One
thing
I
should
mention
is:
is
everyone
here
familiar
with
select
object,
try
not
to
use
it.
If
you
don't
have
to
the
reason.
Why
is
because,
if
you
ever
use
select
object,
what
you're
doing
is
you're
asking
powershell
to
just
give
you
what
you
were
looking
for
and
it
discards
the
rest
of
the
information?
B
D
B
So
in
this
case
there's
a
lot
of
properties
on
process,
but
I
only
want
the
default
to
be
displayed,
so
I
could
remove
this
view.
I
could
cut
cut
out
this
process
system.diagnostic
process
from
the
format
file
and
when
I
ask
for
a
get
process,
what
would
happen
is
that
powershell
will
go
through
the
selection
process
and
say:
okay?
Is
there
a
formatted
view?
Oh
no,
this
stuff
doesn't
exist.
B
B
B
Yeah,
if
you
ever
do
select
object,
you're,
instructing
powershell
to
throw
away
everything
that
you
didn't
ask
for.
So
that's
why
that's!
My
suggestion
is
to
not
use
it
if
you
don't
have
to,
because
if
you
didn't
save
that
information,
if
you
didn't
save
that
object
to
json
or
xml
or
even
to
notepad
after
you
retrieved
it
like,
say
you're,
for
example,
you're
doing
a
long
database
call
you
waited
15
minutes
for
the
object.
B
You
didn't
save
it,
and
now
you
have
the
object,
and
you
say
I'm
going
to
ask
powershell
via
pipeline
to
do
select,
object
and
just
give
me
name
and
id
it's
going
to
construct
a
new
custom
object
in
the
background,
and
it's
going
to
populate
that
with
the
name
and
id
and
that's
the
object
that
you're
going
to
get
and
then
you
may
exited
your
session
and
realized.
I
don't
have
access
to
the
object
anymore.
I
just
threw
away
all
of
the
data
that
I
that
I
could
have
used
after
for
something
else.
B
So
I'm
just
kind
of
throwing
that
out
just
to
you
know
give
some
hindsight
for
maybe
some
of
the
newer
guys
that
read
some
of
the
literature
out
there
and
you
see-
hey,
select,
object,
just
to
be
aware
that
when
you
create
a
view,
you
still
have
all
of
the
information
there.
It's
just
not
constructed
in
the
view,
it's
hidden
in
the
background
on
the
object
where
select
object,
you're,
throwing
it
away.
C
All
we're
saying
here
dennis
is
that
when
you
do
something
like
get
process
or
get
child
item
get
item
or
get
ad
user,
it's
going
to
come
back
with
a
default
view.
That
view
is
going
to
come
based
on
the
members
that
are
in
that
view
right.
So
the
properties
that
came
back
when
you
said
get
ad
user
or
get
child
item
and
it's
going
to
look
up
that
object
type
and
it's
going
to
say,
does
all
these
things
match?
Oh,
I
know
what
basic
format
to
display
the
data
as
when
you
go
select
object.
C
What
happens
is
you're
just
basically
going
you're
going
off
the
plan
now
and
it
might
work
it
might
not.
If
you
cut
too
much
data
away
and
it
doesn't
match
anything
in
the
type
or
the
format,
then
it's
going
to
go
to
the
lowest
common
denominator.
It's
going
to
say:
well,
I'm
just
going
to
give
the
best
view
I
can
based
on
what
data
you
gave
me.
So
if
it's
two
fields
I'll
do
a
list,
if
it's
more
fields
I'll
do
a
table,
I
got
that
backwards,
but
does
that
make
sense
dennis.
C
B
C
B
Yeah
and
you
can
those
you
can
create
custom
these
you
can.
You
can
get
pretty
elaborate
with
these,
the
ones
that
I'm
just
showing
tonight.
These
are
just
basic
table
and
list,
but
you
can
you
know
if
you
want
to
get
fancy
and
putting
html
objects
in
the
xml
and
having
it
rendered?
You
know
you
can
get
pretty
elaborate
I'll
see
if
I
can,
if
I
can
track
that
one
down
and
get
that
one
back
to
the
group.
B
Some
of
those
are
actually
handled
in
the
c
sharp
code
in
the
background,
when
the
object
is
being
constructed
and
being
served
back
to
you.
So
if
you
actually
look
in
the
powershell
source
code,
there
are
some
formats
in
there
where
you'll
see
like
you
know,
bytes
divided
by
a
thousand,
you
know,
there's
they
have
the
calculations
that
are
in
there
and
then
the
object
is
serialized
back.
So
some
of
those
won't
be
in
the
views.
The
the
views
are
more
for
just
constructing
what
you
want
to
see
on
the
on
the
screen.
D
B
Yeah
that
now
that
you
know
something
like
that,
yeah
that
you
can
do
and
I'm
actually
I
have
an
example
of
that
and
I
will
show
you
how
to
do
that.
It's
like
it's
here!
This
is
like
one
example,
but
if
you're
looking
on
an
event
log
entry
when
you're
formatting
the
table,
you
can
actually
put
code
in
here
so
they're
using
a
formatting
string
for
this.
I
have
other
examples
in
mind
so
like
here,
so
you
can
do
that
by
achieving
that
with
a
block.
B
All
right,
so
I
think
I
think
this
will
help.
If
we,
you
know
we'll
jump,
put
it
on
the
screen,
so
you
can
see
it
so.
Procedurally,
there's
a
couple
different
ways
that
you
can
extend
these
objects.
One
is
with
add
member
another
one
is
with
update
type
data
and
update
format
data.
So
let
me
put
this
up
here.
So
all
right,
I'm
going
to
give
you
example.
So
I'm
going
to
clear
out
the
screen
and
I'm
going
to
create,
if
is
I
hope,
everybody's
familiar
with
ps
custom
object.
B
A
B
B
B
Ps,
custom
object,
so
I
gave
it
a
hash
table
of
values.
I
said
first
name
last
name
date,
which
I
just
did
a
little
formatting
on
there,
and
this
is
what
powershell
gave
me.
It
gave
me
back
an
object
that
has
some
methods
to
it,
and
the
member
types
are
note
properties-
and
this
is
these
note-
properties
are
containing
my
data.
B
B
B
B
B
B
C
B
You
you
can
you
can
what
I
have
seen
in
testing.
That
is,
if
your
type
name
is
on
there
and
the
type
name
is
first
in
that
list.
What
will
happen
is
powershell
will
look
up,
and
so
let
me
take
a
step
back.
Yes,
it
will
find
it
when
you
start
powershell
and
powershell
creates
that
local
session.
For
you,
it
reads
those
type
files,
the
ps1,
the
types
ps1
xml
and
the
format
ps1
xml,
and
it
creates
a
custom
types
and
format
cache
table.
B
So
now,
if
I
added
that
system.diagnox
process
to
my
own
custom
object
when
powershell
goes
through
that
selection
process,
it
will
see
if
there's
a
custom,
predetermined
view
and
it'll
say:
oh
looks
at
the
type
names
and
says:
wait:
this
has
system.diagnostic
process.
It
will
look
up
that
view
and
print.
That's
the
view
you'll
get
to
the
screen.
D
B
Yeah
and
you
now
you'll
you'll
notice
here
and
I'll
show
you
I
was
going
to
show
you
this
later
on,
but
I'll
just
I'll
show
it
to
you
now
in
my
custom
project.
Here
all
of
my
custom
objects
are
associated
with
that
ps
type
name.
So
here
I
have
one
for
ps
utilities
job
and
then
I
could
scroll
down
you'll
see
that
I
have
some
custom
code.
B
This
is
a
script
block
that
I've
basically
added
to
say
if
the
character
length
is
greater
than
15
display,
dot,
dot
dot
and
as
I
scroll
down
you'll
notice.
Now
I
have
one
for
sessions.
You
can
add
multiple
and
the
recommendation
is
always
to
have
one
format
file,
but
you
can
create
multiple
views
for
your
objects.
B
It
can
get
a
little
bit
hairy,
but
you
just
gotta,
be
careful
with
what
you
want
to
show,
because
you
can
have
a
custom
view
you
may
want
to
create
just
a
table.
You
may
just
want
to
have
a
default
for
different
objects.
I
have
seen
the
recommendation
internally
create
one
view
for
one
object
just
to
keep
it
simple.
B
B
A
So
are
you?
Are
you
really
saying
it's
like
an
it's
almost
like
the
the
inheritance
process
of
you
know
it's
a
system
prop
it's
a
system.
Then
it
becomes
a
string.
Then
it
becomes
a
char
and
all
that
stuff
and
you
can
and
it's
effectively
just
an
array
and
it
goes
down.
It
goes
into
the
queue
and
then
it
pops
them
off
the
queue
in
that
order
too.
So
you
you
had
your
system
object.
Then
you
called
it
my
custom
and
then
you
called
it
by
custom
one.
A
So
if
you
have
a
a
you
can
do
something
with
custom
object.
One
well
it'll
take
that.
But
if
it
doesn't
know
anything
about
system,
object,
object,
one,
but
it
does
know
something
about
system
object.
It'll
pick
up
system
object,
so
you
can
kind
of
like
tear
them
and
then
it'll
just
pick
up
the
first
one.
It
sees
from
the
popping
of
the
of
the
the
wreck.
B
You're
going
to
get
to
a
system
object
which
is
a.net
object,
and
it's
just
going
to
say
here
you
go
most
likely,
that's
going
to
be
a
ps
custom
object,
because
the
way
the
power
shell
is
designed
for
system
stuff,
like
get
process
get
system,
you
know,
get
windows,
feature
and
other
things.
There
are
built-in
types
associated
with
those
objects.
B
C
So
so
another
way
to
think
about
this
is
string
is
a
type
of
object
right.
So
when
you
looked
at
the
previous
examples,
when
we
were
talking
about
multiple
types
or
multiple
types,
on
an
object,
they're
really
subtypes
right,
there's
the
broad
category
and
then
like
phil,
said
string
and
then
a
char
and
we're
really
narrowing
down
to
getting
to
more
specific
types.
D
B
A
B
D
C
B
There's
a
lot
I
mean
like
that's,
let's
go
back
to
my
reference
before
where
I
was
it
was
suggesting,
and-
and
I
do
this
quite
often
I
run
git
member
on
everything
and
then
I
run
it
on
every
individual
property,
that's
on
there
and
it
dumps
out
a
lot
of
stuff.
So
you
can
actually
see
it
now.
The
one
thing
to
remember
with
get
member-
and
I
don't
know-
I
don't
know
how
known
this
is-
but
I'll
I'll-
let
you
know
anyway,
if
you
have
a
collection.
B
See
that
there's
three,
if
I,
if
I
run
get
member
on
this
by
default,
get
member
is
going
to
show
me
that
it's
a
system
in
32
right
you.
What
you
want
to
do
is
if
you
want
to
see
all
of
the
elements
this
is,
and
I
should
say
let
me
take
that
back.
This
is
this
is
a
collection
of
n32s,
but
if
I
wanted
to,
you
can
either
put
a
comma
in
front
of
it,
which
tells
tells
get
member
to
do
not
flatten
the
collection.
B
B
B
B
B
B
So
I
had
I
oh
so
yeah
I
have
a
string
and
I
added
one
two
three,
so
three,
three
ins
and
I
added
a
string
or
a
char
to
it.
I
ran
get
member
get
member
shows
the
first
element
to
n32
right
because
there
was
three
of
them
and
then
it
shows
me
a
system
string,
it
flattens
every
flattens,
the
collection.
B
Powershell
goes
through
the
parser
and
then
it
starts
to
work
on
those
objects
and
it
enumerates.
It
says:
okay,
what's
here,
powershell's
job
main
main
job
in
my
mind,
is
to
take
a
look
and
inspect
every
single
object
figure
out.
What's
there
does
it
need
to
be
casted
or
not
from
one
type
to
another
for
those
that
are
not
familiar
with
casting
it's?
Basically,
when
you
take
an
object
and
you
change
it
to
another
type.
B
So
if
I
was
to
do
say,
for
example,
a
equals
1,
I
can
see
that
a
is
isn't
it's
an
int
now,
if
I
follow
powershell's,
you
know
parsing
rules
for
using
quotes
and
single
quotes.
I'm
still
typing
in
the
same
thing,
but
powershell
knows
now,
based
on
the
two
single
quotes,
that
that
was
not
a
number.
It
was
a
string,
and
so
now,
when
I
get
member,
it
shows
me
hey.
What's
there.
B
D
B
C
C
B
B
B
I
go
to
sub
reference,
the
ps
type
names
and
I
also
pass
that
to
get
member
and
what
that
is
showing
me
is
that
there
are
of
this
type
system
string.
There
are
some
methods
here
and,
if
you
notice,
when
I
had
said
earlier,
when
you
have
an
object
that
you
have
methods,
they
allow
you
to
take
actions
on
an
item.
B
What
I'm
doing
is
I'm
calling
the
insert
method
off
of
the
ps
type
names
object,
that's
associated
with
custom
object,
3
and
if
I
dump
this
out,
you'll
notice
that
it
just
has.
It
was
an
object
and
I
extended
it
and
now
I'm
going
to
call
the
insert
method
and
I'm
going
to
insert
that
my
custom
object,
33,
which
was
a
typo
and
you'll,
see
that
it's
there
now
subsequently.
I
can
also
call
the
remove,
because
I
made
a
mistake.
B
B
Typo
somewhere,
oh
okay,
yeah
be
careful
when
you
do
this.
If
you're
calling
the
remove
these
are
case,
sensitive,
you'll
notice
here,
where
I
did
the
cut
and
paste
it
had
a
capital
c
before
it
didn't,
and
this
will
return
true
or
false.
So
now,
if
I
go
back
to
the
type
name,
you
can
see
that
I've
actually
removed
it
from
the
type
names
table
and
now
I
can
go
back
and
I
can
fix
that
and
add
it
back
here.
B
Okay,
so
now
this
custom
object
has
a
name,
that's
great,
but
so
now
what
does
this
do?
Well
now,
as
I
mentioned
before
you
have
to
let
me
take,
let
me
take
a
step
back
right
to
the
beginning
again
of
this
object
creation.
So
we
can
see
this
since
we
got
off
a
little
bit,
I'm
going
to
pull
up
my
custom
object.
B
And
for
the
type
names
I
added
this
type,
my
custom
object.
If
I
dump
this
custom
object
out,
I
just
get
a
list,
that's
not
cool!
I
don't
like
that.
So
what
I'm
going
to
do
is
I
want
to
update
this
on
the
fly
for
this
session,
so
I'm
going
to
call
update
type
data
and
the
type
name
is
the
one
that
I
want
to
update
in
this
case.
It's
my
custom
object
which
matches
my
custom
object.
B
B
C
B
B
B
C
B
C
B
B
C
B
Yeah
now
remember
that
the
interesting
thing
here
is
that
that
it
affects
my
list
and
my
table,
but
everything
is
there
now.
I
could
totally
do
a
select
if
I
wanted
to,
and
you
can
totally
do
that
but
say
I
wanted.
You
gave
me
a
request
and
you're
like
hey
dave
this
I
need
you
to
add
some
more
stuff,
so
I
go
back
to
the
display
and
I
say
all
right.
Let
me
let
me
add
last
name
and
you
can
update
this
thing
on
the
fly.
A
I
got
you
so
that's
the
magic
and
or
that's
the
that's
the
hidden
secret
in
that,
because
you're
just
changing
the
display
of
the
object
and
not
changing
the
objects.
And
I
understand
now
when
you're
saying,
if
you
start
selecting
out
the
different
parts,
technically
you're,
just
you're,
doing
something
different
you're.
A
B
B
System.Management.Automation.Ps
custom
object,
that's
holding
my
information
now
I
passed
it
down
the
pipeline
right,
we
did
a
pipe
and
we
did
ft
and
we
said
show
us
everything.
So
what
happens
is
right
before
it
gets
to
the
screen?
This
is
where
that
formatting
engine
goes
through
and
says.
Is
there
a
predefined
view?
Well,
we
do
have
a
predefined
view,
because
we
ran
update
type
data
type
data
and
we
said
and
originally
show
us
first
name
and
date,
and
so
that's
what
it
returned.
B
If
that
wasn't
there,
you
know
in
this
can
now
this
case
for
system
process.
This
wouldn't
be
here
because
that's
not
predefined.
We
have
a
user-defined
view,
which
is
the
second
one.
So
we
go
to
that
and
then
we
just
go
down
the
selection.
If
there's
no
user
defined,
but
there
was
a
system
process,
then
we
see
if
we
just,
we
have
a
default
display
property
set.
C
So
so
one
of
the
things
that
I
find
interesting
about
this
is
that
I'm,
I
do
do
custom
objects
a
lot
when
I
make
some
functions
to
output.
Basically,
a
custom
set
of
a
custom
view
right,
but
I've
always
thought
of
a
custom
object,
as
let
me
make
the
object,
be
what
I
want
to
see
on
the
screen
instead
of
well.
Maybe
I
want
to
collect
a
whole
bunch
of
data
and
let
me
just
customize
what
people
could
see
in
the
default
view.
B
Yep
now,
and
just
to
show
you
this,
if
I
write
here's
my
custom,
you
know
my
custom
object.
Here
is
the
three
that
we
defined,
but
I
can
still
show
you
that
everything's
still
there
I
can
still
construct
whatever
formatting.
I
want,
because
those
note
properties
still
exist
as
metadata
on
that
object.
A
B
Yeah
yeah
and
if
you
notice,
I
was
going
to
show
you
this
later
on,
we
don't
have
to
too
much
more
here,
but
I
was
going
to
show
you
how
to
do
it
for
a
module.
But
when
you
create
a
view,
let's
say,
for
example,
I
have
one
for
jobs
and
there's
a
data
field.
If
here's
the
data
field
here
your
table,
let
me
see
if
I
can
get
enough
screen
and
I'm
going
to
open
these
up
as
well.
You
have
your
table
headers,
which
have
to
have
the
names
right.
B
B
If
the
first
one
is
center,
so
you
see
I
have
this
one
and
then
I
have
name.
If
I
look
down
here,
you
see
I
have
index
and
then
this
instead
of
name,
it's
the
script
block,
and
so
this
is
where
I'm
using
that
script
block.
When
we
do
the
format
we
look
at
this
table
column
and
we
go
hey.
There's
the
script
block
here.
B
We
doing,
and
I'm
basically
saying
take
the
name-
and
I
in
my
case
I'm
saying
if
the
length
is
greater
than
15,
then
I
want
you
to
chop
it
down
to
construct
a
smaller
view
and
then
just
put
dot
dot
dot
on
it.
This
script
block
can
be
any
code
that
you
want
to
create
and
that
you
want
to
do
on
your
formatting.
B
A
And
so
the
real
data
is
just
a
freaking
number,
but
if
you
send
it
out
to
a
form
to
a
table,
it
comes
out
in
the
form
you
want.
But
ultimately
it's
this.
You
know
this.
You
know
the
number
of
ticks
from
like
last
password
set,
it's
ticks,
I'm
like
who
the
hell
is
going
to
make.
It
need
to
go
sick
ticks,
but
I
want
to
see
it
in
the
date
form.
Yes,.
B
Absolutely
this
is
it
right,
the
powershell
formatting
engine
his
whole
job
is
to
say
how
do
you
want
to
see
this
data
and
then
it
just
goes
to
look
to
see
if
there
was
predefined
or
a
user
custom,
and
if
there
is
that's
its
job
is
to
display
that
to
the
console
interesting
now,
there's
some
other
now,
there's
some
other
cool
things
that
you
can
do.
I
don't
know
how
many
people
here
I'm
a
contributor
to
ps
framework.
B
I
can
just
do
custom
formatting
on
the
fly,
while
I'm
retaining
the
object.
One
of
the
things
that
he
does
in
ps
framework
is
he's
very
big
on
object
retention.
So
if
I
had,
for
example,
in
mike's
case
mike
does
a
lot
of
ad
stuff
when
you
make
calls
to
active
directory
that
data
has
to
be
serialized.
B
If
you're
asking
for
computer
names
nine
out
of
ten
times
the
computer
names
coming
back
like
if
you're
looking
for
domain
controllers
are
going
to
be
deserialized
ps
framework,
he
has
methods
in
there
that
retain
the
original
objects,
so
you
can
have
serialization
and
still
be
able
to
do
customizations
on
on
objects.
So
I
could
do
you
know
other
things
like
you
could
do
get
date,
and
this
would
show
you
the
date
and
then
I
could
format
this
and
change
the
numbers.
B
So
if
I
know
how
to
do
it
in
ps
framework,
I
haven't
done
it.
I've
cheated.
I
use
ps
framework
to
do
it
because
he
has
some
methods
in
there
that
basically
allow
you
to
collapse
the
objects.
So
that
way
you
can
print
them
out
csv,
but
typically
anything
that
gets
printed
out
to
an
out
file
or
csv.
If
it's
a
string,
it's
going
to
have
those
the
marks
on
it.
A
B
To
work
yeah,
that's
the
last
one
that
it's
going
to
run
through
so
before
you
before.
You
actually
have
it
outputted
if
you're
exporting
it
that
data
is
being
manipulated
and
then
it's
just
being
displayed
now.
These
views,
these
are,
are
going
to
be
the
views
that
you
see
on
the
screen.
When
you
go
to
out
file,
it's
going
to
be
a
little
bit
different.
B
B
I
believe
that
you
would,
you
would
end
up
having
no,
you
would
have.
You
were
you'll,
get
the
fields,
but
if
you
did
say
some
custom
programming
here
to
like
add
commas
or
to
remove
commas,
those
should
be
gone
because
you're
processing
it
and
that's
something
you
you'd
have
to
just
you
know:
you'd
have
to
test
out
because
you
could
put
a
command
in
there
to
strip
out
commas
quotes
and
things
like
that.
B
B
D
B
Here
it
is
right
here,
okay,
so
I
didn't
have
it
on
notepad,
but
because
I
just
rebuilt
this
machine,
but
I
always
save
my
stuff.
So
if
I
go
back
to
the
presentation
you'll
see
here
that
I
already
had,
I
didn't
have
it
on
the
notepad,
where
I
didn't
have
it
dumped
out,
but
I
have
it
in
the
project.
So
what
I
did
was
I
I
went
and
got
the
xml
and
I
just
basically
called
it.
My
custom
object.
B
So
here's
my
custom
object,
here's
the
type
name
and
the
table
columns
right
and
I'm
just
putting
them
all
to
the
center
and
I
defined
the
table
rows.
So
I
want
to
see
first
name
last
name
date,
city,
very
generic.
What
I'm
gonna
do
is
I'm
actually
gonna
to
make
this
work.
I
gotta
put
this
in
a
notepad
real.
B
D
B
All
right,
I'm
going
to
save
that.
So
what
I'm
going
to
do
now
is
I
have
the
data
in
in
notepad.
Let
me
just
open
it
up,
make
sure
it
opens
up
cool
all
right,
it's
there.
So
here's
my
my
xml
view
and
what
I'm
going
to
do
is
I'm
going
to
update
my
format
view
on
the
fly.
Let's
see
what
happened
here.
B
B
So
now
I
ran
update
format
data
so
before
we
ran
update
type
data
where
we
created
the
default
display
property
set.
Now
I'm
creating
my
view
and
now,
if
I
go
and
dump
out
my
custom
object,
there's
my
table,
I
can
also
dump
it
out
in
the
list
and
the
list
now
did
you
guys
notice
something
different
that
happened
there.
B
B
B
B
Yep
still
there,
so
if
I
go
back
here
and
I
do
get
member
there's
all
my
stuff
there
first,
you
know
first
name
company
date,
which
I
can
clearly
go
and
do
you
know
this
formatting
and
there's
all
the
stuff
there
now
I
could
do
something
like
say.
I
want
to
update
this
again
and
I
want
to
do
I
don't
I
don't
like
name
let's
just.
B
D
D
D
B
B
B
A
B
B
A
A
A
B
And
now
I've
I've
effectively
still
have
the
same
view,
but
I've
changed
it.
So
my
view
now
shows
first
and
last,
and
I
can
change
these
to
whatever
I
want.
But
if
I
go
and
look
at
my
my
object,
you'll
notice
that
the
original
still
first
name
so
I've
just
changed
the
view.
So
maybe
this
is
the
object
that
I
got,
but
mike
is
in
hr
and
mike's
like
hey
the
data
that
you're
sending
to
me
really
doesn't
work
for
me,
because
I
can't
import
this.
A
B
My
suggestion
is
that
you
always
have
it
match.
If
you
want
to
mess
around
with
stuff
and
test
it,
I
would
say,
for
production,
environments
always
have
the
match,
because
it's
very
easy
for
somebody.
You
know
you
could
put
a
comment
in
vs
code
and
say:
don't
touch
you
know,
will
will
just
you
know,
destroy
view
or
something
like
that.
B
B
Modulename.Format.Ps1Xml,
which
should
reside
in
your
xml
directory,
you
only
want
to
have
one
of
these.
You
don't
want
to
have
multiple,
multiple
files.
The
recommendation
is
to
create
one,
and
then
you
could
put
multiple
objects
in
there.
So
you
could
see
here.
I
have
one
for
jobs
and
one
for
sessions
and
then
the
types
this
is
just
you
know
as
for
me,
this
is
just
a
regular
custom,
ps
framework
or
ps,
develop
module
development,
module
creation.
B
In
your
psd1
file,
you
have
to
make
sure
that
you
specify
the
formats
to
process
and
you
want
to
point
it
to
that
format.
Xml.
So
what
happens?
Is
that
runtime,
when
you
do
a
ip
ipmo
or
that's
alias,
for
import
module
and
it
imports
it?
It
looks
at
the
formats
the
process
and
powershell
says:
go
to
the
xml
directory
and
load
this
format
file
into
this
powershell
session,
which
essentially
runs
the
update,
format,
type
data
and
pulls
your
views
into
the
cache
table.
So
you
have
them
now.
One
thing
to
note
about
that.
B
B
B
All
right,
so
what
I'm
going
to
do
is
you
can
run
the
command,
get
type
data
and
what
this
is
going
to
do
is
since
we're
working
on
a
job
object.
I
want
to
dump
out
all
of
the
job
objects
so
by
doing
get
type
data
you
can
do
this
for
any
type
and
it
will
dump
those
out
for
you.
What
I'm
really
concerned
about
here
is
the
management
automation
job.
B
B
B
This
is
what
I
have
come
back
so
for
me,
I
find
it
incredibly
frustrating
when
I'm
working
with
jobs
and
I
run
a
receive
job
and
I
end
up
throwing
the
data
away
because
I
didn't
use
the
keep
command.
So
what
I
have
done
was
I
wrote,
a
custom
function
which
is
get
job
type.
I
gave
it
an
alias
and
I
created
a
custom
object
which
you
saw
earlier
and
I
gave
it
to
type
name,
ps
utilities,
job
which
is
in
the
format
file
right
here
and
then
you'll
notice.
B
B
So
you
know
get
process
was
definitely
more
and
I
have
my.
I
have
a
data
field
I
like
to
do
stuff
by
index.
So
if
I
run
jobs,
I've
pulled
them
back.
I
can
easily
look
at
job1
dot
data
and
there's
all
my
mailbox
data,
and
I
have
my
mailbox
users
and
I've
still
retained
the
data
because
in
my
get
job
I
I
run
keep
and
receive
job
so
I've.
You
know
essentially
just
created
my
own
custom
job
with
the
data
that
I
want
to
see.
B
B
And
so
I
can
pull
back
supported
versions
and
I
can
start
to
dig
down
to
things
where
I'm
troubleshooting
connections
to
remote
hosts
to
see
what
type
of
protocols
they're
using
and
and
so
forth,
and
then,
if
I
decide
to
dump
out
lists,
you'll
notice
that
these
just
look
kind
of
just
they
look
disgusting
right.
There's
you
have
the
state
idle
times.
You
know
I
like
to
see
a
little
bit
more
detailed
information.
So
I've
you
know
changed
these
views,
you
know,
is
it
available?
B
B
This
is
where
I
start
to
dig
around
and
I
look
to
see
what
the
session
is
you.
If
you
dig
around
in
the
ps
base
application
private
data,
you
can
see
like
the
supported
versions
for
remoting
those
are
in
there
and
then
this
is
where
I've
done.
Some
of
my
you
know:
custom
hours
based
on
the
you
know,
microsoft
docs
that
are
out
there
to
tell
me
what
the
idle
timeouts
should
be,
and
that's
that's
pretty
much
how
you
know.
D
B
Yeah,
if
you,
you
could
definitely
have
some
issues
if
you
run
into
overriding
a
ps
custom
object.
But
if
you,
if
you
have
the
type
name
set,
you
you're
pretty
much
going
to
be
good
to
go.
It's
the
only
time
that
you
would
really
run
into
that
is.
If
you
have
multiple
component
teams
working
on
on
the
same
code
base,
you
really
shouldn't
run
into
that
issue.
B
I
I
appreciate
I
tried
to
keep
it
as
simple
as
I
could
yeah.
I
know
we
have
a
lot
of
experienced
guys
on
the
phone.
I
hope
I
didn't
lose.
Anyone
if
you
know
I'm
definitely
have
time
to
hang
around
if
you
guys
want
to
do
do
some
stuff
or
you
if
you
want
to
share
your
screen,
if
you're
stuck
on
something,
definitely
here
to
help
you
guys,
you
know
work
with
this,
and
and
hopefully
this
saves
you
some
time
you
know
in
in
your
day-to-day.
A
I
think
the
magic
of
you
know
the
fact,
even
if
it
did
go
beyond
some
people
and
went
over
their
heads,
that
you
know
you
can,
we
will
be
recording
this
or
this
is
recorded,
and
you
know
this
is
an
opportunity
to
watch
the
video
again
so
it'll
be
posted
up
onto
youtube
and
you
know
watch
it
as
many
times
and
format
and
then
certainly
reach
out
to,
and
I
think
dave
is
you
know
open
to.
You
know
he's
on
twitter.
B
And,
and
by
the
way
I
had
this
little
christmas
present
for
you
guys.
If
anybody
cares
to
power,
you
know
debug
this
process,
here's
the
link
on
github,
you
can
get
the
powershell
the
latest
powershell
code,
that's
out
there.
These
are
the
break
line,
break
points
and
the
line
numbers
where
you
can
set
them.
If
you
do
a
search
for
default,
display
property
set,
you
can
set
a
breakpoint
there
and
then
just
if
you
want
to
do
a
simple
repro,
just
do
like.
B
We
did
here,
create
your
own
custom
object
and
give
it
a
type
name
and
just
create
a
simple
view
and
set
that
break
point
and
build
your
environment
and
run
it,
and
you
can
step
through
the
code
and
you
can
actually
see
all
four
of
the
steps
that
we're
going
to
run
through.
You
know
there
go
through
the
format,
view
manager,
some
of
the
base
command
stuff,
the
marshalling,
but
you
can
see
how
all
of
this
all
of
this
works.
D
D
I
had
a
quick
question
about
using
minus
or
dash
is
on
on
this,
because
with
ps
type
names
can
you
use
dash
is
or
will
it
recognize
that
type
name?
I
haven't
been
able
to
do
it
successfully
myself,
but
I
was
wondering
if
there
is
a
way
to
actually
have
it
recognize
the
object
type
with
with
a
dash
in
it.
No,
like
dash,
is
like
to
check
the
object
type
it
doesn't.
D
B
D
D
D
Same
idea
created
a
custom
object
added
a
custom
object,
type
name.
It
didn't
recognize
the
this
object
type
when
I'm
using
minus
or
dash
is
like
that
and
I've
tested
this
before,
and
I
was
just
wondering
if
there's
a
better
way
of
using
this
with
ps
type
names.
So
you
know
I
had
to
instantiate
an
object,
so
I
created
a
quick
class
and
then
testing
it
and
it's
kind
of
coming
back
with
false.
D
The
reason
for
this
is
I
I
kind
of
use
my
own
custom
object
a
lot
in
my
modules
and
pass
those
objects
between
the
you
know
different
functions
in
my
my
module,
but
I
have
to
instantiate
them
with
a
class
first
and
I'm
wondering
if
I
can
do
it
quickly,
using
just
like
a
ps
type
name
and
earning
it.
That
way.
C
D
That's
a
servicenow
incident
and
I
can
either
take
in
the
incident
number
as
a
string
and
I'm
just
pulling
in
any
type
of
object,
and
then
I
do
the
validation
within
my
function
itself
on
whether
it's
a
string
object
or
whether
it's
a
object,
type
that
I
like
that
I've
created
within
my
module
itself.
But
the
only
way
I
can
see
doing
it
is.
I
have
to
have
custom
classes.
You
know,
building
an
insanity
object,
yeah.
B
A
D
A
So,
oh
you
know,
I
guess
it
says
it
can't
find
that
type,
so
it
wouldn't
even
work
so
the
one
above
it
won't
work.
So
you
you
put
square
braces.
My
custom
object
then
followed
by
quote
of
my
object
right.
So
my
object
of
that
type
and
it
doesn't
it's
trying
to
create
that
of
that
type.
What
that
type
doesn't
exist,
and
so
but
you're
creating
the
class
right.
D
So
yeah
I
created
it
down
here
and
then
test
it
again,
but
that
that's
what
I
was
wondering
is,
even
though
this
object
that
I
created
has
that
ps
type
name,
not
technically
recognizing
it
as
the
same
type
after
you
defined
it
as
a
class.
Did
you
put
test
is
with
the
square
brackets
around
my
custom
object
yeah.
I
did
I
thought
well,
so
this
still
is
the
same.
One.
D
D
D
A
B
D
B
B
B
B
That
makes
sense,
ultimately,
if
that
mar,
if
that
object's
getting
marshalled,
it's
it's
still
a
ps
custom
object.
That's
what
powershell
sees
it
as
any
time.
You
extend
it.
That's
all
it
is
now
you
can
add
a
type
name
to
it.
Type
name
can
be
whatever
you
want.
Type
name
is
not
going
to
get
used
unless
you're
going
to
use
it
for,
like
a
view
or
something
like
that,.