►
Description
Recording of SPFx and JavaScript development in SharePoint Community Call from 12th of April. 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
Hello
and
welcome
to
the
SharePoint
framework
in
JavaScript
special
interest
group,
bi-weekly,
sync
or
bi-weekly
meeting
it
is
April
12th,
2018
I
just
wanted
to
apologize
for
missing
the
last
one
of
these
calls
I
had
taken
a
red-eye
flight,
but
I
want
to
thank
visa
and
the
rest
of
the
team
for
covering
for
me,
so
very
much
appreciated
on
my
end,
they're
jumping
in
talk
about
always
start
with.
What's
the
purpose
of
these
calls?
Why
do
we
do
these
calls?
A
So
this
is
part
of
the
larger
SharePoint
patterns
and
practices
program
and
the
reason
we
started.
These
special
interest
group
calls.
This
was
the
first
and
we
now
have
one
as
well
for
the
powershell
and
sison.
Libraries
was
that
we
just
had
grown
too
much
to
be
able
to
cover
what
we
wanted
to
cover
in
our
single
monthly
calls
and
that's
kind
of
almost
happening
again
now.
A
I
have
to
have
special
interest
groups,
special
interest
groups,
but
so
the
purpose
of
this
call
is
to
really
talk
about
all
things:
client-side
developments
related
to
SharePoint,
so
that's
very
much
the
SharePoint
framework,
but
as
well
other
client-side
development
patterns,
whether
they
be
script,
editor
some
of
the
other
techniques
folks
can
use
and
leverage
and
then
as
well.
We
talked
about
the
PJs
libraries
that
we've
worked
together
to
create
as
a
community
and
build
those
things
up.
A
It's
really
exciting,
to
see
and
learn
from
what
everybody
else
is
doing
so
great
stuff,
and
we've
got
three
great
demos
on
the
call
for
you
today
which
we'll
talk
about
in
just
a
second
before
we
get
there.
Two
quick
links:
the
s
P,
P
and
P
community
takes
you
to
the
Microsoft
tech,
community,
SharePoint
area
channel
or,
however,
we're
labeling
that
that's
a
great
place
for
general
questions.
A
If
you
have
some
topics
around
SharePoint
development,
whether
it's
SharePoint
framework
or
any
of
the
other
SharePoint
development
models
that
aren't
necessarily
specific
issues
against
a
certain
library
or
against
SharePoint
framework,
that's
a
great
general
discussion
forum.
So
your
design
questions.
How
would
I
you
know
design
this
certain
web
part
or
this
application?
A
That's
a
great
place
to
get
those
questions
answered
and
the
second
link
SP
dev
Docs
takes
you
to
the
develop
the
documentation
or
all
SharePoint
development,
so
not
just
SharePoint
framework,
but
all
of
the
SharePoint
development
documentation
is
going
there
and
so
definitely
that's
a
great
link
to
check
out,
especially
if
you're,
just
starting
in
SharePoint
framework
and
want
to
see.
You
know
how
to
get
started.
A
Wonderful,
tutorials
that
really
take
you
from
zero
to
sixty
very
quickly
and
you
know,
get
you
develop
an
environment
built
up,
create
your
first
web
part
create
your
first
extension,
really
easy
to
get
into
and
see.
What's
going
on
there,
so
encourage
you
to
check
out
both
of
those
areas
and
for
today's
agenda
we'll
have
the
engineering
update
on
SharePoint
framework
from
basa.
Then
we've
got
updates
on
the
PJs
libraries,
the
CLI,
as
well
as
the
reusable
client
controls,
and
it
will
have
a
demo
from
elio
on
some
of
the
new
reusable
client
controls.
A
Today
on
the
call
and
then
our
two
main
community
demos
are
first
from
Bob,
the
classic
versus
modern
experience
in
relation
to
the
footer
and
then
as
well
from
David
Warner,
SP,
FX,
extensions
and
dynamic
properties.
So
that's
coming
back
to
how
to
sort
of
configure
things
a
little
more
dynamically
than
sort
of
having
your
static
properties
at
deployment,
time
locked
in
and
then
maybe
a
little
bit
of
time
for
Q&A.
At
the
end,
we
shall
see
before
we
get
to
all
of
that.
A
I
want
to
remind
folks
of
the
ways
to
participate
both
in
the
SharePoint
patterns
and
practices,
and
this
call
one
of
the
main
ways
we
love
to
see
folks
participate
is
demoing
on
the
calls,
so,
whether
it's
a
SharePoint
framework
solution,
whether
it's
p.m.
PJs
project,
what
there
it
is,
none
of
those
things-
maybe
some
you
know
really
cool
thing-
you've
done
in
a
script
editor
web
part
or-
or
you
know
some
of
the
other
techniques
really
like
to
see
those
demos.
A
If
you
would
like
to
do
a
demo
number
one,
we
very
much
wants
you
to
do
that,
just
reach
out
to
us.
Let
us
know
and
we'll
do
our
best
to
get
you
on
the
schedule
as
quickly
as
possible
like
so,
we
can't
always
get
you
on.
Maybe
the
very
next
call,
but
we'll
get
you
on
the
call.
After
that,
you
know
make
sure
you
get
to
do
your
demo,
so
very
much
I
encourage
all
of
you
to
reach
out
if
you've
done
something
cool
and
want
to
show
it
off.
A
This
is
a
great
forum
to
do
so
as
well.
You
can
always
contribute
on
github,
so
through
issues
through
contributing
pull
requests
or
just
and
that
last
block
they're
just
providing
general
feedback
on
all
of
the
things
we
do
so
feedback
on.
These
calls
feedback
on
the
library's
feedback
on
SharePoint
framework.
All
of
that
feedback
is
really
valuable
and
really
taken
to
heart
by
us,
and
we
encourage
you
to
give
us
that
feedback
on
everything
we're
doing
so
that
we
can
make
things
better
for
everybody.
A
So
we
can't
always
act
on
every
piece
of
feedback
immediately,
but
we
do
value
all
that
feedback,
and
you
know
the
core
team
that
the
past
practices,
core
team-
definitely
discusses
all
your
feedback
and
does
our
best
to
you,
know
sort
of
adapt
and
change
and
evolve
and
grow.
What
we're
doing,
based
on
what
we
hear
from
folks
so
hand
things
over.
At
this
point,
too,
they
saw
for
an
update
on
the
SharePoint
framework,
excellent.
B
So
let
me
actually
take
over
this
as
a
presenter,
so
a
few
slides
I
don't
have
actually
that
much
sand
new
or
excitement
because
we
did
have
a
community
call
actually
on
Tuesdays
the
monthly
community
call-
and
this
is
the
bi-weekly
special
interest
group
call
for
SharePoint
framework.
So
nothing
really
super
super
exciting
in
here,
but
I
wanted
to
pinpoint
again
a
few
slides
and
few
things
and
remind
some
resources
and
obviously
the
community
pages.
This
is
a
relatively
new
stuff
which
went
live
just
before
the
last
community
call
shipment
framework
community
call.
B
So
if
you're
looking
into
how
do
I
contribute,
what
are
the
community
calls?
How
what
are
the
open
source
resources
available
or
on
SharePoint
development
or
SharePoint
framework
samples
and
other
whatever
location
it
SP
PMP?
That
will
be
redirecting
you
to
the
new
community
pages
and
pretty
soon
the
old
paces
will
be
really
directed
here
as
well.
So
here
you
can
find
the
description
for
the
repositories
and
all
the
other
stuff
which
is
relevant
for
you
and
if
there's
typos,
if
there's
missing
information,
you
can
actually
contribute.
B
So
you
can
always
click
Edit
and
submit
a
podcast
for
these
pages
as
well.
Now.
The
second
thing
a
reminder
reminder
reminder:
please
please
please
well
not.
Please,
please,
please,
on
this
one,
but
if
you're
looking
into
SharePoint
dev,
documentation,
akms,
s/pdif
dogs
or
dogs
at
microsoft.com,
slash
a
point,
you
can
find
the
official
platform
for
all
the
relevant
SharePoint
documentation,
so
I'm
sure,
including
SharePoint
framework
and
other
SharePoint
development
areas.
B
The
issue
list
kind
of
a
mentioned
as
well
as
so
all
of
the
comments.
In
the
end
s,
PDF
Doc's
will
be
generated
into
our
SPF
dogs
issue
list,
but
this
is
also
an
issue
list
for
you
to
take
granted.
If
you
find
a
an
issue
in
the
back
in
the
api's,
let's
say
some
season,
maybe
I
doesn't
work.
Some
SPF
X
API
doesn't
work.
You
run
in
the
random
issue
within
the
SharePoint
development
and
you
potentially
have
called
to
SharePoint
Online
support
and
then
SharePoint
Online
support
is
saying.
B
Well,
we
don't
support
customization
because
we
don't
know
how
to
support
them.
This
is
the
location
where
you
can
actually
get
help,
which
we
ask
this
multiple
times
in
a
week,
and
then
we
prioritize
the
incoming
issues
based
on
the
criticalness
of
them,
and
then
we
assign
to
our
engineering
engineering
resources
on
them.
Obviously,
we
need
to
also
prioritize
new
feature
development,
but
some
of
the
same
guys
are
assisting
on
a
critical
things.
B
I
found
from
here
as
an
example,
just
a
small
update
on
certain
things,
the
eventing
challenge,
what
we
have
see
consulting
trim,
not
an
issue,
a
challenge.
Well,
it
is
an
issue,
so
the
eventing
eventing
issue
related
on
dates,
transitions
in
SharePoint
framework.
We
did
have
already
a
fix
for
it
internally.
B
A
few
more
assets
getting
started,
which
you
have
on
framework
tutorials,
so
just
there's
always
new
people,
obviously
arriving
on
SharePoint
framework
and
realizing
that
this
is
the
direction
where
we
are
hitting,
because
the
we
probably
should
not
really
prioritize
shape
and
adding
model
development
in
SharePoint,
Online
anymore.
Shape
and
framework
is
the
de-facto
model
and
we
are
gonna
actually
CRO
this
to
be
even
bigger
than
sharepoint.
B
So
we're
looking
into
using
the
similar
models
with
other
services
as
well,
which
is
pretty
cool
more
on
that
one
in
SBC,
small
teasers,
obviously
I'm
here,
but
a
kms
SP,
FX
tutorials
or
you
go
to
the
Doster
microsoft.com
def
platform,
and
you
can
find
the
tutorials
and
links
to
the
videos
which
are
also
showing
how
the
tutorial
works.
Yeah,
which
is
great.
Now
on
that
usage
I've,
been
promising
to
keep
updating
on
this
one.
This
again,
this
does
not
have
any
numbers
most
likely.
B
We
will
explain
some
numbers
in
SBC,
especially
being
the
sharepoint
conference
in
las
vegas
on
the
21st
of
them
May.
But
this
is
showing
you
the
crows
curve
on
adaption
and
used
its
actual
usage
of
SharePoint
framework.
In
SharePoint
Online
I'm
not
going
to
go
to
the
details
of
how
do
we
calculate
this,
and
how
do
we
actually
do
that?
B
Road
map
update
I
went
through
this
one
already
on
Tuesday
as
well,
and
this
week
is
this:
when
we
have
the
monthly
community
called
those
weeks
are
pretty
hectic,
because
then
we
have
two
calls
but
quick
updates
on
this
one.
Potentially
so
a
few
things
to
notice,
we
released
a
new
set
of
site
action,
slide,
design,
action
or
slide
script
actions
earlier
this
week
on
Tuesday
and
that
included,
for
example,
install
an
SPF
X
solution
to
the
side.
B
So
now
you're
able
to
automate
using
the
site,
design
and
slide
script
capability,
installation
of
the
SharePoint
framework
solution
to
the
newly
created
site.
So
whenever
an
end-user
creates
a
new
site
collection,
your
SPF
X
solution
can
be
installed
automatically
to
the
site.
You
don't
necessarily
need
to
have
any
PowerShell
or
admin
operations
or
automation
or
anything
running
in
usher,
and
that's
a
pretty
cool
thing.
There's
a
lot
of
additional,
also
site
design
actions
which
were
released
on
Tuesday.
B
Now,
that's
all
by
what
I
have
from
ship
and
framework
side?
Is
there
no
cool
demos?
For
this
time
we
do
have
called
Emma's
coming
up
from
David
and
Elio
and
Bob.
So,
let's
actually
move
on
in
in
the
topics
so
Patrick
the
mph
is
take
it
away
and
I'll
check
if
I
missed
any
questions
on
the
aisle
window.
Well,
while
Patrick
is
going
for
yep.
A
So
it's
about
dates
on
the
client-side
libraries
we
released
1:04
on
April
6,
those
last
Friday
still
working
on
CD
nsj
support,
like
I,
said
before.
That's
all
been
approved
online
and
it's
just
a
matter
of
their
folks
who
are
super
super
busy
getting
the
chance
to
emerge
that
stuff
into
the
repo.
So
still
working
on
that
we'll
update
folks
when
we
get
there
we're
doing,
we've
been
doing
weekly
beta
releases
on
Fridays,
so
that's
we're.
Gonna,
try
and
hold
to
that
rhythm.
I.
A
Think
it's
nice
to
have
a
schedule
for
those
and
gives
folks
a
chance
to
try
things
out,
maybe
when
they
come
in
back
to
work
on
Monday
or
you
know
Friday
afternoon,
depending
on
your
time
zones
and
then
do
keep
an
eye.
We
we
across
all
patterns
and
practices,
have
made
a
commitment
to
maintain
change
log
files
for
each
of
our
repositories
and
so
we're
doing
that
very
tightly
for
the
PM
pjs
libraries,
and
so
that's
really.
The
source
of
information
for
what's
updated.
A
What's
changed
with
each
release
and
I've
got
a
sample
of
that
over
on
the
side
there.
That's
that
image,
and
so
the
way
to
read
these
is
they'll,
be
a
version
number
with
the
release.
Date
is
kind
of
a
heading
and
then
you'll
have
different
sections
for
added,
fixed
or
changed,
and
so
this
is
just
a
sample
of
some
of
the
stuff
that
was
added
in
the
104
release.
So
some
really
good
stuff,
some
of
it
major
some
of
it
a
little
minor
or
more
minor.
But
that's
that's.
That's
the
way
to
keep
track
of.
A
What's
changing
so
we're
doing
a
way,
I
used
to
do
blog
posts
for
each
release
and
stuff,
like
that
and
I
think
this
is
a
little
clearer
and
it's
right
there
in
the
repository,
so
I
think
that'll
help
everybody
find
any
of
everything
and
as
well,
I'm
trying
to
make
sure
I
link
to
each
pull
request
for
each
change.
So
if
you
say
you
try
and
use
the
Adel
clients,
you
could
go.
Look
at
that
pull
request
to
see
what's
changed
or
maybe
might
help
you
debug
a
problem
and
report
an
issue.
A
If
you
see
some
problems
with
something
new
so
check
out,
the
changelog
I've
been
really
happy
with
how
that's
working
and
I
think
it's
a
nice
way
to
communicate.
What's
going
on
in
terms
of
roadmap,
we
work
on
issues
for
each
release
or
each
beta
for
the
issues
that
have
come
in
an
issues
list.
As
always,
if
you
find
anything,
please
just
report
it
to
us.
Please
do
include
enough
detail.
A
We
can,
you
know,
figure
out,
what's
going
on
and
as
well
kind
of
keep
an
eye
on
your
issue
in
case
we
have
some
follow-up
questions,
but
we'll
do
our
best
to
to
either
answer
your
question
or
fix
whatever
you
might
have
found
as
well
want
to
encourage
folks.
If
you
have
ideas
on
ways
to
enhance
or
grow
the
library,
please
let
us
know
don't
keep
those
to
yourself.
We
really
value
that
feedback,
as
I
said
earlier,
and
use
that
to
help
develop
our
roadmap
and
as
well
I'll
just
tease
a
little
bit.
A
We've
got
some
nice
surprises,
I.
Think
we're
working
on
that
I
think
will
come
out
for
the
community.
That
I
think
will
be
pretty
cool,
but
we're
gonna
keep
those
under
wraps
a
little
bit.
Just
because
I
like
to
surprise
people
and
then
so
links
there.
The
PNP
jeaious
that
first
link
will
take
you
to
the
documentation
for
the
PNP
jeaious
libraries.
You
can
follow
the
hashtag
Keene
PJs
on
Twitter
and
as
well.
You
can
follow
me
on
Twitter.
It's
been
a
while,
since
I
put
my
handle
up
here
so
I'm
at
mediocre
bowler.
A
So
you
can
find
me
on
Twitter
and
I'll
generally
announce
each
of
the
beta
releases
as
well
as
major
releases
and
that
sort
of
stuff
on
the
Twitter
so
check
that
out
and
then
I
did
want
to.
It
is
April,
so
I
wanted
to
kind
of
update
folks
on
the
March
numbers
and
what
we're
seeing
so
continue
to
see
phenomenal
growth,
for
which
I'll
always
say.
A
This
is
a
similar
growth
curve
to
what
we
saw
then,
so
we
started
off
obviously
with
nothing,
but
then
we
kind
of
went
to
7
million
and
then
I
think
it
was
14
million
or
16.
Something
like
that
so
excited
to
see
folks
starting
to
migrate
to
the
@pn
pjs
libraries
and
would
encourage
you,
as
you
have
a
chance,
do
start
to
migrate.
A
July
will
be
the
last
release
of
SPP
and
PJs,
so
that
library
will
will
not
go
away
rocket,
would
delete
anything
or
take
it
off
of
NPM
or
anything
crazy
like
that,
but
we're
gonna
stop
really
growing
it
and
adding
to
it
and
improving
it
and
be
focused
on
the
new
library.
So
we
have
a
transition
guide
out
there
check
that
out.
A
Excuse
me:
I've
got
my
spring
allergies,
so
you
get
my
allergy
voice
today
and
we've
got
a
whole
suite
of
new
commands
that
have
come
out
for
the
CLI
in
that
beta
or
since
we
last
talked
I'm,
not
gonna
read
all
of
them,
but
you
can
check
out.
They
have
a
change
log,
of
course,
as
well,
for
that
project
check
that
out
great
new
additions
in
there
and
a
lot
of
those
are
coming
from
folks
in
the
community.
A
So
if
you're
looking
for
ways
to
contribute
and
you're
interested
in
the
office,
365
CLI
Waldeck
has
put
there's
a
bunch
of
issues
already
there.
So
you
can
go,
grab
an
issue
and
add
a
command.
It's
not.
Each
command
isn't
terribly
difficult
and
they're
fairly
atomic.
So
you
can
work
on
a
command
and
get
that
added
and
it's
great
to
see
the
community
involve
and
continue
to
grow
for
the
office365
CLI.
You
can
install
it
directly
from
NPM
and
you
can
watch
or
check
out
their
tutorials
on
that.
A
Excuse
me
and
then
down
there
in
the
corner.
A
wall
Beck
is
following
office:
365
CLI
on
Twitter,
there's
a
git
er
channel
as
well,
and
then
you
can
check
out
the
office
365
CLI
docks
at
AKA
ems,
365
CLI,
so
those
Doc's
will
get.
You
started
again
from
having
never
used
it
before
to
being
effective
and
using
it
as
a
great
tool
to
help
manage
your
tenant
and
just
a
reminder.
Please
do
try
to
stay
on
mutes
impossible.
A
So
we've
got
a
quick
update
as
well
on
the
reusable
components.
So
we
just
had
a
release
of
1
to
5
for
the
react
controls
with
fixes
for
the
list.
Listview
item
selection
after
the
array
updates
undoing
that
selection,
that
was
issue
number
55,
has
been
fixed
and
then
as
well.
The
property
controls,
one
500,
have
had
several
great
enhancements
around
the
property
field
list,
picker
the
turn
picker
and
as
well.
A
C
Okay,
so
we
had
some
great
contributions:
well
speak
to
the
field
list
speaker
and
to
the
term
picker.
So
what
has
been
added
last
week,
Christiane's
has
added
the
new
and
availability
of
the
select,
all
and
deselect
all
capability
of
the
list
speaker.
So
now
you
can
select
all
lists
at
once
and
also
for
the
term
picker.
It's
now
aligned
to
share
points
out
of
the
box
is
offering
in
lists
and
libraries.
C
So
before
with
the
term
picker,
you
have
to
click
on
the
tag
and
then
you
could
select
in
the
tweet
view
the
term
you
were
interested
in
and
save
it
and
will
be
select
for
you
button
now.
As
of
the
latest
release
for
1.5.0,
you
can
also
type,
and
it
will
also
find
the
terms
and
from
the
moment
you
press
enter,
it
will
select
the
terms
and
only
if
everything
should
go
all
right.
C
A
Great,
thank
you
Elia
awesome
to
see
that
and
great
stuff,
as
always
from
the
community.
So
great
work
really
appreciate
those
contributions.
One
of
these
days,
I'll
get
better
at
clicking
through
Skype
to
share
things
so
I
believe
the
next
presenter
up
is
going
to
be
Bob
German,
so
Bob
is
ready
as
we
got
whoops.
Excuse
me
for
a
sec,
we're
not
at
a
Q&A.
So
if
Bob's
ready,
we've
got
classic
versus
modern
experiences
with
the
footer.
Yes,.
D
A
D
It
great
so
what
you
should
see
is
on
the
left,
a
classic
publishing
site
and
on
the
right,
a
modern
site,
so
I
work
with
in
my
job
I'm
back
at
Microsoft,
now
really
throw
up
about
that.
My
job
is
in
one
commercial
partner,
so
I
work
with
manage
partners
in
the
US
to
help
make
them
successful.
This
one
partner
is
doing
a
huge
migration
of
a
big
multinational
company
and
they
want
to
go
a
modern
as
much
as
they
can,
but
they
still
need
classic
publishing
pages
for
some
scenarios.
D
So
the
challenge
that
they
threw
to
me
was:
how
can
we
build
and
they
had
already
built
a
SharePoint
framework
extension
from
menus
and
footers
I
actually
made
much
simpler
ones
here,
so
you
can
see
here's
my
little
menu
up
top
and
it's
all
works.
Fine.
If
your
needs
are
simple,
you
can
just
take
this
as
it
is.
If
your
needs
are
complex,
you
can
use
it
as
a
starter
and
then
down
here
on
the
footer
are
some
links
and
a
compliance
message,
and
now
here's
the
same
thing
in
classic.
So
this
was
their
goal.
D
Was
a
hundred
percent
common
code?
They
wanted
to
reuse
the
work
they
had
done
in
the
SharePoint
framework
over
on
the
classic
side,
and
that's
really
the
that
was
really
the
goal
of
the
sample
which
is
now
up
on
the
PNP
extension
samples.
So
here
I
have
a
little
tool
that
I
like
to
use
called
beyond
compare.
It
compares
whole
hierarchies
of
files,
and
you
can
see
here
on
the
left
again,
it's
the
classic
code
and
on
the
right
is
the
modern
code.
D
I
actually
could
have
arranged
this
so
that
the
common
folder
was
outside
of
the
two
folders
and
you
know
kind
of
they
both
referenced
the
same
physical
files
but
for
whatever
reason,
I
decided
to
make
copy
of
it.
But
you
can
see
here
and
beyond,
compare
that
the
vast
majority
of
the
solution
is
common.
All
of
my
react
components,
my
localization
strings,
my
data
model
and
my
a
service
that
reaches
out
and
gets
the
data
are
all
hundred-percent
common
code.
D
So
that's,
why
you're
seeing
some
some
red
lines,
but
basically
it's
just
an
application
customizer
and
what
it's
doing
is
it's
reading
in
a
JSON
file
from
from
my
tenant
that
has
all
the
headers
the
menus
and
the
footers
and
all
that
stuff
and
then,
when
it
gets
that
it's
calling
out
to
something
it's
grabbing
the
placeholder
content.
And
then
it's
calling
this
thing
called
the
component
manager
on
line
55
which
actually
renders
the
the
react
side.
D
So
I
moved
all
the
react
out
of
this
file
where
the
yeoman
template
would
have
normally
put
it
and
put
it
all
in
common,
and
if
we
go
up
to
the
classic
version.
This
is
slightly
more
interesting
over
there
I
have
a
class
called
boot
header/footer,
which
does
something
kind
of
similar,
but
what
it
does,
but
it
does
it
without
the
assistance
of
the
SharePoint
framework,
because
obviously
we're
in
a
classic
site.
There
is
no
SharePoint
framework.
D
So
what
it's
going
to
do
is
make
the
elements
for
the
header
and
footer,
and
then
it's
going
to
go
ahead
and
inject
those
onto
the
page
around
a
well-known
HTML
element,
and
then
it
does
the
same
thing
of
calling
the
calling
the
same
service
using
the
same
component
manager
to
attach
to
those
El
HTML
elements-
and
you
know
the
rest
of
it-
is
the
same,
and
then
there
needs
to
be
something
to
actually
bootstrap
it.
So
down
here
on
line
43,
you
can
see
just
a
tiny
bit
of
code.
D
Let
me
go
back
if
I'm
here
on
my
classic
site,
I
can
easily
find
myself
in
modern
mode
by
just
going
since
I'm
on
SharePoint
framework.
Hey
look
I'm
in
a
modern
page
right.
All
I
had
to
do
is
go
into
a
list
somewhere
and
all
of
a
sudden
I'm
in
modern
right.
So
having
this
common
header
and
footer
actually
is
useful
for
that
too,
because
it
gets
rid
of
some
of
the
jarring
experience
of
having
things
change
when
you
switch
between
classic
and
and
modern,
even
within
the
same
site.
D
So
but
the
other
thing
I
guess
I
would
show
here
and
I.
Don't
you
can
tell
me
how
much
time
to
take
Patrick
and
company
I
could
go
into
more
detail,
but
the
language,
the
multilingual
handling,
was
kind
of
interesting
on
this.
So
this
being
a
a
multinational
customer
at
the
end
of
the
day,
one
of
the
things
that
they
wanted
was
some
kind
of
localization
and
so
I
moved
the
loke
file.
This
localization
folder
into
common
and
I,
have
my
little
my
strings.
So
it's
just
the
footer
message
here
again.
D
This
is
just
a
proof
of
concept
to
show
how
to
do
things
so
I
didn't
need
to
show
12
different
strings.
I
just
have
one
is
enough
to
show
the
principle
and
then
here
it
is
in
English,
and
here
it
is
in
probably
bad
French,
because
I
don't
speak,
French
very
well,
and
you
know,
and
and
it
works
the
same
as
normal
in
SharePoint
framework
but
I
wrapped.
D
The
SharePoint
frameworks
behavior
in
this
little
thing
called
the
language
manager
which
just
imports
the
strings
from
the
localized
strings
from
SharePoint
framework
and
then
spits
them
back
out
using
getstring.
So,
wherever
I
need
strings
in
my
code,
instead
of
calling
in
the
common
code
instead
of
calling
SharePoint
framework,
I
call
this
little
language
manager.
D
Our
old
friend,
FP
page
context
info,
which,
as
far
as
I
know,
is
the
best
way
to
get
to
get
an
idea
of
what
SharePoint
thinks
the
language
is
so
that
this
will
always
stay
in
sync
with
the
rest
of
the
page
as
users
change
their
profile
or
have
different
language
preferences
in
their
browsers.
And
then
it's
simply
going
to
come
in
here
and
look
at
the
UI
culture
and
require
in
those
the
the
appropriate
localization
file
and
return
that.
So
that's
how
how
the
localization
is
working.
So
everything
else
here
is
common
right.
D
There's
this
little
component
manager
that
actually
handles
the
react,
binding
and
so
again,
apologies
for
not
doing
the
npm
install
in
this
copy
of
the
repo.
So
you're
getting
the
little
earth
looking
appearing
to
be
there
that
aren't
really
there
in
visual
studio
code.
But
what
it's
going
to
do
here
is
it's
going
to
take
dom
elements
which
are
sort
of
common
to
both
classic
and
modern,
and
then
it's
going
to
go
ahead
and
and
render
those
with
react
dom
and
you
know
from
there.
Everything
is
just
kind
of
the
same
underneath
of
that.
D
Maybe
one
of
the
cool
things
I
actually
stole
from
somewhere
Tony
Thomas
had
this
great
had
this
CSS
only
navigation
menu,
which
I
gave
him
some
credit
for
here.
The
other
kind
of
reference
around
this
is
Julie.
Turner
did
a
great
series
of
blog
articles
on
how
to
conquer
your
development
tools
or
something
like
that
and
I've
got
a
pointer
to
all
this
in
my
blog
and
it's
also
in
the
documentation
here
in
the
repo.
D
So
what
she
did
was
she
just
kind
of
gave
step-by-step
instructions
on
how
to
set
up
how
to
set
up
web
pack
and
typescript
and
all
those
familiar
tools
that
we
know
and
love
in
SharePoint
framework
to
use
outside
of
the
SharePoint
framework.
So
here's
the
article-
it's
again
it's
on
my
blog
and
it's
also
here
in
the
repo
that
explains
exactly
how
all
this
works
in
more
detail.
D
Then
I'm
going
to
take
time
for
today-
and
this
also
has
a
pointer
to
Julie's
article,
and
so
it
was
kind
of
nice
to
just
basically
use
the
same,
the
same
exact
tools
and
an
approach.
Here's
the
here's,
a
pointer
to
this
article
for
both
classic
and
modern.
So
if
there
any
questions
about
to
just
share
but
I
think
that's
about
what
I
had
to
show
now.
B
B
D
Great
well
thanks
for
saying
that
I
points
out
something
I
meant
to
mention,
which
is
this
exact
scenario.
If
you
look
at
the
you
know,
a
lot
of
us
are
it
in
a
mixed
world
of
classic
and
modern.
A
lot
of
our
customers
are
webparts.
Sharepoint
framework
handles
quite
beautifully
in
that.
If
you
have,
you
know,
feature
pack
of
sharepoint
2016,
you
can
right
on
premises.
D
You
can
run
them
in
classic
mode
on
on
SharePoint
Online,
the
webparts
are
great,
but
what
about
the
headers
and
the
footers
you
I,
don't
know
if
the
actions
and
the
field
field
renderers
field
customizers
make
as
much
sense
to
try
to
comment,
but
this
is
something
that
I
think
a
lot
of
people
are
probably
going
to
need
is
a
common
footer
and
header
for
their
site.
Absolutely.
B
Because
there's
some
visible
elements-
and
it's
such
a
classic
thing
to
embed
and
header
or
footer
to
the
page,
using
the
JavaScript
and
embedding
technique
which
technically
is
SharePoint
framework
shape
and
framework,
is
actually
embedding
JavaScript
on
the
page
as
well,
but
using
the
old
classic
user
custom
action
model.
How
did
you
associate
the
classic
classic
JavaScript
output
file,
so
it
obviously
have
an
output
file.
You
have
a
bundled
I
hope.
The
masked
man
fights
bundle.
D
So
I
have
to
confess
that
it's
hard-coded,
so
the
so
julie
has
the
code
in
her
article
on
how
to
use
gulp
to
push
the
bundle
out
to
classic
to
a
SharePoint
library
and
that's
what
I'm
doing
right
now.
I
may
at
some
point,
move
it
to
CDN,
but
then
I
forgot
to
show
this.
So
thanks
for
the
prompt,
the
installation
is
here.
D
So
this
is
our
old
front,
PNP
powershell,
and
so
what
it's
going
to
do
is
it's
actually
going
to
inject
PNP
JavaScript
links
for
the
four
react,
react
dom
and
for
the
header,
footer
and
you'll
see
wherever
I
have
the
little
tenant.
That
means
I
cheated
and
hard-coded.
My
URL
and
the
instructions
actually
have
you
go
through
and
and
there's
like
three
places
you
have
to
go
in
and
and
fix
the
code.
So
it
would
be
nice
to
get
a
little
bit
fancier
about
this,
but
right
now
it's
hard-coded
in
the
Installer
game.
B
And
this
is
absolutely
fine,
so
so
because,
technically
and
David
is
actually
commenting,
this
one
custom
actions
for
classic
them
still
very
simple.
So,
and
the
answer
is
yes
absolutely
because
that's
precisely
how
SharePoint
framework
extends
actually
work
as
well,
you
actually
add
a
user
custom
action,
and
then
you
associate
that
with
the
client
component
ID
the
the
the
manifest
which
is
an
app
catalog.
So
technically,
what
Pope
is
doing
here
is
just
manually
associating
the
JavaScript
link
to
the
user
custom
actions.
B
E
B
D
Great
cool
yeah,
the
one
thing
that
is
common,
the
bundles
are
obviously
different
because
there's
different
code
in
them
as
well,
but
the
the
actual
links
that
go
out
to
thee.
So
there's
this
little
JSON
file,
here's
a
sample
that
has
all
the
links
for
the
menus
and
builds
all
that
out.
That
is
actually
common
between
the
two
and
I
chose
to
put
that
in
a
SharePoint
document
library
in
its
own
little
site
collection
that
could
be
permissioned
appropriately.
D
B
Absolutely
makes
sense
cool
stuff,
and
this
is
something
which
we
definitely
need
to
think.
How
could
we
automate
this
potentially
in
the
future
more
efficiently
for
customers
making,
because
there
is
maturity
of
customers,
are
still
falling
on
this?
Let's
say
both
modes
experience,
because
it's
really
hard
to
make
sure
that
your
end-users
will
not
fall
on
classic
in
any
scenario.
So
it's
pretty
orbital-
and
this
is
great
great
great
solution
for
avoiding
confusion.
But
thanks
looking
into
the
timing,
Patrick
I
think
it's.
A
Great
stuff
for
Bob
awesome
to
see
that
and
I
know
that's
a
challenge
for
a
lot
of
folks
straddling
that
world
as
we
as
we
all
sit
between
classic
and
modern
and
and
migrating
folks.
So
it's
a
nice
resource
there
to
kind
of
see
some
techniques
to
help
with
that
and
then
David.
If
you're
ready,
you
can
just
go
ahead
and
take
over
the
presentation.
Yep.
A
E
Great,
so
my
name
is
David
Warner
I
work
for
catapult
systems,
there's
my
contact,
information,
work,
email,
personal
email
and
Twitter
handles
so
feel
free
to
reach
out.
You
have
questions
a
couple
weeks
ago,
and
this
is
a
great
add-on
to
Bob's
demo
is.
Is
that
waldek?
And
that's
that
we're
talking
about
deploying
extensions
and
wall
that
could
kind
of
quiz
the
group
around
why
you
would
not
deploy
your
feature
framework
custom
action
at
the
time
and
within
your
package
right?
So
why
would
you
not
include
that?
E
And
it
was
because
there
is
an
opportunity
where
you
can
provide
properties
to
set
the
extension
to
do
something
different
in
each
time.
You
set
up
the
custom
action.
So
that's
what
I
do
as
a
demo
today,
it's
gonna
be
a
simple,
a
very
simple
implementation,
but
a
very
powerful
concept.
So
hopefully
everybody
can
kind
of
see
where
we
can
go
from
the
demo
with
with
overwriting
the
extension
in
terms
of
properties.
So
the
first
thing
I'll
do
is
show
you
I'd
already
created
a
couple
of
extensions.
E
E
So
we
see
the
location,
it's
it's
identifying
the
client
component
ID
in
the
properties
and
it
gets
created
for
us,
but
we
may
not
want
that
because
we
made
able
to
set
up
our
extension
to
do
something
a
little
more
unique
than
just
be
a
base
extension.
So
in
this
case
we'll
come
back
to
our
our
slides
here.
We'll
pretend
we're
Cameron.
E
We
got
a
request
to
create
a
header
with
two
columns
fantastic,
so
we
go
ahead
and
do
that
we
see
right
here,
I've,
just
hard-coded,
again,
simple
implementation,
I've
done
nothing
more
than
hard
code,
a
responsive,
I
guess
you
could
say
three
column,
I've
got
my
logo
and
then
I've
got
two
columns
for
contents.
We
see
their
header
section.
Oh
one,
header
section,
oh
two,
but
when
this
gets
deployed
because
there
is
a
lack
of
feature
framework
that
actually
deploys
the
the
custom
action,
nothing
happens.
E
So
what
we're
looking
at
here
is
the
actual
extension
has
been
installed.
It
is
loaded
on
the
site,
but
if
I
refresh
nothing
shows
up
right
and
that's
simply
because
the
custom
action
doesn't
exist
now
we
may
deploy
that
custom
action
manually.
We
may
deploy
it
through
I,
don't
know,
maybe
site
design,
site
scripts
right
plug
plug
because
those
could
provision
through
PowerShell.
So
that's
what
we're
gonna
use
today
to
create
these
custom
actions.
E
E
You'll
notice,
though,
that
no
properties
are
there,
so
it's
simply
just
going
to
deploy
it,
as
is
so
I'm
gonna
go
ahead
and
run
that
we
see
it
successfully
ran
if
I
do
a
get,
PNP
custom
action
again,
we
can
see
it's
now
there.
So
if
I
go
over
and
refresh
the
screen,
we're
gonna
find
is,
will
now
see
my
custom.
Action
has
been
loaded
and
is
actually
activated.
E
So
we
see
that
I've
got
my
little
pop
Warner
logo,
little
nickname
that
I've
earned
being
a
football
fan
in
my
last
name
being
Warner
and
we've
got
two
headers.
There
are
two
two
header
sections,
our
header,
oh
one
and
header
Oh
and
that's
great.
But
what
can
we
do
with
the
actual
properties?
Well,
what
I'm
going
to
do
is
we're
going
to
we're
going
to
include
content
by
targeting
it
right,
so
I've
pre
created
some
weather
say
a
client
comes
in
and
they
say
what
we
want.
E
We
want
some
weather
put
into
our
our
header
and
so
we're
gonna
go
ahead
and
I'm
gonna,
remove
it
just
using
PowerShell
again
and
then
I'm
going
to
redeploy
my
custom
action.
What
you'll
notice,
though,
is
that
I'm
now,
including
a
client-side
property-
and
it
says,
target
header
section,
oh
one,
so
what
we're
telling
it
to
do
and
I'll
show
you
the
code
in
a
moment
is
we're
going
to
inject
some
hard-coded
weather.
Of
course,
the
implementation
of
that
can
be
much
more
elegant
and
complex
for
a
real
environment.
E
Application
purpose
here
is
to
illustrate
the
use
of
properties
and
so
I'm
going
to
go
ahead
and
deploy
deploy
that
custom
action
see.
It
ran
very,
very
fast
and
successfully
so
now,
when
I
refresh
we're
gonna
see
that
it
is
sunny
and
Vess
Adelphia
all
right,
it's
always
sunny
in
vests
Adelphia.
Now
what
does
that?
Look
like
in
the
actual
code
we'll
come
down
here?
Here's
our
weather
forecast,
very
simple
I
just
got
a
simple
hard-coded
forecast,
div
right
and
we
just
populate
it.
E
What
I
do
is
I
look
at
the
target
string
property
which
is
target
and
then
I
use
that,
as
my
get
class
by
cloud
get
element
by
class
name,
I
set
the
inner
HTML
and
I
populate
the
weather
HTML
into
that.
So
what
that
means
is
now
I
can
make
this
dynamic.
If
we
have
a
client
or
a
business
user,
come
in
and
say
well,
that's
great,
but
I
actually
want
it
in
the
second
one.
E
E
Yes
and
we'll
redeploy
it
identifying
that
our
target
is
now
section
o
its
ran.
I
refresh,
and
now
we
see
it's
over
here.
Much
more
sunny
forecast
is
always
sunny
in
philadelphia
right.
So
a
simple
implementation.
Now,
let's
take
that
a
step
further.
How
can
we
actually,
instead
of
just
targeting
the
location
of
where
our
content
is
going
to
go?
Is
it
possible
to
make
the
structure
of
our
header
a
little
more
dynamic
right?
So,
let's
go
back
to
our.
Let's
go
back
to
our
developer
Cameron!
He
gets
another
request.
E
I
saw
what
you
did
for
clients,
though,
and
so
I'd
love
it,
but
I
want
three
columns.
Okay,
well,
his
smiles
got
a
little
bit
less
kick
to
it
right.
He
does
that,
so
he
creates
another
extension
and
then
he
gets
a
request
from
another
client
or
business
user.
I
want
four
columns,
and
that
was
a
little
more
sad
because
he's
juggling
multiple
extensions
and
then
all
of
a
sudden
he
gets
five
columns
and
he's
freaking
out
right.
So
is
there
a
way
to
solve
that
simple
request
by
creating
and
using
properties?
E
E
And
we're
just
gonna
go
ahead
and
do
the
exact
same
thing
we're
going
to
check
to
make
sure
we
have
no
custom
actions
and
we
don't,
as
we
can
see
down
there,
nothing
was
output
and
we're
gonna
go
ahead
and
deploy
it
at
first
with
with
no
properties.
We're
just
gonna
show
what
it
looks
like
as
it
is.
So
if
I
come
here,
refresh
we're
gonna,
see
the
same
general
look
and
feel
we're
gonna
see
our
logo
there
and
we're
gonna
see
just
one
column
showing
up.
We
see,
we've
got
our
sections
wrapper
right
down.
E
There,
we've
got
our
sections
wrapper
header
sections
wrapper
and,
of
course
we
see
the
the
number
generated
by
the
SharePoint
framework.
That
makes
it
unique
for
the
CSS
and
the
sass,
and
so
now
we're
going
to
look
at
how
we
can.
How
can
we
modify
that?
Well,
we
have
a
column,
count
property
and
what
happens
if
I
go
over
to
the
code?
E
It
can
be
used
with
any
framework
or
library
that
you
want
to
use
to
make
the
building
of
it
easier,
but
for
purposes
of
a
simple
demo
we
just
come
in
and
we
look,
we
get
our
column
count
to
see
how
many
columns
we
want
and
then
we
just
do
a
simple
loop
and
we
build
the
sections
for
our
header
based
on
the
column
count.
So
we
start
at
one
because
we
want
our
actual
ID
to
start
at
one.
We
add
one
to
our
column
count.
So
we
know
the
count
is
always
accurate.
E
We
just
loop
through
it
and
then
we
output
it
to
the
dynamic
HTML
into
the
inner
HTML.
So
what
that
looks
like
once,
we've
implemented
it
we'll
go
ahead
and
remove
the
existing
one
will
redeploy
by
including
the
column
count.
You
can
see
there
client
side
component
properties,
column,
count
3.
So
if
I
go
ahead
and
execute
that
successful,
come
back
to
the
browser
will
refresh
and
we
see,
we've
got
3
columns,
all
responsive
they're
set
up
float:left,
33%
and
they're
each
showing
up
there
for
us
to
be
able
to
to
utilize.
E
And
let's
go
ahead
and
pass
the
column
count
property
of
five,
so
we're
just
not
changing
the
extension
in
any
way,
shape
or
form
we're
just
simply
creating
new
custom
actions
that
point
to
that
extension,
passing
properties
back
refresh,
and
now
we
see
five
and
they're
still
aware
right.
So
we've
set
up
CSS.
That
now
says:
oh,
hey!
Look
it's
20%,
because
we've
set
up
our
CSS
to
know
that,
there's
a
header
count.
Five!
You
can
support
up
to
as
many
as
you
want
with
the
CSS.
Just
have
the
CSS
there
to
support
it.
E
What
was
that
a
class
here
that
has
the
header
section
wrapper
count
5
right
there
on
the
bottom,
so
it
lets
us
know
how
many
we
have
and
then
we
can
apply
the
CSS
to
appropriately
set
the
width
of
these,
so
they
still
are
truly
responsive.
Now
what
if
we
wanted
to
go
ahead
and
couple
our
first
example
and
our
second
example?
So,
of
course,
what
is
something
that
we
would
likely
see
in
our
header?
That
would
give
a
user
comfort
when
they're
experiencing
a
new
website.
E
That
said,
dear
VESA
sharing
is
caring.
That's
that
sharing
is
caring,
calm
right,
it's
one
that
everybody
needs.
We
need
all
need,
links
to
dear
the
email
support,
and
so
how
that
looks
again
in
the
dynamic
header
is
we
have
our
support,
content
and
we're
just
simply
in
this
case
we're
getting
the
support.
Contents
and/or
we're
getting
the
element
class
in
this
case,
I
was
hard
coding,
the
section
o1,
and
then
we
just
in
it's
at
the
Internet
Gmail,
for
support
and
and
injected
there.
E
So
you
can
see
you've
got
a
single
extension
to
get
a
very
simple
implementation
of
what
we're
doing
here,
but
a
powerful
concept,
and
that
we
can
set
up
our
extensions
and
during
deployment
or
provisioning
of
the
site,
whether
it
be
a
site,
design,
site
script.
We
can
set
our
extensions,
headers
or
footers
to
do
something
unique
based
on
the
properties,
a
sign
from
the
headers
and
footers.
What's
the
so
what
I
have
for
the
demo?
That's.
B
Really
really
really
quite
accepted
the
TRS.
Are
you
must
phone
now
on
the
few
things
to
notice
that
this
is
exactly
what
we
explained
like
two
weeks
or
four
weeks
ago,
I
can't
remember
when
we
talked
about
the
things
I'm
great
to
have
a
detailed
demo
walkthrough
and
the
options
on
that
one
as
well.
B
E
E
I
think
that
that's
fantastic,
the
one
thing
that
I
actually
was
getting
ready
to
put
a
user
voice
request
in
for
is
maybe
a
configurable
property
where
the
composite
header,
where
we
have
the
little
square
logo
and
navigation
yep
in
site,
name
being
able
to
hide
that,
because
our
headers
are
usually
going
to
include
some
degree
of
logo
right,
maybe
a
collection
of
content,
whether
if
yeah,
whether
stock
alert,
something
like
that
and
then
likely
another
custom
navigation
that
may
be
responsive
and
mega
menu
whatever.
But
then
it
starts
looking
redundant
right.
E
So
I
would
say
that
to
me
that
that
to
make
the
exchange
is
really
powerful
and
be
able
to
really
control
the
look
and
feel
I
know
we're
not
supposed
to
override
right.
We
can
include
CSS
that
can
hide
that
composite
header
yeah,
but
that's
getting
outside
the
boundaries
of
playing
the
game
by
the
rules.
Yes,
yes,.
C
B
B
Do
we
actually
want
to
provide,
or
do
we
just
have
a
certain
set
of
flexibility
and
because
then
it's
more
safe
and
it
will
reduce
the
support
costs
and
all
of
that,
so
it
is
interesting
discussion,
even
in
generally,
how
much
of
this
stuff
should
we
enable
and
how
much
we
shouldn't.
Obviously,
if
there's
a
user
voice
entry
entered
and
that
we're
getting
a
lot
of
votes,
absolutely
people
will
start
prioritizing
those
changes
in
the
future.
That's
why
we
always
ask
user
voice
entries
yeah.
B
Excellent,
which
reminded
me
on
earlier
today,
I
just
went
through
the
whole
user
for
centuries
for
SharePoint.
If
and
that
should
be
now
pretty
clean,
so
there's
no
kind
of
a
crap
on
that
side
and
all
of
the
unnecessary
things
should
be
clean
so
or
deleted
or
closed
or
whatever,
but
getting
more
items
they're
killing
your
input,
they're
super
valuable
for
new
feature
and
requirements.
Now,
if
you
again,
if
you
find
out
that
there's
an
issue
in
API,
SPF
X
doesn't
work,
you
run
into
random.
B
Unexpected
situation
then
do
issue
list
and
SP
dev
Docs
is
an
option.
If
your
issue
actually
is
a
new
feature
request,
we
will
then
tell
you
that
it
is
a
new
feature
request.
Then
you
can
go
to
user
voice,
but
in
this
case
having
a
support,
for
example,
for
removing
the
whole
header
section
in
the
pages.
That's
clearly
a
new
feature:
that's
not
a
bug!
That's
not
an
issue
as
such
that
it's
a
new
feature.
B
The
we
are
also
looking
into,
for
example,
having
additional
placeholders
now
what
they
will
be
that
will
be
announced
in
SPC,
so
the
SPC
SharePoint
conference
in
Las
Vegas
is
our
spring
moment.
So,
in
the
past
for
past
two
years,
we've
been
having
this
virtual
May
event
for
SharePoint,
where
we
always
announce
the
latest
and
greatest
and
stuff
which
we
are
working
on.
That
doesn't
happen
this
year
because
we
have
SharePoint
conference
in
Las
Vegas.
B
So
the
last
Vegas
is
really
the
moment
where
we
go
through
and
explain:
hey,
here's,
the
new
placeholders,
hey,
here's,
the
new
goodies
for
SharePoint
framework
development,
hey
here's
this
stuff!
Will
we
ship
it
on
SBC?
That's
a
different
discussion.
Some
stuff
will
be
enabled
immediately.
Nice
pieces
and
stuff
will
be
shipped
by
ignite
because
ignite
is
our
autumn
timeframe
even
fit
on
the
placeholders
as
an
example
classic
thing.
But
what
people
are
asking
and
it
is
kind
of
a
frustrating
that
it's
not
yet
there
is
the
footer
and
the
footer
is
floating.
B
So
if
you
scroll
down,
for
example,
if
you
have
a
long
page
the
food
there
is
all
the
time
visible
on
a
page,
so
the
food
er
is
not
inside
of
the
page.
It's
not
in
the
content.
That's
something
what
we're
looking
into
having
and
again
I
can't
promise
you
that
it
will
be
there
at
this
point,
because
I
can't
announce
these
things,
obviously
in
the
community
course,
but
that
is
one
of
the
things.
B
What
we're
looking
into
making
happen,
potentially
by
SPC
and
there's
a
lot
of
other
stuff
I,
think
people
will
be
I,
think
we
got
surprised
even
people
in
SBC,
so
there's
cool
stuff
on
the
pipeline.
I.
Think
a
lot
of
the
NDP
is
for
super
excited
on
the
india-based
summit,
because
they
got
some
level
of
and
insights
what
will
be
happening
cute.
B
He
is
super
excited
on
the
SBC
as
well
as
well.
Now,
AC,
you
have
a
yes
this
there.
It
is
thank
you
and
make
your
voice
heard
on
the
sharepoint
development.
So
there's
the
state
of
sharepoint
development,
comm
link,
so
please
go
there
and
set
that
forum.
We
in
sharepoint
engineering,
even
I'm,
gonna,
use
those
results
to
understand
how
the
community
is
customizing
stuff.
B
This
is
a
survey
run
by
boitano's,
so
asus
company
and
rancor
ring
core
is
well
plenty
of
people
working
there
as
well,
but
we
will
absolutely
take
advantage
of
the
insights
which
we
get
out
of
that
survey
as
well.
So
please
go
and
fill
that
out.
So
absolutely
fine.
How
many
times
can
I
ended?
That
survey?
I
don't
know.
B
B
A
So
thanks
everybody.
Our
next
instance
of
this
call
is
gonna,
be
April
26
for
the
SPF
XJS
special
interest
group,
our
next
general
dev,
a
special
interest
group,
is
next
Thursday
April
19th
same
time
and
look
forward
to
talking
with
folks
on
both
of
those
calls.
Thank
you
everybody
for
joining
the
call
today
and
look
forward
to
talking
with
you
out
there
on
the
various
channels
have
a
great
weekend.
Thank
you.