►
From YouTube: SharePoint Framework Community call – 22nd of April 2021
Description
SharePoint Framework Community call on April 22. Demos: 1) Running the CLI for Microsoft 365 in Azure Container Instances orchestrated by Logic Apps, 2) Advanced Page Properties web part solution, and 3) SharePoint Framework 1.12.1 new features (including demos for 2 of the features). Latest PnP project status. Preview the new Microsoft 365 Extensibility look book gallery. Public preview of SharePoint Framework 1.12.1. There were six PnP SPFx web part samples delivered in last 2 weeks. Great work! The host of this call is Patrick Rodgers (Microsoft) @mediocrebowler. Q&A takes place in chat throughout the call.
Learn more:
• See the full blog post for this call at: http://aka.ms/m365pnp/community/blog
• Download invite for bi-weekly SharePoint Framework call at: https://aka.ms/spdev-spfx-call
• Learn more about the Microsoft 365 Patterns and Practices community at: http://aka.ms/m365pnp
• Visit the Microsoft 365 Patterns and Practices community YouTube channel: https://aka.ms/m365pnp/videos
A
Hello
and
welcome
to
the
sharepoint
framework
and
javascript
special
interest
group
bi-weekly:
sync:
it
is
april
22nd
2021,
I'm
your
host
patrick
rogers.
On
this
call
and
as
always,
we
have
a
great
agenda
for
you
today.
We'll
have
latest
updates
on
the
sharepoint
framework
patterns
and
practices,
program,
updates,
new
community
samples,
details
picture
time
and
together
mode-
and
we
got
three
great
demos
again
from
albert
mike
and
some
guy
named
vasa
talking
about
sharepoint
framework,
so
very
excited
to
get
those
demos
out
to
you,
but
first
details
around
opportunities
to
participate.
A
So
we
always
encourage
folks
to
demo
on
all
of
our
community
calls.
If
you'd
like
to
demo,
please
do
reach
out
to
myself
or
vaso
we'd
love
to
get
you
scheduled
on
the
call.
I
think
it's
one
of
the
best
parts.
These
calls
to
see
all
the
amazing
work
you
are
doing
for
your
customers
or
the
companies
you
work
for
so
please
reach
out
to
us
that
can
be,
for
this
call
anything
around
client,
side,
development
or
the
pmp
offerings.
A
Please
do
reach
out,
or
you
know,
if
you've
got
other
spf
x,
demos
stuff
like
that
love
to
see
it
and
if
you've
got
ideas
for
other
kinds
of
demos
reach
out
anyway,
we
could
find
the
right
community
call
for
you
to
do
that.
Demo
on
love,
love
love
to
have
you
contribute
those
demos
as
well.
You
can
contribute
on
github
through
reporting
issues
too
many
pull
requests
or
helping
with
issues
and
questions.
A
That's
a
great
way
to
contribute
is,
if
you
happen
to
see
somebody
else
with
a
question,
and
you
happen
to
know
the
answer
to.
Please
do
go
ahead
and
answer
that
it
really
helps
everybody
out
and
gets
people
answers
faster
and
then,
as
always,
we
welcome
your
feedback
on
everything
we
do
in
pnp.
So
how
are
these
calls?
How
is
our
documentation?
A
Where
else
can
we
help
and
of
course,
positive
feedback?
Is
okay
too,
if
we're
doing
something
you
like,
perhaps
we
can
do
a
little
bit
more
of
it.
So
please,
let
us
know
and
then
moving
into
our
giant
page,
oh
links,
the
main
link
to
remember.
There
is
aka.msm365pnp
that
will
take
you
to
the
patterns
and
practices
landing
page
which
will
link
you
out
to
all
of
these
other
resources.
So
we
have
developer
videos
which
are
topic
focused
videos
on
things
like
authentication
teams,
app
development
using
the
microsoft
graph
toolkit
and
other
great
features.
A
A
I
think
four
or
five
years
we've
only
missed
one
or
two
recordings,
which
is
kind
of
amazing,
and
then
we've
got
a
ton
of
great
open
source
organizations
that
are
active
and
accepting
your
participation,
so
the
sharepoint
pnp
office,
dev
and
microsoft
graph
orgs,
are
all
open
and
want
you
to
join
in
and
help
out
or
participate
in
how
you
would
like.
So
please
check
those
out
and
then
we've
got
tons
of
samples
in
across
many
galleries.
A
B
Thanks,
patrick
well,
within
our
open
source
and
inclusive
community
of
microsoft,
365
we
have
a
wide
array
of
tools
and
resources
for
everyone
to
take
advantage
of.
In
fact,
you
can
contribute
back
to
those
tools
and
resources
as
well,
but
we
understand
that
sometimes
there's
some
hurdles
in
contributing
back
and,
in
fact,
even
using
those
resources.
B
So
sharing
is
caring,
is
here
to
provide
hands-on
guidance
sessions
which
walk
you
through
how
to
take
advantage
of
these
opportunities,
whether
it
be
your
first
time
contribution
by
updating
the
development
documentation
or
the
microsoft
documentation,
all
of
which
you're
empowered
to
do
creating
new
documentation.
Setting
up
your
workstation,
a
wide
array
of
opportunities
to
learn
how
to
get
more
involved,
and
these
are
safe
space
opportunities
to
ask
any
and
all
questions.
We
don't
record
them
great
opportunities
to
collaborate
with
others
in
the
community
as
well.
B
So
we
invite
you
to
join
any
of
the
sessions
they're,
all
free,
as
I
mentioned,
not
recorded.
In
fact,
we
have
a
session
later
today
on
community
docs.
If
you
would
like
to
learn
more
about
that-
and
we
have
a
special
edition
ama
coming
up
in
the
next
couple
of
weeks
on
the
brand
new
power
platform,
samples
gallery
so
aka
dot,
ms
forward
slash
sharing,
is
caring
register
for
any
and
all
sessions.
We'd
love
to
see
you
and
we
hope
to
work
with
you
soon.
Patrick
back
to
you.
A
Thank
you
david
for
that
update
and
love
to
continue
to
see
the
growth
in
this
sharing
is
carrying
initiative.
It's
really
fantastic,
seeing
so
many
first-time
contributors
come
out
of
that.
It's
great
great
great
resource
if
folks
are
interested
and
getting
started.
As
david
said,
please
join
one
of
these
sessions.
It's
a
great
way
to
learn
great
way
to
meet
some
folks
and
great
way
to
get
involved.
So
aka.ms
sharing
is
caring
and
we
have
a
new
microsoft,
365
extensibility
lookbook
gallery.
A
So
this
is
a
great
way
to
look
at
how
to
customize
various
microsoft
technologies
or
surfaces
such
as
teams,
sharepoint,
onedrive
office,
the
power
platform,
all
great
ideas
on
how
to
you
know,
patterns
to
follow
as
how
you
build
out
your
extensibilities
and
there's
a
lot
of
different
ideas
there
to
help
you
figure
out
in
your
solutions.
You
can
pick
and
choose
different
pieces
of
these,
but
great
resource
here
check
this
out.
A
Ak.Msm365
extensibility,
another
fantastic
community
driven
resource.
So
thank
you
to
everybody.
That's
helped,
contribute
and
build
that
and
love
to
see
that
continue
to
grow
as
well.
We
have
a
new
developer
community
survey,
which
is
now
open
so
help
us
by
answering
these
questions.
So
these
questions
help
us
craft
what
we're
going
to
do
for
the
next
year.
So
microsoft
is
deep
into
planning,
which
means
we're
deep
into
the
pnp
planning
so
think
about
responding
to
this
survey.
It's
probably
a
better
way
to
say
that
and
let
us
know
your
thoughts.
A
This
is
a
great
way
to
give
us
some
feedback
and
every
piece
of
feedback
will
be
reviewed
and
read
and,
and
we
value
it
and
if
you've
got
stuff,
you
would
like
to
share
that
doesn't
maybe
fit
in
the
survey
or
you're
not
comfortable
putting
into
the
survey
feel
free
to
reach
out
to
someone
directly
again,
as
mentioned
earlier.
We
always
are
interested
in
your
feedback
and
your
thoughts.
So
please
do
share
your
thoughts
and
take
the
time
to
complete
this
survey.
Ak
dot.
A
C
C
The
upcoming
features
we're
going
to
focus
more
on,
what's
coming
in
the
later
part
of
the
call
as
well,
but
this
is
available
if
you
want
to
help
us
on
on
validating
the
upcoming
feature
and
we're
going
to
do
this
for
the
all
of
the
future
releases
as
well
and
with
130
and
114,
and
all
of
that
you
can
install
the
latest
version
by
using
the
at
next
in
nbn.
Install
ge
at
microsoft.
Generator
dash
sharepoint
at
next
is
always
the
previous
stuff
and
then
at
the
latest,
as
always
the
currently
in
production
stuff.
C
So
you
can
actually
differentiate.
What
are
you
installing?
That's
just
a
quick
recap
on
this
one:
we're
going
to
focus
more
on
these
items
in
the
later
part
of
the
call,
nothing
new
major
in
here
and
I'll
deep
dive
on
the
plant
schedules
and
all
of
the
individual
things
in
this
list
in
the
last
demo
of
today.
So
I'm
not
going
to
take
more
time
on
this
in
here
we're
planning
to
release
sharepoint
framework
1.12.1
in
upcoming
days,
I'll
tease
in
some
additional
things
in
the
last
demo.
But
let's
get
back
to
you,
patrick.
A
Thank
you
very
so
very
excited
to
see
those
betas
go
out.
Please
take
the
opportunity
to
try
those
out
and
provide
feedback
to
the
team.
Those
betas
are
a
really
valuable
asset
in
you
getting
to
test
new
stuff
in
your
applications,
as
well
as
getting
us
feedback
on
how
we
can
be
better
prepare
those
for
the
actual
eventual
release,
so
fantastic
new
development
to
have
those
betas
available,
and
with
that
I
will
stop
talking
and
pass
it
to
julie
for
client
side
library
updates
with
pnpjs.
D
Hey
so
thank
you,
patrick,
so
we
just
released
the
2.4.0
release
on
april
9th.
There
was
lots
and
lots
of
doc
fixes
and
a
bunch
of
unit
test
fixes.
We
still
do
have
a
little
bit
of
unit
test,
fixing
and
love
to
do.
There
was
a
fix
for
the
ad
chunk
file
names
with
file
names
with
apostrophes
was
fixed.
We
also
added
a
new
graph
endpoint
for
user
presence
so
that
those
endpoints
are
there
now
so
definitely
keep
your
feedback
coming.
D
D
If
you
want
to
see
what's
what's
happening,
certainly
you
can
comment
and
and
would
love
to
hear
any
feedback
you
have,
but
our
plans
have
been
sort
of
set
at
this
point
and
also
I
just
wanted
to
give
everyone
a
heads
up,
especially
those
following
the
repo
that
we
added
a
new
github
action
that
locks
old
closed
issues.
So
that's
because
we
do
not
review
or
check
up
on
any
comments
made
on
closed
issues,
and
we
wanted
to
make
sure
that
was
a
better
user
experience
for
everybody.
D
So
the
the
proper
way
to
start
an
issue
on
something
that's
related
to
a
closed
issue
is
to
start
a
new
issue,
and
then
you
can
reference
the
closed
one
with
any
of
your
additional
details,
trying
obviously
your
best
to
fill
out
those
forms
in
as
much
detail
as
possible
so
that
we
can
get
a
head
start
on
helping
you
with
whatever
your
situation
is
also
don't
forget
to
follow
us
on
twitter,
m365,
pnp,
ejs
and
that's
all.
I
have
back.
A
A
It
is
100,
not
usable
production,
ready
code
at
all
at
this
point,
but
if
you're
interested
in
seeing
what
we're
up
to
it's
there
and
we
will
be
posting
issues
and
things
soon
for
folks
to
help
out
and
now
cli
updates
for
microsoft,
365.,
so
new
beta
3.9
is
out
with
upgrading
spfx
projects
to
the
new
112.1
release,
creating
azure
ad
apps
from
manifest
creating
viva
connections
desktop
app
packages,
that's
a
great
new
addition
and
adding
site
app
permissions
and
more
lots
of
great
sample
scripts.
As
well
now
available.
A
You
can
always
install
the
beta
from
npm
npm
install
dash
g
at
pnp,
cli
dash,
microsoft,
365
at
next.
It's
a
fantastic
tool
for
cross-platform
project
management
or
application
management,
as
well
as
a
lot
of
life
cycle
work
as
well
as
interacting
with
azure
graph
and
sharepoint
directly,
as
well
right
from
the
cli
really
great
valuable
tool.
If
you
haven't
used
it,
it
really
is
a
great
thing
to
have
in
your
back
pocket.
A
If
you
need
to
do
some
quick
action,
some
quick
scripting
cross-platform
really
neat
to
see
that
and
continue
to
grow.
I
mean
it's
really
a
fantastic
place
where
people
have
just
been
contributing
and
developing
and
joining
in
and
helping
out
so
fantastic
to
get
to
see
that
continued
growth
over
time
for
the
cli.
A
Next
up
the
spfx,
reusable
components,
we've
got
two
sets
of
controls.
The
react
controls
are
designed
to
work
in
the
body
of
your
web
parts
and
application.
Customizers
2.6.0
latest
version
there
with
some
new
updates
for
animated
dialogue,
icon
picker
list
item
picker
and
some
various
fixes.
The
react
controls
3o
are
on
hold,
so
that
is
waiting
for
the
actual
release
of
112.1.
A
As
there's
going
to
be
some
breaking
changes
required
to
support
the
new
spfx
release,
so
that'll
be
a
3.0
release,
but
that
is
on
hold
for
now
and
then
there's
the
other
set
of
controls.
The
property
controls
are
designed
to
be
used
in
the
edit
pane
of
your
web
parts
and
those
have
two
new
things:
a
property
field,
editable
combo
box
and
the
column
picker
two
super
new
controls
in
there
and
as
well.
A
The
3.0
version
of
the
property
controls
are
on
hold
for
the
same
reasons
as
the
other
controls
we're
waiting
for
that
1
12,
1
actual
release
there.
So
if
you
haven't
checked
these
out,
it's
a
great
way
to
jump,
start
your
project
and
get
your
development
underway
early
and
save
yourself
a
lot
of
development
time
with
these
ready
to
drop
in
controls.
A
Next
up
is
modern
search,
so
ak
dot,
msp
search.
So
this
is
a
great
set
of
flexible
web
parts
that
you
can
compose
together
to
create
a
modern
search
portal.
It's
responsive
and
it
uses
spfx,
and
you
can
configure
things
to
work,
just
how
you
want
to
work.
So
there
is
a
319
release
in
april,
and
that
has
some
fixes
in
it.
The
my
understanding
is,
the
three
branch
is
sort
of
in
maintenance
mode.
E
Awesome
are
you
looking
for
web
part
extensions
code,
samples
for
the
sharepoint
framework?
Well,
we've
got
hundreds
and
hundreds
of
curated
samples
for
web
parts
and
extensions
in
our
repositories
and
they're
there
to
help
you
get
started
or
maybe
to
just
help.
You
solve
the
development
pattern
and
delivery
solutions
faster.
So
these
updates
are,
for
the
last
two
weeks
on
the
spfx
extension
side,
so
aka
ms
spfx
extension.
E
We
have
a
new
new
sticker
extension
by
ari
gunawan
and
the
extension
allows
you
to
display
news
as
running
text
at
the
top
of
every
modern
page
on
the
spfx
webparts
site.
So
that's
aka.ms,
spfxwebparts,
chandani
prajapati
has
updated
the
data
table
to
actually
add
the
user
display
or
the
people
display
in
the
people,
columns
and
also
updated.
The
pdf
and
csv
export
to
actually
include
the
person's
name
on
an
export.
E
Tristian
o'brien
has
added
the
about
me
and
skills
to
the
staff
directory
web
part
and
andre
has
created
a
new
onedrive
finder
which
allows
you
to
actually
access
your
onedrive
from
a
web
part,
and
then
you
can
actually
navigate
through
and
it's
actually
a
new
file
list
control,
which
you
definitely
should
look
at.
We
also
have
a
new
update
or
new
web
part
by
sebastian.
Never
the
graph
mgt
client,
which
actually
uses
the
microsoft
graph
toolkit
to
to
allow
you
to
create
graph
queries
in
the.
F
E
Part
and
you
can
actually
see
the
results
and
then
finally,
we
have
a
teams-
membership
updater
by
nick
brown,
which
allows
you
to
update
membership
of
a
team
based
on
a
the
content
of
a
csv
file.
So
it's
really
useful
if
you
have
to
do
a
lot
of
migrations,
a
lot
of
moving
people
around
and
that's
also
available
as
well.
I
just
wanted
to
thank
everyone
for
all
your
awesome
sample.
We.
F
E
Just
recently
hit
over
120
000
visitors
in
in
march,
when
we
had
about
90
000
in
february,
so
we're
definitely.
The
word
is
getting
around.
People
are
starting
to
use
the
samples
and
we're
definitely
looking
for
more
samples.
Thank
you,
everyone
for
being
awesome
back
to
you,
patrick
great
stuff,
hugo
thank.
A
C
G
C
Yeah,
okay,
anyways:
let's
do
some
waving
thanks
everybody
for
joining,
like
I
said
so
many
times
on
this
seriously.
It
is
such
a
good
thing
to
see
real
faces
behind
of
these
voices
and
names.
So
thank
you.
Everybody
we've
been
recording
the
screen.
I
will
share
and
clip
a
a
keef
animation
out
of
it.
So
thank
you
and
I
do
apologize.
There's
only
50
people
who
gets
to
the
picture
every
single
time.
C
F
Cool,
let
me
let
me
share
my
screen:
I'm
not
going
to
do
too
many
slides,
just
a
quick
introduction.
What
I'm
going
to
show
you
is
running
the
cli
in
azure
container
instances.
So
for
those
of
you
who
don't
know
the
cli,
yet
the
cli
is
a
cross-platform
way
of
managing
microsoft,
365
in
a
unified
way
from
any
platform
or
tool
chain,
and
it
will
allow
you
to
manage
both
your
tenant
as
well
as
sharepoint
framework
projects.
So
we
believe
it's
easy
to
use,
definitely
check
out
for
yourself.
F
If
you
don't
believe
me,
it
works
on
any
os,
so,
whether
it's
windows,
mac
os
or
linux,
it
works
in
any
shell,
powershell
best
commander
or
whatever
shell
of
your
liking,
and
there
is
one
unified
login.
So
you
just
log
in
once
and
from
that
point
in
time
you
can
talk
to
all
the
services
in
microsoft,
365
that
we
provide
commands
for
now.
F
We
do
have
a
fancy
docker
container
running,
that
you
can
pull,
so
you
can
pull
that
either
locally
or,
as
I'm
going
to
show
you
today,
you
can
actually
pull
it
into
azure
container
instances
and
use
things
like
managed
identity
to
do
long,
running
operations
in
the
cloud
against
your
tenant
and
use
logic
apps
to
orchestrate
those
those
containers.
Now,
just
some
of
the
building
blocks
that
I'm
going
to
show
you,
we
will
use
the
cli
docker
container.
So
we're
not
going
to
introduce
this
into
details
about
that.
F
So
we
just
assume
that
it's
there
believe
me.
It's
there
we're
gonna
use
it.
We
gonna
have
a
look
at
the
logic,
app
that
logic
app
is
going
to
pull
in
something
from
a
github
repo,
we're
not
going
to
go
into
too
much
detail
on
what's
running
in
github,
but
we
pull
in
a
script
and
that
script
will
actually
run
in
the
docker
container.
F
In
our
azure
container
instances
it
will
use
a
managed
identity,
making
sure
that
we
can
authenticate
against
our
tenants
and
that
we
can
use
that
information
to,
for
instance,
get
all
site
collections
or
get
all
side
collections
with
a
specific
state.
So
that
depends
on
the
script
that
you
want
to
run
within
the
cli
samples.
We
do
have
a
bunch
of
sample
scripts
that
you
can
use
or
reuse
in
this
way,
but
basically
these
are
the
building
blocks.
So
with
that,
let's
have
a
look
at
an
actual
demo.
Let's
have
a
look
at
actual
code.
F
Now.
What
you
see
here
is
you
see
a
resource
group
within
the
resource
group?
I
do
have
a
managed
identity,
so
I
created
a
managed
identity
to
make
sure
that
I
can
do
the
things
that
I
want
to
do.
The
advantage
of
having
a
managed
identity
is
that
I
don't
need
to
log
in
into
my
script.
I
can
use
this
managed
identity
when
running
scripts,
so
the
logic
app
will
use
this
managed
identity
to
attach
it
to
the
container
that
we'll
be
running
so
by
doing
so.
F
That
container
automatically
uses
that
identity
and
can
use
that
identity
to
get
a
bunch
of
scripts.
Now
there
is
one
thing
that
you'll
need
to
do.
So
what
you
see
here
is
a
new
tab
where
I
went
to
the
enterprise
applications
and
I
looked
up
my
my
enterprise
or
I
looked
up
my
managed
identity
and
what
I
need
to
make
sure
is
that,
depending
on
what
I
want
to
achieve
with
my
script,
I
need
to
make
sure
that
it
has
the
appropriate
permissions.
F
So
in
this
case,
what
I
wanted
to
do
is
I
wanted
to
do
some
stuff
with
all
site
collections,
so
I
made
sure
that
both
from
the
graph
endpoint
perspective,
as
well
as
the
sharepoint
or
office
365
sharepoint
online
perspective,
I
do
have
the
permissions
with
this
managed
identity
to
actually
read
and
write
items
in
all
site
collections.
If
I
do
not
have
this
set
of
permissions,
then
I
cannot
run
my
script
so
these
are.
This
is
the
bare
minimum
to
authenticate
against
your
tenant?
F
If
you
want
to
do
different
things,
let's
say
you
want
to
read
and
write
all
user
profiles.
You
need
that
if
you
want
to
do
things
with
yammer
or
if
you
want
to
do
things
with
the
power
platform,
you
might
require
additional
permissions
and
you
need
to
make
sure
that
you
add
them
here.
You
need
to
make
sure
that
they
have
the
trend.
Admin
consent
has
been
applied,
but
once
you've
done
that,
then
your
managed
identity
is
ready.
You
can
use
that
manage
identity
from
there
there's
nothing
else.
I
need
to
do
now.
F
If
I
go
back
what
I
then
add
is
I
have
a
logic
app
and
the
logic
app
is
actually
doing
all
the
magic
for
me.
So
there's
no
other
code
involved
and
we're
just
going
to
walk
you
through.
What's
in
the
logic
app,
so
the
first
step
obviously
is
a
trigger
any
logic.
App
or
any
flow
would
require
a
trigger.
I
did
a
http
trigger,
it
can
be
any
other
trigger.
You
can
run
it
on
a
timer,
so
you
can
run
it
every
week
or
every
day.
That's
not
really
the
important
part.
F
I
also
use
two
two
variables
not
really
important
either,
but
because
I'm
using
them
multiple
times,
you'll
need
them
in
multiple
steps.
It's
probably
easy
to
create
to
create
one.
The
real
magic
is
actually
happening
in
the
action
called,
create
or
updated
container
group,
and
this
is
where
the
magic
is
happening.
This
is
where
we
actually
will
create
a
azure
container
instance
where
everything
will
be
run
or
everything
is
happening
now.
In
order
to
do
that,
you'll
need
your
subscription
id.
You
need.
F
A
resource
group
you'll
need
a
resource
group
name
which
well,
I
would
say,
probably
make
some
make
some
sense.
That
container
group
name
is
something
that
you
will
use
later
on.
You'll
need
to
set
a
location,
doesn't
really
matter
where
you
run
it
as
long
as
it's
near
to
wherever
your
microsoft
365
tenant
is,
then
you
will
have
the
best
performance,
but
it's
not
a
requirement,
then.
As
soon
as
you
have
that
container
group,
you
can
specify
the
actual
container
name.
F
So
this
is
what
container
will
be
started
and
you
have
to
specify
a
container
image
and
the
advantage
of
using
a
container
image
is
that
it
can
actually
look
at
the
docker,
the
docker
environment
or
the
docker
repository,
and
it
can
pull
images
from
there.
So
by
doing
this,
specifying
the
m365
pnp
cli
microsoft,
365
colon
latest,
you
will
get
the
latest.
You
can
also
do
next,
and
then
you
get
the
beta
container
with
the
beta
bits,
but
we're
going
to
go
with
the
latest,
just
official
release
that
we
have.
F
Then
you
have
to
specify
for
the
container
that
you
will
start
up
how
many
cpu
power,
how
many
memory
you
will
need,
and
that
kind
of
depends
on
the
size
of
the
scripting
that
you
try
to
execute.
So
in
my
case,
I'm
just
going
to
pull
in
some
sites,
I'm
not
doing
really
resource
intensive
stuff.
So
this
should
be
enough.
F
If
you're
running
on
a
let's
say
large
tenant
with
over
a
million
site
collections,
then
you'll
probably
need
some
more
memory
to
just
process
them
and
work
with
them,
but
for
demo
purposes
this
is
more
than
enough.
Now
then,
there
is
a
bunch
of
stuff
that
you
don't
need
to
specify
you
can
you
can
play
around
with
it
if
you
want
to,
but
there's
not
they're,
not
required,
then
the
next
step
that
you
will
need
to
specify
is
that
you
need
to
make
sure
that
you
actually
can
run
a
script.
F
So
if
you
spin
up
a
container,
you
can
pass
on
command
segments
and
the
requirement
of
passing
on
command
segments
is
that
it
can
only
be
a
single
command,
so
you
cannot
chain
commands.
You
can
only
execute
one
single
command
now,
in
my
case,
what
I
actually
want
to
do
is
I
want
to
do
multiple
steps
into
my
script,
so
I
want
to
log
in
I
want
to
get
all
sites.
I
might
want
to
get
all
owners
for
all
sites,
so
I
actually
want
to
do
more
in
order
to
do
that.
F
What
you
need
to
do
is
you'll
need
to
execute
a
best
script
or
a
powershell
script
for
that
matter,
and
you'll
need
to
specify
that
actual
script
that
needs
to
come
in.
So
in
this
case,
I'm
going
to
say:
okay,
I'm
going
to
ask
you
best.
This
is
the
script
that
I
want
to
execute,
and
then
I've
got
a
bunch
of
other
parameters
that
I
can
skip
not
really
important,
but
that
script
actually
needs
to
come
in.
I
need
to
get
that
script.
That
script
is
not
part
of
the
container
image.
F
So
if
you
pull
in
the
container
image
that
script
is
not
variant
in
order
to
get
a
script
there,
what
you'll
need
to
do
is
you'll
need
to
make
sure
that
you
have
a
reference
to
that
script
and
that
you
can
say
I'm
going
to
say
the
container
volume
I'm
going
to
mount
a
container
volume.
So
by
specifying
a
repository,
giving
the
name
or
specifying
the
name.
I
can
then
mount
that
container
image
and
that
container
image
is
actually
coming.
If
I
scroll
down
a
little
bit
more,
it's
actually
coming
from
a
git
repo.
F
So
what
this
does
is
this
will
pull
in
the
git
repo
I'll
specify
the
git
repo
name
called
git
repo,
and
then
what
you
can
do
is
you
can
say,
I'm
gonna
mount
git
repo
on
this
path,
meaning
that
on
this
path,
all
the
scripts
will
reside
that
are
coming
from
my
git
repo.
Now
this
kit
repo,
I
can
open
it,
it's
it's
a
public
repo.
So
for
production
purposes,
this
is
not
a
best
practice.
F
You'll
probably
want
to
use
a
private
repository,
because
potentially
someone
can
change
that
script
would
work
the
exact
same
way.
The
only
thing
that
you
then
need
to
do
is
you
need
to
authenticate
your
logic
app
or
your
azure
subscription
to
be
allowed
to
access
your
private
repository.
In
this
case
I
just
put
in
a
test
script
where,
in
that
test
script
I
do
a
login
action
and
I'm
gonna
list
all
site
collections.
F
Now,
if
you
remember
that
login
action
that
I
just
talked
about
the
managed
identity,
I
said
there's
no
need
for
me
to
log
in
there's
nothing.
I
need
to
do
there's
only
one
step
within
the
cli
I'll
need
to
say
this
is
the
id
of
the
managed
identity
and,
within
that
container,
in
image,
I
need
to
say
use
that
id
of
the
managed
identity
and
if
that
id
matches
the
managed
identity
of
the
container
that
got
spun
up,
then
everything
worked
flawlessly
then
it
can
sign
in
and
then
it
actually
works.
F
F
The
other
thing
that
you'll
need
to
do
is
you
need
to
actually
specify
that
the
container
group
is
using
that
managed
identity
and
that's
something
that
you
do
by
setting
the
managed
identity
type
I
chose
the
user
assigned,
you
can
also
use
the
system
assigned,
and
then
you
can
say
this
is
the
actual
user
that
you
want
to
use
and
what
you'll
see
here
is
slightly
confusing,
because
if
you
look
at
the
docs
it
will
give
you
a
sample
on
how
things
should
look.
It's.
F
It
might
be
small
on
your
screen,
but
if
you
would
zoom
in
you
would
see
that
it
gives
you
a
format
on
how
things
would
look,
but
the
actual
stuff
that
you
need
to
put
in
there
is
slightly
different,
so
the
dogs
lack
a
little
bit
behind
on
the
actual
content
that
you'll
need
to
put
in
there.
So
what
you
see
here
is
I
need
to
specify
okay,
I'm
using
this
subscription
with
this
id
I'm
using
this
resource
group
and
then
I'm
using
this
actual
menace
identity.
F
That's
already
succeeded
just
to
walk
you
through,
and
you
will
see
that
all
the
actions
are
green
and
then,
in
this
case
that
it
took
five
iterations
to
check
whether
the
container
image
was
finished
and
if
I
go
to
then
the
get
locks.
What
you
see
here
is
a
bunch
of
json
with
all
my
site
collections
here
you
can
see.
I've
got
my
site
design.
F
I
can
see
some
details.
The
reason
that
I
get
json
is
because
in
the
script
I
defined
it
to
be
output
json
and
now
I
can
either
def
or
refine
my
script
by
filtering
or
doing
additional
steps,
or
I
can
say
I
want
to
have
that
logic
in
my
logic
app
in
place.
So
we
see
that
this
is
something
that
we
run
at
customers
where
we
can
explain
to
sysadmins
who
might
not
have
that
much
experience
with
either
powershell
or
cli
commands.
F
We
can
just
set
this
up,
put
the
script
in
place
and
explain
if
they
want
to
do
different
things
with
the
output,
they
can
use
the
logic
app
to
send
it
as
an
email
or
send
it
as
an
adaptive
card
to
teams
or
do
things
what
they
whatever
they
want
to
do.
With.
With
that,
I
saw
a
question
about
the
slides.
I
think
the
slides
will
actually
be
shared
if
not
reach
out
on
twitter.
I
can
definitely
share
them
some
important
links
in
there.
F
If
you
want
to
read
more
on
the
cli,
then
there
is
the
aka.ms
link.
If
you
want
to
see
what's
happening
on
the
project,
you
can
find
everything
in
github.
The
docker
image
is
on
docker
hub,
and
I
did
a
write
up
a
walkthrough
of
all
the
steps
that
I
took
to
get
this
to
work.
So
if
you
want
to
well
replay
or
actually
get
screenshots,
how
to
do
this
definitely
check
out
the
the
walkthrough
and
that's
it
for
today.
A
A
F
H
H
One
of
the
ways
that
I
solve
client
problems
at
three
will
is
we
do
a
lot
of
this
digital
workplace
consulting
and
a
lot
of
times.
That'll
start
with
workshops
and
oftentimes
will
end
in
like
full-blown
automation,
site,
template
provisioning,
and
I
bring
that
up
because
it's
a
good
segue
into
why
I
built
this
web
part
in
the
course
of
these
digital
workplace
journeys.
We
inevitably
end
up
with
a
set
of
pages
that
have
both
rich
content
and
rich
metadata.
H
You
know,
we've
got
you
know,
for
instance
the
capsule
display.
You
know
over
time.
Things
have
have
just
continued
to
modernize
in
the
lists,
but
the
page
properties
web
part
has
not
so
much
improved
over
time.
It's
still
got
a
little
bit
of
that
older
look,
it
doesn't
react
to
the
theming,
especially
backgrounds.
That's
always
a
big
one.
H
It
doesn't
support,
links,
currency
images
and
then
it
has
kind
of
this
default
behavior
for
dates
and
numbers.
Not
it
doesn't
necessarily
abide
by
the
actual
sub
properties
that
you
configure
it
for
so
you
know,
like
I
said,
like
solving
problems
like
building
things,
so
my
way
to
contribute
was
to
try
to
take
something
that
might
normally
look
like
this
and
actually
address
those
those
issues
that
I
mentioned
so
that
I
can
have
something.
That
looks
a
little
more
like
that.
H
H
So
you'll
notice
that
out
of
the
gate
it
it
tries
very
hard
to
look
almost
identical
to
the
original
part,
definitely
wanted
it
to
feel
familiar,
maybe
slightly
different
icons,
but
otherwise
everything's
just
about
the
same.
The
big
difference
is
just
that.
I'm
getting
more
properties
available
to
me.
You
know
it
still
does
the
same
old
ones
like
text,
and
you
know,
like
a
term
set,
that's
the
usual,
but
you
can
see
I'm
trying
to
actually
style
it.
A
little
more.
H
H
Let's
see
what
happens
there
and
let's
go
ahead
and
add
a
date
like
an
anniversary
date
and
the
big
difference
there
is
that
it's,
it
is
actually
abiding
by
the
format
that
you've
even
specified
in
the
field
as
well.
So
that's
kind
of
the
part
in
action.
You
know
the
normal
stuff
is
also
there.
You
know
I
can
I
can
I
can
delete,
I
can
change
just
the
standard.
You
know
functionality
that
we've
had
in
the
past
as
well.
Just
does
more
right.
H
H
H
H
There's
a
bit
of
strange
alchemy,
just
below
here,
where
I
had
to
kind
of
by
trial
and
error
start
to
figure
out
what
properties
microsoft
was
using
to
determine
what
goes
into
that
drop-down
and
that's
kind
of
these.
The
stuff
that
you
see
up
here
in
the
top
part
of
the
condition
and
then
down
here,
are
some
different
types
that
I've
had
to
exclude
for
now.
H
H
The
only
other
thing
to
point
out
about
the
web
part
is
the
way
that
we
have
to
render
out
the
property
pane,
because
that's
really
the
big
deal
with
the
web
part
and
everything's
governed
by
what's
in
the
selected
properties
array
so
as
they
add,
as
they
delete
we're
affecting
change
on
the
selected
properties
array.
So
you
can
see
that
I've
got
an
event
handler
for
when
they
click
delete
when
they
click,
add
we're
either
pushing
polling
or
or
changing
an
actual
value,
and
that's
all
against
our
selected
properties.
H
So,
let's
jump
over
to
the
component
itself
that
the
web
parts
loading
at
it
doesn't
have
to
do
that
much
it's
just
all.
In
the
logic
right,
you
can
see
we're
using
react
hooks
and
the
main
thing
we
need
to
track
state
on
is
this
value
page
prop
values
I'll,
take
a
quick
detour
just
to
show
you
that
object
type,
just
because
it's
worth
pointing
out,
because
this
is
really
at
the
heart
of
it
right
I
at
runtime.
H
I
need
to
know
as
much
metadata
about
the
field
itself
and
then
I
need
to
be
able
to
capture
any
and
all
possible
values
for
that
field
for
the
page,
so
we
need
to
cast
the
widest
net
possible,
and
so
it's
in
any
array,
oh-
and
I
guess
I'll
point
out
too.
This
is
just
the
standard.
Pmp
object
for
the
field
information,
but
that
gets
us
everything
that
we
need
just
below
that
you
can
see
where
I'm
setting
the
theme
variant
again
making
use
of
that
all
in
the
display
at
runtime,
so
refresh
properties.
H
H
We
know
the
selected
properties,
so
we're
going
to
go
ahead
and
make
a
call
using
pmp
to
actually
get
that
list
item
out
and
all
of
the
values,
regardless
of
what
they
are
and
then
we
also
need
to
establish
all
the
metadata
for
each
field
so
that
we
can
figure
out
how
we're
gonna.
You
know
what
rules
we're
gonna
employ
right.
H
Like
I
mentioned
before,
I
need
to
ensure
that
I'm
casting
the
widest
net,
so
I've
got
to
make
sure
that
I
can
convert
anything
to
that
any
array.
So
that's
kind
of
you
know
what's
going
on
here,
some
of
the
fields
based
on
their
type
they
come
down.
You
know
you
don't
know
exactly
which
way
they're
going
to
come
down.
They
could
have
different
properties,
they're
they're,
completely
different
objects.
H
You
got
to
be
prepared
for
that
so,
and
that
includes
having
to
convert
it
to
an
any
ray,
can
be
a
little
bit
different
depending
on
the
type
again
use
effect
whenever
the
property
gets
changed
in
the
property
pane.
We're
pushing
that
down
to
the
component
and
that's
going
to
trigger
another
refresh
of
the
of
the
display.
H
The
the
rendering
is
a
little
bit
nested.
You
know
as
we
go
down,
you
know
we're
we're
looping
through
all
of
the
properties
right
here
and
then
we're
actually
displaying
all
the
actual
property
values
based
on
the
property.
So
that
gets
us
to
the
main
method,
which
is
our
render
page
prop
values
for
display
and
again
it's
very
reactive.
H
You
can
even
see
as
we
get
into
something
like
a
date
time
display.
We
might
interrogate
some
of
those
sub
properties
that
you
save
it,
as
in
the
list,
that's
going
to
help
us
know
which
way
to
format
the
date
according
to,
and
I
basically
I
I
used
the
way
it
gets
displayed
in
the
list,
as
my
baseline
for
how
I
was
going
to
display
it
in
the
in
the
web
part
and
that's
essentially
it
the
only
other
thing
again.
I'll
just
point
out,
you
may
have
already
noticed
it
throughout.
H
H
H
You
know
page
properties,
part
on
a
number
of
pages
still
for
customers,
and
they
always
want
to
be
able
to
click
the
capsules
they
kind
of
they
they
feel
like
they
should
be
kind
of
almost
like
tags,
so
I'd
love
to
come
up
with
with
a
solution
to
actually
allow
those
to
actually
be
clickable
and
do
something
with
it.
People
field
is
the
only
one
that
I
don't
support
that
the
original
does
so
I'd
definitely
like
to
get
that
and
I'd
love
to
get
any
other
ideas
from
the
community.
H
So
please,
if
you
feel
inclined,
go
out
to
the
get
repo
of
pnp
samples
and
if
you
put
in
an
issue-
and
that
mentioned
me
I'd-
be
happy
to
help
or
contribute
with
you.
Thank
you
again
for
your
time.
Like
I
said
you
can
read
up
on
this
part
on
the
tech
community
blog
and
you
can
access
the
code
in
the
pmp
samples,
repo
and
please
contribute.
A
Really
fantastic
stuff
mike.
Thank
you
for
sharing
that
and,
if
folks
are
interested,
you
know
he's
asking
for
contribution.
Help
so
that'd
be
a
great
way
if
you're
looking
for
a
place
to
contribute
and
get
involved.
This
seems
like
a
really
fantastic
opportunity,
and
our
next
presenter
is
somebody
who
needs
no
introduction.
C
Thank
you.
So
that's
that's!
What's
fast,
so
I'm
gonna
talk
about
the
sharepoint
framework,
112.1
I'll,
do
two
quick
demos
related
on
that
one.
Obviously,
we
are
on
the
end
of
the
community
call
and
we're
always
running
out
of
time,
but
we'll
certainly
have
more
demos,
as
we
ga
112.1,
but
I'll
show
some
information
on
it,
which
probably
haven't
seen
yet
so.
First
of
all,
I
do
want
to
always
show
the
overall
bigger
picture,
as
our
sharepoint
framework
is
really
intended
right.
Now,
it's
it's
extending.
C
So
it's
intended
to
be
actually
the
extensibility
platform
for
microsoft,
aviva,
microsoft,
teams
and
sharepoint
and
of
course,
it's
most
likely
being
used
in
a
sharepoint,
but
it's
actually
highly
convenient
for
microsoft
teams
as
well
and
and
viva
as
we're
surfacing
sharepoint
inside
of
the
the
microsoft
teams.
The
really
the
power
is
is
the
fact
that
you
don't
need
to
set
up
the
azure
applications.
Everything
is
other
hosted
and
optimized
for
hosting,
especially
if
you
only
have
a
ux
capabilities
or
you're
hitting
craft
apis.
C
I
will
share
one
simple
packaging
demo
around
that
one
as
within
the
following:
slides
as
well,
but
really
the
the
power
of
spfx
within
the
teams
is
that
you
don't
need
to
set
up
that
dasher
application.
You
don't
need
to
worry
about
app
app
registrations,
permissions
scopes,
any
of
that
one!
Everything
is
basically
automatically
taken
care
of,
so
you
can
just
synchronize
the
solution
to
microsoft,
teams,
app
catalog
and
voila.
C
So
whatever
has
been
released
right
now
with
vivo
connections,
just
just
a
scratch
on
on
on
all
of
the
things
which
are
in
the
pipeline.
So
I
can't
share
too
much
on
that
one.
But
within
few
weeks,
there's
microsoft
build
and
jeff
deeper
is
going
to
show
some
of
those
stuff
which
are
in
the
plan
now
on
the
112
one
release
details.
So
we
are
updating
the
note
version
to
14,
which
is
super
important,
so
we
are
finally
catching
up
on
the
latest.
C
Lts
version
of
node
will
have
more
access
on
the
base
structure
and
context
to
avoid
dome
dependence.
I'll
show
this
one
in
practice.
It's
not
a
mind-blowing
thing,
but
you'll
get
access
on
something
which
out
of
the
box
reports
are
using
to
understand.
Are
they
being
rendered
as
a
full
white
or
in
a
section
or
in
smallest
pieces,
which
is
important
for
web
parts
for
sure
the
support
for
the
complex
microsoft
team
solution,
I'm
going
to
show
a
demo
a
quick
demo
on
that
one
as
well.
So
how
does
it
actually
work
in
practice?
C
But
this
is
really
for
the
fact
that
if
you
as
an
example,
want
to
build
a
microsoft
teams
needing
application,
which
is
now
possible
with
onedrive
one
with
sharepoint
framework,
you
will
need
to
set
additional
settings
in
the
microsoft
teams
manifest
so
that
the
microsoft
teams
will
understand
that.
Oh,
this
component
is
intended
to
be
used
as
a
microsoft
teams,
meeting
application
and
in
those
scenarios
you'll
simply
embed
the
zip
file
or
the
manifest
file
or
the
microsoft
teams.
C
Solution,
structure
or
the
microsoft
theme
solution
manifest
file
inside
of
the
sppkt
file
and
I'll
show
that
one
in
practice
how
it's
actually
being
created
and
packaged
and
how
sharepoint
handles
that?
That's
for
synchronizing
things,
so
technical
nuances,
initial
support
from
the
team's
meeting
application,
there's,
unfortunately,
small
delays
on
the
microsoft
team
side
on
the
on
getting
some
of
the
server-side
changes
out,
so
we're
still
bending
on
some
some
areas
on
there,
and
there
was
a
good
demo
on
that
one.
C
However,
two
weeks
ago
and
the
recording
is
already
available
by
none
deep
who
showed
how
to
do
sharepoint
framework
driven
microsoft
themes
applications.
So
I'm
not
gonna
show
that
today,
right
now
we're
gonna
support
microsoft
teams,
sdk
1.8
1.9,
is
in
the
roadmap,
so
it's
going
to
be
supported
in
1.13
of
sharepoint
framework,
but
not
yet
again.
Technical
dependencies
here
and
there,
which
are
delaying
things
and
something
which
is
new
on
this
list,
is
also
the
list
and
library
subscription
general
availability.
C
So
previously
our
you
were
able
to
associate
your
web
part
to
be,
let's
say,
subscribed
to
events
from
document
libraries
and
sharepoint
sites.
But
now
you
can
actually
do
that
for
lists
as
well.
So
you're,
basically
able
to
say
whenever
a
new
item
is
added
on
the
list
or
a
library
or
whenever
there's
a
property
change
or
an
item
modification
in
a
list,
your
web
part
will
get
notified
so
you're,
basically,
then
able
to
refresh
the
web
part
ux
automatically
when
there's
new
items
being
added
on
the
list.
C
So
as
an
example
just
a
random
scenario,
you
have
like
something
like
power,
automate
pumping
in
your
business
data
from
azure
or
in
a
safe
way
to
a
list,
just
the
relevant
data,
just
just
that
data
which
you're
going
to
expose,
and
then
you
have
a
sharepoint
framework
webpart,
which
is
exposing
some
business
related
data.
It's
a
really
cool
scenario
as
well,
and
then
there's
a
lot
of
small
improvements.
C
Whatever
was
reported
in
112
for
those
are
going
to
be
fixed
and
then,
as
an
example
in
the
the
new
year,
generator
we're
going
to
show
the
version
number
of
the
spfx
which
are
running
a
simple
thing,
but
as
an
example,
chris
kent
has
been
requesting
that
feature
for
a
long
long
time.
So
that's
now
actually
there.
So
that's
chris,
at
least
this.
For
you
all
right
now,
let's
actually
do
a
few
demos
on
this.
C
Like
I
said
we
don't
have
a
massive
amount
of
time,
but
I'll
show
the
two
scenarios
in
a
more
detailed
way,
so
more
access
on
the
base,
structure
and
context
about
dome
dependency,
now
not
a
rocket
science
thing,
but
what
it
actually
means
is
that,
let
me
actually
add
here
is
really
a
simple
web
part,
just
focusing
on
the
scenario
and
and
technical
thing.
What
we're
doing
here
and
the
web
part
name
is
something
like
white
tester.
C
If
you
have
a
different
rendering
output,
when
you
are
in
less
than
400
pixels,
you
can
take
advantage
of
that.
Previously,
this
kind
of
a
functionality
required
that
you
are
detecting
the
dom
structured
and
then
analyzing.
Am
I
in
a
what
kind
of
a
section
how
many
columns
there
is
in
the
section,
and
then
you
adjust
your
rendering.
So
as
an
example,
the
out
of
the
box,
hero,
webpart
and
the
newest
web
parts
are
using
this
to
change
their
rendering
logics
logistics
from
being
multiple.
C
Well,
I
think
the
smallest
one
is
that
every
single
image
is
being
rendered
one
by
one
and
then
being
transferred
one
step
at
a
time.
So
it's
a
good
example
of
an
autobox
web
part
which
is
actually
taking
advantage
of
this
and
how
this
actually
works
again,
simple
thing,
but
I
think
it's
a
good
ad
add-on
and
it's
just
fair
that
you
will
get
access
on
the
same
things
as
what
out-of-the-box
web
parts
have,
and
this
is
really
nothing
more
than
let
me
actually
get
rid
of
that.
C
There
is
a
new
white
property
which
is
in
the
base
class
of
the
of
the
web
board,
which
will
give
you
the
white
in
pixels,
and
then
you
are
basically
able
also
to
subscribe
on
after
after
resize
event,
and
this
is
basically
for
catching
the
resizing
happening
on
a
page
so
that
you're
able
to
re-render
whatever
you're,
rendering
and
changing
the
rendering
logic.
In
this
case,
this
is
a
super
super
simple
example.
Just
focusing
on
the
chains
in
here,
but
good
to
see.
C
George
rodriguez
is
already
super
excited
on
the
on
this
one,
but
absolutely
a
useful
thing
and,
like
I
said,
of
the
box,
webparts
has
been
taking
advantage
of
this
one
as
well,
so
it's
good
to
be
available
for
you
as
well
now.
The
second
thing
is
that
we're
gonna
change
slightly
the
packaging
structure
and
packaging
model
within
the
sharepoint
framework
solution.
C
This
is
not
gonna
break,
obviously
anything
which
is
already
there,
but
this
is
an
additional
option,
and
what
we're
going
to
do
is
that
by
default
sharepoint
framework,
when
you
sync
your
solution
to
the
teams
by
default,
what
happens
is
the
sharepoint
framework
basically
reads
the
config
packet
solution
information?
It's
going
to
use
this
information,
for
example
in
the
developer
section
it's
for
the
name
and
website
url
privacy
url
in
terms
of
yours
and
npm
id
and
few
additional
settings.
C
C
C
Let's
open
it
in
here.
So
this
is
manually
created
c
file
which
have
been
created
by
adding
mic.
My
image,
my
manifest,
which
I
created
manually
and
the
two
of
the
images
and
then
basically
just
created
a
zip
file
in
here.
Of
course,
you
can
use
app
studio
in
in
teams
or
whatever
tooling.
You
prefer
to
create
the
manifest
file
and
then
export
that
from
there.
C
But
then
I
need
to
have
the
zip
file
named
as
teams
spfx.zip
and
that's
basically,
then
a
detection
for
sharepoint
that
oh
this
is
that
kind
of
a
zip
file
which
is
intended
to
be
the
one
which
was
synchronizing
the
teams.
So
so,
when
we
are
then
packaging
the
solution,
let
me
actually
do
that
quickly.
C
C
We
can
see
that
if
we
extend
the
sharepoint
folder
in
here
and
the
debug
folder,
which
actually
contains
what's
inside
of
this
sppkg
file
in
the
client
side
assets,
we
have
the
teams
spfx
app,
zip
file
available,
and
then
this
means
that
whenever
I'm
actually
installing
the
package
manifest
solution
inside
of
the
app
catalog
and
synchronize,
we
actually
take
that
manifest,
which
is
included
in
the
spp
kt
file.
And
then
we
use
that
one
yeah
where's
my
pros
and
there
we
go.
We
use
that
one.
C
Then,
to
actually
synchronize
or
add
and
install
that
to
the
themes
catalog
so
like
in
this
case,
I've
just
created
an
example
which
is
just
using
the
asynchronous
as
well
back
or
for
testing,
but
I'm
able
to
modify
all
of
this
stuff
directly
in
the
json
file
or
creating
the
whole
manifest
in
the
manifest
in
the
app
studio
and
then
synchronize
that
in
so
and
that
gives
the
flexibility
it
can
have
a
dependency
or
whatever
it
can
have
association
to
bots.
It
can
do
additional
other
settings
whatever
the
manifest
is
supporting.
C
We
support
that
as
part
of
the
spfx
solutions
as
well
and
also
including
store
deployments.
So,
if
you're
looking
into
getting
a
solution
to
the
store
that
works
as
well,
but
now
we're
running
out
of
time.
So
that's
a
really
quick
demo
on
two
of
those
things.
I
just
want
to
make
sure
that
everybody
understands
what
they
are
because
we
talked
about
it.
The
meeting
application
was
really.
C
There
was
a
great
demo
from
nandeep
nohan
two
weeks
ago
and
the
video
of
this
one,
individual
video,
will
go
out
in
a
few
days,
but
you
can
already
find
the
recording
from
two
weeks
ago
for
where
nandi
did
a
great
job
of
showing
how
to
build
microsoft,
teams,
meeting
application
with
sharepoint
framework.
The
recording
of
this
this
particular
call
will
be
out
within
the
microsoft
365
community
youtube
channel
within
24
hours,
and
please
follow
up
on
us
on
twitter.
C
But
thank
you
mike
and
and
abby
for
great
demos.
Today
I
do
apologize.
I
went
slightly
long
on
my
explanation
on
this
latest
on
spfx,
but
thank
you
everybody
for
joining.
Thank
you
for
your
feedback.
Please
keep
the
feedback
coming.
We
are
building
all
of
our
this
capability
for
you
as
our
customers
and
partners.
So
please
please,
please
remember
to
let
us
know
what
works
and
what
doesn't,
but
that's
it
for
now,
thanks
everybody
stay
healthy
and
we'll
be
in.