►
Description
Recording of SPFx and JavaScript development in SharePoint Community Call from 29th of March. Topics include updates from SharePoint engineering on SPFx, latest on PnP JS Core, Office 365 CLI and Reusable SPFx controls.
You can download an invite to this bi-weekly call from https://aka.ms/spdev-spfx-call.
A
Welcome
to
the
shipment
framework
and
JavaScript
special
interest
group
call-
and
this
is
the
bi-weekly
sink
around
the
shipment
framework
and
the
client-side
development
topics.
My
name
is
Wesley
Warren
I'm,
a
Senior
Program
Manager
for
SharePoint
engineering.
Typically,
this
particular
call
would
be
led
by
Patrick
Rodgers,
but
he
is
actually
in
a
plane,
so
he
has
a
valid
excuse
not
to
lead
this
course
so
he's
flying
back
from
the
Richmond
from
Redmond
back
to
his
home
somewhere
in
North.
America.
Remember
worried
about
now.
A
So
welcome
everybody
on
this
one-
and
this
is
the
bi-weekly
special
interest
group
cork
weekly,
explaining
what
this
is
all
about,
because
we're
always
getting
new
people
on
this
course
as
well.
So
this
special
interest
group
call
is
all
around
the
latest
on
SharePoint
framework
talk
about
the
sharepoint
framework
and
client-side
development
and
also
the
related
topics.
I
would
ask
people
to
remember
to
mute
themselves
when
you're
calling
on
this
call,
because
otherwise
we
will
have
quite
a
lot
of
audio
background
noise.
Now
we're
talking
about
the
SharePoint
framework
with
DES.
A
We
will
answer
to
your
questions.
If
you
have
anything
on
that,
I
window
will
talk
about
BMP,
jeaious
libraries,
and
we
need
to
actually
update
this
line
because
we
always
talk
about
also
office
365,
CL,
I
shared
my
framework,
reusable
components
and
controls,
and
all
of
that
stuff,
so
anything
related
on.
Let's
say:
JavaScript,
driven
development
to
what
SharePoint
ice
talked
about
within
Disko.
A
We
do
have
another
bi-weekly
call,
which
is
happening
at
the
same
time
on
thursdays,
where
we
talk
about
more
on
into
end
solutions
and
also
at
the
provisioning,
BMP
powershell
and
all
of
that
kind
of
stuff.
So
you
can
choose
if
we
want
to
join
all
of
these
course,
which
is
quite
a
lot
of
stuff
and
to
join
and
follow,
or
you
can
decide
to
follow
only
on
SharePoint
framework
or
only
on
provisioning
or
only
on
monthly
basis.
So,
there's
multiple
options
to
stay
in
touch
within
the
SharePoint
community.
A
Now,
today,
are
we
gonna
talk
about
a
few
engineering
updates
on
the
SharePoint
framework
and
I
have
some
news
new
things,
what
we
are
being
releasing
a
related
on
our
documentation
side
of
the
story
as
well,
then
we'll
do
a
quick,
intro
or
quickly
run
through
on
the
status
around
the
BMP,
J's
client
libraries.
So
what
has
happened
over
there?
A
We'll
talk
about
office,
365
CLI,
while
the
case
on
a
call
to
actually
cover
that
with
the
live
demo
so
in
office,
365
CLI,
that's
quite
a
lot
of
new
stuff
actually
available
so
well,
that's
gonna
demonstrate
some
of
those
and
then
we'll
have
a
quick
slide
on
the
BMP.
Reusable
client
controls.
Let's
talk
about
them
as
well.
A
So
what
has
changed
there
since
the
previous
call,
which
we
have
two
weeks
ago
and
then
we'll
have
some
demos
so
or
say
the
first
one
is
not
a
demo,
and
please
please,
please
do
remember
to
knit
yourself
this
again
a
few
people
with
a
background
noise
coming
in
so
there
we
go
quickly
and
there.
So
there
we
go
so
the
first
one
on
the
demo
section
is
around
SharePoint
framework
deployment
options,
so
we'll
cover
the
different
deployment
options.
What
we
have
for
SharePoint
framework-
and
this
is.
A
Explaining
what
is
a
tenant
deployed
solution
versus
what
is
the
site-specific
deploy
solution,
how
the
site
collection,
app
catalog
impacts
on
that
one?
And
how
do
you
light
up
your
ship
and
framework
customizations
within
sites?
And
then
it's
it's
more
around
discussion.
I
have
slides
I'm
not
going
to
do
a
live
demo
on
that
one,
because
I'm
pretty
sure
that
we
will
run
out
of
time
if
I
would
do
a
live.
A
Demo
I
tend
to
take
too
much
time
on
these
things
anyway,
and
then
we
have
a
live
demo
from
polar
around
automated
builds
for
SharePoint
framework
solutions
and
Visual
Studio
online.
This
relates
on
one
larger
projects
which
we
are
doing
related
on
SharePoint
framework.
So
we
can
actually
talk
about
that
one,
and
during
that
section
and
one
more
time,
please
please
please,
please
remember
to
meet
yourself
when
you
are
joining
on
this
course,
so
we
don't
actually
have
to
meet
yourself
forcefully
on
their
on
their
and
windows.
A
Now,
let's
actually
get
done
going
so
before
we
go
to
the
actual
to
a
big
just
when
I'm
a
pinpoint
this
one
and
if
you
aren't
interested
on
participating
on
this
community,
will
talk
about
these
options
slightly
detailed,
actually
on
the
phone
as
well.
But
there
are
multiple
different
options
getting
more
closely
involved
with
it
being
a
SharePoint
community.
So
you
can
absolutely
demo
or
do
a
live
demo
in
this
course
around.
A
If
you
build
something
on
SharePoint
frameworks,
that
would
be
brilliant
because-
and
it
doesn't
necessarily
have
to
be
something
which
has
been
shared
open
sourced
in
a
key
table.
It
could
be
you're
really
awesome
solution
which
you're
you
are
planning
to
potentially
sell
to
somebody
or
whatever,
just
to
demonstrate
the
pattern
and
explain
how
it
has
been
built.
A
If
you
have
time
if
you're
willing,
if
you
want
to
share
if
you
want
to
share
others
and
what
you're
doing
contribute
on
a
keypad
also,
you
can
demonstrate
SBP
and
be
chased
in
a
project,
PM,
peaches
or
other
technologies
related
on
sharepoint
favor,
and
please
please,
please
remember
to
mute
yourself
this
time.
This
is
really
difficult
for
some
reason.
When
getting
all
the
time
go
out
of
background,
no,
it's
never
go
and
then
provide
feedback.
A
So
if
nothing
else,
please
let
us
know,
what's
isn't
from
your
perspective,
isn't
quite
up
to
date
or
something
something
which
we
can
fix
from
a
Microsoft
side,
and
we
will
fix
that
sooner
or
later.
Please,
please,
please,
give
us
feedback
so
we're
able
to
address
your
gaps
related
on
SharePoint
development.
Now,
let's
actually
go
to
the
SharePoint
framework,
section
I
actually
have
quite
a
few
slides
here
and
there's
some
new
development
related
on
assets.
What
have
we
been
doing
and
also
new
stuff
which
I
wanted
to
go
through?
A
So,
first
of
all
we
have
now.
This
hasn't
been
yet
even
shared
in
social
media.
It
we
have
a
new
SharePoint
development
community
pages,
so
we
kind
of
are
gradually
moving
to
a
different
location.
If
you
go
a
kms
SP,
deaf
community,
you
will
be
landing
on
the
Deaf
documents
or
documentation
site,
and
we
have
two
community
in
the
table
of
content
on
the
navigation
from
here.
You
can
actually
find,
for
example,
details
along
the
shipment
community
cause.
What
what
are
we
covering
in
them
contribution
options
for
sharepoint
development,
documentation,
samples
and
other
assets?
A
You
can
find
a
list
of
open
source
projects
and
also
clarification
on
what
other
SharePoint
repositories
in
Akita.
So
what
they
are
for
this
is
now
went
live
earlier
today.
So
this
is
super
super
new
stuff,
so
we're
looking
into
still
polishing
in
the
information
there
and
feel
free
to
submit
any
pull,
requests
or
suggestions.
If
any
content
is
missing
from
there
good
but
anyway,
so
super
curious
on
on.
How
do
you
do
usefulness
of
this
stuff
as
well?
A
The
second
thing
which
went
live
in
the
social
media
I
think
yesterday
or
day
before
yesterday,
I'm
not
sure
if
you've
found
and
noticed
this,
we
have
now
enabled
to
download
a
PDF
option
in
the
SharePoint
abducts
and
which
is
there
for
those
who
need
to
have
an
offline
version
of
the
documentation.
So
there's
quite
a
lot
of
people.
A
Typically
this
this
some
people
are
saying:
why
would
you
have
a
PDF
download
option,
but
there
is
an
areas
in
the
world
where
the
network
connectivity
isn't
super
reliable
or
when
you're
flying,
for
example,
across
the
world
in
a
plane.
It
might
be
useful
that
you
have
a
PDF
version
of
the
documentation,
so
you
can
actually
download
that
it
is
working.
Surprisingly,
fast
I'm
not
actually
100%
sure
on
the
tech
behind
of
this,
it
is
a
service
which
is
available
in
the
dr.
Marcus
come,
but
you
basically
are
getting
the
full
copy
of
the
dr.
A
maestro
from
SharePoint
deaf
documentation
as
a
PDF
version.
It's
not
really
made
super
optimal
from
a
table
of
content
perspective,
but
at
least
you
have
a
full
version
which
you
can
read
in
offline
offline
way
now
other
stuff,
we
went
live
with
this
one
yesterday.
Actually,
so
we
do
have
a
new
ship
one
development
for
developer
portal
available
in
the
office
new
well
as
part
of
the
office
new
development
office
portals.
So
SharePoint
is
one
of
the
fellows
in
here.
If
you
go
a
kms
s
PDF,
that's
probably
the
easiest
way
to
actually
see
this.
A
In
practice,
you
will
find
the
developer
portal,
where
you
actually
find
the
latest
news
or
on
SharePoint
development,
the
latest
videos
around
shape
and
development
and
the
sample
gallery
around
SharePoint
development,
which
is
super
super
exciting
as
well.
So
we
have
more
than
300
samples
available
for
you
and
a
search
tool,
so
you
don't
actually
have
to
go
to
the
key
top
and
trying
to
find
potentially,
if
somebody
has
done
something
on
a
user
profile.
No,
no!
A
You
can
actually
go
to
this
portal
and
you
can
then
easily
find
the
relevant
sample
for
you
there's
quite
a
lot
of
filtering
options
there
as
well,
so
you
feel,
for
example,
looking
at
react
based
customizations.
You
can
actually
feel
the
death
based
on
the
language,
and
this
is
once
again.
This
is
the
first
version
of
the
portal.
This
is
evolving
gradually
as
well.
So
feedback
is
absolutely
welcome.
I'm
gonna
show
this
one
in
practice
in
a
few
minutes,
but
super
excited
on
this
one.
A
Finally,
getting
this
one
out,
our
old
portal
was:
how
would
I
put
it
not
quite
up
to
date,
so
it's
good
to
get
this
up
to
date.
From
that
perspective,
now
what
else
new
news
from
an
engineering
side
or
from
a
marketing
ethnic
marking
inside
engineering,
sign
some
of
the
things?
What
I
repeat
in
all
of
this
course
is
the
documentation.
Please
please,
please.
First
of
all,
use
our
documentation,
akms
SPD,
air,
ducts
or
dos
that
my
stuff
that
comes
last
sharepoint
and
then
the
sharepoint
development
documentation.
A
This
is
really
meant
to
be
the
consolidated
platform
for
all
sharepoint
dev
topics.
Now
we're
still
partly
in
the
progress
of
killing.
Absolutely
everything
moved
over
and
and
let's
say,
and
the
active
documentation
moved
over
from
amnesty
and
do
some
resource
constraints,
but
we'll
get
there.
Maturity
of
the
active
documentation
is
already
in
the
doorstep.
My
circumcised
and
all
of
the
new
content
is
getting
in
here.
What's
really
cool
around
this
one
as
well.
A
Is
that
if
you
find
a
bug,
if
you
find
an
issue
or
if
you
have
a
suggestion
of
the
documentation,
you
can
actually
add
a
comment
which
will
be
then
actually
an
issue
in
a
key
top
list.
So
we
can
then
tree
us
that
in
the
engineering
and
fix
the
current
documentation
order,
based
on
your
comments,
so
please
please
please.
If
something
is
missing,
something
will
something
is
lacking.
There's
a
mistake!
Please
let
us
know
so
we're
able
to
fix
that
or
if
you
don't
agree
on
something,
what
we've
written
there.
A
Please
let
us
know
as
well
that
helps
us
on
evolving
the
guidance
and
please
please,
please
remember
the
meet
yourself
quite
a
lot
of
again
background
noise,
so
I'm
muting,
a
few
additional
people
who've
been
joining
there.
We
go
cool.
The
second
thing:
what
I
always
keep
on
these
slides
is
the
issue
list.
So
please
please,
please
again,
if
you
find
an
issue
you're
hearing
an
API
which
isn't
working
or
you're
using
SharePoint
framework
application
customizers
are
behaving
strangely.
Let
us
know
please
go
to
the
SPD
of
issues.
List,
create
an
issue
and
we'll
tree.
A
Ask
this
at
least
twice
a
week
in
the
engineering.
It
doesn't
mean
that
we
actually
fix
the
issue
right
away,
but
the
triaging
means
that
we
are
evaluating
your
submission.
We
go
through
and
prioritize
your
submission
and
we
assign
that
forward
for
the
engineering
people
to
actually
take
a
look.
So
really
really
super
important
for
us
to
know.
If
you
run
into
any
random
issues
in
SharePoint
Online
around
the
development
topics,
so
you
were
able
to
also
report
them
to
us,
so
we're
able
to
fix
them.
A
Our
official
support
in
SharePoint
Online,
unfortunately,
does
not
provide
support
for
any
development
topics
and
it's
it's
not
an
optimal
situation.
So
we're
trying
to
kind
of
resolve
this
by
using
this
issue
list
as
well,
because
you,
if
you
call
the
official
support,
they
typically
say
that.
Well,
we
don't
actually
provide
support
for
development
topics
and
then
the
question
is:
where
can
you
have
get
help?
Well,
you
can
get
help
from
the
community
or
if
it's
an
actual
potential
park
in
the
service.
Please
submit
an
issue
and
we'll
have
a
look
at
that.
A
Nothing,
not
quite
the
final
thing
before
we
go
to
the
demo
section
and
everything
else
getting
started
with
SharePoint
framework.
Tutorials
I
just
wanted
to
have
a
reminder
of
this
one
in
here,
because
obviously
there's
always
new
people
moving
into
the
ship
on
framework
SharePoint
framework
is
rapidly
rapidly
rapidly
growing
from
a
user's
perspective.
A
I'll
show
you
the
chart
in
a
second,
so
people
are
looking
into
moving
on
SharePoint
framework
and
if
you
are
not
familiar
of
the
SharePoint
framework,
we
do
have
up
to
date
getting
started
with
SharePoint
framework
tutorials,
and
we
keep
on
updating
this
like
food
for
the
tree
to
fall
times
in
a
year
to
make
sure
that
they're
up
to
date,
sure
the
written
format
is
always
the
most
up-to-date
version.
The
video
formats
are
getting
updated
slightly
well
three
to
four
times
in
a
year
as
well,
but
these
are
free.
A
These
are
available
for
you
in
the
written
format
and
the
video
format
as
well,
and
you
can
easily
then
understand
how
to
get
started
on
a
SharePoint
framework
development
so
and
if
there's
any
gaps,
if
there's
any
tutorials,
which
would
you
need
to
be
there,
please
let
us
know
so
we're
able
to
add
those
tutorials
in
our
catalog
for
the
future.
P
and
again,
we
have
some
background
noise.
Please
please,
please
remember
to
meet
yourself,
so
we
don't
actually
hear
and
the
background.
No,
it's
cool
moving
on
on
things
so,
on
the
SharePoint
framework
usage.
A
A
Is
this
actually
really
used,
and
the
answer
is
oh,
yes,
the
SharePoint
framework
is
super
super
widely
used,
so
I
do
not
have
permissions
to
show
you
the
exact
numbers,
but
this
will
show
you
the
learn
at
the
curve
and
the
adaption
curve
or
SharePoint
framework
from
last
August
until
actually
Tuesday
this
week.
There
is
a
small
data
gap
on
Sunday.
A
I
will
need
to
access
that
in
our
dashboards,
but
don't
mind
that
one,
but
what's
interesting
here,
is
that
if
you
have
a
look
on
the
growth
from
let's
say,
September
or
October
until
the
this
week,
we
kind
of
we.
The
usage
is
more
than
four
times
it
within
six
months,
and
the
growth
curve
is
basically
insane.
So
what
I'm
trying
to
do
with
this?
One
is
just
to
show
you
that,
if
you
are
in
between
of
should
I
actually
learn
to
do
SharePoint
framework
and
development
or
not,
the
answer
is
absolutely
people
are
using.
A
This
customers
are
using
this
customers
are
adapting
that
and
what's
cute
about
the
SharePoint
framework
is
that
it
is
and
based
on
industry
standards.
It
is
a
based
on
a
model
which
isn't
specific
for
SharePoint,
so
we
and
the
most
important
thing
we
as
a
Microsoft,
we
build
our
own
stuff
using
SharePoint
framework
as
well,
so
you
can
currenty
that
as
long
as
we
build
our
own
stuff
using
SharePoint
framework,
this
model
will
remain
and
we
keep
on
supporting
this
model.
A
We
keep
on
improving
this
model
as
we
need
it
for
ourselves
as
well,
so
super
important
thing,
Oh
a
lot
of
sites
and
lot
of
discussions.
So
let's
actually
talk
about
so
quick
update
on
the
SharePoint
development
roadmap.
You
probably
heard
about
this
one
already
in
the
past,
we
delivered
quite
a
lot
of
stuff
since
ignite
as
we
promised
to
do
in
ignite
since
September
2017.
The
next
big
announcements
will
happen
in
the
SBC
18,
so
in
the
20th
of
May
in
the
Las
Vegas,
the
SharePoint
Conference
2018.
A
That
is
our
spring
event
spring
event
or
spring
moment.
Where
we
will
then
say
what
are
the
things
what
we've
been
now
working
on
and
what
are
the
things
which
we
will
be
shipping
within
the
next
six
to
twelve
months,
but
I've
added
here,
a
few
things
which
were
already
in
here
also
in
a
week
ago,
which
is
more
planting
options
as
over
looking
into
introducing
the
font
option
for
modern
sites
and
modern
themes
within
this
spring
before
SPC,
and
also
there
will
be
more
site
design
actions.
A
So
one
of
the
decided
there
will
be
site
design
sections,
for
example,
for
installing
SharePoint
framework
solution
to
a
site
as
part
of
the
site,
design
getting
applied
on
the
site,
so
you're
able
to
then
automate
customization
deployments
as
part
of
the
site,
design
model
gute,
so
nothing
in
two
months
on
the
roadmap
side.
But
what
I
wanted
to
quickly
go
through
still
in
here
is
to
share
my
screen
and
quickly
reiterate
the
new
assets.
A
What
we
have
now
available
in
the
documentation
side,
and
also
in
the
auto
side,
so
you'll
have
a
better
recollection,
hopefully
around
the
stuff,
what
is
available
so
I'm
sharing
my
screen.
Somebody
needs
to
tell
me
when
the
screen
sharing
is
good,
so
you're
able
to
see
what
I'm
sharing
it's
loading
stuff
for
Ralph
and
while
doc
is
saying,
yes,
we're
good
to
go
and
let's
get
up
one
more.
A
Ok,
David
got
it
so
that
means
two
persons
from
a
108
got
it.
So
that
means
the
maturity,
probably
got
it
so
I
wanna
show
up
on
development.
So
basically,
if
you
go
dosed
up,
Microsoft
SharePoint,
I'm
gonna,
actually
one
more
time
shoulders
Doc's
that
my
stuff
that
comes
SharePoint.
This
is
the
replacement
for
MSDN
and
we're
moving
in
there
Mustaine
content
gradually
some
areas
slow
more
slowly
than
other
areas.
The
activity
documentation
has
been
already,
however,
moved
over
in
this
selection.
You're
able
to
then
select.
A
Are
you
looking
into
how
using
SharePoint
Server
or
are
you
a
SharePoint
Server
or
are
you
a
SharePoint
developer
and
obviously
we
are
shape
on
developers,
so
we
can
actually
go
to
the
developer
site
on
the
developer
site
and
yes,
I've
used
that
joke
quite
a
few
times
so
on
the
developer
site.
Now
we
have
this
new
item
in
the
left,
navigation,
which
is
called
community,
and
this
is
basically
replacement
off
the
old
old
SharePoint
BMP
age.
A
If
you
ever
run
into
that,
Bates
in
the
dev
tools
come
because
we
are
shutting
down
the
left
of
the
common,
replacing
that
with
a
new
portal
and
do
logical
reasons.
It
just
makes
more
sense
to
have
it
in
here.
If
you
click
the
community,
you'll
find
all
of
additional
information
around
the
community
or
SharePoint
developer
blog
posts,
videos,
Twitter
feeds
issue,
notes,
community
calls
and
getting
all
of
this
stuff,
so
you're
able
to
download
the
invites
which,
by
the
way,
this
particular
link
is
still
wrong
and
I
need
to
remember
to
fix
that.
A
I
was
supposed
to
fix
that
before
this
call,
but
anyway,
I'll
get
that
one
fixed
after
the
call
and
there's
also
betas
around
how
to
contribute.
This
is
a
question
what
we're
getting
all
the
time,
for
example,
how
to
contribute
on
the
on
a
sharepoint
community
if
you
are
willing
and
if
you're
interested
in
doing
so,
we
also
have
a
page
for
open
source
projects
underneath
the
SharePoint
deaf
communities.
Help
on
PNP
initiative.
Kids
are
preparatory
is
what
are
these?
What
are
they
for?
A
How
they
actually
work-
and
we
keep
on
evolving
to
messaging
here
as
well
and
then
there's
quite
a
few
links
around
other
topics
like
sharepoint
development
in
youtube
or
videos,
twitter,
tweets,
developer
forum
feature
requests
and
all
of
that,
so
this
way
you
have
a
one
location
from
where
you
can
find
all
what's
relevant
for
you
as
part
of
the
as
part
of
the
community
and
sharepoint
development
work.
Hopefully
it
will
be
used
more
and
more,
and
hopefully
you'll
find
this
one
useful.
A
If
you
don't
like
set,
please
go
to
the
to
the
individual
page
and
then
keep
documentation
feedback,
and
this
will
be
done
an
issue
in
a
key
tab
and
very
able
to
fix
or
change
or
add,
content
based
on
your
opinions
as
well.
Super
super
important.
Let
us
know
something
is
missing.
Something
is
wrong.
Please
let
us
know
that
you're
able
to
fix
that
cool.
A
The
second
thing:
what
I
wanted
to
show
quickly
is
the
new
SharePoint
developer
portal.
So
if
we
go
to
the
developers
of
Microsoft
that
come
slash
office,
let's
actually
go
there.
It
will
redirect
us
today.
En-Us
office
version
will
be
the
localization
versions.
I,
don't
know
at
this
point,
but
this
in
here
we
are
in
the
office
developer
portal
and
one
of
the
big
things
by
the
way
which
has
been
recently
updated,
is
the
developer
program.
If
you
need
to
have
an
office
365
tenant,
please
join
office
365
with
developer
program.
A
You
will
get
a
free
tenant
and
for
your
development,
which
is
pretty
cool
from
here,
we
can
then
refine
SharePoint
in
the
middle
apparently
and
in
the
shape
on
developer
portal.
We
can
then
find
what's
relevant
to
news,
what's
relevant
videos
for
SharePoint
and
also
what
is
the
code
samples
and
also
support
blocks
and
there's
additional
assets
here
as
well
now,
in
the
code
samples,
if
we
go
there,
we're
able
to
actually
interesting,
that's
not
a
code
sample
by
the
way,
so
I
need
to
again
report
some
little
small
issues
on
this
photo.
A
A
So
now
in
our
search,
we
can
actually
filter
the
sample,
SharePoint
resources,
the
SharePoint
and
then
we're
able
to
say
content
types
will
be
samples
in
our
case,
if
you
want
to
find
samples-
and
if
we
wanna,
for
example,
find
what's
relevant
for
react,
there's
eighty-one
samples
built
on
react,
and
these
are
actually
samples
which
are
in
Akita
on
a
quick
way.
Comment
on
the
Gary's
question
around
the
developer,
tenant
and
mr.
M
subscribers.
The
developer
tenant
is
actually
free.
A
It
is
not
time
limited
as
long
as
you
use
to
develop
return
and
for
developer
topics.
So
as
long
as
you
keep
on
using
the
developer
tenant
for
development
activities
like
during
development
on
a
SharePoint
framework,
you
will
actually
get
that
renewed
automatically,
which
is
super
cool,
so
what's
actually
driving
the
categories
in
the
sample
page.
So
this
one
in
here
on
the
left
side.
A
So
these
are
right
now
selected
by
certain
group
of
people
from
their
slightly
different
organization
than
our
SharePoint,
and
if
there's
any
feedback
around
these
selections
or
the
scenarios
or
the
languages-
and
we
need
to
add
more-
please
let
us
know
we
can
absolutely
add
additional
additional
selection
in
here
and
obviously
we'd
also
have
a
nice
search
tool
here.
So
let
me
actually
unblock
the
react
and
do
something
classic
and
the
user
profile
and
since
I'm
searching
user
profile,
I'm
actually
able
to
find
user
profile
related
samples.
Some
of
these
are
old.
A
Some
of
these
are
new,
but
I'm
able
to
find
what's
relevant
for
them
or
if
I'm
interested
on
react,
application
and
customizer,
and
there
we
go.
We
have
multiple
application,
customizers
built-in
react
and
that's
actually
critical,
because
it
used
to
be
quite
difficult
to
find
our
samples
from
a
key
table
because
there's
quite
a
few
of
them.
So
now
you
can
easily
find
these
things
and,
as
an
example,
this
one,
let's
say,
do
any
Q&A
chat
was
an
awesome
demo,
which
was
demonstrated
by
Rodrigo.
While
back.
A
You
are
then
redirected
to
the
github,
and
then
you
can
actually
access
the
sample
all
down
the
sample
or
learn
about
the
sample
and
learn
about
the
things.
So
super
super
useful
cool.
Let
me
go
back
on
slides
and
then
continue
on
other
stuff
and
wrote:
Rico
he's
happy
on
on
getting
and
mentioned
or
covered,
but
that
was
a
really
cool
sample.
So
please,
please,
please
have
a
look
on
that
great
work
from
Rodrigo
on
that
one.
A
So
let
me
flip
back
on
the
slides
and
see
what
else
we
want
to
actually
do
and
David
confirmed
that
it's
already
loaded
that
was
fast
or
opposite
loading.
Somebody
else,
please
confirm
one
more
time
so
exile
that
was
fast,
interesting
cool.
So
let's
do
a
quick
update
on
the
BMP,
TAS
client-side
library.
So
like
say,
Patrick
Rodgers
isn't
here,
Patrick's
is
really
the
person
who's
leading
the
BMP
chase
and
the
BMP
Chase
is
kind
of
evolving.
It's
just
quickly
clarifying
this
one
as
well.
A
A
If
you
are
familiar
with
REST
API
in
SharePoint
no
problems,
you
can
use
that
as
well,
but
this
one
helps
if
you,
if
you
want
to
use
kind
of
a
more,
how
would
I
put
its
managed
code
style,
fluent
API
style
way
of
accessing
information,
so
you
don't
have
to
remember
the
rest
api
is
you
can
actually
do
BMP
dot
work,
dot,
get
to
where's
the
list
and
and
that's
it.
The
main
changes
here
is
that
we
change
the
repository
name.
The
PM
pjs
is
in
the
BMP
organization.
A
There's
there's
going
to
be
announcements
on
that
one
slightly
later
in
the
future.
We're
doing
some
reorganization
of
our
samples,
but
p.m.
PJs
is
on
the
BMP
organization
and
the
BMP
chase.
Repo
has
been
renamed
from
from
come
on
from
the
BMP
as
PHAs
and
the
fact
that,
if
you
have
already
forked
this,
it
doesn't
actually
impact
you
github
is
super
super
super
smart
on
these
things.
So,
even
though
you
would
be
submitting
pull
requests
or
changes
back
on
the
old
URL,
github
is
actually
redirecting
that
to
the
new
URL
with
the
super
super
cool.
A
There's
a
CDN
and
support
is
in
the
works.
There's
a
weekly
beta
release
this
on
Friday,
so
Patrick
is
planning
to
release
a
new
version
on
Friday
this
week,
together
with
the
community
members,
change
lock
is
updated
regularly.
There
is
a
updates
on
the
roadmap
and
please
please
PLEASE
report
issues
on
this
one
as
well.
Bmp
github,
that
is
last
p.m.
peaches,
is
the
URL
and
documentation
for
this
one,
but
more
changes
on
this
one.
Obviously,
next
time
when
Patrick
is
also
available.
Now
the
next
topic
is
to
office
365,
CLI
and
I'll.
B
B
A
B
You
very
much
so
cui
is
a
cross-platform
command-line
interface
that
you
can
use,
no
matter
where
you
work
on
a
Mac,
Windows
or
Linux
to
manage
your
tenant.
We
support
different
things
like
manipulating
your
settings,
getting
files
creating
sites
creating
different
things,
creating
groups
we
even
support,
and
recently
we
added
even
support
for
the
Microsoft
flow.
So
in
other
words,
it
is
a
command-line
tool
that
allows
you
to
manage
the
settings
of
your
tenant
and
soon
one
day
we'll
have
more
will
expected,
but
that's
announcement
forward
for
them.
Recently
we
released
a
version.
B
One
point
point
zero,
basically
to
indicate
that
since
October,
when
we
started
the
work,
we
didn't
get
any
major
blockers
or
input
that
would
require
us
to
read
them
the
way
it
works.
So
with
that
we
thought
is
going
to
be
fair
towards
us
and
everybody
else
who
works
on
it
to
have
one
one,
one,
one
oh
and
basically
show
everybody
that
that
that
that's
July
is
going
to
work
that
way
that
that's
the
right
direction
in
a
few
days
time
we'll
have
new
version
version
1.1
and
probably
the
biggest
addition
to
it.
B
His
support
for
the
Microsoft
flow,
which
is
new
workload
that
we
added
and
we
thought
it
would
be,
a
good
idea
because
we
see
more
and
more
people
actually
using
within
companies
right.
So
we
want
to
give
you
the
ability
to
manage
these
flows
in
a
scripted
way
right.
You
can
build
scripts
with
with
with
Xilai
and
are
not
limited
to
only
browser
and
a
manual
management.
If
you
will.
B
B
We
added
the
ability
to
work
with
groups
improve
that
we
have
the
ability
to
get
configuration
of
the
site
classification
and
a
few
other
things
that
I
do
not
recall
and
I
cannot
see
because
I
see
sites
other
than
that
we
go
full
steam
ahead.
We
really
have
the
luxury
of
many
people
who
help
us
contribute,
either
with
the
code
or
feet
or
or
the
feedback.
B
So
we
really
appreciate
everybody's
time
and
effort
that
they
put
into
that
and
basically
brings
your
life
forward
to
be
a
more
powerful
tool
than
it
already
is
with
that
yeah.
If
you,
you
would
like
to
know
more
about
CLI,
please
go
to
aka
dot,
ms
all
3-6-5,
CLI
and
I.
Believe
for
everybody
else.
Except
me.
You
can
see
the
URL
on
your
screen
that
so
that's
a
yes!
B
So
that's
a
one
single
URL
for
you
to
go
to
and
in
there
you'll
get
the
manual
how
you
acquire
CLI
install
it
manage
it
updated
work
with
it,
basically,
everything
and
and
anything,
including
links
to
the
issue
list,
github
repo,
the
places
where
you
can
catch
us,
two
things.
So
it's
just
one
location
for
you
guys
to
go
to
and
have
all
the
info
you
would
like
about
sea
life.
B
A
Let's
actually
try
your
sharing,
and
there
was
a
question
on
now:
flour
around.
Is
this
the
new
powershell
just
to
clarify
that
one
again,
this
is
not
a
replacement
for
sharepoint
online
publisher
or
the
BMP
powershell,
and
actually
the
BMP
powershell
is
planned
to
be
cross-platform
pretty
soon
as
well.
This
is
a
just
an
option
on
the
tooling.
Some
people
prefer
to
see
a
live
way
of
doing
customers
and
management.
Some
people
prefer
powershell
style
of
ordering
management.
B
It
is
a
different
tool
to
same
end.
Yes,
exactly
alright,
so
with
that
speaking
of
about
the
devil,
let
me
start
the
CLI
by
running
all
three
six
five
and
then
we'll
bring
me
into
the
immersive
malware.
I
have
now
the
three
six
five
prompt
and
with
that
I
can
already
start
interacting
with
with
CLI.
B
Let's
start
with
connecting
to
the
azure
management's
service
that
that
that
exposes
the
this
API,
so
Azure
management
connect
with
it
I
will
get
a
URL,
and
for
that
we
use
the
all
of
device
code
flow
and
we
basically
log
in
in
browser.
The
benefit
of
that
is,
if
you
work
with
MFA
or
you
work
with
conditional
access
all
that
that
will
be
handled
by
aad
right.
B
So
you
can
use
that
you
can
apply
that
when
you
work
with
the
CLI,
so
here
I
am
signing
in
with
my
admin
account
I
go
back
to
the
command
line
to
my
shell
is
3
to
1
and
I'm
connected
and
I
can
confirm
that
by
running
a
sure
management
status-
and
here
in
here
you
can
see
that
I
am
connected
with
this
account
so
flow.
Has
your
management
flow,
you
always
start
with
environments
right
before
you
can
access
flows.
B
You
have
to
know
your
environments
and
you
can
get
them
by
saying
as
your
management
flow
environment
list,
and
that
will
give
you
the
list
of
all
environments
or
Michael
of
Microsoft
flow
environment
in
your
tenant.
Once
you
have
environment,
you
grab
its
name
and
then
you
say:
Azure
management
flow
environment.
Get
that
if
you
would
like
to
get
additional
info
about
the
environment
like
who
created
it,
who
is
the
owner
as
forth
and
so
on.
B
Now,
if
you
would
like
to
get
flows
use
also
a
dev
environment,
but
then
you
say:
Azure
management's,
flow
list,
environment
and
now
you'll
get
the
list
of
all
flows
in
your
environment.
Now
these
are
the
flows
that
I
own,
but
what,
if
I,
am
an
admin
and
I
want
to
see
all
flows
well,
for
that
I
can
say
as
admin
and
3
2
1
as
admin.
That
should
be
the
case
and
with
that
I
will
get
the
list
of
all
Microsoft
flow
flows
in
this
environment
and
not
only
the
ones
that
I
own.
B
In
this
case
they
are
online
because
I
am
the
only
account
there.
But
if
you
are
an
admin,
you
will
be
able
to
use
a
CLI
to
get
the
access
to
all
and
all
Mike's
of
flow
flows
in
this
environment
now
for
a
particular
flow.
If
you
would
like
to
get
more
info,
you
can
grab
grab
its
name,
which
happens
to
be
a
good,
and
for
that
you
can
say,
as
your
management
flow
get
a
name
and
then
we
also
need
to
need
to
have
an
environment
right,
because
a
flow
exists
inside
an
environment.
B
So
you
have
to
have
that
and
enter
and
there's
a
little
greatness
about
that,
and
here
you
have
the
basic
info.
But
if
you
would
like
to
have
more
info,
you
can
say:
output
Jason,
don't
worry
about
that,
and
there
you
go
right
so
with
that,
if
you
build
a
script
or
you
want
to
have
more
info
about
flow,
like
all
details,
activities
connections-
basically
that's
in
there-
you
can
get
that
from
the
CLI.
So
that's
a
perfect
way
for
you.
B
If
you
would
like
to
build
some
kind
of
automation
today,
when
we
record
this,
you
can
only
get
flows,
but
but
we
already
have
a
an
idea
on
roadmap
to
actually
be
able
to
export
the
flow
and
also
import
it
at
some
point
right.
So
you
can
expect
that
soon
then
want
one
that
you
will
be
able
to
use
CLI
to
actually
do
that.
The
kind
of
automation
with
that
I
give
it
back
to
Meza.
Thank.
A
You
thank
you
well
deck,
it's
good
to
see
how
this
is
evolving,
really
really
fast
as
clear
in
high
interest
on
on
helping
on
on
those
contributions
and
and
not
taking
anything
away
from
the
PMP
PowerShell
or
the
chip
and
online
power
shop,
which
no
doubt
is
used
widely
as
well.
So,
but
it's
it
again,
a
new
option,
a
new
way
of
doing
stuff.
Now,
on
the
demo
start
what
I
wanted
to
do?
We
still
have
20
minutes.
A
Oh
sorry,
SharePoint
framework,
reusable
components,
not
forgetting
these
ones,
so
on
these,
so
the
new
ones,
there's
a
new
version.
One
point
two
point
four
which
is
out,
and
this
is
around
enhancements
on
hiding
placeholder
title
on
small
zones.
So
when
your,
if
you
are
really
really
in
a
small
zone
or
in
responsive
or
a
smaller
device,
it
will
actually
hide
the
title
in
a
same
way
as
with
out-of-the-box
web
part
and
then
there's
a
fixes
on
the
iframe
handling
which
will
help
on
on
the
on
the
dialog
handling.
A
Sorry,
there's
fixes
on
the
iframe
and
dialog
handling.
Now
the
whole
point
of
the
reusable
SharePoint
framework
controls
is
that
these
are
open
source
ready
to
use
controls
from
the
community
for
the
community
under
the
umbrella
of
SharePoint
BMP.
So
we
from
engineering
we
are
looking
into
this
quality
of
these
controls.
We
are
not
right
now,
planning
to
release
out-of-the-box
SharePoint
framework
controls
as
an
open
source,
but
what
are
we
planning
to
do?
Is
harvest
our
web
pots
and
our
out-of-the-box
first
body
stuff
and
release
them
as
part
of
this
initiative.
A
So
basically
share
you
the
best
things.
What
engineering
has
done?
True,
the
PMP
you
want.
We
definitely
want
to
have
a
look
on
to
release
reusable
controls,
for
example,
from
your
property
panel
configuration
for
your
web
part.
They
are
super
super
super
useful
now
the
other
topics.
What
I
wanted
to
quickly
go
through
for
a
ten
minutes,
because
we
need
to
give
ten
minutes
for
Paulo
is
a
discussion
potentially
with
Waldeck.
A
So
what
they
can
ask
me
actually
ask
me
the
questions
as
needed
around
the
deployment
options,
and
this
is
a
round
deployment
options
on
a
SharePoint
framework,
so
how
to
enable
the
customizations
in
the
sides-
and
this
is
almost
like-
a
reiteration
of
some
of
the
webcasts,
what
we've
been
having,
but
since
we're
getting
more
and
more
developers.
Moving
on
to
the
SharePoint
framework,
I
think
it's
better
to
repeat,
rather
than
wait
or
assume
that
everybody
has
followed
up
on
everything
what
we
have
released
No.
A
B
A
B
A
Pod
framework
solutions,
internals
so
now,
there's
two
main
ways
of
getting
the
SharePoint
framework
solutions
deployed
on
your
tenant.
There's
there's
a
option
of
installing
the
solution
to
a
site
or
then
you
do
the
tenant
deployment
option
and
the
kernel
deployment
option
basically
means
that
your
customization
is
immediately
available
within
the
sites
whenever
it
has
been
deployed
to
the
app
catalog
on
the
the
alternative
option,
which
was
the
site
by
site
level,
installation
which
I
do
actually
have
a
slides
on
on
both
of
this.
A
It
means
that
you
need
to
explicitly
install
the
solution
to
a
site
before
it's
available
for
you.
So
you
as
a
solution
designer
or
an
architect
of
the
customization,
will
need
to
make
this
decision.
How
do
you
actually
enable
your
functionalities
to
be
available?
So
now?
Let
me
actually
go
a
few
slides
on
our
Volvic.
Ask
some
of
the
questions
now.
There's
two
main
differences.
So
there's
two
main
component
sets
in
SharePoint
framework
there's
the
web
pods
and
they
basically
have
an
end
user
driven
a
picker.
A
So
whenever
a
bit
part
is
getting
deployed
on
a
site,
it
will
be
then
available
in
the
web.
Part
picker
easy
to
deploy
it
using
a
tenon
scoped
option
or
in
the
site
level
it
doesn't
really
matter
the
web
part
selection
will
be
all
the
custom
web
part
will
be
available
in
the
web.
Part.
Bigger,
SharePoint,
favorite
extensions
are,
however,
slightly
different
that
these
are
technically
available
on
a
site,
but
because
there's
no
UI
to
actually
enable
them
for
end-users.
A
That's
why
they're
not
automatically
lighted
up
in
the
site
level,
so
you
need
to
do
explicit
additional
steps
to
make
them
actually
available
in
the
site
level
and
let
me
actually
quickly
go
through
or
we
can
actually
start
asking
questions
one
after
this
following
following
slide.
So
this
is
the
option
number
one:
how
do
I
get
my
shape
and
framework
solution
activated
on
a
site
level,
option
number
one
site
by
site:
the
installation
of
share
one
framework
solution.
A
A
Think
December
and
it
so
you're,
basically
all
be
able
to
automate
this
one
and
what
it
also
means
that
the
web
part
as
an
example
when
it's
the
solution,
which
is
installed
on
a
site
if
it
contains
a
web
part
in
the
web
part,
will
be
immediately
available
in
the
web.
Part
picker,
but
the
extensions
are
not
so.
The
extensions
will
need
to
be
explicitly
light
up
in
the
right
component
in
the
SharePoint
site,
and
for
this
one
you
can
use
feature
framework
or
you
can
use
AP
is
to
make
the
tab
now
well
deck.
A
No,
no,
no
and
there's
a
good
question.
Yes,
sorry,
sorry,
there
was
a
good
question
in
the
conversation
around
site
collection,
app
catalog
can
I,
have
a
site
collection,
app,
catalog
and
use
the
tenon
deployed.
Option
answer
is
yes,
we'll
get
back
on
that
one
in
a
second
as
well,
did
I
actually
cover
all
of
the
things
already
or
should
I
go
to
the
tenant
deployed
option,
and
then
we
can
have
a
discussion
either
way.
A
Deployment
option,
apparently
animation
is
slightly
well,
it's
not
too
much
stuff,
so
the
tenant
scope
deployment
option
does
support
both
tenants,
app
catalog
or
site
collection,
app
catalog,
and
what
it
means
is
that
when
you
are
installing
a
SPF
X
solution,
SP
pkg
file,
either
to
the
tenant
level
or
inside
collection
level.
That
solution
is
automatically
enabled
in
the
scope
where
you
actually
off
to
attack
a
catalog.
So
if
you
boot
the
solution
in
a
tenant
app
catalog,
it
means
that
solution
is
enabled
poof
automatically
across
the
whole
tenant.
A
If
you
put
the
solution
in
a
site
collection,
app
catalog,
it
will
be
enabled
across
all
of
the
sites
within
that
site
collection.
So
if
there's
multiple
sub
sites,
it
will
be
done
available
in
all
of
the
sub
sites
and
again
the
same
rules
apply.
If
it's
a
web
part,
it
will
be
automatically
in
a
web
part
picker.
If
it's
an
extension,
you
need
to,
however,
again
explicitly
light
up
the
functionality.
So
how
do
we
make
the
extensions
being
visible
automatically
using
the
tenant
level
option?
A
As
an
example,
you
put
the
solution
in
the
tenant
app
catalog
and
then
you
run
code.
You
explicitly
go
to
the
site
level
and
say
site
dot,
use
a
custom,
action,
dot,
add
and
you
add,
a
user
custom
action,
which
then
has
a
reference
to
the
clients
and
component
ID,
essentially
the
ID
of
the
solution,
and
it
will
light
up
the
extension
automatically
for
that
one
I
do
not,
unfortunately,
have
exact
steps
I
slightly
run
out
of
time
on
on
explaining
the
whole
setup
of.
A
Now,
if
your
business
scenario
means
that
hey,
we
need
to
have
the
exact
same
footer
or
hitter
in
all
of
our
site
collections
across
the
whole
tenon,
then
you
absolutely
use
the
term
scope
deployment
option
and
then,
as
part
of
your
site,
provisioning,
for
example,
in
your
site,
design
or
in
your
whatever
custom
provisioning.
You
are
then
enabling
that
extension
to
be
available
whenever
the
site
is
getting
created.
Hopefully
that
again
makes
sense.
B
B
B
In
XML
they
are
stuck
inside
a
package,
so
every
single
time
it
will
be
exactly
the
same
setup.
But
if
you
imagine
that
you
would
like
to
have
extension,
that
I
will
that
either
shows
different,
color
or
location
or
anything
else.
Then,
when
registering
it
on
their
separately
on
on
different
site
through
a
customer
action,
you
can
specify
properties
when
you
light
it
up
on
that
particular
site
for
for
that
site.
So
that
gives
you
that
extra
ability
to
do
that
that
you
don't
get
when
you
would
use
XML
absolutely.
A
Absolutely
and
that's
why
we
have
the
clients
and
component
properties
option
in
the
user
custom
action,
so
we're
able
as
an
example
in
the
user,
custom
action
or
in
the
field
object
of
a
SharePoint,
so
we're
able
to
parameter
size
that
instance
to
be
behaving
slightly
differently,
for
example
the
background
color
in
the
case
of
header
or
footer.
But
it
could
be
much
more
complex
in
area
as
well.
A
Yes,
but
I
think
what
we
need
to
do
in
the
future
and
I'm
more
than
welcome
and
getting
that
feedback
from
the
people
in
the
call
as
well.
Should
we
have
more
detailed
discussion,
an
architectural
discussion
around
these
solution
patterns
in
this
course,
rather
than
doing
too
many,
always
individual
demos
on
individual
samples.
So
are
you
interested
from
a
community
called
perspective
on
and
having
slightly
more
detailed
discussion
or
Kadesh
or
discussion
when
to
use
which
option,
which
would
then
be
supporting
your
things?
Okay,
yessssss!
A
So
that's
what
we
were
thinking
as
well,
we'll
just
need
to
make
sure
that
we
spent
and
Buch
enough
time
on
making
sure
that
we
cover
the
topics
in
a
more
detailed
or
a
detailed
enough
way
in
this
course.
Now
Paulo.
We
don't
want
to
actually
we
we
know
that
you
prepared
your
demo.
We
know
that
you
have
a
cool
demo
around
doing
build
automation,
visitors
to
the
online
for
SharePoint
frameworks
projects,
so
take
it
away.
Yeah.
C
Continuous
delivery
approach,
so
just
a
few
words
about
the
idea
and
then
I
will
switch
to
the
demo
environment,
sorry,
but
for
my
bad
voice,
but
I
have
a
little
bit
of
a
cold.
So,
first
of
all,
let's
assume
that
you
have
a
SharePoint
framework
solution
in
which
you
have
multiple
clients.
That
would
part
and
client-side
extensions,
and
you
want
to
automate
the
provisioning
of
that
solution,
which
is,
for
example,
build
and
minutes
from
a
source
code
and
project
management
perspective
using
github,
and
they
get
flow.
That's
what
we
do.
C
For
example,
in
a
what
big
project
we
are
working
on
as
PMP
team
to
create
a
new
demo
which
will
be
available
in
the
upcoming
month
for
the
whole
community.
So
we
have
a
project.
We
have
multiple
people
working
all
over
the
world.
We
have
keith
urban
in
the
backend
for
source
code
management
and
we
want
to
leverage
the
PMP
provisioning
engine
for
the
provisioning
of
the
information
architecture
of
the
solution,
as
well
as
for
the
deployment
and
provisioning
of
the
customizations
built
with
SPF
x.
C
Levering
the
ALM
API
is
that
we
have
a
now
in
SharePoint,
Online
and,
of
course,
in
PMP
as
well.
So
we
decided
to
use
as
an
example
for
the
community
and
for
the
enterprise
companies
to
use
VSDs,
which
is
the
team
services
for
computer
integration
and
continuous
delivery
to
automate
the
delivery
of
the
solution,
targeting
a
developer
tandem
that
we
use
for
testing
purposes,
as
well
as
being
able
to
prefer
reconfigure
a
provision
completely
from
scratch.
C
The
target
side
or
the
target
page,
is
modern
pages
that
we
have
decide
whenever
there
is
a
new
merge
in
the
dev
branch
of
the
repository
in
which
we
store
the
source
code
of
the
solution,
so
that
we
can
almost
on
a
daily
basis,
see
how
the
project
is
evolving
and
now
is
moving
forward.
So,
let's
say
just
to
give
you
the
context.
Let
me
switch
to
first
of
all
Visual
Studio
code,
and
let
me
show
you
that
what
I'm
going
to
share
with
you
is
based
on
joint
forces.
C
C
Comment
like
that.
We
have.
We
try
to
figure
out
if
the
heart
we
need
to
install
in
the
target
tenant
is
already
there
and
if
it
is
there,
we
remove
it
in
order
to
being
able
to
update
it
and
to
replace
it
with
a
new
one
or
if
it
is
not
yet
there.
We
simply
need
to
add
a
new
solution
in
the
app
catalog
and
right
now
using
the
ulema
TI,
which
are
get
the
tentative
catalog,
which
is
the
only
one
we
can
target.
C
Hopefully,
in
the
future
we
will
have
the
LME
PR
able
to
target
the
site
collection
of
catalog
two,
then,
once
we
have
done
that,
we
also
play
around
the
hub
sides
and
stuff
like
that,
and
then
we
apply
a
provisioning
template.
And
what
is
interest
interesting
here
is
that
we
have
a
first
provisioning
template,
which
is
this
solution:
dot
XML,
which
will
simply
use
the
syntax
that
we
have
in
the
schema
in
the
PMP
praveen
schema
to
install
in
the
App
Catalog
or
package
to
configure,
if
needed,
a
content,
delivery
network.
C
This
is
a
new
feature
which
will
come
out
with
the
next
master,
merge
of
the
provisioning
engine
and
then
at
the
template
level.
We
use
the
application
lifecycle
management
element
to
provision
in
our
package,
so
on
HP
pkg
in
the
target
site,
let's
say
that
we
have
a
portal
XML
template
provision
interpreter
which
would
provision
a
bunch
of
stuff,
including,
for
example,
at
the
very
end
of
the
template,
a
bunch
of
custom
actions
which
will
be
client-side
extensions
that
we
created
in
SDF
X.
C
So
we
want
to
automate
this
process
through
a
automated
build
up
in
VSDs.
So
let
me
switch
to
VSDs
here
we
have
a
project
in
VSDs
and
yeah.
I
have
a
builder
a
custom
builder,
which
is
based
on
a
set
of
steps
and,
first
of
all,
whenever
you
want
to
automate
the
provisioning
and
continuous
delivery
of
your
solutions
on
a
target
environment.
If
it
is
a
sharepoint
frame
or
solution,
you
will
need
to
have
the
NPM
install
command
executed
to
install
all
of
the
packages.
C
You
will
have
to
build
and
prepare
the
package
and
you
will
have
to
upload
the
package.
For
example,
through
PMP,
a
provisioning
engine
is
like,
as
we
do
in
the
powershell
script,
that
I
showed
you
before.
So
what
we
do
in
the
build
action
is,
first
of
all,
thanks
to
a
feedback
from
baalbek,
we
install
the
latest
version
of
nodejs,
because
with
this
one
we
can
speed
up
quite
a
lot
the
NPM
install
stage.
In
fact,
we
install
the
version
8
point
the
ex
of
mojo,
yes
and
right
after
that.
C
We
simply
need
to
make
it
possible
to
have
the
PMP
PowerShell
extensions
available
in
the
host
surrounding
the
build
process.
In
order
to
do
that,
we
installed
a
new
get
support
for
the
current
user,
as
well
as
the
support
for
the
model.
Sharepoint
MP
powershell
online,
still
for
the
current
user,
and
you
can
find
much
more
information
about
this
approach
in
the
document
which
is
in
the
wiki
area
of
PHP
powershell
and
which
was
written
by
Vincent
in
the
community
and
Thank
You
Vincent
right
right.
C
After
that,
we
can
now
run
npm
install,
which
is
not
our
task
of
VSDs.
So
we
can
install
all
the
packages
that
we
need-
and
this
will
include
also
the
gulp
package,
for
example,
so
that
later
on
with
another
powershell
script,
which
is
a
just
an
inline
script,
we
can
run
gulp,
which
is,
as
you
can
see,
available
in
a
nod
models
of
the
current
folder,
which
is
the
folder
of
our
solution.
C
In
the
host
running
the
VSDs,
the
build
tasks
we
can
just
do
the
GALT
bundle
ship
and
the
guard
bundle
package
solution
ship
so
that
we
will
have
the
SP
pkg
file
ready
to
be
uploaded
onto
the
target
environment.
And
once
we
have
done
that,
we
can
execute
the
nother
PowerShell
script,
which
will
be
deploy
ps1
file,
that
I
showed
you.
C
Actually
it's
a
slightly
different
one
deploy
BSP,
which
is
slightly
different,
because
we
need
to
provide
a
set
of
credentials
to
authenticate
against
the
target
environment
and
we
get
those
credentials
from
a
couple
of
variables
that
we
get
as
input
parameters
for
this
script.
And
then
we
just
call
the
deploy
ps1
script
that
we
have
and
through
the
script
we
do
the
real
magic.
C
Those
variables
are
defining
the
variables
of
the
builder
definition
and,
of
course,
we
have
a
password
which
is
well
protected,
as
well
as
the
user
name
that
we
use
to
automate
the
build
process
process.
Moreover,
we
configure
them
the
Builder
to
be
enabled
for
continuous
integration
so
that
whenever
there
is
a
new
merge
in
the
target,
they
have
a
branch
when
we
execute
a
full
delivery
of
the
solution,
avoiding
to
execute
multiple
deliveries
happening
while
one
is
already
happening.
So
with
this
flag,
Abed
changes
will,
while
a
build
is
in
projects.
C
Well,
if
there
is
already
a
build,
proper
progress
running,
we
avoid
queuing
much
more
requests
if
there
are
much
more
merges,
but
we
wait
for
the
build
process
to
complete
before
handling
any
new
emerge,
just
to
avoid
overloading
the
hosts
and
the
visual
studio
team
services
process.
Let's
say
that
here
is
just
the
outcome
of
a
builder
which
is
which
has
been
already
executed
a
few
hours
ago,
because
it
takes
about
5
between
six
minutes,
as
you
can
see
to
do
the
full
process,
but
here
we
do
all
the
stuff.
C
C
We
are
ready
to
execute
the
provisioning
through
powershell
of
the
solution
using
the
PMT
provisioning
engine
and
I
think
that's
a
really
useful
way
of
working,
because
we
can
have
full
control
on
the
deployment
process
and
we
never
a
fully
automated
deployment
process
targeting
the
dev
and
testing
environment
and
basically,
on
the
daily
basis.
We
can
do
proper
testing
of
the
solution.
That's
it
was
a
quite
a
short
sharing
of
ideas
and
experiences
in
a
real
life
project
that
we
are
working
on.
I
can
give
you
back
the
mic
design.
A
Excellent
Thank
You
Boris,
oh,
and
there
was
a
questions
around
sharing
all
this
stuff
already,
potentially
on
the
build
automation,
so
Vincent
actually
has
excellent
stuff
on
the
build
automation.
I
know
that
some
other
people
have.
This
is
based
on
Vincent
and
Helios,
and
Paolo's
thinking
and
Ervin
has
been
involved
and
a
few
other
people.
Now
we
are
potentially
getting
this
one.
The
build
automation,
guidance
out
earlier.
We
are
actually
building,
as
you
can
kind
of
guess,
from
a
name
of
the
of
the
build
and
the
name
of
the
of
the
story.
A
We
are
building
end
to
end,
let's
say
demo
portal
case
where
we
are
demonstrating
the
limits
of
the
modern
capabilities
building
a
custom
portal.
Now
that
one
will
still
take
quite
a
few
weeks
to
get
completed,
because
we
can't
share
you
just
the
code,
because
it
would
be
too
many
questions,
so
we
need
to
first
give
first
complete
the
code
first
complete
the
solution
and
complete
all
the
other
stuff,
and
then
we're
able
to
share
your
and
the
documentation
and
share
you
the
story.
A
Modern
experiences
in
SharePoint
Online,
but
that's
a
teaser,
you
probably
want
to
be
in
built
or
well
definitely
an
SBC
or
European
collaboration
summit
and
to
get
more
details
on
this
one
quick
question:
we
are
three
minutes
on
the
on
the
out
of
the
clock:
Vincent
I
think
I
can
loop
in
Paolo
if,
on
the
email,
discussion,
I
know
that
Paolo
probably
doesn't
have
a
share
his
email
directly
in
I
window,
because
then
there's
too
many
emails
flying
around
I
know
for
a
fact
that
my
inbox
as
an
example
is
complete.
Mess.
A
John's
question
is
the
LM
functionality
MP
MP
polish
of
working?
It
should
be
working.
We
are
using
that
as
part
of
that
deployment
option
as
well.
If
there's
any
issues,
please
do
report
an
issue
on
the
PMP
sites
core
repository
around
that
one.
So
we're
able
to
have
a
look
thanks,
John
cool
I
think
that's
it
for
this
one,
we're
four
minutes
out
of
out
of
our
time.
Sorry
for
that
one,
and
that
lets
play
me
on
that.
A
So
that
was
me
taking
too
much
time
on
the
intros
and
everything
else,
but
thank
you
for
your
feedback.
Thank
you
very
back
around
the
future
way
of
sharing
more
and
more
solution,
design
guidance
as
well
here,
which
will
definitely
do
starting
already,
potentially
from
next
week
from
a
provisioning
and
trending
guidance.
Perspective.
You'll,
see
more
on
that
in
our
agenda.
We're
trying
to
boost
your
tender
always
24
hours
before
the
session
latest,
but
every
single
Thursday
well
bye,
weekly
Tuesday's.
A
We
have
to
SharePoint
framework
one
and
then
why
weekly
we
have
the
general
shape
on
day
one
and
then
we
have
monthly
community
calls
coming
up
as
well,
but
thank
you,
everybody
for
joining
Thank,
You
Paula
for
the
demo,
Thank
You
bollock
for
the
demo.
Thank
you
from
all
of
you,
your
valuable
input
on
the
iron
window.
Please
please,
please
go
to
the
issue
list,
give
us
feedback
ping
us
in
social
media.
Let
us
know
if
something
is
wrong,
so
we're
able
to
help
you
on
your
journey
in
the
SharePoint
development.