►
Description
Recording of the SIG from February 8th. Detailed agenda and covered topics are available via the MS Tech Community (http://aka.ms/sppnp-community).
This SIG had some SP Dev news on latest capabilities followed by live demo on using new ExecuteQueryAsync capabilities with CSOM. Preview of upcoming PowerShell Core 6.0 version of PnP PowerShell. Consuming and accessing SharePoint data using Microsoft Graph.
You can download the invite to the bi-weekly special interest group call from http://aka.ms/sppnp-core-sig-call.
A
Welcome
everybody:
this
is
to
sharepoint
patterns
and
practices
generation
to
sharepoint
development,
special
interest
group.
I'm
not
sure
if
the
sikh
statement
is
super
super
obvious,
but
it
means
a
special
interest
group
and
it
means
a
community
course,
and
these
are
bi-weekly
costs
around
sharepoint
general
development
like
provisioning,
see
some
powershell
capabilities
and
then
talking
about
general
chevron
development.
Also
in
server-side
we
do
have
another
bi-weekly
call,
which
is
at
the
sharepoint
framework.
Bi-Weekly
call
where
we
talk
about
the
client-side
development
and
those
topics
more
so
anyway.
A
On
this
course,
we
will
actually
talk
about
the
the
sharepoint
kind
of
intent,
automation
and
solution
designs.
That's
part
of
this
call,
and
rather
than
the
sharepoint
framework,
which
has
been
more
concentrated
on
that
have
another
call.
There's
two
actresses
on
this
slide
is
a
game
SSP
PMP
community,
that
is
a
link
to
the
tech
community
site
ship
on
dev
sign
where
people
are
having
a
discussions
and
answering
on
the
questions
around
sharepoint
and
then
there's
they
came
as
SPF
docs,
which
is
our
official
documentation.
A
Location
hope
cover
that
one
in
upcoming
slides
as
well,
because
I
promised
to
kick
that
slide
in
my
presentations
until
end
of
this
year,
at
least
now
it's
actually
get
on
going
on
today,
so
my
name
is
stay,
so
you
want
us
to
quickly
introduce
myself
as
well
I'm
a
Senior
Program
Manager
from
SharePoint
engineering.
Technically,
it
is
one
try,
SharePoint
engineering,
but
don't
get
fooled.
It
is
it's
not
gonna.
Actually,
it's
just
our
internal
organizations.
A
So
if
you
ever
see
ODSP,
that
means
one
crime,
SP
engineering,
but
actually
it's
just
tackles
both
of
them
and
I
work
in
the
team
with
the
who's
responsible
of
the
interent
development
experience
within
the
SharePoint,
so
we
should
SharePoint
framework
and
all
of
the
other.
Eighty
is
now
before
we
actually
code
today's
agenda.
A
What
was
program
that
is
a
crate
as
a
Cheston
from
Ralph,
but
as
they
do
a
demo
in
a
community
call.
So
if
you're
interested,
please
let
us
know,
and
in
general
please
provide
feedback.
We
in
SharePoint
engineering.
We
absolutely
love
your
feedback.
We
need
to
understand
if
there's
something
which
isn't
working
properly
or
something
is
broken.
A
Please
please
please
let
us
know,
don't
assume
that
somebody
else
has
already
reported
that,
because
if
everybody
assumes
that
nobody's
can
actually
tell
us
that
it's
broken
so,
but
let's
get
back
on
that
one
in
a
second
as
well
now
on
today's
agenda,
I
have
few
points
and
Gotham.
Let's
not
talk
about
what
happened
this
week,
so
I
have
few
items
on
the
agenda
and
I'm
gonna
have
few
slides
going
through
the
general.
Let's
say
the
SharePoint
announcements
and
few
updates.
A
What
this
one
really
really
big
update,
which
are
just
with
pushed
live
in
social
media
about
ten
minutes
before,
and
then
we
have
three
different
demos,
super
cool
demos,
so
we'll
talk
about
using
a
sync
option
with
the
new
SharePoint
Online
season
and
look
at
packets.
So
this
was
released
in
January,
23rd
or
something
like
that
and
everybody
is
gonna.
Do
a
live
demo?
What
does
it
mean
in
practice
when
you're
writing
managed
code
using
the
system?
What
does
the
execute
query
async?
What
does
it
give
you?
What
does
it
actually
mean?
A
If
you
want
to
use
that
in
future,
then
we'll
have
a
preview
of
upcoming
cross-platform,
powershell,
core
6.0
version
of
PMP,
partial,
so
obviously
sorry
Irvin,
the
father
of
the
MP
PowerShell,
is
behind
of
this
one.
Sir
Irvin
is
going
to
do
a
live
demo.
What
does
that
mean
and
talk
about
the
progress
on
that
side?
This
is
the
first
time
we're
actually
talking
about
this
one
openly,
so
we
are
looking
into
porting
or
transforming
the
existing
PMP
PowerShell,
also
to
powershell
course.
Expand.
A
Zero
reason
is
that
the
powers
of
six
powershell
core
6.0
is
actually
cross-platform
powershell.
Now
we
already
have
an
office
365
CLI,
which
is
a
one
option,
but
also
the
powershell
core
seems
to
be
growing
an
interest
across
the
community,
so
we're
looking
into
having
some
of
the
existing
PMP
powershell
functionalities
ported
over
its
an
early
preview,
or
it's
going
to
talk
about
also
the
sort
of
progress
on
that
one
and
what's
gonna,
happen
next,
but
it's
an
early
early
preview.
A
When
and
let's
see
when
it
actually
goes
live
it
does
not
replace
existing
PMP
powershell,
it's
a
complementary
framework
on
top
of
it.
Whenever
we
get
it
actually
out
and
then
a
final
thing
is
consuming
SharePoint
data
with
your
customization
using
Microsoft,
craf,
API,
so
what's
actually
supported
and
how
to
access
the
SharePoint
data
from
Kraft.
If
you
approach
SharePoint
development
from
a
shipment
API
perspective,
then
maybe
this
isn't
really
a
super
interesting
topic.
A
But
if
you
come
from
a
CRO,
Microsoft
craft
perspective,
and
you
want
to
access
SharePoint
data,
then
the
access
points
and
access
the
way
we
are
accessing
the
data
and
files
and
items
in
a
list
is
the
exact
exactly
the
same
from
an
authentication
approaches
perspective.
So
Paula
is
gonna,
follow
up.
The
LRC
is
gonna
walk
through
that
one
and
he's
gonna
try
and
slightly
late
today.
Now
some
practicalities
before
I
go
my
quick
intro
and
we
leave
the
audience
for
ruddy.
A
I
need
to
personally,
unfortunately,
drop
from
this
call
immediately
when
I'm
done
with
my
intro
section,
but
Bert
Andrade
and
Irvine
and
Paul
is
going
to
take
good
care
of
you.
So
I'll
be
back
absolutely
next
week
in
the
intercept
and
favor
call
and
biweekly
in
the
future
as
well
and
currently,
where
I'ma
charts
in
a
Arctic
cloud
challenge
hackathon
in
Oslo,
and
we
have
a
judge's
reviews
on
the
solutions
after
day.
One
on
the
topic,
so
I
need
to
actually
go
and
have
a
look.
A
What
our
attendance
is
and
attendees
have
actually
created
during
the
day.
Anyway,
that's
enough
about
me
and
let's
actually
move
on
on
the
other
topics.
So
quick
reminder:
aka,
MSSP,
dev,
Docs
and,
like
I
said:
I
will
keep
this
in
our
slides
always
so.
People
will
understand
that
locations
have
changed
and
they
will
remember
the
address
so
HMS
spdf
docks.
You
will
guys
you
or
dr.
max
after
come
/
share
points.
A
Last
death
we'll
try
to
do
the
official
SharePoint
development
documentation,
we're
looking
into
having
quite
a
significant
changes
there
and
additional
investments
on
the
documentation
so
really
really
making
going
through
the
existing
documentation,
for
example,
inside
of
the
SharePoint,
adding
guidance
and
drop
or
everything
well
update
everything
and
make
sure
that
it's
still
up
to
date,
SharePoint.
That
is
absolutely
suitable
solution.
In
the
future,
as
well,
but
well
more
on
those
changes
as
slightly
later,
but
this
is
a
great
platform
if
you
find
a
buck.
A
If
you
want
an
issue,
if
you
want
to
contribute,
if
you
want
to
add
something
on
an
existing
platform,
you
can
actually
do
that
within
a
Kitab
platform
in
a
github
by
clicking
and
edit
on
the
any
of
the
page.
And
then
you
can
submit
your
suggestion
to
us,
which
is
a
great
great,
great
way
of
contributing.
Now.
The
other
thing,
what
I'm
starting
to
keep
always
on
these
slides
and
presentations,
is
the
MSSP
dev
issues.
A
Unfortunately,
I
said
today
we
are
officially
announcing
and
slightly
science
in
site
scripting,
as
scripts
are
now
gradually
moving
to
production
mode,
so
we're
right
now
in
50%,
roughly
and
in
the
production
level
or
in
the
production
we're
actually
probably
in
70%.
We
were
50%
in
like
20
hours
ago,
so
pretty
soon
within
a
day,
max
prof.
Lee.
You
will
have
the
site
designs
and
side-street
capability
within
your
tenant,
even
though
you
would
not
be
targeted,
release
tenant
or
first
release
Donna.
So
this
is
now
going
to
be
available
in
production
used
in
SharePoint
Online.
A
Then
what
are
you
actually
contributing?
We
do
actually
have
a
kids
have
creeper
repository,
which
is
referenced
also
in
our
existing
documentation,
around
site,
designs
and
side
scripts
and
which
contains
sample
definitions
and
site
site
scripts
and
which
you
can
reuse
or
you
can,
if
you
build
your
own
side,
scripts
you're
able
to
contribute
that
for
somebody
else
to
take
advantage
as
an
example
for
their
implementation.
So
please
take
advantage
of
that
option
as
well
cool
quick
update
on
the
roadmap,
so
this
is
not
going
to
take
too
much
it's
the
classic
slide.
A
A
A
Demos
and
topics
so
like
sent
into
agenda,
so
ruddy
is
going
to
start
around
a
sink
in
the
new
season.
New
gate
package,
which
was
released
two
weeks
ago,
and
then
we
moved
to
Irving
around
the
preview
of
the
publisher,
core
version
of
pimp,
a
PowerShell
and
then
Paul
is
joining.
Probably
are
right
about
that
time
and
Paul
is
going
to
do
the
life
and
the
last
demo
around
accessing
SharePoint
data
using
the
Microsoft
graph
API
sand
its
it
is
a
good
discussion
are
also
around.
A
When
would
we
when
would
you
use
those
versus
the
native
API?
So
please
have
a
great
discussion
on
the
I
window
as
we
move
along
today
in
this
demos
ready.
Please
start
sharing,
and
we
can
say
that
everything
is
working
fine
and
at
that
point,
I
will
have
to
then
drop
away
from
the
call
unfortunate.
B
A
So
yep
I've
actually
got
it.
Let's
double
check
this
one
quickly
answering
on
tyrannous
question
in
the
update
on
site
collection,
ap,
app,
catalog,
API
collection
and
catalog
API,
activating
the
apps,
through
that
there
doesn't
update
some
issue
list
on
that,
one
by
the
way,
a
screen
sharing
works,
which
is
good
yeah.
So
we're
able
to
actually
do
your
demo
running,
but
we'll
have
will
I,
don't
have
an
exit
update
on
the
on
the
collection,
app
catalog
API,
but
we
are
resolving
some
of
the
issues
known
issues
around
there
within
days
as
well.
A
Whenever
we
get
the
latest
versions
to
SharePoint
Online
now,
for
this
moment,
ready
take
it
away
and
Bert
rowdy
and
urban
is
kind
of
their
hosts
until
the
rest
of
this
call,
I
need
to,
unfortunately
drop.
So
thank
you,
ruddy
and
Irving
and
power
for
your
demos
beforehand,
but
would
be
absolutely
in
touch.
Thanks.
B
So
January
new
sison
version
has
really
cool
new
method.
Here,
execute
query:
I
think
it's
been
added,
so
I
wanted
to
quickly
go
over
a
sinkers
theory,
so
I'm
just
going
to
skip
the
slide
about
me.
It's
not
that
exciting
and
we're
recording
as
well
so
I
think
Anna
wait.
Why
is
it
important
in
general,
because
when
we
write
code
we
typically
have
two
sets
of
blocking
operations
blocking,
meaning
that
technically
meaning
CPU
thread
is
busy
or
waiting
for
something,
so
it's
either
working
or
waiting
for
something
else
to
do
its
work.
B
It
pisses
off
our
clients
makes
our
software
irresponsive
or
unresponsive.
When
it
comes
to
server
side
software,
it
makes
it
unable
to
process
more
requests
across.
So
it
was
overloaded
when
it
comes
to
clients,
just
people
hate
it
and
because
probably
most
of
your
developers,
you
can
probably
relate
to
this
when
visual
studio
locks
up-
and
you
can't
do
anything
about
it.
That's
good
examples
of
blocking
you,
I,
so
blocking
generate,
can
be
CPU
bound
and
I/o
bound
CPU
balance
operations
you
solve
in
a
completely
different
way.
B
You
solve
through
parallelism
and
and
basically
multi-core,
processing
or
other
ways
an
I/o
bound
operations.
You
typically
sold
through
basically
parallel
execution
tracing
programming
in
the
same
thread.
I
think
a
wait
in
c-sharp
is
really
all
about
code.
Syntax,
there's,
no
threads.
It's
just
a
nice
way
to
manage
basically
task
execution
and
task
returning
before
c-sharp
live.
B
There
was
the
task
parallel
library,
it
works
great,
but
your
codes
pretty
damn
ugly,
so
basic
weight
got
released
with
Visual
Studio
2012
basically
improves
your
code
flow
and
readability
and
it
sort
of
pushes
developers
to
write
more
efficient
code,
more
easy,
which
is
very
important
when
it
comes
to
see
some.
Why
do
we
care
about
async
await?
Well?
First,
if
we
write
a
client
application,
so
maybe
a
WinForms
application
or
a
console
application
that
calls
out
SharePoint
through
see
some
it
can
be
written
in
the
async
await
pattern.
B
Instead
of
doing
crazy
tasks
processing,
you
can
write
good
code.
Essentially,
it
leads
us
to
write
good
efficient
clients
on
the
server
side.
If
we're
writing
something
like
an
asp.net,
Web,
API
or
whatever
is
processing
incoming
inquests
then
reaches
out
to
SharePoint
through
the
CSUN
library,
we
can
potentially
make
this
more
efficient,
quick
to
quick
to
work.
Basically,
when
code
hits
something
that's
async
and
that
starts
throwing
off
the
I/o
bound
operation,
your
code
flow
gets
released.
Your
web
server
can
process
the
next
request,
and
so
on.
Keep
very
very
important
here.
B
Async
await
is
not
about
multi-threading,
it's
about
asynchronous
programming.
Sorry,
my
voice
is
cutting
off
not
where
they
spoke
for
three
minutes.
So
enough
talk.
Those
are
my
my
talking
sessions,
no
questions
so
straight
into
visual
shooter.
This
is
a
sample
I
put
together.
I
have
several
different
projects
that
will
illustrate
typical
sison
code
in
the
old
days.
What
we
typically
do
is
get
a
client
context.
Object,
maybe
wrap
it
in
using
statement,
so
it
gets
the
supposed
load,
something
with
a
load,
something
in
the
context
and
then
do
an
execute
query.
B
If
I
run
this
I'm
sure
everyone
once
now.
This
is
a
blocking
operation.
It'll
take
as
much
time
as
the
load
operation
takes,
plus
the
authentication
that
will
wrap
around
and
once
this
is
done,
code
will
continue.
This
is
a
typical
blocking
operation.
How
CPU
does
not
depend
on
a
memory
or
whatever
does
not
as
much
as
CPUs.
We
have
we're
not
going
to
improve
this,
because
it's
an
I/o
bound
operation.
It
reaches
out
to
a
third
party
service,
and
that
takes
in
this
case
it'll
take
about
half
a
second
or
500
milliseconds.
B
To
return
honestly,
if
there's
any
questions,
that
will
distract.
Oh
no
questions.
So
now
we
can
write
that
with
the
with
the
proper
task
execution,
and
here
I've
got
basically
abstracted
away
everything.
That's
not
important
to
show
the
example
so
I'm
using
Python
style
indenting
just
to
confuse
you
people,
but
generally
we
have
a
method
that
does
work
and
in
this
case
it's
mark
with
async
at
the
back
following
design
patterns.
It
is
an
async
method,
so
this
method
in
general
is
marked
as
async
and
has
a
no
weight
operate.
B
Everything
after
the
await
operator
will
it
will
basically
get
executed
after
the
task
is
completed.
Anything
before
that
will
get
executed,
I've
said
before,
and
the
the
general
rule
of
the
weight
is
code
flow,
gets
returned
to
its
parent
and
all
the
way
back
to
the
top
notice.
My
console
application
is
not
a
sync,
which
means
that
we
cannot
await
this
method,
because
c-sharp
5
will
not
allow
us
to
do
that.
So
this
method
will
return
a
task
object.
The
moment
we
get
that
task
object,
it's
basically
our
ticket
to
our
operation.
B
That's
running,
basically,
in
the
message
loop
of
the
current
thread,
this
line
of
code
will
get
executed,
so
we're
going
to
get
loads
straight
away
here,
declaring
a
promise
or
a
callback,
essentially
in
Sioux
shop.
We
don't
really
call
them
promises,
it's
just
a
callback,
so
this
thing
says,
creates
a
continuation
that
executes
asynchronously
once
the
task
is
completed
so
continue
with,
will
essentially
execute
this
code
after
the
async
operation.
B
B
I
have
speed
lo
here
running
I'm
just
going
to
clean
it
up
just
so,
we
can
see
what's
going
on
in
the
background
I'm
going
to
run
this
just
to
quickly
show
it
I've
got
four
more
minutes,
which
is
not
enough,
so
I've
I'm
using
ship
on
online
authentication.
So
these
first
five
requests
are
using
that
everything's
blocking
it's
executing
it
sequentially.
You
can
see
the
difference
here
is
very
little.
Then
we
wait
800
milliseconds
for
the
task
to
complete,
so
basically
the
first
set
of
requests.
B
All
the
way
up
to
here
we're
dealing
with
SharePoint,
Online
credentials
or
authentication,
and
everything
from
here
below
is
dealing
with
my
see
some
code,
so
the
request
did
continue.
This
line
did
show,
however,
we're
using
here
just
pure
task
objects,
and
you
notice
our
console
application
was
not
really
much.
Does
they
think
if
we
change
the
language
of
the
project
to
c-sharp
seven,
we
can
actually
get
this
call
benefit.
We
can
get
an
async
task,
main
method.
As
an
entry
point
to
our
co-op
console
application.
B
Then
we
can
probably
write
a
white
code,
so
we
can
await
this.
We
don't
need
to
return
it.
What
I
need
to
do
anything
with
this
task
and
get
rid
of
this
way?
I've
been
testing
to
break
it.
This
will
do
exactly
the
same
thing.
However,
if
you
run
it,
it
will
just
execute
and
do
its
thing.
So
this
is
a
great
example
of
how
we
can
use
an
asynchronous
console
application
and
use
execute
query
async
very
funky.
B
B
I've
taken
the
typical
WinForms
example,
because
WinForms
32
is
essentially
a
main
thread,
which
is
our
UI
thread,
and
typically
we
do
operations
off
the
main
thread
through
dispatchers
or
through
maybe
the
threading
or
other
difficult
things,
a
typical
event
handler
or
button
click
event
handler.
If
it's
not
marked
as
a
sink
in
the
language.
The
only
thing
that
we
can
do
here
is
we
can
execute
the
query.
This
will
be
a
typical
blocking
application.
I
have
a
timer
that
shows
that
the
UI
is
working
or
not.
We
can
have
an
async
button
click.
B
This
will.
Let
us
essentially
do
the
good
code.
We
can
call
execute
query
async.
We
can
a
way
to
get
back
the
tasks,
doing
nothing
with
the
tasks
I'm,
putting
this
in
a
loop
to
essentially
put
some
load
on
the
WinForms
application,
and
here
I'm
doing
a
quick
hack,
and
this
is
the
reason
why
I'm
doing
this
is
because
I
missed
an
sharing,
a
new
client
context,
I'm
setting,
authentication
and
then
I'm,
not
loading.
Anything,
but
I
made
this
a
cute
little
query.
B
The
reason
why
I'm
doing
this
so
I
get
all
my
authentication
heart
shaking
out
of
the
way
and
then
reusing
my
context
in
order
to
do
the
load
and
operation
stub
moment
loading
this
so
I'm
going
to
start
this
just
steered
in
action
this
time,
I,
don't
know
if
screens
updating
that
quick.
This
time
it
has
a
sink
web.
So
that's
my
sink
button.
You
can
see
the
time
is
stopping
here
for
a
probe
about
500
milliseconds
to
a
second.
We
can
do
that
as
much
as
we
want
the
moment.
B
I
execute
the
async
task
and
I'm
going
to
load
fiddler
here
on
the
side,
so
we
can
actually
look
at
it
in
action.
We
can
pull
this
off
so
we're
doing
authentication
our
timer
is
still
counting
and
then
we're
doing
all
of
the
process
queries
and
basically
our
UI
is
still
running
and
being
able
to
update
itself
I'm
using
a
WinForms
timer
which
actually
creates
a
background.
Third,
that's
relevant
to
the
point.
The
point
is
that
we
can.
B
We
can
fire
this
up
multiple
times
and
you
will
see
if
it's
quick
enough-
a
short
delay
here
during
with
indication,
but
as
long
as
processed
query
is
running,
our
thread
is
running,
so
it's
pretty
cool,
which
leads
us
to
one
good
practice
in
this
case
and
that
good
practice
is
just
a
reminder
to
reuse.
Your
client
contacts
never
instantiate
an
inner
loop
because
you
have
the
overhead
of
authentication
handshaking.
This
particular
example
is
using
SharePoint
Online
credentials.
B
I
will
test
to
see
if
authentication
handshaking
is
blocking
with
tokens
and
apperently
contexts,
and
things
like
that
at
the
moment,
I
get
time,
but
that
is
my
demo
I'm
exactly
on
time
and
I
just
want
to
see
Leo's
comment.
So,
yes,
you
can
do
get
a
way
to
get
result.
That
is
the
same
as
calling
a
wait.
So
if
we
go
back
to
something
like
this
particular
code,
of
course,
here
I
can
say
tasks.
Object
would
get
a
waiter.
So
here
we
get
the
a
waiter
and
then
we
can
say
get
results.
B
This
will
return
a
void
because
it
understands
that
this
particular
method
does
nothing
which
is
essentially
very
close
to
this
any
other
questions
that
I
could
help
answer
this
code
is
it's
currently
in
our
one
bit.
Software
repository,
but
I'll
put
it
as
part
of
the
samples
in
PNP
just
so.
This
stays
there.
Having
looked
at
throttling
with
semaphore
slimmin
I
have
essentially,
this
will
throttled.
So
the
fact
that
we
are
improving
the
client
or
the
server
only
technically
makes
us
do
more
requests
and
we
will
be
throttled.
B
B
C
Someone
can
confirm
yep
screams,
good
yep,
good
okay,
so
what
I
will
show
today
is
a
few
slides
about
PNP
PowerShell
core,
which
is
a
working
title.
There's
not
necessarily
be
the
end
name
of
what
we're
doing,
but
for
now
we
call
it
PNP
PowerShell
quarters
to
differentiate
it
from
PNP,
powershell
and
I'll
talk
you
through
what
what
the
challenges
are
and
how
our
approach
will
be
and
why
we're
doing
this.
C
C
You
actually
end
up
with
development
teams
that
are
using
different
platforms,
so
people
running
Windows
machines
windows,
these
people
running
Mac
machines.
However,
there's
a
lot
of
investment
out
there
already
based
upon
the
PNP
PowerShell.
A
lot
of
scripts
have
been
created.
I
mean
we're
running
over
a
billion
requests
per
month,
just
from
PNP
PowerShell
towards
over
365.
So
it's
a
pretty
pretty
popular
tool
to
use,
but
if
you're
on
a
Mac
on
the
Linux
you're
sort
of
most
part
of
that
that's
easy
to
crypting
world
anymore,
it's
it's
over
250
commandlets
to
use
now.
C
Another
thing
is
just
at
the
for
the
future
of
dotnet
is
actually
pointing
towards
top
net
court
on
that
standard.
This
is
where
we
going
easy.
That
market
invests
a
lot
in
those
platforms
and,
of
course,
that's
the
dotnet
framework.
The
main
baked
on
that
framework
is
still
growing
and
there's
also
still
maintained.
A
new
functionality
comes
out,
but
they
put
a
lot
of
effort
into
that
core
and
don't
not
standar.
Then
that
makes
sense
because
it's
multi-platform
so
powershell
5
is
the
current
version
that
runs
in
Windows.
C
But
there
was
still
some
bottlenecks
and
it
will
be
regards
to
authentication
so
is
should
be
focus
on
that,
or
should
we
go
for
another
way
with
when
it
comes
to
power
shot
because
pimpy
power
shot
behind
the
scenes?
Use
the
season
so
I've
been
looking
into
that
and
I
came
up
with.
This
idea
is
to
port
PNP
PowerShell
to.net
standard
notes
of
that
core
battlenet
standard,
because
this
will
work
both
between
this
PowerShell
and
PowerShell
course.
So
this
will
work
both
with
Windows
Windows,
PowerShell,
5
and
PowerShell.
C
6.0,
so
it
doesn't
matter
which
variant
of
partial
you're
running
it
will
work,
because
Windows
PowerShell
support,
stop
net
standards
and
a
PNP
PowerShell
6.0
supports
not
not
standard.
So
how
do
we
approach
this?
So,
first
of
all
very
clear:
we
do
not
have
the
intention
to
port
season
to
dope
that
core,
absolutely
not
in
our
roadmap.
That
would
be
crazy.
It's
gonna
be
so
much
work.
If
someone
would
do
that,
I
hope,
it'll
be
Microsoft,
that's
Louie
from
PNP
will
not
go
there.
We
will
pour
PNP
power.
C
Schultz
use
rest,
the
rest,
api
s--
and
we
are
familiar
with
limitations
of
rest.
There
are
some
things
like
the
combination
of
fields
and
content
types.
There
are
some
side
columns
and
constant
times
they
have
some
challenges.
There
is
currently
no
rest
api
for
taxonomy
and
ten
of
the
administration
calls
have
Arnold
fully
exposed
at
all.
Actually
in
the
rest
api
now
that
there
are
ways
around
that
one
of
the
the
I
don't
want
necessary,
call
it
the
dirty
hack
but
and
hack
around.
C
It
is
by
calling
the
SV
client
SVC
directly
just
the
way
as
season.
Does
it
also
to
realize
that
if
we
move
to
a
rest
back
end,
so
we
call
rest
api
from
powershell?
Some
low-level
tasks
will
not
work
anymore.
Some
people
have
been
doing.
That's
where
you
receive
the
context.
You
receive
a
web,
your
updated
title
and
you
do
update
and
you
do
an
execute
query.
C
You're
effectively
riding
season
code
that
will
not
work
anymore
because
we
have
rest
behind
the
scenes
and
it
works
fundamentally
different
from
season,
but
we
might
have
an
answer
there,
which
I'll
show
you
right
now.
So
let
me
show
you
where
we
are
today
and
let
me
pop
up
pimpy
powershell.
So
this
is
powershell
6.0.
As
I
said,
this
is
available
for
Windows,
Mac
and
Linux
users,
and
it
is
simply
install
you
download
the
MSI,
your
bonnets,
if
you're
on
Windows
and
you're
there,
and
they
can
live
side
by
side.
C
So
it's
not
a
replacement
for
Windows
or
Windows
PowerShell.
You
can
have
windows,
powershell
and
powershell
core
installed
side
by
side
and
if
you
install
the
commandments
and
there
the
package
is
not
available
yet.
So
you
cannot
download
this
from
the
powershell
gallery.
But
if
you
install
the
command,
that's
your
approach
will
be
similar
to
the
old
fashioned
PP
Power
Cells.
You
do
connect
PP
online
and
so
the
URL
points
comm.
C
The
connection
to
this
site.
If
I
do
get
PNP
lists
idea
is
the
same.
So
we
output
the
same
type
of
data,
I,
guess
a
peek
at
spear,
PNP
content
type.
So
the
same
time
of
data.
You
can
see
all
the
properties
that
come
with
that
with
those
objects.
You
can't
read
them,
so
it's
not
only
that
what
you
see
on
the
screen
is
what
you
get.
We
get
you
actually
more.
So
if
I
go
for
insist,
take
a
list
gets
P
and
P
list
and
I
say
test.
C
You
see
the
basically,
the
majority
of
the
properties
are
being
exposed
to
the
list
to
the
object
here
and
you
can
use
that
and
and
and
reach
values
out
of
it
and
I
said
read
values.
So
we
have
an
approach.
I
am
working
on
a
proposed
which
also
might
help
you
in
updating
things
but
I'm
not
on
the
present
Syria.
If
you
want
to
go,
that's
death
Road,
because
it
is
a
bit
of
work
also
from
a
coding
perspective,
it's
actually
a
maintenance
issue,
but
I'll
show
you
what
we
mean.
C
So,
for
instance,
if
we
have
this
list
and
I
have
the
title
here
is
currently
test,
it
can
actually
say
title
equals
P
and
P
rocks.
How
do
I
update
this?
Well,
it's
just
a
matter
of
saying
update.
You
do
not
have
to
execute
the
query.
The
list
title
has
been
updated
now
already,
so,
if
I
say
get
P
and
P
list,
you
will
see
there
is
now
a
PP
rocks
list
here.
So
that
is
one
of
the
approach.
C
So
it's
not
a
given
that
this
approach
that
I
just
showed
you
here,
where
you
actually
update
a
property,
will
be
the
end
product.
One
of
the
reasons
there.
The
complexity
is
not
necessarily
the
first
level.
Properties
is
actually
second
level
of
third
level
properties.
Where
you
can
go
into
the
permissions
of
a
list
and
in
there
you
can
find
groups,
maybe,
and
in
the
group
she
can
go,
so
you
can
very
deep
and
then
how
do
we
generate
the
actually
update
rest
query
behind
the
scenes
for
this?
C
So
we're
thinking
about
this.
So
where
are
we
today?
Well,
if
we
say
get
commands
module,
share
points,
P
and
P
PowerShell,
core
I
put
this
in
a
variable.
That's
account.
We
currently
have
50
is
hard
to
see
if
it's
actually
just
coming
off
the
screen
50
to
come
at
this.
We
have
currently
so
actually
quite
a
list
already
that
we
imported
just
to
show
you
an
overview
of
what
we
F
I
wish
for.
C
So
the
disease
around
apps
custom
actions,
master
pages
homepage
event,
receivers
lists
they're
there
already,
so
this
set
of
commanders
are
there.
How
do
we
approach
it?
Well,
one
by
one.
We
effectively
do
not
have
to
rewrite
much
of
the
command
list.
We
just
basically
copy
the
commands
over
to
the
new
project,
and
then
we
rewrite
every
cool
to
see
some
through
a
rest
call,
and
we
have
helper
classes
to
make
our
life
a
bit
easier.
C
So
we
do
not
have
to
rewrite
all
the
connection
code
there,
but
basically,
if
we
look
in
a
command,
that's
here
for
this
command,
we
see
here
where
we
actually
that
can
zoom
in
a
bit.
We
have
the
the
rest
request
that
we
execute
from
the
lists
endpoints,
and
then
we
expand
a
couple
of
variables
here
and
then
we
return
a
collection
of
lists.
C
So
this
is
the
approach
we
have
currently,
as
I
said,
fifty
two
Commandments,
and
because
this
is
written
in
dotnet
standards.
The
cool
thing
here
is
that
if
I
go
to
the
windows,
powershell
I
actually
have.
If
I
look
here,
gets
module,
I
have
the
same
library
loaded
and
the
same
commandlets
work
here
too,
so
it
doesn't
really
matter
which
platform
you're
on.
If
you
like
windows,
if
you
do
know
what
install
powershell
six-
that's
not
an
issue,
you
can
still
run
it
now.
C
What
is
well
the
limitations
here,
because
we
do
realize
that
the
biggest
use
of
PP
powershell
is
when
it
comes
to
the
PP
provisioning
engine
and
the
pimpy
provisioning
engine
is
by
far
the
most
complex
parts
of
the
PHP
code,
and
it's
been
written
based
on
seasoned
porting
that
come
to
rest
will
have
its
challenges.
It
is
possible,
we
believe
it's
possible,
but
it
will
be
a
lot
of
work.
C
It
will
not
happen
anytime
soon,
so
it
could
very
well
be
that
the
core
powershell,
whatever
name
it
will
have
from
PP,
will
initially
not
support
the
PP
provisioning
engine,
but
that
is
to
be
rated
and
then
we'll
see
when
this
comes
out
and
as
I
said,
this
is
a
preview.
This
is
not
publicly
available.
Yet
you
cannot
download
this.
C
It
might
be
that
in
the
very
near
future
we
just
really
create
a
public
repo
where
you
can
already
contributes
I,
make
this
happen
and
and
and
builds
out,
the
list
of
command
lists
and
port
the
commandlets
right
now,
as
I
said
it's
a
one
by
one,
so
we
just
take
an
old
commander.
It
copied
over
rewrite
some
codes
and
it's
part
of
it
so
I
haven't
seen
if
there
were
any
questions.
So
let
me
see
here,
there's.
B
C
Will
my
mixed
scripts
from
Marshall
is
asking
here
mix
scripts
with
Caesar
my
peepees
to
the
work?
No,
no,
because
season
is
not
running
until
my
score.
If
you're
running
Windows
PowerShell,
you
might
be
able
to
refer
to
the
season
classes
manually,
but
there
is
no
season
support.
So
I'm
not
saying
this
will
replace
PP
powers,
so
I
do
believe
that
the
pimp
a
PowerShell
based
on
sees
them,
has
a
place
and
see
some
is
not
not
going
anywhere.
So
it
will
it.
It
will
still
be
around
PP
PowerShell.
C
C
Could
you
make
mixed
it
with
classic
PNP
PowerShell?
Well,
the
idea
is
question
from
Kevin.
The
idea
is
that
will
be
full
backwards
compatible,
so
your
old
scripts
will
still
run
as
long
as
you
do
not
venture
out
into
direct
season
calls
from
objects.
So
if
you
stick
with
the
commandlets
only
then
it
should
just
work.
There
are
some
small
changes
where
we're
thinking
of.
C
If
we
should
support
like
classic
artifacts
like,
for
instance,
event
receivers
and
maybe
only
two
remote
event,
receivers
and
web
hooks
those
kind
of
things,
but
that
that's
a
question,
but
we
will
we
try
to
be
as
complete
backwards-compatible
as
possible,
be
available
pretty
soon
I
think
pretty
soon
I
did
not
plan
a
release
date.
Yet
of
this
beta,
even
I
is
not
around,
but
she's
not
going
anywhere.
C
If
you
work
for
classic
workflows
or
did
not
the
classic,
but
the
current
workflow
engine,
for
instance,
is
also
calling
season
behind
the
scenes
to
that's
how
we're
not
talking
about
much,
let's
flow
but
just
and
the
chamfered
workflows
they're
using
season
2
to
call
back
into
the
server.
So
season
is
not
going
anywhere.
C
Question
from
Andrew
some
setting
I
don't
know
if
we
should
there
are
sort
of
for
now
at
least
complementary,
especially
for
those
scripts
where
you
still
want
to
call
back
into
in
to
see
some
in
low-level
season,
but,
as
I
said
as
I
demoed
we're
thinking
of
providing
you
with
a
similar
way
of
doing
things.
But
it's
it
didn't
crystallize,
yes,
but
not
sure.
Yet,
because
I
said,
the
downside
of
that
approach
is
that
we
would
have
to
maintain
the
objects
representing
lists.
C
For
instance,
we
have
to
like
create
objects
based
on
a
list
and
then
I
expose
the
methods
and
properties
to
those.
So
that
is,
there's
gonna
be
a
bit
of
a
maintenance
he'll
we're
getting
into
because
effectively
we're
we're
we're
maintaining
sort
of
a
lightweight
version
of
C's
them
them,
and
that
would
mean
it
every
time
a
new
version
comes
out
and
your
properties
are
being
released.
C
C
Marcel
Walter
asked
if
there's
a
plaintiff,
extending
arrest
by
Microsoft.
Yes
they're
constantly
working
on
this,
you
might
have
noticed,
for
instance,
the
side
design
api's.
They
almost
come
out
first
in
arrests
and
then
season.
So
the
rest
api
has
a
strong,
strong
focused
for
Microsoft.
So
basically
everything
comes
out
in
arrests
first
and
then
it
sees
them
and
some
of
the
French
that
he
doesn't
even
come
out
in
see
them.
Take
the
ALM
API
to
activate
and
install
and
deploy
in
publish
apps.
There
is
no
C
some
equivalent.
C
C
That
was
it
for
now
seek
review
in
the
coming
weeks.
We
most
likely
will
push
this
one
out
as
and
as
an
repo,
so
you
can
have
a
look
at
it
and
play
with
it
if
you're
wondering,
by
the
way,
how
we
do
the
authentication,
because
this
is
not
the
classic
authentication
I
didn't
demo-
that
I
need
to
explain
other
bits.
We
use
the
same
way
of
authentication
as
the
office
365.
She
lined
us.
C
So
basically,
when
you
do
a
connection
you
will
be,
we
will
launch
a
browser
and
you
will
have
to
enter
a
code
that
is
shown
in
PowerShell
of
that
moment
on.
We
have
a
connection,
we
have
an
access
token
and
refresh
token.
That's
how
can
we
store
in
your
credential
manager,
on
your
local
machine
or
on
the
Mac
in
the
hearing
or
I'm,
not
actually
100
percent
sure
what
does
cause
on
a
Mac?
C
And
yes,
it's
a
device
login
and
from
that
moment
on,
we
have
an
access
token,
a
refresh
token
and
the
moment
the
access
token
expires.
We
take
me
get
any
one
bit
of
refresh
token:
almost
you
have
a
session,
so
that
is
the
that's
it
as
I
had
52
characters.
Currently,
when
we
released
this,
which
might
be
in
a
week
not
promising
anything,
we
probably
are
going
towards
to
100
is
already
so
it's
it's.
It
goes
pretty
smooth
to
move
the
commandlets
over.
D
D
And
now
we
will
lightly
change
the
topic.
We
will
talk
about
consuming
still
about
rice
to
the
eyes,
but
about
consuming
a
sharepoint
using
the
micrograph,
because
since
a
few
months
ago
we
have
the
capability
to
use
some
of
the
functionalities
of
sharepoint
online
through
the
micrograph.
I
guess
now
you
see
my
screen,
but
just
let
me
yeah:
okay,
cool,
okay
power.
Okay,
thank
you
ready.
D
So
in
this
short
demo
I
will
show
you:
what
is
the
procedure
to
be
able
to
consume
such
a
pie?
So,
first
of
all,
and
as
like
as
whenever
you
need
to
consume
the
micro
graph,
you
need
to
register
an
application
in
a
direct
directory,
and
the
application
is
ready
from
a
settings.
Perspective
will
need
to
have
a
set
of
permissions
for
the
max
of
graph
VI
and
specifically
from
a
sharepoint
perspective.
There
are
some
new
permissions
which
are
related
to
consuming
the
content
or
managing
the
sides.
D
You
have
a
sharepoint
online,
so
there
are
permissions
like
sides,
dot
read
the
all
or
side
dot,
read,
write
all
size,
dot
manage
inside
dot,
full
control
and
those
permissions
are
available
in
the
application
permissions
group
or
in
the
delegate.
Permissions
group,
for
example,
in
these
up,
which
is
the
one
I
will
use
in
just
coming
demo.
I,
have
to
make
it
easier.
The
full
control
permissions
aside
that
full
control
dot
all
for
a
delegated
access
token.
D
So,
on
behalf
of
my
current
user
and
not
with
an
application
only
token
and
through
the
UI
of
is
ready.
Of
course,
you
can
set
your
permission.
For
example,
here
you
can
see
the
create
edit
delete
items
and
lists
in
all
set
collection
which
corresponds
to
the
site,
dot,
manage
that
all
permission
and
so
on
so
forth.
So
you
create
an
application.
You
register
the
application
and
you
ready
you
configure
the
API
permissions
for
the
max
of
graph,
depending
on
what
you
want
to
do
and
through
the
documentation
you
can
see
what
you
will
need.
D
So,
for
example,
if
you
want
to
get
a
single
site
using
the
max
of
graph,
you
can
see
that
those
are
the
required
permissions
running
as
the
up
with
the
application
only
token
or
with
a
delegated
token,
for
example,
and
so
on
so
forth,
for
all
of
the
API
is
more
over
here.
I
have
an
asp.net
MVC
application,
which
is
the
path
which
is
registered
in
is
ready
and
which
I'm
working
on.
So
it's
not
yet
100%
completed.
D
It
will
become
a
new
demo
in
the
PMP
repo
as
soon
as
it
will
be
fully
completed
right
now
we
have
some
of
the
capabilities,
which
will
be
the
ones.
I
will
show
you
now
and
this
application.
Let
me
let
me
execute
it.
It
is
already
should
be
already
running
in
my
browser.
It's
a
very
classic
MVC
asp.net
application,
in
which
I
have
the
capability
to
get.
For
example,
a
site
object
using
the
rest
and
point
of
graph
and
the
site
object
can
be
retrieved.
D
In
order
to
do
that,
let
me
show
you
the
code
under
the
cover
we
need,
first
of
all,
to
use
in
asp.net,
ad
Al
and
so
Active
Directory
authentication
library,
as
we
usually
do.
Whenever
we
want
to
get
an
access,
token
form
is
ready
and
to
consume
the
maxigrove
or
any
other
api
registered
in
is
ready
whenever
we
are
in
dotnet.
D
So
I
can
still
provide
the
name
of
my
tenant
of
SharePoint
comma
and
followed
by
the
relative
URL
of
the
site
that
I
want
to
retrieve
they're.
Both
valid
syntax
is
to
retrieve
a
site
object.
You
will
get
back
an
object
which
will
have
which
will
add
some
information
like,
for
example,
equation,
day
time
and
the
last
modified
date,
time
of
the
site,
the
description,
the
display
name
and
the
ID
we
were
talking
about
few
seconds
ago,
as
well
as
the
name
and
the
URL
of
the
site
using
the
ID
of
a
site.
D
You
simply
need
to
get
an
access
token,
as
always,
and
as
usual,
and
then
you
can
get
the
sides
and
point
you
provide
the
idea
of
the
site
be
careful
here.
You
can
only
provide
the
ID
made
of
the
tenant
name,
the
idea
of
the
site
and
the
idea
of
the
web,
the
other
identifier
doesn't
work,
so
the
relative
URL
doesn't
work
right.
D
When
you
get
back
the
list
or
the
collection
of
lists,
you
can
also
use
that
end
point
to
create
a
new
list,
for
example,
and
here
I
have
an
arrow
function
which
will
be
able
to
create
through
a
post
request.
Http
POST
request,
targeting
the
collection
of
lists
in
my
target
site
will
be
able
to
create
a
new
list
to
create
a
new
list.
D
You
need
at
least
to
provide
the
display
name
of
the
list
and
the
template
that
will
be
used
to
create
the
list,
but
you
can
also
provide
custom
columns
so
that
you
will
have
a
custom
information
architecture
for
your
list.
Right
now,
for
the
sake
of
simplicity,
I
will
simply
create
a
new
list
which
will
have
a
name
which
will
be
based
on
the
current
date
and
time.
D
And
if
you
see
here,
I
have
a
list
most
likely
this
one,
because
it's
for
553
in
my
time
zone-
and
this
is
the
lista
I-
have
just
created
and
as
I
told
you
in
order
to
create
the
list
that
you
just
need
to
make
a
post
request,
you
will
get
back.
It
is
an
object
which
will
represent
the
just
created
list
so
that
you
will
be
able
to
retrieve
the
ID
of
the
list
and
play
and
being
able
to
playing
with
the
items
of
the
list
to
do
that.
D
Changing
the
context
and
move
it
to
fiddler.
Just
to
show
you
the
low
level
rest
requests
you
can
play
like
I'm
doing
here,
so
you
can
refer
to
the
micrograph
version
1.0,
because
those
functionalities
are
already
available
in
the
1.0
endpoint
of
the
graph.
You
get
the
side
as
I
told
you,
you
get
the
ID
of
the
target
side,
which
is
quite
badly,
but
it
works,
and
you
access
the
list
of
lists
in
your
side.
If
you
want
to
access
a
specific
collection
of
items
in
a
list
you
can
just.
D
D
It
will
be
just
a
collection
of
items,
but
you
can
also
make
a
post
request
targeting
the
collection
of
items
to
create
a
new
item
and
you
will
need
to
provide
a
JSON
object
with
the
collection
of
fields
that
you
want
to
fill
that
you
want
to
fit
in
the
item
that
will
be
created.
Of
course,
you
can
also
update
with
a
patch
request
a
target
item.
If
that
will
be
the
case,
you
will
have
to
select
the
specific
item
ID
in
the
collection
of
items
in
your
list.
I
provide
the
cells.
D
Please
remember
to
mute
your
Microsoft
base
and
you
will
have
to
provide
the
field
that
you
want
to
update
as
well
as
you
can
delete
an
item
still
providing
the
item.
Id
the
integer
item,
ID
of
the
so
the
index
of
the
item
in
the
collection
of
items
in
your
target
lists,
so
pretty
smooth,
pretty
easy
to
do,
and
right
now
through
the
micrograph,
that's
what
you
can
do
using
sharepoint
online.
So
you
can
access
aside.
D
You
can
get
the
list
of
lists
and
libraries
inside
or
of
the
subsides
in
a
sighting
which
you
are
you
can
play
with
the
lists
and
you
can
create
them
and
you
can
play
with
the
items.
That's
it
so
far
the
demo
I
showed
you
will
be
available
in
PMP
in
the
upcoming
days
as
soon
as
it
will
be
100%
completed
and
will
be,
they
are
just
to
take
inspiration
or
to
learn
about
how
to
use
those
new
api's,
and
that's
it
on
my
side,
the
two
so
we
have,
maybe
some
questions
can
be.
D
One
point
me
to
graph
docs
access
token
docs.
Well,
actually,
if
you
want
to
learn
about
the
micrograph,
you
can
just
go
to
graph
my
croissant
IO,
and
this
will
bring
you
to
the
entry
pointer
from
a
Dell
perspective
of
the
micrograph
and
under
documentation.
You
will
find
a
bunch
of
information,
including
how
to
get
an
access
token
and
how
to
do
all
the
things
that
you
can
do
playing
around
the
micrograph.
So
that's
the
entry
point
grass
dot
Microsoft
dot.
D
Are
you
I
think
we
have
two
three
minutes
more
for
Q&A
or
random
topics
and
let's
sit
on
my
side
about
consuming
sharepoint
online
through
the
micrograph.
So
if
there
are
any
questions,
any
any
feedback
or
any
other
random
topic,
feel
free.
To
ask
an
example
code
for
that.
Yes,
we
already
have
in
the
PMP
repo
some
sample
applications
to
use
the
Microsoft
graph
to
show
how
to
use
the
micrograph
this
sample-
I,
just
showed
you
will
become
available
in
the
upcoming
days-
is
not
yet
there,
but
it
will
come.
D
Anything
else
there
is
one
question
related
to
PMP
season.
So
can
you
process
PMP
season
core
pr's
faster?
Well,
we
are
already
trying
to
do
our
best.
Keep
in
mind
that
we
we
process
most
of
the
content
in
our
spare
time,
and
you
all
know
that
the
spare
time
is
always
fair
so,
but
we
are
always
trying
to
do
our
best
and
we
will
try
to
speed
up
as
much
as
we
can,
but
no
guarantee
no
promises.
Sorry
about
that.
D
Anything
hang
pass.
We
are
approaching
the
end
of
the
hour,
so
so
in
expansion
of
micro
teams
for
graphs.
Well,
if
you
wanna
know
about
what
is
coming
next,
you
can
just
have
a
look
to
the
beta
reference
still
going
through
going
to
graph
dot,
max
dot,
IO
and
then
documentation
and
there
you
will
find
a
full
set
of
beta
functionalities.
So,
as
you
can
see
there,
there
are
some
useful
endpoints
and
actions
related
to
the
max
of
team's
service
and
keep
an
eye
on
this
one,
and
here
you
will
see
what
is
upcoming.
D
Of
course,
if
you
use
the
beta
n
point,
there
is
no
guarantee
that
it
will
work
100%,
but
it's
the
beta.
So
you
should
be
aware
of
that.
On
the
other
side,
whenever
any
action
or
any
functionality
will
be
moved
from
the
beta
endpoint
to
the
V,
1.0
m
point
feel
free
to
use
it
in
production
and
in
your
environment.
D
D
Let
me
say,
because
something
is
changing,
and
in
the
upcoming
days
there
will
be
some
interesting
news
and
if
you
take
a
look
I'm
talking
with
Michael
and
if
you
have
a
look
to
the
sinkhole,
we
made
that
think
couple
of
weeks
ago,
you
will
find
a
recording
of
a
demo
about
how
to
use
those
new
capabilities
which
again
will
become
available
in
the
upcoming
days.
So
stay
tuned
and
there
will
be
a
new
client
object
and
new
technique
to
get
an
access
token
from
is
ready
through
way
the
LGS
natively
included.
D
Think
we
hit
the
hour,
so
we
should
stop
here
if
there
isn't
anything
else,
burning
I'm,
also
asking
where
win
rowdy
and
the
other
guys
in
the
call.
If
there
is
anything
else
burning
or
we
can
just
say,
thank
you
and
close
here,
I
think
we
can
close.
So
thank
you
guys,
firewood
close,
thank
you
guys
and
take
care
and
see
you
in
the
next
week
or
in
the
monthly
calls
all
right
goodbye.