►
Description
This is a recording from MVP Summit 2016 where we had 7 of the PnP Core team members in one table talking about the future of SharePoint development for on-premises and online.
A
So
welcome
everybody.
This
is
sharepoint
a
dozen
practices
webcast,
and
this
time
we
have
something
slightly
special,
because
there's
six
or
seven
I
can't
count
us
on
the
I'm
sitting
on
the
same
table
I.
This
is
really
rare,
so
the
pnt
core
team
is
at
the
in
the
MVP
summit
in
redmond
and
it's
seven
of
us
actually
sitting
on
the
table.
A
So
it's
me,
my
name
is
Reuben
I'm
senior
program
manager
in
SharePoint
engineering
with
me
here
is
well
deck
master
cards,
urban
vanhouten,
Patrick,
Rodgers,
iliya
streets
again
pronounce
Ilyas
last
name
properly
and
Bert,
Johnson
and
all
of
the
lrc.
And
what
we're
planning
to
do
is
just
a
random
discussion
on
the
future
of
sharepoint
development
and
everything
related
on
that
one.
A
A
B
So
maybe
maybe
I
can
explain
to
me
why
I
started
with
the
pp
powershot
matters
because
they
come
from
a
background
where
I
noticed
that
during
my
day-to-day
development
tasks,
I
wanted
to
do
simple
short
code.
Snippets
and
I
always
ended
up.
Writing
console
applications
to
do
that
and
it
felt
awkward,
especially
if
you
may
I
had
to
make
a
little
change
whatever
so
I
was
like.
Okay
can
I
use
PowerShell,
but
an
office
365.
B
There
was
no
sane
powershell
solution
that
you
could
do
like
developing
type
of
tasks
with
so
I
started
to
look
into.
Could
I
expose
the
whole
season
object
model
to
the
powershell
and
you
can
by
using
all
kinds
of
complex
scripting
things
you
can
expose
the
whole
system
object,
but
it
didn't
feel
natural,
especially
if
you
used
by
rachelle
commanders
before
they
had
to
be
more
power.
Shelley
use
that
word.
So
that's
where
the
about
the
pp
commanders
came
from.
They
are
a
more
power
shell
based
approach
or
the
command.
B
Let's
have
a
more
power
shell
nature
than
using
season
directly
and
and
that's
and
that's
also
where
I
see
where
they
make
a
lot
of
sense,
and
especially,
for
me
at
least,
is
that
in
my
day-to-day
development
tasks,
I
use
the
pp
commanders
as
an
as
an
addition
to
my
development
tasks
to
check
out.
If
my
co
did,
the
right
thing
is
that
artifact
created
or
may
be
able
to
make
a
little
change.
B
That's
where
I
use
the
PowerShell
commands
for
yeah
makes
that
so
it
makes
yeah,
but
then,
of
course,
there's
the
IT
pro
side
of
the
story
where
the
SharePoint
PowerShell
command
list
in
2010
in
2013
2016
basically
are
for.
They
also
make
sense
in
the
case
of
office
365
to
use
the
PNP
ones,
because
the
office
365
management,
shell,
doesn't
do
anything
with
artifacts.
It
judged
our
content.
Oh
it's.
A
B
Administration
tasks,
rating
sites,
adding
users,
groups
etc,
where
the
PNP
ones
are
yeah,
they
go
a
bit
further,
add
a
focused
mainly
on
artifacts,
creating
lists
items
in
lists,
content,
types,
etc,
etc,
etc.
So
they're
an
addition
to
what
you
already
have
their
and
for
me
there
are
ice.
Think
of
them
as
a
rate,
create
additional
tool
set
as
a
developer.
Yeah.
A
D
B
Question
yeah
yeah,
yeah
yeah.
The
thing
is,
of
course
this
is
open
source.
I
would
say
that
typically,
we
can
react
faster
on
changes
them
sure
to
say
marshalled
cam,
which
is
I,
think
a
great
benefit
of
the
PMP
commanders
I
mean
we
release
them
every
month,
a
new
version
with
fixes
updates
additions,
etc.
So,
pretty
recently
we
added
now
Lee
Commandments
for
the
photograph
written
by
Paolo,
sound.
B
Yeah
yeah
so
yeah
it
makes
sense
there.
Wasn't
we
made
a
mistake
when
we
released
the
pnp
PowerShell
command,
'let's
that
we
used
in
and
prefix
that
was
overlapping
with
the
mic,
the
microphone,
so
we
use
the
SPO
prefix.
We
will
fix
that
in
the
upcoming
release.
We
renamed
the
command
'let's
to
use
the
PNP
prefix.
So
there's
no
conflict
anymore.
You
can
easily
use
them
side
by
sides
together,
sew
and.
A
I
think
actually
I,
like
that,
the
thinking
of
the
BMP
being
much
more
a
child.
We
can
actually
do
stuff
and
I'm
from
sharepoint
engineering,
and
I
know
that
our
processes
are
not
as
flexible
as
the
BMP
process.
So
that
kind
of
makes
sense
and
why
not
have
them
as
two
separate
one
so
weak
inversion
them
differently
and
release
new
versions
differently,
as
well.
Yep.
D
A
Build
it
yourself,
yeah
cool,
let's,
let's
move
on
on
a
slightly
different
topic,
so
that
was
the
VMP
power
shall
L.
So
let's
talk
about
slightly
to
BMP
provisioning
engine
and,
let's
actually
start
a
discussion
with
Burt
Burt
Johnson
is
one
of
the
main
architects
of
the
of
the
provisioning
engine
as
well,
and
what
would
be
your
thinking
on
the
future
of
the
VMP
appreciating
engine
related
on
the
discussions,
for
example,
what
we
had
to
earlier
today
with
engineering
so
does
the
BMP
provisioning
engine?
D
B
D
Children
yeah
yeah
no,
but
the
frigging
engine
is
really
one
of
the
a
game.
One
of
the
more
popular
elements
in
pnp
we
have
like
think
about
to
reach
a
thousand
stands
a
month
using
the
engine
to
create
site
collections
so
to
create
sites
operation
sites
inside
their
their
tendencies,
so
which
means
it
that
is
very
popular,
is
cleared
amount
on
the
engine.
People
just
want
to
create
custom
size
of
the
Box
sites,
our
gay,
but
not
sufficient
for
all
the
scenarios
that
customers
have
now
with
microsoft.
D
D
Sites
you
can
create
a
group
using
the
outlook,
experience
from
sharepoint
sake.
Let's
call
the
modern
inside
of
it.
Essentially,
it's
the
site
linked
to
a
group,
any
change
and
that
site
is
becoming
more
and
more
popular
and
being
push
more
by
engineering
is
the
difficult
aside
to
use,
which
sense
also
means
that
they're
from
the
PNP
site,
we
will
work
on
the
engine
side
to
make
it
compatible
with
those
sites
again
so
well.
D
If,
in
the
future
your
default
site
will
be
a
group
site
can
still
use
the
engine
and
to
customize
it,
because
this
is
the
SharePoint
site.
It
just
looks
slightly
different
as
a
modern
look,
but
still
is
under
hood.
It's
a
SharePoint
meaning
castle
customize
it.
There
are
some
gorgeous
some
things
which
are
not
possible,
but
overall
can
be
customizable,
and
and
that's
what
we
will
add
in
the
engine,
yeah.
A
A
Yeah
and
over
sooner
or
later,
the
right
now,
the
engineering
is
looking
for
the
MP
engine,
say
innovation
and
inspiration
for
their
native,
let's
say
provisioning
and
engine
as
well,
but
that's
not
really
in
a
short-timer
in
so
that's
going
to
still
take
a
while
for
engineering
to
come
back
with,
and
especially
on
the
level
of
the
PNP
provisioning
engine,
which
has
a
lot
of
lot
of
different
capabilities
available
already
today.
So
obviously,
that
will
have
valid
future
within
a
within
a
year
easily
and
we'll
see
even
further
LOL.
D
A
No
job,
no
ok,
moving
on
on
the
honest
following
person
on
the
table-
and
this
is
really
fun
that
we're
all
sitting
on
the
same
table.
So
we
have
Paolo
on
the
table
by
been
working
on
under
power,
shell
and
the
engine
and
the
BMP
stuff
in
general.
But
one
of
the
things
but
paula
is
also
worth
but
heavily
is
the
Microsoft
craft?
What
about
sharepoint
and
Microsoft
graph?
E
So
I'm
really
happy
to
see
that
now
in
the
preview
endpoint
in
the
beta
in
point
of
the
max
of
graph,
we
also
have
a
few
one
point
for
sharepoint
online
as
well
to
manage
lists,
item
and
side
and
I
am
looking
forward
to
see
much
more
employment
available.
Most
likely,
we
will
not
be
able
to
see
all
the
rest
api
that
are
right
now
available
in
sharepoint,
somehow
brat
or
migrated
into
the
micrograph,
because
it's
not
that
easy
to
do
that
yeah.
E
But
on
the
other
side,
what
will
be
really
useful
to
create
real
business
solution
will
be
there.
In
my
opinion,
it
will
be
a
step-by-step
route
and
that's
why
we
started
in
PMP
to
provide
some
new
cmdlet
also
for
the
micrograph
as
a
win
said
a
few
minutes
ago,
because
we
think
that
we
need
to
properly
provide
support
to
developers
and
kaity
pro
guys
to
play
with
the
graph
as
well.
And
so
there
is
a
nice
future
behind.
A
A
B
E
Be
could
be,
but
I
think
it
will
not
be
comparable
to
what
we
can
do
right
now
with
season
and
with
the
provisioning
engine
and
that's
my
opinion
again.
I
think
it
will
never
happen
that
we
will
have
a
full
coverage
of
all
of
the
capabilities
that
right
now,
we
provide
with
the
engine
also
truly
micrograph
right,
because
it's
not
needed
to
be
fair.
We
already
have
to
engage
in.
There
will
be
the
provisioning
edging
coming
from
the
product
group.
So
there's
no
need
for
that
in
my
and.
F
Yeah
and
I
guess
that
there's
also
another
edge
right,
because
the
shape
of
offsides,
for
example,
changes
a
lot
or
like
in
the
past.
We
could
add
webparts
tool
is
abuse
right
and
we
move
more
and
more
away
from
that
and
I
think
that
what
we
will
see
is
that
api's
align
more
with
future,
so
allein
more
around
scenarios.
What
you
can
do
and
achieve
so
create
documents
or
move,
move
a
document
and
not
really
manage
a
weapon
on
a
page.
F
A
E
A
F
A
So
she
upon
framework,
is
available
in
the
developer
Tenon's
pretty
soon
in
the
first
release,
tenants
as
well
and
one
of
the
things
what
people
keep
on
asking
around
the
ship
on
framework
is
to,
let's
say
the
two
knowledge
gap
of
learning:
how
to
do
modern
web
stack,
development
of
type
screen
and
elio
has
been
doing
that
for
quite
a
long
time
actually
already
before
we
release
the
SharePoint
framework.
So
how
did
you
learn
to
do
the
more
my
afternoon,
development
in
a
web
style
using
the
web
stack,
develop
an
auto
so.
G
I
started
with
with
the
beginning,
so
what
is
coming
in
SharePoint
framework
like
typescripts
I,
started
learning.
What
start,
how
can
you
use
typescript
I,
don't
start
with
learning
everything
at
once,
because
that's
too
hard,
you
know
if
you're
checking
out
a
SharePoint
framework,
you
have
react.
You
have
mpm
nodes
and
all
these
kind
of
things.
If
you're
going
to
do
everything
at
once,
it
will
be
too
much
information
to
capture
so
start
one
by
one.
G
A
G
I
think
a
lot
of
developers.
It
is
in
the
past,
so
in
sharepoint
2010
in
SharePoint
2013.
We
all
put
some
web
parts
on
the
page
and
linked
scripts
or
linked
something
an
HTML
page
to
it,
and
then
it
was
a
web
part,
but
there
was
no
development
story
around
it.
So
the
great
thing
about
sharepoint
framework
is
that
you
now
have
development
story
which
you
can
now
publish
your
new
web
parts
or
whatever
is
coming.
Oh,
yes,
and
before
everyone
is
its
own
ways
of
doing
that.
G
A
And
and
SPF
x
is
obviously
offering
a
lot
of
services
for
you
to
consume
as
well.
So
you
don't
have
to
worry
about
certain
things.
You
get
a
pre-loaded
data.
You
get
a
lot
of
API
available
for
you
to
call
so
what's
really
great
as
well
couch
moving
along
on
things,
so
we
get
to
Google
fix
or
moving
along
across
the
people.
So
we
switch
between
the
people
and
discussion
point
so
Patrick
Patrick
Rodgers
on
a
table
as
well.
Patrick
is
one
of
the
fathers
of
B&B
javascriptcore
captain
right.
A
A
C
The
relationship
actually
started
out,
they
said
myself
and
actually
I-
think
everybody
at
the
table
were
had
was
part
of
sort
of
getting
to
see
an
early
look
at
the
upcoming
SharePoint
framework,
and
we
looked
kind
of
all
it
ourselves
and
thought
well.
Patterns
in
practice.
Program
really
doesn't
have
sort
of
a
formal
story
around
client-side
development
or
anything
with
the
modern
web
development
stack.
So
we
thought
well.
We
should
really
do
something
there,
but
we
were
in
a
position
where
we
couldn't
announce
to
the
world
what
was
coming
because
it
was
still
under
development.
C
It
was
still
you
know,
sort
of
a
Microsoft
internal
thing
at
that
point,
so
we
started
a
series
of
meetings.
There
was
weekly
meetings
and
we
started
encouraging
the
use
of
typescript
and
introducing
these
technologies
such
as
gulp
react
things
like
that
that
a
lot
of
classic
SharePoint
developers
who've
done
some
very
advanced
development
in
the
past,
perhaps
weren't
familiar
with
or
hadn't
used
before,
I
know
myself.
C
I
had
to
do
a
fair
amount
of
learning
very
quickly
to
get
up
to
speed
on
these
things
and
so
I
kind
of
came
from
where
classic
SharePoint
developers
were
coming
from.
So
we
started
this
program
and,
as
part
of
that,
we
needed
also
had
the
idea
of
the
seesaw
emcor,
the
managed
code,
core
libraries
that
folks
have
been
using
for
a
couple
years
now
we're
very
successful
and
really
help
the
community
do
a
lot
of
powerful
development
without
having
to
necessarily
rewrite
this
kind
of
same
boilerplate
code
again
and
again.
C
So
in
parallel
with
this
idea
of
educating
folks
about
what
was
coming
without
being
able
to
tell
them
what
was
coming,
we
started
this
idea.
We
should
also
have
sort
of
a
core
library
to
help.
Folks
now
now,
as
I
can
think
about,
is
coming
up
with
a
better
name,
but
this
core
library
to
sort
of
follow.
With
the
the
see
some
core
idea
of
or
a
usable
library,
the
folks
can
use,
and
that's
where
that
came
from
and
how
it
relates
to
SharePoint
framework
is
sort
of
that
origin.
C
But
then
you
can
certainly
consume
and
use
the
library
within
your
SharePoint
framework
projects
and
and
I,
and
we
very
hope
you
know
have
very
much
hope
you
do,
but
it's
certainly
not
required.
The
SharePoint
framework
itself
provides
a
lot
of
great
support.
Great
you
know,
HTTP
client
support
and
things
like
that.
The
disadvantage
of
that
is,
you
have
to
remember
all
the
URLs.
C
You
have
to
parse
a
lot
of
the
data,
and
so
again
it's
something
we're
hoping
is
just
very
helpful
and
helps
folks
concentrate
more
on
what
they
want
to
do
and
less
on
exactly
how
the
REST
API
is
work
under
the
hood,
especially
get
requests.
Obviously-
and
rest
folks
are
familiar
with
it's
very
simple,
but
a
lot
of
the
post
requests.
Updating
things
stuff
like
that
can
can
really
be
a
little
bit
more
complicated.
C
We've
also
wrapped
up
a
lot
of
common
functionality
like
batching
and
caching,
and
things
like
that.
That
folks
obviously
write
themselves,
but
we're
hoping
just
makes
a
little
bit
easier,
especially
if
you
ever
tried
to
work
with
the
batching
functionality.
We
think
inside
the
API
we've
written
to
kind
of
wrap.
All
that
makes
it
a
lot
simpler
and
a
lot
easier
and
we've
actually
worked
on.
We've
got
enhancements
in
the
next
release,
which
will
probably
out
next
week
whenever
we're
recording
this
to
really
help
with
batching.
Additionally,
as
well.
C
B
A
E
F
C
A
F
Why
I
actually
gave
it
a
try
in
the
context
of
a
webpart,
a
client
side
clipart,
and
I
love
it.
I
love
the
way
it
works
and
if
you
compare
the
code,
I've
built
actually
a
sample
that
illustrates
performing
crud
operations
in
SharePoint
with
rest
rest
and
compare
it
with
the
library,
and
you
can
really
easily
see
significant
improvement
in
simplicity
of
the
code
like
how
easily
you
can
I
dad
and
in
a
way
you
could.
I
think
you
could
compared
to
type
script.
F
The
same
way,
types
that
offers
you
design
time
features
to
check
your
code,
the
same
way
with
the
PM
pjs
core
library.
You
get
exactly
the
same
with
interaction
with
lists,
la
ivories
and
items
and
size.
So
all
of
the
objects
that
you
have
in
your
sights
right.
You
get
all
the
checks
design
time
as
opposite.
If
you
would
use
raw
rest,
that
you
will
get
errors
on
runtime
and
there's
no
way
for
you
to
check
that
upfront
as
part
of
your
cut
hi
sweets
other
than
to
execute,
really
complex
test.
G
I
used
it
for
some
crud
operations
in
a
small
applications
on
of
365
or
SharePoint
hawaii.
So
I
think
it
was
a
couple
of
months
ago
that
I
started
using
it,
and
I
immediately
saw
a
lot
of
value
in
it.
You
only
need
to
write
a
couple
of
lines
of
code
instead
of
30
or
50
lines
to
do
some
current
operations
yeah
and
a
couple
of
weeks
ago,
I
also
the
pull
request
to
support
or
either
add
support
for
web
books
in
sharepoint
online,
so
yeah.
A
A
C
A
Call
me
so
and
let's
move
still
to
waldeck,
so
we
haven't
actually
talked
with
waldeck
and
or
we
haven't
started
the
discussion
which
world
again
so
well.
They
obviously
has
been
doing
a
lot
of
SharePoint
framework
work
same
ship
on
framework
stuff
with
us
and
we'll
be
doing
that
in
the
future
as
well.
And
what
about?
What's
your
take
on
the
classic
statement
on
people
are
getting
kind
of
a
scared?
Is
this
all
of
the
development
in
SharePoint
only
in
JavaScript
now
so
only
to
crime
site
development?
A
F
F
So
we
learned
a
lot.
All
of
us
learned
a
lot
and
based
on
that,
we
came
to
a
new
point
that
actually
it's
not
that
bad
idea
to
split
the
everything
that
we
do
in
in
in
to
right.
So
on
Hannah
hand,
there
is
the
client
side
where
you
show
things
and
then,
on
the
other
hand,
you
have
to
have
still
the
engine
that
does
problem
processing,
business
rules
and
operation,
and
these
can
be
really
heavy
processing
long
on
expressions,
so
things
that
you
would
never
ever
do
in
browser,
because
that
might
be
closed.
F
That
might
fail
you,
the
my
break,
so
you
want
to
be
able
to
combine
the
power
that
the
clients
offers
you
with
terms
of
create
react,
reactive,
responsive
UI,
and,
at
the
same
time
you
want
to
be
sure
that
everything
that
you
build
the
process
are
are
integer
right.
So
the
the
data
is
correct,
that
that
does
not
break
that
your
workflows
process
and
operations
are
run
the
way
they
are
supposed
to.
So
you
actually
see
that
things
emerge
like
slope.
F
F
You
have
the
client
that
becomes
more
dynamic
and,
on
the
other
hand,
we
have
more
and
more
need
for
complex
processing,
ensure
that
it
runs
that
it
scales
that
it
supports
the
demands,
the
peaks
that
we
have,
that
that
we
can
have
in
usage,
yeah,
so
I
think
that's
the
direction
Deb
yeah
loyalton.
So.
A
F
A
F
A
I
think
we're
finally
getting
there.
That's
the
promise
of
the
future
or
has
been
for
years.
Yes,
so
we're
finally
getting
there,
and
whenever
we
get
the
modern
theme
sites,
the
modern
least
experienced
a
stone
from
the
citizenship
on
2016.
That's
gonna
help
on
that
as
well,
so
we
will
get
a
parity
between
the
sharepoint
online
and
on
Chrome,
even
though
online
is
evolving
months
faster
anyway
in
the
future
as
well.
So.
C
F
F
F
And
I
guess
that
at
sample
you
want
to
scale
right,
because
there
is
more
demand
more
use.
We
see
that
I
think
every
other
week
or
a
month.
You
share
the
numbers
like
how
the
program
and
and
everything
that
the
whole
team
built
grows
and
you
we
only
see
that
grow
and
grow
and
grow
more
right
right.
So
with
that,
you
can
imagine
that
the
demand
increases.
There's
more
need
for
more
features,
more
support,
more
questions.
So
do
you
have
any
plans
around
that
how
to
facilitate
that
growth?
I?
Would.
A
Say
that
the
number
one
way
to
facilitate
that
crow
is
it's
really
to
get
the
internal
and
external
community
more
closer
in
World,
delicate
and
make
sure
that
we
have
a
group
of
trusted
people
who
can
help
us?
That's
really
hard
is
quite
arena.
Get
more
MVPs
more
closely
involved,
try
to
figure
out
a
way
how
we
can
scale
the
coordination
as
well.
A
For
me
and
I
would
say
that
the
internal
in
Microsoft,
we
need
to
make
slightly
more
investments
on
the
initiative
as
well,
because
we're
running
out
of
time
to
coordinate
daily
BS
are
highly
interested
on
getting
more
closely
involved.
Internal
organizations
who
want
to
be
involved,
and
so
number
one
thing
is
actually
crow.
The
internal
commitments
from
sharepoint
engineering
maybe
scale
us
could
be
a
tree.
Persons
in
the
who
are
leading
to
BMP
well
in
quotes,
leading
because
we
don't
actually
lead
the
native
initiative,
leads
itself
or
with
together
with
community
but
coordinate
those
actions.
A
A
F
A
A
But
hopefully
you'll
find
the
discussion
interesting.
We
didn't
have
any
video,
we
didn't
have
any
demos,
but
this
was
more
around
discussion
across
the
table
on
the
future
or
on
the
future
of
SharePoint
customization,
so
we'll
come
on
will
absolutely
come
up
with
a
new
web
cast
again
sooner
or
later,
thanks
for
listening
and
buy
buy,
buy.