►
From YouTube: Microsoft 365 & SharePoint PnP Weekly – Episode 88
Description
In this weekly discussion of latest news and topics around Microsoft 365, hosts – Vesa Juvonen (Microsoft), Waldek Mastykarz (Rencore), are joined by - Andrew Connell - MVP, Instructor, owner of Voitanos. Andrew’s “Mastering SharePoint Framework” course – a 2-year endeavor is content complete – well almost. Waiting on SPFx v1.11 release. Discussed: SPFx – capabilities, reliability, completeness, engineering communications, need for functional consistency across apps and tools that encompass more just SharePoint. Insights around UX components including Office UI or Fluent fabric versions – what to use? Additionally, in this episode, 18 recently released articles from Microsoft and the PnP Community are highlighted.
See the full blog post for this episode at https://aka.ms/M365DevBlog
• Download the podcast for this episode at http://pnpweekly.podbean.com.
• Learn more about the SharePoint developer community at: http://aka.ms/m365pnp.
• Visit the Microsoft 365 & SharePoint Community - PnP YouTube channel: https://aka.ms/spdev-videos
B
B
A
Yeah,
we'll
still
have
12
episode,
so
it's
okay.
Now
it
is
22nd
of
June
and
2020
and-
and
it
is
take
number
three-
apparently
no-
it's
not
take
number
one
today,
but
before
we
go
to
our
visitor,
so
my
name
is
Devin
and
I'm,
a
program
manager
from
the
one
crochet
bond
platform
team
and
the
PMT
weekly.
It's
all
about
what's
happening
within
the
extra
365
area
within
the
week,
so
we're
trying
to
collect
all
of
the
teams
block
articles
in
365,
developer
articles,
SharePoint
articles.
A
B
B
B
C
B
C
C
My
shoulders
look
a
little
bit
higher
they
might,
they
might
look
a
bit
higher
from
the
weight.
That's
been
removed,
yeah
it
was.
It
took
a
lot
longer
than
I
anticipated
and
part
of
that
was
because
I
over
scoped
it
and
didn't
think
too
much
about
the
business
side
and
had
to
pick
up
a
couple
like
contract
type
jobs
in
the
middle
of
it
a
few
times
to
be
like
just
to
maybe
pay
the
bills
and
stuff
but
yeah.
C
So
my
mastering
the
SharePoint
framework
course
is
content
complete.
It's
not
I
would
I'll
say
it
done,
but
there's
still
a
bunch
more
work.
I
want
to
do
to
it
like
refreshing
stuff
when
it
takes
to
it
years
to
build
a
course
Microsoft.
You
guys
have
shipped
a
few
things.
I
can
go
back
and
refresh
a
couple
of
those
videos,
so
right
used
to
do
this.
C
In
the
past,
a
good
I've
started,
making
a
spreadsheet
and
I've
got
a
little
schedule
of
how
how
many
videos
I'm
gonna
go
through
every
day
or
every
week,
and
then
catalog
like
what
has
got
to
be
changed.
What
should
be
changed
and
what
would
be
nice
to
be
changed
is
probably
never
gonna
get
changed,
but
what
needs
a
video
record?
What
can
just
be
notes
on
the
slide
on
under
the
notes
and
stuff
like
that,
so.
A
Yeah
so
related
on
that
one
actually,
because
your
training
is
really
about
to
show
up
on
framework.
That's
that's
precisely
what
we
wanted
to
bring
you
here
for
and
have
a
discussion
on
that.
What's
what's
your
take,
your
training
is
now
feature
complete
mm-hmm.
What's
your
take
on
a
shape,
one
framework,
is
it
a
mature
enough?
Is
it
what's
your
kind
of
feelings
around
the
platform.
C
To
be
completely
honest,
man
I
really
do
like
what
what
what
mic
redun
I
really
do
like
the
framework.
I
love
the
direction
of
being
client
side.
First
I,
like
the
supported
stuff
that
you
provide
server
side
for
especially
around
like
the
azure
ad
stuff
and
the
deployment
everything
I
really
like
about
it.
I
know:
I
talked
to
someone
recently
we're
like
well,
what
more
would
you
really
want?
A
C
Thing
that
I
think
gives
me
the
most
frustration.
It's
not
just
me,
but
I
feel
like
I'm,
echoing
what
a
lot
of
the
developers
are
seeing
is
that
I'm
concerned
about
a
confidence
level
and
the
SharePoint
framework
going
forward,
and
it's
mostly
because
so
many
things
that
have
shipped
don't
feel
like
they've
shipped
and
then
been
finished,
I
feel
like
we've
shipped
an
MVP,
or
we
finished
like
a
v1,
but
then
it
hasn't
been
fully
complete.
So
a
great
example
of
this
there's
really
two
good
examples
of
this.
C
One
of
them
is
around
so
many
changes
that
we
see
coming
from
I
presume
from
the
team
that
is
engineering
all
the
UX
for
the
lists
infrastructure
and
there's
events
that
are
supposed
to
be
bubbled
up
and
the
snow
when,
like
a
view,
changes
or
when
this
changes
and
those
a
lot
of
those
things
break
and
when
they
break,
we
don't
have
any
kind
of
insight
into
okay.
Was
that
a
SharePoint
framework
break
or
is
that
a
platform
break?
C
Is
a
code
break
and
then,
when
they
go
back
in
and
they
say
they
fix
something,
there's
no
real
follow
up
on
what
fix,
and
so
it's
really
hard
to
understand
what
that
is,
and
if
I'm
a
developer
building
something
on
top
of
this
platform,
it's
hard
to
have
confidence
in
it.
The
other
one
too
is
that
goes
along
with
that
is
around
Microsoft
teams,
where
I
mean
if
I,
if
I'm
supposed
to
take
stuff
for
SharePoint
framework,
can
be
I
use
it
both
in
SharePoint
framework
or
SharePoint
Online
and
Microsoft
teams.
C
I
expect
it
to
work
the
same
way
and
I.
Just
I
feel
like
there's
a
lot
of
stuff
with
teams
both
the
web,
the
desktop
and
the
mobile
client
that,
when
I'm
building
a
SharePoint
framework
based
solution,
it
works
one
way
in
SharePoint.
It
works
one
way
in
teams
web
one
way
in
teams
desktop
in
one
way
in
teams,
mobile
and
I.
That's
the
part
that
it
it's
I'm!
C
Yeah,
it
just
feels
like
there's
stuff
that
just
could
be
buttoned
up
and
just
be
a
little
bit
tighter
there
to
give
me
more
confidence
on
it
and
I'd.
But
overall
it
still
I
love
the
framework.
I
love,
what
I
love,
what
you
guys
have
done
and
I
love
I
think
one
of
the
things
that
I've
seen.
That
is
probably
the
biggest
challenge
like
from
one
of
the
nice
things
about
doing
a
course
like
this
and
working
on
it.
C
For
two
years,
two
and
a
half
years
and
having
you
know,
thousands
of
customers
that
are
that
are
gonna
have
gone
through
the
course
I
see
a
lot
I
get
lots
of
feedback
from
them
and
see
lots
of
questions
that
they
ask
and
I
think
the
overwhelming
thing
that
people
still
the
majority
of
the
developers
don't
really
see.
At
least
those
are
new
to
the
SharePoint
framework.
Is
that
there's
really
not
all
that
much?
C
That's
special
and
I
mean
that
as
a
compliment,
it's
client-side
dev
and
you
don't
need
to
they're
like
well
I'm
trying
to
do
this
I'm
trying
to
do
this.
I
can't
get
over
a
SharePoint
framework,
I'm
like
when
you
go
to
Google
something
stop
putting
SharePoint
in
your
description,
all
right,
I
think
you're
gonna
find
so
many
more
solutions.
You
have
a
problem
with
like
node
or
an
NPM
thing.
I
keep
this
thing.
I
keep
doing.
Sharepoint
you've
done
it
out,
I'm,
trying
to
I'm
trying
to
do
the
gulp
server
like
okay,
you're
thinking.
A
B
Yeah,
but
then
then,
there's
also
the
audience
that
right
that
I
that
for
years,
they
were
used
to
doing
exactly
that
right
like
if
you
wanted
to
do
things
on
SharePoint,
you
have
to
do
it
this
specific
way
with
disposition
tools,
and
there
was
no
alternative,
whereas
so.
This
is
their
use
very
much
to
dis
minds
like
in
everything
that
they
search
include
SharePoint
in
there,
because
you
will
not
find
it,
whereas
nowadays
that's
no
longer
the
case
right
right.
C
And
that's
and
you're
right
role
like
and
that's
the
that
is
part
of
the
heart.
The
hard
part
about
this
is
that
we're
we're
trying
to
bring
people
from
the
there.
Have
this
baggage
mindset
and
it's
it's
not
that
it's
bad,
it's
just
that
a
lot
of
it
doesn't
apply
now
and
and
then
you're
I'm,
not
when
I
try
to
when
I
talk
to
my
students
about
it,
I
don't
I,
try
to
put
it
across
them
going
look.
C
This
is
actually
easier
than
you're,
making
it
out
to
be
you're
trying
to
make
this
work
in
SharePoint,
and
if
you
take
a
step
back
and
don't
try
to
make
it
a
work
in
SharePoint,
but
think
what
is
the
client-side
way
of
doing
what
you're
trying
to
do
your
life
is
going
to
get
better
and
if
you
need
something
specific
to
SharePoint
like,
for
example,
how
do
I
get?
How
do
I
call
a
secured
service?
C
Well,
if
it's
an
azure,
ad
and
you're
building
something
in
SharePoint
Online,
the
SharePoint
framework
API
is
going
to
do,
is
gonna,
provide
you
some
tools
that
makes
your
life
a
lot
easier.
You
don't
have
to
worry
so
much
about
how
to
get
a
token
and
how
to
call
the
ground.
A
lot
of
that
stuff
is
simplified,
but
don't
think,
like
you
know,
I'm
trying
to
do
I,
don't
know
I.
C
A
A
A
C
This
is
a
this
is
actually
a
blog
post.
That's
it's
in
draft
form.
Right
now
on
my
on
my
laptop
along
with
my
other
summer
wish
list.
I
wish
I
had
these
out
before
we
did
this
cult,
but
to
me
a
library
component
only
makes
sense
in
one
scenario
or
two
scenarios,
and
one
of
them
to
me
is
is
heavily
discounted,
but
I
also
recognize
that
people
don't
agree
with
me
on
this.
C
Whereas
if
you
do
an
NPM
package,
you've
got
to
put
a
JavaScript
file
somewhere
in
a
CDN
somewhere
or
wherever
to
me,
I
discount
that
because
I'm
like
look,
if,
if
that's
actually
a
big
issue
to
you
of
all
the
other
stuff
you're
doing
of
putting
a
file
somewhere
that
you
can
get
to
Mike
seriously,
how
long
have
you
been
a
web
developer,
so
I,
don't
I,
don't
buy
that
as
a
as
a
as
an
option.
I
understand
people
like.
Oh
you
understand
my
scenario.
Meisner
is
unique.
I'm,
like
nobody
is
unique
in
this
world.
C
So
to
me,
I
always
go
with
like
an
NPM
package,
because
unless
I
have
to
have
a
SharePoint
API,
because
it's
the
SharePoint
API
there's
no
sense
in
putting
an
NPM
package.
I'm
not
gonna,
be
able
to
test
the
thing
anyway.
So
I
look
without
doing
like
a
ridiculous
amount
of
mocking
so
I'm
like
alright
I'm,
also
just
doing
a
library
component
and
just
be
done
with
it,
because
I'm
already
kind
of
I've
already
handcuffed
myself.
C
A
Was
one
of
our
top
requests
in
user
voice
and
even
internally
there
was
people
who
were
saying
well,
why
do
they
need
this
yeah?
We
we
use
it
internally
because
of
the
the
mono
repo
setup
which
we
have,
which
is
super
massive
and
it's
super
complex
and
all
of
that
stuff
and
and
it
actually
helps
and
abstracting
certain
reusable
components
and
all
that
which
okay
fair
point
and
but
then
basically
a
certain
clever
people
notice
that
hey
you
have
a
cleric,
compare
the
component
type
code
library
we
wanted
as
well.
A
B
So
the
interesting
case
for
that
that
I
find
is
the
fact
that
libraries,
what
what
you
get
for
free,
is
that
it
only
loads
and
runs
once
on
a
page.
So
I
imagine
that
you
have
three
webparts
that
you
put
on
a
page.
It
will
be
loaded
and
it
will
run
only
once
on
a
page.
If
you
want
to
sure
you
can
achieve
the
same
on
NPM
package,
but
then
you
will
need
to
build
all
of
that
by
yourself
or
here,
you'll
get
it
for
free
right.
It's
there.
C
No
I
don't
think,
but
that's
not
I.
Don't
is
that
really
true,
though,
because
when
you
do,
if
I
have,
if
I
have
three
webparts,
if
I
build
an
indian
package-
and
I
put
that
and
I
host
that
in
some
CDN,
if
I
build
three
separate
webparts
with
three
separate
sharepoint
framework
solutions
and
like
projects,
three
different
mps,
PPK
g's
and
they
all
reference
the
same
bundle
from
from
a
using
in
the
config
file
pointing
to
the
externals,
then
the
sharepoint
module
the
module
loader
on
that
the
sharepoint
framework
employees.
C
C
How
the
sharepoint
framework
is
pulling
this
stuff
down
as
a
library
component,
because
you're
just
pulling
something
from
some
remote
look
at
the
manifest
it
ends
up
being
this
and
the
net
result
correct
me
if
I'm
wrong
well
that,
because
I
like
when
I
looked
at
the
I've,
looked
at
the
manifest
that's
generated
on
both
options,
I
don't
see
a
difference.
Aside
from
one
is
pulling
from
locally
inside
of
SharePoint
Online,
with
the
other
one
is
pulling
from
some
extraction.
B
C
B
Default
thing
for
hey
I
want
to
have
this
reasonable
thing.
Your
first
choice
is
always
this
not
like
your
first
choice.
It's
exactly
is
that
you
should
go
10
p.m.
because
that
is
what
the
world
does.
If
you
happen
to
have
this
specific
case,
where
you
need
to
have
one
and
no
not
less,
no
more
of
one
of
something
on
a
page,
libraries
might
be
an
easier
way
around
it,
but
that
is
just
like
this
very
specific
case.
Right
yeah.
C
And
you're
right
and
then
the
other
thing
to
it
as
well.
That's
also
beneficial
of
using
a
library
component
is
that
you're
using
the
you're
using
the
SharePoint
framework
build
tool
chain
and
if
I
decide
to
go,
build
my
own
NPM
package.
You
got
to
stand
that
up.
I
mean
there's,
there's,
there's
a
tons
and
tons
of
ways
you
can
go
through
and
stand
this
up,
but
there's
like
in
my
course
I
showed
both
options.
C
I
showed
you
a
library
component,
then
I
showed
it
an
NPM
package,
but
then
I
find
that
the
way
the
best
way
to
get
people
the
SharePoint
developers
to
understand
that
the
NPM
package
is
a
good
option.
Is
I
stand
up
the
the
NPM
package
in
the
build
tool
chain.
As
close
I'm
model
it
Orient's
it's
inspired
by
the
SharePoint
framework,
so
like
I'm,
using
a
very
similar
web
pack,
setup
I'm
using
a
very
similar
like
I'm,
using
an
NPM
script
instead
of
using
a
gulp
task.
C
It's
just
not
necessarily
for
what
I'm
showing
you
it's
unnecessary,
I'm,
not
saying
the
SharePoint
framework
was
unnecessary
to
use
it,
but
if
you
can
model
it
the
same
way,
then
I
think
things
do
get
simplified
a
bit,
but
I
mean
look
cards
on
the
table.
You've
got
two
options
and
people
can
choose
either
one
they
want,
and
that's
one
of
the
nice
things
that
I
can
choose
to
say:
I,
don't,
like
library
come
on,
it's
I'm
only
gonna
use
NPM
packages,
whereas
someone
else
can
say
no
I
prefer
library
come
on.
C
A
About
other
areas
of
SharePoint
framework
and,
let's
say
modern
team,
modern
development
and
modern
SharePoint
experiences.
How
what's
your
feedback
to
you
as
they
related
on
the
on
the
experience?
There's
any
other
kind
of
a
pointers,
overlay,
sure
the
consistency
polishing
here
and
there
we
get
that
with
the
go
and
absolutely
be
knit
together
and
invest
our
time
on
there,
not
other
than
dance.
Well,
what
are
the
other
things
which
comes
in
mind
or
any
general
feedback
is.
C
General
feedback:
well,
is
this
the
compliment
section
or
is
this
the
grit,
the
errant,
the
grievances,
the
area
I,
think
you
know
the
one
thing
that
I
think
that
as
many
times
as
Microsoft
does
try
to
to
clarify
it
and
I
think
the
parts
that
does
get
a
little
confusing
is
the
story
around
the
UX
components.
I
think
it's
I
mean
between
from
going
from
you
know,
office,
UI
fabric,
the
JavaScript
Edition,
then
the
core
editions
and
the
react
conditions
now
we're
going
to
fluid.
C
C
What
I
guess?
What
kind
of
scares
me
a
little
bit
is
the
fact
that
we
have
a
fluent
package.
That's
got
a
name
called
North
Star
and
it's
like.
Oh
my
god.
Please
don't
try
and
do
everything.
Please
don't
try
and
do
everything
regardless
it's
one
of
the
things.
That
is
something
that
all
of
us
do
still
struggle
with
and
part
of
it's
because
we're
in
this
I
was
gonna.
A
Say
begin:
can
we
explain
the
recommendations
and
what
it
is,
because
those
who
are
not
super
familiar,
they
might
not
be
following
up
on
what
I
were
referring
to.
So
by
default,
we've
been
saying
use
of
a
CI
fabric
as
the
UX
lair
for
your
SPF
X
components,
but
obviously
our
fabric
is
now
gone,
but
this.
C
A
C
Spent
a
good
amount
of
time,
the
last
two
weeks,
making
sure
that
I
understood
this
because
I
updated
the
docs
on
this
as
well-
and
this
is
not.
This
is
not
andrew
saying
this
is
and
repeating
what
the
fluid
guys
and
the
microsoft
guys
said:
yeah
the
sharepoint
guys
so
just
to
cut
to
the
chase.
The
TLDR
is
the
sharepoint
team
says,
use
the
office.
Ui
fabric
react
components,
period
use
those
today.
So
what
you
get
any
sharepoint
framework
project
use
that
same
package.
Don't
flip
things
over
to
use
fluent.
C
If,
under
the
covers,
they
do
that,
don't
don't
screw
with
it,
don't
mess
with
it.
Just
leave
it
as
is
use
the
lot
use.
What's
provided
to
you,
what
mike,
what
what
the
fluent
team
has
done
is
their
or
they've
renamed
that
package.
If
you
look
at
the
NPM
package,
they've
renamed
that
package
to
app
fluent
UI
/
react:
that's
what
the
office,
your
I
thought
react.
C
C
That's
that's
verbatim
from
the
fluent
team,
so
in
other
words,
for
you,
SharePoint
developers
that
are
out
there
remember
how
back
in,
like
1.8
and
1.9,
we
had
stuff
get
refactored
out
of
the
web
part
base
package
over
property,
paying
stuff
and
moved
in
the
proper
paying
package,
and
all
that
did
was
just
export
things
back
and
forth.
That's
where
we
are
right
now
with
fluent
okay,
yeah,
so
keep
using
the
office
UI
fabric
keep
an
eye
on
fluent
UI.
We
don't
have
a
timeline.
We
just
know
what
their
inspiration
is.
A
C
A
And
the
situation
might
evolve
on
Orton,
but
one
step
at
a
time,
so
I
think
we're
in
this
yet
ia
autumn.
But
I
didn't
say:
there's
this
classic,
let's
say
I
think
both
of
you
do
agree
understand,
and
so
this,
the
one.
How
would
I
put
it
one
kind
of
a
characteristics
of
doing
a
website
development,
is
that
people
always
want
to
use
the.
C
A
A
B
For
big
part,
that's
on
on
us
and
and
on
us
was
I
say
like
us
three
and
then
PNP
group
to
basically
offer
the
guidance
and
tell
everybody
like
people
ask
that,
because
they
do
not
know
where
they
are
so
so
they
turned
out
and
I.
Think
it's
our
job
to
clarify
that
it
is
done
the
better
we
do
it.
Then
the
fewer
I
said:
okay,
we're
here.
These
things
have
been
announced,
but
they're
not
Yeti,
not
ready,
yet
to
be
used
in
Congress
of
that
and.
A
And
one
of
the
things
where
people
need
to
pay
super
careful
is
that
the
before
you
start
using
any
of
the
new
components,
really
double
check
the
status
and
a
license
days
and
all
of
that
because,
obviously,
at
the
same
time
when
we
call
out
that
need
to
explicitly
give
the
guidance
on
when
it's
actually
usable
there's
a
lot
of
interests,
form,
let's
say
I'm,
not
referring
the
fluent,
but
there
are
other
components.
Library
makers
who
would
love
you
to
use
their
stuff?
A
Is
it
actually
usable,
that's
a
separate
discussion,
but
they
would
love
you
to
use
the
stuff
because
then
they
get
usage
and
and
there's
always
this
kind
of
an
interesting
balance
of
yeah.
You
were
saying
that
it's
ready,
but
I
found
these
and
these
issues
well
yeah.
So
those
are
issues
which
we
knew,
but
so
what
is
actually
usable
and
what's
not
usable
might
be?
And
what
is
the
message
and
is
it
actually
usable?
My
fits
your
different
things
so.
B
Should
not
be
tasked
with
doing
their
own
research
into
all
these
different
libraries
issued
by
Microsoft,
because,
like
one
like,
why
redo
the
same
work
all
over
again
come
to
the
different
conclusions
and
have
there
is
that
somebody
might
find
something
and
they
miss
something.
So
I
think
that
we
should
offer
a
single
channel
for
all
these
different
questions
and
I
think
we're
doing
that
to
a
part.
Can
we
improve
it?
Absolutely.
A
A
Official
Docs
from
Microsoft
and
then
we
go
to
the
office.
You
have
fabric
usage
guidance,
which
is
he
has
updated
as
well.
So
if
you
updates
there
wasn't
too
much
support
posts
recently
bit
in
past
few
weeks,
and
there
are
certain
reasons
on
it
which
we
don't
need
to
live
in
the
discussion,
and
you
will
see
the
normal
cycles
to
actually
start
moving
this
week
and
by
the
way,
as
an
example
see
some
dotnet
standard
is
scheduled
to
go
out
this
week.
A
C
People
have
been
harping
on
this
for
so
long
I'm.
Now
that
it's
gonna
be
available
this
week.
We
better
see
those
downloads
really
kick
in,
because
if
it,
if
it
comes
out
the
downloads,
aren't
there
it's
like
what
that
you
guys
were
asking
for
something
and
they
did
it
and
they
didn't
man
you're
not
using
it.
Are
you
kidding
me
maybe.
A
Now,
technically,
that
is
actually
unfortunately
possible,
but
let's
not
scare
to
technical
details
related
on
this
one.
So-
and
you
heard
it
from
here
first
this
week,
you're
seeing
this
on
Tuesday,
it
might
already
be
out,
but
there's
gonna
be
a
new
version
of
Microsoft
SharePoint
Online
system,
which
includes
and
contains
also
a
standard
version
of
season.
So
so.
A
Correct
so
when
you're,
using
that
in
Universal,
Studio
or
in
environment,
which
is
targeted
for
dotnet
core
or
doesn't
standard,
you
got,
those
templates
will
be
reusable.
That's
a
big
win.
Finally,
and
the
reason
why
it's
by
the
way,
epic
win,
know
I'm
Andy,
railing
user
voice,
share
points,
and
is
this
one?
B
B
A
Now
this
one
is
is
basically
much
tougher
to
get
adds
presents
templating
for
the
looking
component,
a
react,
wrapper
preview
and,
more
so
basically
improved
experience,
improved
layouting
related
on
that
presence,
information,
I,
think
waldek,
because
we're
and
actually
a
sea
of
course
you're.
The
old-school
SharePoint
you
extra
dollar,
as
well
already
combined
in
the
content,
management,
server
and
SharePoint
2003
and
making
stuff
happen.
A
C
You're
in
the
part
that
you've
highlighted
here,
I
are
when
I
pulled
the
link
up
earlier
and
posted
it
in
a
little
chat
for
you
guys
to
put
in
the
show
notes.
I
already
saw
like
in
that
third
paragraph,
there's
a
typo
in
there
so
I've
already,
I'm
already
got
it
like
highlighted
on
my
machines.
I'm
like
it
will
be
a
PR
going.
A
B
C
B
A
A
A
C
Are
in
that
is
a
good
nice
highlight,
though,
because
we
are
in
the
middle
of
doing
a
huge
refresh
on
our
was.
We
are
doing
a
huge
refresh
on
all
the
SharePoint
framework
talk
right
now
so
like
today
we
refreshed
everything
from
in
the
SharePoint
framework
section
all
the
way
down
to
library
components,
so
extensions
library,
components,
webparts
getting
started
overview.
All
that
stuff
was
refreshed,
analyzed.
C
It
was
the
content,
has
all
been
it.
There's
no
reorganization.
It's
all
just
making
sure
that
everything
is
correct.
Everything
is
current.
There's
no
typos!
We
have
a
lot
of
formatting
issues,
spelling
issues,
but
everything
is
just
getting
cleaned
up
and
current.
So
you
know
that
it's
like.
Does
this
still
work?
This
is
still
apply
so
like,
for
example,
if
you
scroll
down
on
this
page,
you'll
see
a
section
where
it
even
calls
that
big
note
section
right
there.
It
talks
about.
C
C
B
C
A
So
this
this
is
also
something
which
we
discussed
before
the
recording,
but
I,
it's
fine
dimension
and
during
the
recording
as
well.
So
obviously,
we
need
to
be
more
specific
on
what
this
actually
means
in
practice
for
the
enterprise
customers,
because
in
the
system
integration
world
or
let's
say
a
consultant
world
consultant
build
something
for
customers.
It
has
to
remain
there
and
not
suddenly
get
broken
out
of
blue,
because
the
consultant
is
no
longer
available.
So
we'll
we'll
definitely
get
more
guidance
and
clarifications
on
these
things.
A
C
Have
it
let's
open?
This
is
an
open
question
to
the
team
about
this
is
affluent
guys,
which
is
basically.
Does
that
mean
if
I
build
something
today
and
I
roll
it
out
and
I
don't
touch
it?
Is
there
a
chance
that,
without
touching
anything
stuff
is
gonna
just
break
in
the
next
up
to
two
times
over
the
next
year?
And
it's
unclear
I
mean
I,
get
it
if
you
roll
out
it.
C
If
you
roll
out
some
breaking
changes
and
in
a
new
major
version,
that's
fine
I
mean
I'm,
not
saying
you
guys
aren't
entitled
to
make
changes,
but
it's
more
that
are
those
changes.
What's
gonna
be
deployed
and
all
in
my
project
is
gonna,
be
relying
on
those
things
on
SPO
and
without
making
a
change
you
broke
my
stuff
or
is
it
like
SharePoint
framework,
where
I
reference
a
specific
version,
and
rather,
if
1.11
comes
out
and
it
does
a
breaking
change,
it's
not
gonna
affect
my
1.8
component,
which.
A
Is
most
likely
the
case,
but
let's
get
the
clarity
on
that
one.
So
now
articles
something
new
which
came
out
actually
last
week
as
well
related
on
under
the
under
the
SharePoint.
But
this
is
absolutely
a
big
focus
area
and
for
us,
as
well
so
under
the
shipment
development
and
build
for
Microsoft
teams.
A
So
there's
a
article
series
which
we
well
a
basically
waldek
was:
was
the
author
of
these
things
and
really
concentrating
on
on
the
fact
that
when
you're
building
stuff,
the
team's,
the
considerations
and
and
preferences
and
areas
to
figure
out
and
make
a
decision
so
on,
like
the
the
settings
and
configurations
related
on,
you
know
personal
application,
good
example
or
the
this,
which
you
can
say
that
the
the
the
title
of
the
web
part
is
not
rendering
it
off
sui
fabric
styling.
So
it's
not
at
using
the
right
font.
So
how
do
you
fix
that?
A
Or
the
considerations
for
data
on
that?
So
all
of
that
is
basically
being
called
outs,
which
is
helping
people
that
then
builds
SharePoint
framework
solution
for
Microsoft
themes,
so
really
cool
stuff
as
well.
Now,
advancing
marks
of
teams
so
natural
operating
a
pandemic
scale,
so
this
is
actually
Microsoft
one.
This
one
is
pretty
interesting
from
our
crucian
offs.
A
Basically,
how
did
we
deal
with
the
massive
jump
on
on
the
demand
in
the
cloud,
because
almost
everything
in
Microsoft
resist
5
is
being
built
on
top
of
Microsoft
Azure,
and
then
how
did
we
scale
up
the
things
during
this
in
this
last
month,
because
well,
growth
has
bent
out
of
this
world
so
really
cool
stuff,
absolutely
and
then
nobody
there,
based
on
the
learnings
and
based
on
the
things,
we're
doing
all
sort
of
changes,
for
example
in
SharePoint
Online,
and
speeding
up
the
performance
and
all
that
stuff,
so
really
pretty
cool
stuff.
That's
cool.
C
A
This
actually
gets
slightly
interesting,
but
anyway
using
the
microsoft
search.
Api
is
to
with
the
graph
from
chevron
framework.
That's
basically
what's
happening
in
here,
and
this
one
is
from
chilla
Rodriguez
from
storm
technologies
and
merge
PDF
files
from
SharePoint
using
Azure
function
as
a
really
cool
stuff
as
well.
So,
basically
again,
pretty
much
I
didn't
have
a
look
on
this.
One
super
detailed,
but
I
think
we're
using
myself
craft,
no
we're
using
PDF
documents
as
an
object
anyway.
A
B
Well,
so,
yes,
so
that
is
in
our
preview
of
211,
with
improved
creation
of
teams,
improved
upgrade
of
SP
FX
project
and
new
sample
script,
which
is
about.
If
you
have
a
number
of
images
in
a
document
library
how
you
can
insert
them
into
a
Word
document
and-
and
that
is
also
including
the
help
from
CLI
to
get
these
images
out
and
then
in
the
dock.
So
ya.
A
In
school
and
this
one
making
SPF
X
back
part
searchable
lesson
learned
from
Thomas
daily.
So
how
do
we
expose
and
the
metadata?
What
are
the
properties
which
should
be
indexed
by
the
search
good
stuff
as
well?
I
think
we
did
mention
this
in
the
docs,
but
it's
kind
of
a
one
mention
here
and
there
and
it's
good
and
I.
A
Face
detection
so
Ambus
facial
recognition
on
the
sharepoint,
so
pretty
cool
stuff,
actually
again
combining
a
sure,
machine,
learning
and
intelligence
together
with
sharepoint
and
implementing
stuff,
so
really
cool
stuff.
From
that
perspective,
and
how
do
I
do
is
stuff
in
company
with
services
how
things
work
face
api
and
off?
That's
a
really
really
cool
stuff.
A
This
is
from
Sergey,
as
their
gave.
Sharepoint
framework
fast
serve
now
supports
library
components,
so
he
basically
has
built
this
fast
serve
process
which
will
speed
up
the
gulp,
the
the
bundling
and
packages
and
all
that
stuff
in
in
SharePoint,
and
now
it
supports
library
services
as
well.
So,
basically,
you
call
SPF
X
first
serve
there.
We
go
and.
C
He's
done
a
lot
of
really
cool
stuff
around
performance
on
the
build
tool
chain
that
I
mean
it's
cool
stuff
that'd,
be
great
to
see
it
kind
of
baked
into
the
underlying
tool
chain,
but
it's
stuff
that
I
mean
it
definitely
is
it's
definitely
more
on
the
400
level.
If
people
want
to
dive
in
and
take
a
look
at
it
and.
A
Then
this
one
from
Gautam
says
provisioning,
I,
show
80
users
and
assign
them
licenses
using
PMP
turn
on
templates.
So,
and
this
is
good
good,
you
know
it
is
from
yeah.
Go
them
as
well.
Hey
I
wasn't
aware,
but
basically
a
PMP
tenant
templates
do
support
actually
provisioning
of
users
as
well,
which
is
pretty
cool,
so
you
can
do
your
automation
cross
the
demand
for
your
test
environment.
So
that's
pretty
cool
stuff
configuration
ad
application
with
integration,
assistance
by
wall
Dex.
You
want
to
actually
do
a
quick
brief,
quick.
B
Pressures
so
there
was,
there
was
a
new
thing,
I
noticed
in
ad,
where
there
is
new
option
available
that
allows
you
to
check
if
the
80
ad
that
that
you
registered.
If
that's
set
up
correctly
for
scenario,
you
want
to
use
it
for.
So,
if
you
build
a
web
app,
you
need
different
things.
Then,
for
example,
when
you
build
mobile,
app
or
desktop
app,
daemon
say
right,
so
there
are
different
ways
to
use
ad
yeah
and
there's
now
an
option
available
in
portal.
B
That
tells
you
that
that
allows
you
to
check
what
kind
of
app
you
want
to
build
and
then
based
on
that
checks,
do
you
have
everything
in
place
like
you
can
see?
There
I
have
three
three
things
correctly,
but
there
are
two
things
that
require
attention,
so
all
of
that
is
now
they're
available
out
of
the
box,
helping
you
to
catch
your
ad
FS
in
place,
because
all
is
the
very
first
thing
you
have
to
do
before
you
can
even
do
anything
and
it's
often
the
thing
that
does
struggle
with
the
most
right.
A
Lot:
it's
it's
a
crazy
investment
area
for
sure
providing
guidance
directly
in
there
on
that
location.
So
this
one
is
from
Robert
winter
and
tweet
stream
and
he's
actually
twists.
Twitch
twitch
streaming
doing
SharePoint
framers
development,
so
working
with
their
probably
been
a
ship
on
framework
web
parts,
and
these
are
pretty
long.
But
it's
actually
pretty
cool
to
get
a
detailed
description
and
description
on
how
things
work
and
not
on
the
month,
necessarily
in
the
400
500
level,
which
is
great
but
a
lot
of
rather
you're,
learning
the
basics
and
getting
started
on
doing
develop.
A
C
A
A
So
now
then,
from
Jonah
client
site
since
the
dividend
documents
within
so
basically
talking
about
license
ID
since
sensitivity
and
labels
and
security
and
how
do
how
do
these
actually
impact
and
then
on
the
most
racist
five
super
important
things
as
well
to
understand
what's
their
out
of
the
box,
because
there's
a
lot
of
radically
man
for
this
kind
of
control
and
governance
from
a
from
a
a
company's
perspective.
So
and
these
were
basically
the
nuclear
packages
related
on
and
the
almonds
were
later
I'll
see
some.
A
So
let's
get
back
on
the
on
this
discussion
and
we
need
to
close
up
quite
soon
because
we're
running
out
of
time
as
well,
but
a
few
things
from
my
side.
What's
gonna
happen
this
week,
big
things
we're
gonna,
hopefully
release
the
see
some
donuts
and
who
gets
now.
Did
you
hear
heard
from
here?
First?
Finally,
it
looks
really
positive,
so
this
is
gonna
happen,
99.99%,
certainly,
and
so
it's
just
a
matter
of
writing
the
blog
post
and
pushing
stuff
out,
and
then
we
kind
of
release.
The
new
new
videos
here
is
related.
A
Ownio
teams
will
have
eight
different
MVPs.
Well,
one
Microsoft,
employee,
Bob
chairman
and
it's
seven
different
MVP
is
actually
explaining
how
to
get
started
on
yo
teams.
We're
gonna
talk
about
ship
and
starter
kit,
be
to
release,
and
so
there's
kind
of
be
a
blog
post
related
on
that
one.
What
else
is
happening
but
I?
What's
on
yours,
I'm
working
on.
C
B
C
Yeah
so
anyway,
I'm
that'll
come
later,
but
yeah
I'm
working
on
I'm
working
on
a
similar
to
how
that
leads
teams
app
that
you
that
wold,
like
that
you've
created
using
SharePoint
framework,
I'm
working
on
something
similar
to
that.
That
is
kind
of
like
a
reference
sample
kind
of
like
something
that
developers
may
want
to
even
install
on
their
own
tenant
to
be
able
to
use.
That's
gonna
expose
if
you're
a
SharePoint
developer.
A
Reference
samples,
the
team's
development,
is
such
a
big
focus
topic
for
us.
So
then
also
we're
working
together
with
ACN
and
Wallach
on
these
areas,
and
the
guidance
and
vasa
could
see
that
the
New
York
ated
guidance
on
the
documentation
as
well
and
having
a
reference
samples
super
important,
because
those
help
then
people
to
explain
the
stories.
And
why
would
you
do
it
excellent
yeah.
B
C
A
B
A
A
C
Yeah,
when
people
just
need
to
make
sure
they
understand
too,
that
it's
not
when
people
are
doing
this,
that
doesn't
mean
we're
always
complaining
I
mean
it
is.
It
is
like
I'm
glad
that
an
opportunity
to
actually
talk
about
you
know
what's
good,
there's
a
lot
of
stuff.
That's
good
and
I
do
like
it
just
because
you
hear
people
saying
well,
I
want
this
and
I
want
this.
It's
like!
No,
no
you,
you
guys,
you
guys
are
doing
a
good
job.
The
SharePoint
framework
is
a
very
good
platform.
C
We
yeah
it's
just
stuff
like
where
do
you?
Where
do
you
want
to
do
next?
What
do
you
want
to
build
next
and
that's
the
kind
of
the
attitude
that
it
buddy
has
is
looking
forward.
How
can
we
make
things
better
than
they
already
are
today,
and
that's
just
the
spirit
of
where
this
kind
of
feedback
comes
from
absolutely.
A
A
Cool
thanks,
everybody,
who's
listening
and
watching
whatever
is
their
chosen
way
of
actually
consuming
the
the
show,
and
please
keep
the
feedback
coming.
Please
use
the
hashtag
P
and
be
weekly,
and
if
you
want
your
articles
to
be
mentioned
and
uncovered
in
the
show
and
will
keep
on
believing
and
next
one
within
a
week,
so
we'll
we'll
see
who's
the
visitor
in
there.
Thank
you
we'll
be
cheering.