►
From YouTube: PnP SIG JavaScript Weekly - 11th August 2016
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hello
and
welcome
to
this
week's
JavaScript
special
interest
group
weekly
meeting
is
August
11
2016
I
remain
Patrick
Rodgers
senior
program
manager
with
office,
365
and
I.
Think
we've
got
a
good
meeting
for
you
this
week
to
talk
about
some
neat
stuff
and
some
upcoming
announcements
as
well,
but,
as
always
I
want
to
start
off
with
a
discussion
of
kind
of
who
we
are
and
what
we
do.
We
are
the
sharepoint
patterns
and
practices,
JavaScript
special
interest
group,
and
we
exist
inside
the
larger
sharepoint
patterns
and
practices
program.
A
We
do
carry
this
idea
of
worldwide
one
team,
so
wherever
you
are
in
the
world
and
whoever
you
are
you're,
absolutely
welcome
to
join
in
and
participate,
whether
that's
through
the
social
channels
or
whether
that's
through
contributing
code
or
reporting
issues
or
any
of
those
things.
So
everyone
is
welcome.
We're
absolutely
excited
to
get
everybody
involved
that
would
like
to
be
involved.
To
that
end.
We've
got
a
couple
of
ideas.
The
first
is
this
idea
of
an
elastic
team.
So
folks,
it's
folks
will
have
a
lot
of
time
some
weeks
in
less
time.
A
A
If
you
you
know
one
week
get
really
busy
and
another
week
can
come
back,
we'd
love
to
have
you
when
you
have
the
time
we
also
remain
very
community
driven,
so
we're
always
looking
to
make
improvements
and
grow
and
provide
or
get
great
feedback
from
the
community
and
also
provide
great
services
out
to
the
community,
whether
that's
use
of
our
code,
library
or
use
of
our
guidance
or
samples,
or
things
like
that.
So
always
looking
for
that
feedback,
for
you
know
what
we
can
be
doing
better
and
incorporating
that
into
the
work
we
do.
A
A
That's
an
ongoing
journey.
Of
course,
we're
always
looking
for
help
making
those
improvements
in
the
documentation.
Testing
we'll
talk
about
that.
A
little
bit
later,
two
links
at
the
bottom
one.
The
first
two
are
Yammer
group.
Yes,
we
are
still
in
Yammer,
so
that
time
being
is
the
place
to
go
for
discussions.
If
you
have
general
questions,
things
like
that
and
the
bottom
link
is
our
github
repository.
A
So
if
you
want
to
contribute
to
the
code
report,
an
issue
or
just
kind
of
want
to
see,
you
know
have
a
look
at
the
code,
something
like
that
go
ahead
and
check
out
the
github
repository
there.
So
thank
you
again
to
all
our
contributors.
We
haven't
had
any
new
contributions
in
the
last
week.
Nothing
even
from
myself,
like
I,
said
so,
but
thanks
to
these
folks
who
have
all
contributed
in
the
past,
jorn
H
I'd
love
to
get
a
full
name
for
you.
A
If
you
ever
listen
to
this
I've
reached
out
to
a
couple
ways,
so
we're
about
to
get
a
full
name
if
you
want,
and
as
for
everybody
else,
has
contributed
if
you
attended
the
monthly
call
which
was
earlier
this
week
for
the
patterns
and
practices
for
the
patterns
and
practices
program,
you
did
see
us
sort
of
surfacing
up
those
company
logos
and
getting
that
recognition
out
for
the
companies
that
allow
their
folks
time
to
participate
here
in
the
program.
So
and
I
extend
again
that
invitation
to
all
of
you.
A
If
your
company
is
providing
you
time
to
contribute
and
would
like
some
additional
recognition.
Please
let
us
know
we're
very
happy
to
get
a
logo
from
them
and
recognize
the
time
they
give
you
to
participate
here
in
our
program.
So
it's
it's
a
sort
of
the
least
we
can
do
is
say,
thank
you
as
much
as
we
can
and
we
do
want
to
get
everyone
the
recognition
they
want
and
very
much
deserve
in
that
regard.
A
Lastly,
on
this
again,
I
try
and
set
every
week
if
you
see
your
name
in
the
author's
file
and
you'd
like
updated,
perhaps
I've
spelled
it
wrong,
for
which
I'm
very
very
sorry
but
you'd,
like
perhaps
an
email
address
or
some
other
piece
of
information
in
that
authors
file,
also
very
happy
to
make
those
updates
again
trying
to
get
everybody
as
much
recognition
as
we
can.
So.
Thank
you,
everybody
that
has
contributed
and
we'll
talk
about
opportunities
if
you'd
like
to
contribute
in
the
future.
A
So
our
agenda
for
this
week
we're
going
to
talk
about
topics
tremaine
regular,
do
our
weekly
stand
up
opportunities
for
contribution,
and
then
our
team
discussion
this
week
we'll
talk
more
about
sandbox
solutions
and
talk
about
some
of
the
I'll
call
them
opportunities
around
sandbox
solutions
for
folks
on
this
call
and
who
might
have
you
know
their
own
companies
or
do
that
kind
of
consulting
work.
There's
a
upcoming
SharePoint
event
on
8
17,
we'll
talk
about
that
a
little
bit
and
the
node
console
app.
A
If
you
attended
the
monthly
call
and
stay
to
the
bitter
end,
you
saw
a
quick
demo
of
a
node
console,
app
kind
of
concept
and
I
want
to
dive
into
that.
A
little
more
deeply
on
this
call,
because
it's
something
I've
been
using
myself
a
lot
lately
and
playing
with
it's
kind
of
a
neat
idea.
So
it's
sort
of
a
little
bit
easier.
I
think
than
spinning
up
a
visual
studio,
console
app
and
then
on
all
that.
So
we'll
take
a
look
at
that,
so
in
Yammer
and
get
er
two
things
this
week.
A
The
first
one
there's
been
some
general
comments
around
well
I.
Just
don't
have
time
to
contribute
and
I
did
want
to
address
that
a
little
bit
and
that's
totally
expected
there's
again
that
idea
of
an
elastic
team
some
weeks
you'll
have
time
some
weeks.
You
won't,
but
I
would
absolutely
invite
everyone
who's
listening
to
this
or
who
will
who
will
do
the
recording
of
this
at
a
later
date
start
small
like
get
involved.
Maybe
you
just
kind
of
update
some
code
comments
which
again
will
help
and
update
our
documentation
and
make
the
documentation
better?
A
Maybe
there's
a
typo
somewhere
or
you
just
see
you
know,
maybe
there's
a
method
that
could
be
done
a
little
bit
more
efficiently.
So
you
know
really
start
small.
You
don't
have
to
make
giant
contributions
to
get
started
so
I
know
a
lot
of
these
tools
are
new
to
folks,
for
example,
github
you
know
node.
A
All
these
sort
of
things
are
new,
so,
like
any
project
start
small,
you
know
try
and
get
involved
if
you've
got
questions
reach
out
on
Yammer
reach
out
on
get
er
folks
will
help
out
I'll,
try
and
help
you
out
as
much
as
we
can.
But
you
know
understand:
everybody
is
very
busy
understanding.
Everybody's
time
is
tight,
but
very
much
open
invitation
for
anybody
would
like
to
contribute.
They
don't
have
to
be
big
contributions.
A
They
can
be
small
contributions,
dip
your
toe
in
the
water
kind
of
see
how
things
work
see,
how
creating
a
pull
request
works
and
once
you
kind
of
do
it,
you
know
56
times,
like
anything
else
in
life,
it'll
become
sort
of
second
nature.
You
know
so
I
mean
when
I
first
picked
this
up,
gosh
I,
don't
know
about
a
year
ago,
I
started
to
get
involved
in
this
kind
of
stuff.
A
But
if
somebody
gets
a
chance,
if
we
can
update
the
latest
version
and
if
gulp
lint
works-
and
we
come
back
clean
on
that
very
happy
to
just
up
the
version
in
the
package.json.
So
that's
an
easy
fix,
but
did
want
to
sort
of
address
that
that
that
is
fixed
right
now,
because
there
was
a
bug
in
the
TS
lint
library
that
was
impacting
us.
So
just
did
recognize
that,
but
haven't
had
a
chance
to
dive
into
that
myself.
A
But
if
somebody
else
has
a
chance
to
just
take
a
quick
look
at
that
and
if
we
can
update
that
in
the
package.json,
you
know
very
happy
to
do
so.
Two
links
down
there
at
the
bottom
again
into
the
Yammer
and
to
our
get
ur,
so
both
of
those
are
great
places
if
you
have
general
questions
or
discussions
or
want
to
make
a
contribution
and
aren't
sure
necessarily
how
to
go
about
it.
A
Those
are
both
great
places
to
jump
in,
and
you
know,
ask
those
questions
or
you
know,
give
this
hardening
and
give
those
comments
and
feedback
again
for
now
still
on
Yammer,
we
will
let
you
know
what
our
plans
are
moving
forward
with
that,
but
I
don't
have
details
really
to
share
around
where
we're
moving
yet
so
that
will
be
forthcoming.
So
weekly
standup
what's
been
going
on
the
upcoming
public
tools
preview.
So
that's
going
to
be
very
cool.
It's
going
to
get
stuff
into
folks
hands
that
want
to
start
building
on
the
SharePoint
framework.
A
Devstack,
it's
going
to
start
with
webparts,
it's
going
to
start
out
building
on
localhost.
I
cannot
tell
you
a
date
that
a
public
preview
will
be
released,
but
I
can't
tell
you
there's
an
upcoming
keynote
on
817,
where
the
details
of
this
will
be
discussed.
That's
a
sharepoint
fest
in
seattle,
so
I'll.
Let
you
guys
connect
the
dots
on
that,
but
so
really
exciting.
I'm
excited
for
everybody
to
get
a
chance
to
get
their
hands
on
the
dev
tools
and
again
coming
out
of
that.
I
expect
a
lot
of
great
feedback.
A
Can
everybody
just
double
check
their
own
meat
for
me,
so
some
upcoming
blog
posts
still
working
the
documentation
generation?
One
is
pretty
much
done:
I
just
need
to
publish
that
I've
got
one
on
the
web
pack
trick,
we'll
discuss
that
a
little
bit
later
and
then
the
node
console
app.
But
I'm
going
to
show
you
good
folks
today.
We
will
also
want
to
do
a
blog
post
on
that
cuz.
A
I
think
it's
kind
of
a
nice
way
to
use
the
library
and
do
some
simple
sharepoint
operations,
so
sandbox
solutions
we'll
come
back
to
this
in
the
discussion,
but
did
want
to
mention
the
we
talked
about
this
last
week,
but
there
is
a
script
to
list
just
solutions
from
your
tent.
That
has
been
updated.
So
if
you
or
your
customers
are
impacted,
we've
got
the
updated
script
there.
A
We
also
have
a
lot
of
guidance
coming
on
migrating
out
of
various
sandbox
solution
scenarios,
so
are
trying
to
help
out
as
much
as
we
can
in
that
regard
and
smooth
the
process
of
getting
out
of
sandbox
as
much
as
we
can,
after
the
sudden
announcement
of
the
deprecation
so
coming
up
opportunity
to
contribute
again.
These
are
unchanged
from
last
week,
like
I
said
I
myself
haven't
had
time
so
still
have
the
same
area
as
we're
looking
to
get
some
help
in
documentation,
styling
and
the
general
ux
of
the
api
docs.
A
I
think
that's
a
great
opportunity
for
one
or
more
folks
that
want
to
have
a
very
visible
impact
for
the
community
testing
again
using
the
library
get
us
that
feedback
report
issues.
There
are
a
couple
issues
I
saw
on
github
and
haven't
had
time
myself
to
have
a
look
at
those.
If
anybody
in
the
community
has
chance
and
wants
to
take
a
look
at
that
very
happy,
you
know
for
folks
to
submit
pull
requests
that
are
fixing
knows
and
I.
A
Don't
frankly,
know
the
details
of
those
issues
yet
so
I
don't
really
have
a
measure
on
complexity
at
this
time,
writing
tests.
Well
we're
still
looking
for
help
a
writing
test.
Writing
tests
against
share
points.
So
we've
got
some
examples
of
that
out
there.
You
can
comment
again
on
issue
number
42
grab
an
area.
That's
to
help
us
not
you
know
not
so
I'm
sorry
overlap
on
work.
Apologies
for
that!
My
brain
is
fried
after
the
last
two
weeks,
so
I
just
grabbed
an
area.
A
A
So
team
discussion
this
week,
I
did
mention
I've
got
some
upcoming
blog
posts
of
my
own
I
did
want
to
mention
again
if
you
are
out
there
and
you're
blogging
about
this
about
the
JavaScript
core
library.
Specifically,
let
me
know
I'm
very
happy
to
help
advertise
that
I
will
tweet
that
out
with
what
reach
I
have
there,
but
I
also
am
working
on
a
series
of
blog
posts
and
working
on
a
way
to
incorporate
this
into
our
documentation
or
into
the
wiki
somehow,
but
want
to
start
directing
folks
who
are
asking
those.
A
How
do
I
get
started,
questions
or
things
like
that
out
to
community
blogs
as
well,
so
that
the
you
know
the
voice
isn't
just
necessarily
for
myself
or
the
core
team,
but
folks
can
see
the
community
work.
That's
going
on
around
this
as
well,
so
if
you
are
doing
some
blogging,
please
let
me
know:
I'd
love
to
help
advertise.
What
you're
doing
out
there
and
I've
tried
to
do
that
as
much
as
I
can
but
I,
don't
always
catch
stuff
myself.
A
So
just
you
know
hit
me
on
Twitter
or
shoot
me
a
note
on
Yammer
and
we're
very
happy
to
help
advertise
that
stuff
out.
I
did
want
to
give
a
brief
update
on
sandbox
solutions.
I
know
this
is
the
JavaScript
special
interest
group
and
you're
asking.
Why
would
you
be
talking
about
sandbox
solutions
and
at
the
end,
you'll
kind
of
see,
but
I
did
want
to
mention
if
you
or
your
customers
are
impacted,
please
do
call
support
or
engage
with
microsoft
support.
A
It
was,
admittedly,
a
little
rocky
at
the
very
beginning,
but
we've
got
a
very
solid
process.
The
support
team
has
done
a
great
job,
so
we're
very
more
efficient
at
helping
you
out.
We
want
to
you
know,
that's
the
channel
in
its
call,
support
and
there's
two
main
paths,
whether
you
want
existing
solutions
to
run
longer
or
you
want.
The
ability
to
activate
new
instances
of
a
solution
engage
with
support,
support
will
get
the
information
required
and
we
will
as
fast
as
we
can
get
that
stuff
going.
A
So
you
probably
asking
yourself
again:
why
are
you
bringing
this
up
in
the
JavaScript
special
interest
group?
Call
if
you're
out
there
and
you
have
customers
or
yourself
or
affected
by
this?
This
is
a
great,
a
sort
of
alcohol
at
opportunity.
It
will
be
a
forced
opportunity
to
look
at
the
possibility
of
rewriting
a
lot
of
this
functionality
in
a
more
client-side
model
on
the
upcoming
public
preview
of
the
dev
stack
will
help
with
that,
but
also
you
can
start
writing
this
stuff
in
a
lot
of
JavaScript
a
lot
of
client-side
technologies.
A
For
example,
a
lot
of
the
things
we're
seeing
are
simple
forms.
You
know
it's,
it's
literally
a
couple
of
fields
and
it
writes
to
a
list.
That's
a
great
client,
a
great
candidate
for
a
client-side
solution.
You
know
other
things
like
that.
Anything
that's
webparts
great
opportunity
for
a
client-side
solution.
So
that's
a
great
chance
to
start
discussing
that
with
your
customers.
A
It
doesn't
have
to
be
based
on
the
SharePoint
framework,
but
there's
ways
and
as
soon
as
I
get
time,
it'll
be
a
blog
post
or
rather
sorry-
and
I
think
it's
going
to
be
msdn
article
on
getting
visual
web
parts
over
into
a
sort
of
the
client
a
side
space
and
how
to
do
that.
So
it's
a
good
opportunity
to
start
having
those
conversations
with
your
customers
around
moving
to
a
more
client-side
model
and
if
you
can
do
that,
that's
going
to
play
into
the
SharePoint
framework.
A
So
it's
a
way
to
transform
the
discussion
into
kind
of
a
this
is
unfortunate.
But
let's
look
at
the
future
and
this
is
how
we
can
progress
and
if
you
were
going
to
rewrite
some
things
for
the
upcoming
SharePoint
framework.
This
is
a
good.
You
know
kind
of
on-ramp
to
do
that.
So
did
want
to
mention
one
last
time
that
SharePoint
event
on
817
will
tie
into
the
upcoming
public
preview
of
the
tools
for
which
I
cannot
announce
a
date
but
check
out
the
thing
on
817
for
that.
A
A
A
So
I
try
to
align
this
to
a
visual
studio
solution.
You've
got
a
main
class,
so
we
have
a
main
dot
J
s
right
now.
It's
a
type
script
file
when
it
gets
built
it
gets
built
into
a
JavaScript
file.
Think
everybody's
familiar
with
that
at
the
at
this
point,
and
then
we
execute
that
and
it'll
run
whatever
we've
put
into
that
type
script
file,
so
that's
kind
of
the
build
pipeline
and
the
command
there
is
just
gulp
run,
we'll
build
it
and
then
execute
it.
A
So
pretty
neat
looking
at
our
main
I'll
just
show
you
right.
Real
quick
is
just
a
super
simple
little
thing
rights
to
the
console,
nothing
important
there,
and
then
we
look
at
those
of
you
who
have
seen
some
of
the
previous
calls.
We
looked
at
the
blog
post,
the
P&P
set
up,
I'm
setting
up
our
node
client
options,
so
this
is
allowing
us
to
make
requests
directly
from
node.
Those
of
you
who've
seen
this
before
nothing's
changed
there,
so
just
a
client
ID,
a
secret
and
a
site
URL
if
anybody's
trying
to
be
sneaky.
A
This
is
set
up
as
read-only
on
my
site.
So
don't
be
too
excited
about
that,
and
then
you
can
just
execute
your
patterns
and
practices
commands
so
I'm
going
to
comment
all
this
out
and
I'm
going
to
grab
my
command
window
here
and
I
can
just
do
gulp
run
and
that's
going
to
run
real,
quick
and
then
we'll
get
our
requests
back
from
the
site.
So
this
is
a
role
kind
of
neat,
simple,
quick
way
to
run
requests.
A
A
You
know
this
is
something
you've
all
seen
before,
but
but
again
in
node
and
I.
Think
sort
of
easy
to
use,
so
one
challenge
I've
had
is
batching
currently
does
not
work
in
node
and
I'm
working
on
debugging
that
it
works,
but
it
the
note
is
exiting
out
before
we
get
the
response
back.
So
I'm
playing
around
with
that
I
think
likely.
A
Execute
is
going
to
need
a
promise,
but
in
in
trying
to
figure
this
out,
one
thing
I
wanted
to
do
is
I
want
to
debug
right,
I
want
to
see
what's
going
on,
how
do
I
debug
well,
the
way
you
do
that
in
Visual
Studio
code
is
through
this
launch
dot,
JSON,
and
so
this
is
a
again
I'll
include
this
in
the
little
zipped
up
file,
and
then
this
was
all
auto-generated
except
I
updated
this,
which
is
pruning
to
our
program.
So
again,
that's
just
build
main
jas
and
then
I
updated
this
pre-launch
task.
A
So
what
they've
done
is
they've
made
this
clever
enough
Visual
Studio
code,
clever
enough
to
understand,
we've
got
gulp
and
our
gulp
has
tasks,
and
one
of
those
tasks
is
run
that
I've
defined
right,
and
so
it's
going
to
call
that
gulp
task
run
before
it
does
anything,
and
what
that
allows
me
to
do
now
is
go
to
this
little.
This
is
a
bug.
It
took
me
a
little
bit
to
figure
that
out.
A
This
is
a
bug
with
a
cross
through
it,
so
this
is
for
debugging
I'm,
not
great
on
icon,
sometimes,
but
so
you
can
just
hit
the
start
arrow.
So
this
is
very
much
that
visual
studio,
f5
experience
and
you're.
Seeing
now
the
exact
same
thing
we
were
seeing
in
our
console
you've
seen
the
response
come
back.
So
that's
what
we
saw,
but
then
now
you've
seen.
We've
got
an
error
not
found,
so
we
can
start
to
add
breakpoints
in
here
we're
we're
deep
in
nodejs.
So
we
can,
you
know,
actually
add
a
breakpoint.
A
A
I
may
need
reading
glasses,
yeah
I
probably
did
I
probably
need
to
up
my
prescription.
Oh
and
of
course,
because
we're
in
a
demo
it
missed
my
break
point,
but
so
generally
break
points
are
going
to
get
hit.
But
this
is
letting
you
start
to
see
what
the
different
things
are
and
start
to
actually
get
a
real
debugging
experience.
The
stuff
here
is
going
to
be
sort
of
useless
because
we're
in
nodejs,
which
is
obviously
the
node
itself,
so
we're
not
getting
much.
A
You
know
help
there,
but
you
know
I'm
not
going
to
waste
everybody's
time.
Trying
to
make
my
break
break
points
work
but
you'll
be
able
to
get
into
your
code.
Do
some
breakpoints
see
some
things
happen.
Do
some
real
kind
of
visual
studio
style
debugging,
you
can
add,
watches
and
things
like
that.
So
I
think
it's
going
to
be
a
nice
addition
to
kind
of
the
work
we've
all
been
doing
and
helping
us
with
our
debugging
story
around
that
so
again,
I'll
package,
this
up,
but
this
is
kind
of
where
I've
been
going
on.
A
A
You
know
related
to
my
work
on
sandbox
solutions,
so
it's
been
nice
to
be
able
to
just
do
quick
little
things
against
the
SharePoint
site
using
javascript
and
using
our
library
so
did
want
to
highlight
this
I
think
it's
a
going
to
be
a
nice
addition
again
working
on
batching
batching,
not
working
to
be
a
very
clear
currently
in
node,
so
working
on
figuring
that
out
and
we'll
continue
to
grow
this
as
we
grow,
iterate
improve
all
things.
So
with
that
said,
does
anybody
have
any
questions?
You
know
things
like
that?
A
Oh
I
did
want
to
show
you
guys.
There's
been
some
questions.
This
is
a
good
opportunity
to
ooh
oops
and
give
me
a
second
I
closed,
my
browser,
so
I
wanted
to
show
there's
been
some
questions
for
folks
that
are
maybe
new
to
sharepoint
on
actually
how
you
register
these
apps
and
give
me
a
second
I've
got
to
get
my
text
message.
A
And
slowly
but
surely
alright,
so
we're
into
the
site,
and
so
this
is
just
my
dev
site
for
folks
on
the
call
you've
seen
this
many
times,
but
the
way
you
register
these
apps
is
you
go
to
a
page,
appt
reg,
new
aspx,
and
if
there
are
plenty
of
articles
out
there
on
how
to
do
this,
but
I
did
want
to
kind
of
walk
through
it,
just
to
kind
of
show
folks
and
you're
going
to
get
this
page,
which
asks
for
some
information
and
so
for
client,
ID
and
secret
I
just
generate
a
new
one.
A
This
is
just
a
random
goo.
It
and
I
generate
a
new
secret.
This
is
actually
just
a
set
of
random
bytes
and
then
I
give
my
appetite.
Alytchai
usually
give
it
something
like
you
know,
demo
delete
me
pleased,
and
that
reminds
me.
This
is
for
a
demo
and
I
should
delete
it
when
I'm
done
and
then
there's
two
more
fields
here
which
can
confuse
some
folks
for
what
we're
doing
they
don't
matter.
A
So
we
do
have
a
new
registration.
App
identifier
has
been
created,
so
I
like
to
copy
that
to
somewhere,
I,
won't.
Forget
it
and
I've
copied
that
off-screen
here
and
then
the
next
step
is
you
go
to
another
layouts
page
app,
I
NV
dot
aspx,
so
this
app
registration
has
two
parts
to
it.
The
first
is
what
we
just
did,
which
is
generating
the
client
ID
and
the
secret,
but
right
now
that
client,
ID
and
secret
has
no
permissions
to
my
site.
A
So
what
I've
done
is
I've
pasted
that
client,
ID
and
I
don't
know
why
our
labels
are
different
everywhere,
but
app
ID
is
client,
ID
I've
pasted
that
in
here
click
look
up
and
you
can
see.
My
information
here
has
been
populated,
but
I've
got
another
value
here
at
the
bottom,
for
permissions
request
xml.
So
if
you've
ever
created
an
add-in
through
visual
studio,
visual
studio
creates
this
for
you
after
you
go
through
there's
the
permissions
tab.
A
You
select
your
permissions,
but
you
can
also
create
that
XML
by
yourself
and
so
just
to
sort
of
show
you
here's
our
XML,
and
this
can
be
very
complicated
or
you
know,
have
a
lot
of
different
app
permission,
requests
or
just
a
very
few
like
I
have
one
but
the
key
for
what
we're
doing
is.
You
have
to
include
this.
A
Allow
app
only
policy
equals
true,
so
that
is
what
allows
us
to
make
calls
from
our
a
dinner
from
node,
which
is
acting
as
an
added
in
this
case,
and
then
I've
got
one
single
request,
which
is
a
scope
to
the
site,
collection
and
I'm,
asking
to
be
able
to
read
everything
in
that
site.
Collection.
I
won't
go
right
now
into
all
the
different
permission
requests,
but
there's
plenty
of
posts
out
there
on
that
and
plenty
of
additional
info.
A
There
paste
that
into
your
permissions
request,
XML
field
and
hit
create,
and
you
get
this
trust
screen.
This
will
actually
list
out
all
the
things
you've
asked
for
so
let
it
share
its
permissions
with
other
users.
That's
the
app
only
policy
and
then
let
it
read
items
in
the
site
collection
and
this
one
is
always
going
to
be
there.
Let
it
access
basic
information
about
users
of
this
site.
A
A
Still
getting
that
so
I'm
not
going
to
go
into
this
any
further
trust
me
this
process
does
work.
Of
course,
every
time
this
week
is
just
a
week
of
things
like
this
happening,
so
I'm
just
going
to
go
with
that.
So
with
that,
but
that's
going
to
be
the
console
app
so
working
on
sharing
that
out
for
folks
and
then
I've
got
a
bunch
of
questions.
I
can
see
going
on
over
here
in
the
eye
on
Windows.
Let's
take
a
look
at
those
nope,
a
bunch
of
stuff.
A
A
Why
can
we
not
use
the
same
testing
tools
as
Burt
demonstrated
yesterday
vases
answered
this
and
we
are
the
end
goal
is
to
do
something
very
similar
and
automate
that
testing
against
sharepoint,
but
the
first,
a
kind
of
part
of
that
is
getting
the
test
coverage
built
out
and
then
figuring
out
how
we
can
run
that
against
sharepoint
again
on
a
I,
don't
know
if
we'll
need
to
do
a
daily
basis,
but
on
maybe
a
weekly
basis
or
then
there's
a
lot
of
open
source,
continuous
integration
tools
out
there.
A
A
I
think
it's
something
we
can
do
it's
something
we
have
to
share
permissions
out,
and
so
I've
got
to
figure
out
kind
of
how
to
make
all
that
work
if
you
will,
but
so
that's
something
we're
definitely
looking
at
is
we
won't
be
able
to
use
exactly
what
Burton
is
using
because,
as
basis
said,
that's
sort
of
in
the
visual
studio
testing
side,
but
we
will.
We
are
looking
at
ways
to
automate
testing
you.
B
A
B
Just
to
clarify
on
slightly
more
on
that
one,
so
so,
obviously
just
to
clarify
these
are
not
come
to
completely
isolate
a
thing
need
Patrick
and
birds
are
having
meetings
almost
every
single
day
on
thinking
through
what
we
want
to
do.
How
do
I
ultimate
testing?
How
do
we
do
web
testing
for
this
library
as
an
example?
A
Why
not
use
the
PMP
provision
engine?
It
is
more
popular.
The
provision
engine
is
very
popular
and
works.
Very,
very
well.
I'll
apologize
a
little
bit
because
I
forget
the
context
of
when
that
question
would
have
come
in
so
I,
don't
know
exactly
what
that
was
asked.
A
I
thought
this
sig
would
build
upon
the
work
done
by
the
original
team,
Erwin
Paulo
and
Bert,
but
we
seem
to
have
gone
off
on
a
tangent.
Should
this
sig
not
be
building
functionality
and
typescript,
which
calls
the
pnp
code
so
little
and
I
see.
There's
some
answers
there.
A
little
confused
by
that
the
PMP
code
is
C,
sharp
managed
code
that
runs
sort
of
in
executive,
all
environment,
so
on
a
Windows
machine
or
server,
or
something
like
that.
A
I've
been
closely
involved
with
all
those
folks
and
they're
all
doing
amazing
work,
but
but
their
work
is
in
managed,
see
some
code,
and
so
we
are
in
sort
of
the
JavaScript
world
which
is
typically
going
to
be
run
in
a
browser
and
or
in
node,
which
neither
of
those
areas
support
a
c-sharp
currently
and
I.
Don't
believe
ever
will
so
I
say
that,
of
course,
tomorrow
somebody
will
release
an
open
source
project
that
lets
node,
run
c
sharp,
but
sub.
A
Yeah
this
week
has
taught
me
humility,
but
so
we
so
they're
different
technologies,
they're
not
competing,
but
they're
complementary.
So
it's
when
folks
want
to
do
stuff
in
a
managed
code.
Environment
absolutely
see.
Some
is
the
way
to
go
and
we
are
not
ever
going
to
try
and
sort
of
supplant
that,
but
for
folks
that
are
looking
to
do
operations
in
the
browser
or
operations
in
now
in
node.
Oh,
that's!
Where
we're
looking
to
be
to
help
out.
A
We
absolutely
don't
have
feature
parity
at
this
point
between
the
managed,
see,
Psalm
and
our
library
and
I.
Don't
know
that
it's
appropriate
read
have
full
feature
parity
between
the
two
and
we
might
have
some
features
that
the
sison
library
doesn't
and
so
forth.
You
know,
in
vice
versa,
so
I
think
they're,
two
different
things.
A
We
are
all
working
together
and
we
are
all
working
to
enable
the
same
kinds
of
scenarios,
but
in
two
different
environments
right
so,
for
example,
I
don't
think
we
ever
should
or
will
have
as
full
a
provisioning
story
as
exists
in
the
seesaw
library.
They've
done
an
amazing
job,
it's
incredibly
deep.
The
work
they've
done
on
the
templates
is
incredibly
strong
and
I,
don't
frankly,
see
a
reason
to
duplicate
that
if
somebody
wants
to-
and
somebody
wants
to
duplicate
all
that
work
and
we
can
run
it
from
node.
B
B
If
you're
building
a
asp.net-mvc
site,
for
example,
then
you'd
want
to
use
these
c
sharp
libraries
and
if
you
would
run
something
the
browser,
you're
forced
to
use
javascript,
but
if
you're
I
think
it's
a
great
example
that
you
gave
in
that
demonstration
earlier
Patrick,
where
you
were
building
a
console
application,
but
you
could
use
either
in
that
situation,
but
some
developers
might
prefer
to
use
JavaScript
and
node
and
and
that's
a
great
solution.
Yeah.
A
B
We
can
know
about
a
quick
comment
on
that
one.
So,
even
though
it
technically
would
also
be
kind
of
an
interesting
to
have
the
template
color.
Oh
sorry,
that
the
provisioning
engine
fully
as
type
great
and
JavaScript-
and
there
are
let's
say,
challenges
to
run
that
one,
because
whenever
you
would
be
doing
that
to
you,
but
that
essentially
be
dependent
on
the
pros
session
and
that's
not
necessarily
a
recommended
pattern.
Because
what
will
happen
if
somebody
will
close
the
browser
why
it's
actually
still
provisioning
and
all.
B
A
Microsoft,
a
typescript
is
not
the
way
the
universal
way.
Microsoft
wants
us
to
go.
It's
the
way,
we're
moving
for
this
sort
of
client-side
scripting
and
for
the
SharePoint
upcoming
SharePoint
framework
is
going
to
be
in
typescript,
but
it's
absolutely
a
hundred
percent
still
a
valid
to
be
writing.
C
sharp
code
with
the
the
sea,
solemn
library
and
all
those
things.
That's
I
mean
unless
there's
a
major
announcement.
I,
don't
know
about
that's
not
going
away
anytime
soon
at
all
yep.
A
There
is
an
API
discrepancy
which
hopefully
we're
going
to
get
fixed
up
as
much
as
we
can.
The
new
SharePoint
will
go
to
the
type
strip
way,
so
we
are
going
the
type
strip
way.
That's
this
JavaScript
library,
but
that's
for
the
UI
and
the
client
scripting.
It's
not
necessarily
for
again
the
server-side
kind
of
stuff
right.
If
you
typically
written
a
provider
hosted
ad
in
NB,
C,
C,
sharp
posted
in
will
say,
Azure
keep
doing
that.
A
That's
not
going
to
change
in
a
big
part
of
the
SharePoint
framework
story
is
going
to
be
a
micro
services.
So
this
idea,
since
in
the
browser,
you
obviously
can't
elevate
permissions,
because
that's
you
just
can't
so
if
you
need
to
do
something
in
an
ad
in
only
manner
and
sort
of
essentially
elevate,
that
particular
user,
that
model
is
still
going
to
be
to
call
from
the
browser
out
to
your
micro
service,
to
call
back
to
SharePoint
to
do
those
activities
as
the
add-in
only
permissions.
So.
A
You
know
so
all
of
that
is
still
a
hundred
percent
valid
way
to
do
it.
This
isn't,
you
know
one
way
or
the
other.
It's
it's
all
these
technologies
working
together
in
the
best
way
to
meet
the
needs
of
whatever
solutions
being
developed.
So
that's
all
of
that
is
going
to
continue
to
be
used
and
then,
let's
see
yeah
so
I'm
back
at
the
bottom
of
the
thread.
Are
there
any
other
questions
comments,
discussion
points
anybody
wants
to
bring
up.
A
Well
with
that
I'll
say
thank
you
to
everybody,
I'll
try
and
get
some
blog
posts
out
this
week
or
maybe
this
weekend
and
then
do.
If
you
have
some
time
again,
small
contributions
absolutely
are
as
valuable
as
large
contributions,
so
it's
a
great
way
to
get
involved.
So
thank
you
to
everyone
really
appreciate
it.
It
really
appreciate
the
time
look
forward
to
talking
to
you
next
week
and
I'll
see
you
on
all
the
various
social
channels.
Thanks
everybody.