►
Description
See https://techcommunity.microsoft.com/t5/SharePoint-Developer/SharePoint-Patterns-amp-Practices-JS-amp-SP-Fx-Special-Interest/m-p/11406#M349 for detailed content.
Presentation available for download from http://docs.com/OfficeDevPnP.
A
Hello:
everyone
welcome
to
the
SharePoint
framework
in
JavaScript
special
interest
group
weekly
meeting
at
September
15
2016,
I'm,
Patrick
Rodgers,
I'm
joined
by
visa,
you've,
onan
and
we're
here
to
talk
through
a
couple
of
great
topics.
As
always,
now
we've
got
a
few
questions
for
you,
folks
in
the
community,
on
how
we're
going
to
move
forward
with
these
meetings
so
moving
right
into
what
we
got
want
to
talk
a
little
bit
about
what
we
are.
What
the
JavaScript
special
interest
group
is
all
about.
A
We've
been
evolving
over
the
last
two
three
weeks
now
to
start
to
bring
in
a
lot
more
of
the
SharePoint
framework
front
and
center,
and
that
coincided
with
the
public
preview
release
of
that
SharePoint
framework
and
for
which
I
believe
update.
3
has
now
dropped.
So
that's
out
there.
If
you
want
to
grab
the
latest
and
greatest
updates
around
that
and
so
we're
starting
to
pull
that
into
the
conversation.
A
A
little
bit
more
as
folks
are
going
to
be
using
that
more
going
to
naturally
start
to
have
more
questions
around
that
you
don't
want
to
try
new
things
or
looking
for
new
features.
So
we
want
to
make
sure
we
highlight
that
as
a
more
sort
of
clear
part
of
the
discussion
and
provide
a
way
for
folks
to
get
updates
on
this
call
about
the
latest
of
what's
going
on
with
the
SharePoint
framework
and
luckily
not
we've
got
they
so
tired
right
in
with
that
team.
A
Now,
so
we're
able
to
get
some
really
great
kind
of
sort
of
insider
information.
A
little
bit
sometimes
may
be
ahead
of
some
other
folks,
which
I
think
is
a
really
great
perk
of
attending
these
meetings
and
the
other
thing
we're
still
going
to
focus
on.
That's
not.
The
change
is
the
JavaScript
core
component.
We
are
at
a
place
with
that.
Where
we're
sort
of
I'll
call
it
were
a
fairly
stable
place.
We
don't
have
a
large
rapid
blocks
of
development
happening
as
we
did
in
the
past,
but
we
still
want
to
focus
on
that.
A
Keep
expanding
that
keep
improving,
that
we
do
get
some
issues
reported
now
and
then
so
that
is
still
very
much
supported
very
much
a
part
of
what
we're
doing.
But
it
is
just
part
of
the
story
now,
as
we
bring
in
a
little
bit
more
focus
on
the
SharePoint
framework.
So
those
are
our
two
core
pieces.
We're
going
to
talk
about
in
these
meetings.
You've
got
two
links
down
there
at
the
bottom.
The
first
goes
to
the.
A
What
are
we
calling
another
microsoft
tech
community,
but
that
link
will
always
work
wherever
we
end
up,
so
that
AKA
ms
sharepoint
pnp
community
be
sure
to
join
us
there.
That
is
your
replacement
for
Yammer.
So
if
you've
been
posting
questions
and
asking
things
on
Yammer,
that's
that's
the
new
location
to
do
the
same
sort
of
activities,
I'll
confess
I'm
still
mentally
transitioning
there.
A
So
if
there
are
questions
kind
of
pending,
I
will
try
and
follow
up
with
those,
but
do
encourage,
as
folks
are
doing,
on
Yammer
for
the
community
to
reach
out
and
help
each
other,
and
we've
also
got
dev
office,
calm,
/
SharePoint,
which
is
great
hub
for
all
things,
sharepoint
and
sharepoint
development.
A
little
bit
more
specifically
so
you'll
get
a
lot
of
links
there.
A
lot
of
sharepoint
framework
information,
as
well
as
general,
sort
of
sharepoint
updates
and
things
like
that
again
focused
around
the
development
side
of
things.
A
So
we've
not
left
anything
behind.
We've
brought
in
a
little
bit
more
focus
on
the
SharePoint
framework,
still
great
same
great
group
focused
on
client
site
development
and
all
those
great
tools
that
are
available,
and
we,
you
know,
continue
to
be
part
of
the
larger
SharePoint
patterns
and
practices
program,
so
no
changes
there
as
well.
A
So
moving
into
our
agenda
for
this
week,
sharepoint
framework,
like
we
mentioned
a
little
bit
earlier,
latest,
updates
around
that
guidance.
Things
like
that
great
chance
to
sort
of
start
to
think
about
questions
for
the
later
open
discussion.
We'll
do
our
update
about
the
core
component,
all
good
and
then
we've
got
one
demo
today,
I
believe
from
waldeck
is
going
to
do
sort
of
crud
a
demo
around
who
I
don't
see
on
the
call
right
now.
So
this
is
gonna
be
a
fun
demo.
Oh
sorry,.
B
A
Perfect
perfect
perfect,
if
not
we'll
we'll
ad-hoc
a
demo,
but
so
what
a
great
demo
again
from
him
and
then,
of
course,
we'll
close
out
with
open
discussion,
she's
a
great
opportunity
for
everybody
who
joins
the
call
to
ask
questions,
provide
feedback
either
on
the
SharePoint
framework
core
component
things
like
that,
just
general.
You
know
open
discussion
as,
as
the
title
says
so
moving
right
into
it.
I'll
pass
this
off
to
visa
to
give
us
an
update
on
the
SharePoint
framework,
Developer
Preview.
A
B
B
There's,
there's
there's
going
to
be
future
articles,
there's
going
to
be
additional
tutorials,
there's
documentation
and
all
of
that
also
the
ship
on
web
hook.
Information
which
is
in
Developer
Preview
as
well,
is
underneath
the
death
of
calm,
/,
sharepoint
and
that
was
released.
I
think
last
week,
clusters
day,
two
hours
after
our
call
I
knew
that
that's
going
to
happen.
So
we
had
a
kind
of
a
sneak:
it's
coming,
it's
coming
pretty
soon,
but
we
were
unable
to
actually
explain
when
and
then
contributions
for
this
one
are
actually
welcome.
B
So
if
you
find
any
typos,
if
you
find
any
issues,
if
you
find,
if
you
actually
want
to
even
write
an
article,
that's
absolutely
possible
as
well
so
indicator
becomes
a
SharePoint
/s,
PDF
docs
and
that's
actually
with
the
source
of
the
left
at
office.com
SharePoint.
So
we
actually
automatically
have
a
purpose
in
mechanism
whenever
we
merge
stuff
from
the
master
branch
to
disturb
the
story,
staging
prams
to
the
master
branch.
That
stuff
is
getting
a
pup
list
in
the
left
of
stock
2.com
/
SharePoint.
B
So
it's
a
fully
automated
system
which
helps
on
on
giving
the
flexibility
on
any
any
issues
or
any
additional
articles
extremely
fast,
not
like
it
used
to
be
with
msdn
for
months
and
months
and
months
waiting
for
any
updates
to
actually
happen.
So
this
is
extremely
good.
The
other
thing
what
has
happened
so
last
night
well
last
morning,
depending
again
on
which
time
zone
you
are
sitting,
will
release
the
new
top
of
the
shipment
framework
so
truck
number
tree,
and
that
has
some
additional
fixes.
B
It
has
some
additional
capabilities
and
stabilization
things
for
the
SharePoint
framework.
Well
we're
closing
in
to
the
ignite
conference,
which
is
within
one
and
a
half
weeks.
Oh
by
the
way,
do
you
have
a
PMP
both
in
the
indexed
instability
section
as
well,
so
cliff
feel
free
to
drop
by
and
see
live
demos
and
have
questions
around
anything
on
a
sharepoint
customizations,
but
most
likely
we
will
not
have
additional
troops
or
I
would
doubt
that
there
will
be
additional
drops
before
the
ignite,
because
we
want
to
stabilize
the
platform.
B
We
want
to
make
sure
that
there's
no
ad
hoc,
last-minute
changes
within
our
demos,
which
will
kind
of
present
within
the
breakouts
as
well
and
I,
think
ignite
stations
are
all
getting
recorded.
So
you
can
watch
those
later
on
by
yourself
as
well
good
moving
alone
on
on
the
changes
within
the
last
within
the
week.
B
If
I
can
actually
get
this
moving,
something
happened
there
we
go
so
shape
and
framework
report
sample
repository
is
now
open
for
the
community
contributions
and
we
are
actually
during
this
week
I
think
we
got
through
the
three
additional
contributions
from
a
community
beside
so
individual
samples
which
are
showing
scenarios
so
they'll
say
it:
scenarios
for
power,
bi
integration,
which
have
been
framework
crackpots,
there's
the
search
web
part
with
Elio
presented
week.
You
can
go
and
have
a
look
on
the
recording
if
you're
interested
it's
over
there.
B
That's
well,
that's
a
few
examples
already
and
there's
few
other
ones
as
well
and
we're
looking
into
adding
those
there
as
well
or
additional
samples
in
the
shipment
framework
webpart
sample
repository
as
we
move
along.
There
will
be
also
engineering
driven
samples
in
that
ripple,
but
some
of
them
are
now
on
the
under
final
review.
Some
of
them
are
available
in
the
deaf
ranch
and
and
but
there
will
be
additional
samples
available
all
the
time
and
some
of
the
some
things
around
the
existing
essence
much
we
have
available.
B
So
if
you
go
to
directed
officer,
comes
a
SharePoint.
Obviously,
please
do
remember
that.
That's
rest,
that's
relatively
easily.
Remember
remember
ball.
What's
the
right
word
from
that,
but
you
can
find
in
future
all
of
the
ship
and
related
topics
there
will
link
the
BM
based
off
a
link.
Webcast
will
link
all
the
additional
articles
there
as
well
for
the
shipment
framework
itself,
there's
already
existing
tutorials.
B
So
right
now
we
do
acknowledge
that
it's
a
really
early,
Developer
Preview,
and
but
it's
if
you
want
to
kind
of
a
catch
up
on
what's
actually
happening,
even
though
you
don't
have
time
to
really
start
playing
with
the
SharePoint
framework.
I
would
really
encourage
you
to
go
through
the
toros
one,
two
and
three
and
four,
because
then
you
get
a
nice
understanding
on
okay.
This.
This
is
what
the
tooling
is
all
about.
B
This
is
how
the
stuff
works
and
I'll
come
back
to
that
whenever
they
it's
more
stable,
because
I
need
to
work
on
the
existing
customization
models.
Obviously,
if
you
are
free
to
follow
up
on
the
other
tutorials
as
well,
and
if
you
rather
wanna
watch
a
video
where
the
tutorials
are
walkthrough,
that's
available
as
well.
B
B
We
do
acknowledge,
and
absolutely
we
understand
if
you
are
coming
from
a
SharePoint
background,
if
you're
coming,
let's
say
from
a
sharepoint
server
side
background,
there
is
a
learning
curve,
but
the
B&B
is
there
to
help
if
you're
coming
from
a
web,
let's
say
from
a
web
development
background
not
from
a
sharepoint
server
side
background
and
we've
the
BMPs
there
to
help
on
on
what
does
the
beer?
What
does
the
sharepoint
actually
provide?
So
we
try
to
be
there
on
the
on
getting
started.
B
We
try
to
be
there
on
the
more
advanced
topics
as
well
and
that's
what
the
B&B
is
all
about.
It's
the
community
work
and
helping
you
guys
to
understand.
If
you
have
any
questions
around
specific
topics,
can
we
move
on
Patrick
on
the
following
slides
now
that
you
are
my
lovely
assistants
on
the
on
the
slides,
so
three
things
and
now
the
opportunities
to
contribute
our
on
SharePoint
framework,
so
obviously
testing
tutorials
your
input
is
absolutely
more
than
welcome.
B
I,
don't
know
actually
what's
going
to
happen
later
today
or
tomorrow,
but
the
story
at
least
seems
to
be
that
if
you
try
to
go
to
the
old
Yammer
links,
they
will
redirect
you
to
the
tech
community
of
microsoft
com,
which
is
a
pity,
because
it
means
that
the
old
questions
and
answers
will
be
lost
and
trust
me.
We
know
that
how
awful
the
situation
is,
but
somebody
has
made
that
decision
obvious
a
desk
platform
demo,
your
stuff
in
the
BMP
special
interest
recall.
B
B
So
we'll
get
you
an
optionally,
your
company
mentioned
as
an
example
in
the
upcoming
ignite,
we
have
like
25
companies
explicitly
called
out
within
the
slides
around
the
PMP
session,
who
well
persons
from
those
companies
has
contributed
to
the
BMP
initiative,
and
we
want
to
absolutely
make
sure
that
the
companies
are
getting
credits
out
of
it
as
well,
and
and
yes
tell
us
your
feedback.
So
if
something
is
painful,
if
something
is,
is
horrible
tell
us
so
we're
trying
to
help
you?
B
We
do
know
that
especially
the
if
you're
coming
from
the
classic
sharepoint
development
side,
it
might
feel
pretty
challenging
the
landowners
stuff
and
then
let's
have
an
open
discussion.
What
do
we
need?
What's
the
guidance
what's
lacking
and
all
of
that
the
DMP
is
here
to
help
and
and
personally
I
work
within
the
SharePoint
engineering.
So
I
can
actually
bypass
all
the
feedback
to
the
right
channels
as
well,
but
good
moving
on
patrick
on
the
following
things.
I
think,
when
I'm
heading
to
the
j
score
site.
A
So,
as
I
was
saying
with
the
weekly
standup
quiet
week,
but
do
look
forward
to
getting
some
more
stuff,
I've
been
traveling
this
week
for
work,
so
I
myself
haven't
had
much
time
but
still
working
on
writing
tests
and
continue
to
grow.
That
library,
as
we
talked
about
earlier
mike,
has
a
great
question.
What
is
the
use
case
for
the
JavaScript
provisioning
engine
was
so
to
me.
I,
don't
really
see
a
use
case
for
using
the
provisioning,
for
example,
in
a
browser.
A
I
think
that's
a
going
to
be
a
very
timeout,
likely
scenario
where
I
do
see.
It
is
if
somebody
wanted
to
write
a
note,
j/s
provisioning
service
I
think
that
would
be
a
very
valid
use
case.
So
again
it
runs
server
side,
but
it's
something
that
you
could
call
out
to.
You
could
have
a
front
end
for
much
like
you.
Would
you
know
if
you
were
writing
a
provisioning
provider
hosted
app
in
you,
know
normal
dotnet
and
see
some.
A
A
Score
library
we
could
move
forward
with
you
know
might
be
a
quicker
way
to
create
and
configure
a
list
right
if
you,
if,
if
we
got
such
parody,
that
you
could
create
the
XML
template
drop
it
into
a
method
and
get
your
list
with
all
the
fields
and
everything
I
I,
don't
know
it
doesn't
exist
right
now,
I,
don't
know
how
long
that
would
take
in
JavaScript.
So
maybe
that's
something
we
could
do
from
the
browser.
A
B
In
common
yep,
oh
yeah,
sorry,
a
quick
comment
Patrick
on
that
one,
because
I
think
that
the
we
get
so
many
questions
around.
Why
can
I
create
a
site
collection
using
javascript
api?
Why
can
I
do
this
outside
using
javascript,
api
and
I?
Think
you
clearly
nailed
it
and
the
problem
is
that
the
cella
script
you
would
be
stealing
over
the
frozen
and
creating
a
site
or
a
site
collection,
while
site
collection
especially
might
be
taking
15
minutes.
B
So
would
we
actually
then
rely
on
on
the
fact
that
dangers
that
would
be
waiting
for
15
minutes
for
looking
in
the
key
funimation
before
the
site?
Collection
is
done
and
that's
really
why
we
want
to
rather
extend
this,
isn't
a
synchronous
process,
but
anyway,
that's
as
reinforcing
what
you
were
saying.
That's
right,
yep.
A
Then
I'm
sure
we
could
find
some
very
interesting
gifts
for
people
to
watch
yeah,
that's
true,
yes
and
then
so.
Finally,
just
talking
a
little
bit
about
opportunities
to
contribute
in
the
core
library,
still
very
much
write
a
web
part
and
demo
it
on
this
call.
So
we've
had
some
uptake
the
last
few
weeks
on
that,
but
if
you've
written
a
webpart,
big
or
small
demo
it
on
this
call,
let
us
know
let
myself
know
let
basin
Oh
we'll
get
you
a
slot
on
here
to
demo.
A
We
really
want
to
start
highlighting
the
work
the
community
is
doing
because
I
think
we
all
benefit
and
learn
from
each
other
in
that
regard,
like
I
said
before
bonus
points
in
a
way,
if
you
use
the
jas
core
framework
in
that
web
part
love
to
see
folks
starting
to
use
that
actually
I
didn't
do
a
slice
should
have
done
a
slide
on
this.
We
for
the
104
library
we
got
our
first
version
targeted,
metrics
back
in
the
way,
we're
doing
it
with
the
see
some
and
so
we're
being
used.
A
A
The
the
document
generation
is
now
part
of
the
project
and
looking
to
enhance
that
styling
in
that
layout,
I
didn't
work
there
and
I
will
confess
very
openly
I'm,
not
a
CSS
and
styling
guru.
So
if
one
or
more
of
you
folks
are,
would
love
to
have
your
help,
but
I
do
believe,
there's
still
an
open
issue
around
that.
So
a
question
now
for
the
folks
on
the
call
we've
got
32
participants,
which
is
fantastic
this
week,
really
love
to
see
that
participation.
A
But
one
of
the
questions
we've
been
talking
about
on
the
core
team
is.
This
has
been
a
weekly
meeting
now
for
probably
not
quite
a
whole
year,
but
clothes
and
some
weeks
we
have
a
lot
of
folks
like
this
week,
other
weeks,
less
folks,
which
is
great,
but
what
it
makes
sense
to
move
this
to
every
two
weeks.
We
have
a
lot
of
patterns
and
practices
meetings.
Now
we
realized
in
the
core
team
on
our
calendars,
which
means
for
you,
folks
that
all
participate
in
these.
A
You
have
a
lot
of
meetings
on
your
calendar
now,
so
we
thought
of
pulling
that
back
a
little
bit
making
sure
you
know,
because
each
week,
some
weeks
we
have
a
lot
of
great
updates
other
weeks,
a
little
bit
less
so
moving
it
to
bi-weekly
would
really
allow
us
to
have
a
very
sort
of
much
more
meteor
meeting
each
each
time.
So
that's
kind
of
our
thinking.
We
would
do
our
best
to
communicate
that
out,
make
sure
you
know
we
don't
lose
folks
in
that
process.
A
B
A
B
A
Cool
yeah
you're,
really
in
and
out,
unfortunately,
one
yeah,
so
thanks
everybody
for
the
feedback
on
this
no
decision
at
this
point,
but
look
for
us
to
say
something.
Maybe
stay
weekly
around
ignite
in
cases
of
big
announcements.
I,
don't
think
we're
going
to
make
this
change
prior
to
ignite
regardless
just
from
a
messaging
standpoint.
A
D
Let
me
know
when
you
can
see
my
screen:
that's
always
the
question
when
a
mac
I,
like
the
demos
Mike,
yes,
thank
you
Mike
all
right.
Let
me
know
when
you
can
see
my
screen.
According
to
my
computer,
you
should
be
seeing
it.
I've
got
it
now,
all
right,
everyone
else
as
well
tip
3,
2,
1,
all
right,
all
right!
D
So
currently
we're
working
on
a
sample
that
illustrates
how
you
can
do
SharePoint
crud
operations
in
SharePoint
framework,
client-side
web
parts,
and
we
don't
have
a
favorite
so
because
we
can
reach
an
agreement
and
the
joke.
We
will
have
a
sample.
That
shows
how
you
can
do
that
with
angular.
How
you
can
do
that
with
no
specific
framework,
which
is
the
option
that
you
have
when
scaffolding
new
SharePoint
framework
client-side
web
parts,
then
you
will
have
react
and
then,
especially
for
Pat
Patrick,
how
you
can
do
that
exactly
the
same
with
the
SharePoint
p.m.
D
pjs
library.
So
with
that,
you
will
be
able
to
compare
and
what
I
use,
angular
or
react
or
something
else.
We
believe
that
you
will
be
able
to
use
the
samples
as
boilerplate
to
implement
crud
operations
in
your
web
parts
and
then
then
the
great
thing
is
that,
if
you're
interested
in
comparing
the
benefit
of
using
the
spp
MPG
as
well,
highbury,
comparing
to
doing
everything
with
red
with
rest
by
yourself,
you'll
have
a
great
comparison
like.
How
does
that
look
like
and
what's
the
benefit?
So
here?
D
Is
he
the
web
part,
which
is
so
currently
the
one
that
you
see
on
screen
is
implemented
using
the
SP
p.m.
pgs
light
hi
brary,
but
if
I
pick,
for
example
the
one
in
angular,
it
will
look
exactly
the
same
and
that's
exactly
the
point
that
they
look
exactly
the
same
and
when
you
add
them
to
the
page.
I.
Don't
think
that
you
have
to
add
is
the
name
of
your
list,
but
we
will
have
all
of
that
described
in
a
step-by-step
annual.
How
do
you
set
them
up
and
how?
D
How
do
you
get
them
to
work
on
your
machine?
And
the
basic
point
point
is
not
really
what
it
does,
but
actually
the
code,
but
we
so
we
will
dive
in
a
code
in
this.
Second,
but
first
let
me
show:
oh
you
what
it
does.
So
first,
you
create
new
item
in
a
list
right,
so
we
have
a
create
operation
and
then,
when
you
do,
you
will
see
a
new
I
and
quite
a
method
here
with
an
ID
and
the
title,
then
you
it.
Then
you
can
read
the
item
from
the
list
right.
D
So
that's
the
are
in
crud,
then
we
also
have
and
the
ability
to
read
all
items
in
the
list.
Currently
we
don't
support.
Paging
are
all
that,
but
just
an
easy
way
to
get
all
the
items
in
the
list
and
I
guess
that
by
default
and
rest,
for
example,
you'll
get
50
items
right,
I,
guess
that
that's
the
the
default
and
then
we
also
have
the
update
operation.
So
the
update
updates
the
latest
item.
That's
in
the
list,
so,
for
example,
we
create
now
item
with
ID
47
49,
and
then
we
will
update
the
item.
D
D
D
So,
for
example,
if
you
would
like
to
compare
what's
the
benefit
of
doing
the
SharePoint
p.m.
pjs
like
library,
let's
open
these
two
side-by-side
so
first
I
open
the
SharePoint
p.m.
pgs
library
and
then
on
the
other
side.
Let
me
open
the
no
framework
at
all
and
that's,
for
example,
say:
let's
ignore
the
rendering.
Let's
say
if
you
would
like
to
update
an
item
so
here
on
the
right
hand,
side
you
have
plain
rest
which
is
used
which
uses
the
HTTP
client
that
you
get
from
from
the
web
part.
D
D
So
here
you
can
see
how
we
achieve
exactly
the
same.
So
on
the
right
hand,
side
with
plain
res:
we
basically
construct
the
complete
URL
by
passing
in
the
URL,
the
web,
underscore
API
Webley
and
all
that,
whereas
here,
on
the
left
hand
side,
when
we
used
a
pap
component,
we
can
basically
have
semantic
approach
to
that
where
we
just
say.
D
Okay,
we
want
to
have
web
from
web
on
that
list
from
collection
of
list
when
I
have
that
one
by
title
and
then
want
to
get
one
item
by
ID,
and
then
we
want
to
get
get
that
and
updated.
So
there
is
a
way
easier
way,
more
error-prone
approach
to
getting
it
and
its
order
as
as
well,
because
there
are
quite
a
few
things
that
you
don't
need
to
take
care
of.
D
So,
for
example,
here,
if
you
would
like
to
see
the
update
in
update
you,
if
you
do
it
manually
yourself,
you
have
to
construct
the
payload
with
the
right
right
metadata
with
the
right
typing
and
all
that
and
inject
it
into
your
request,
and
you
also
need
to
take
care
of
the
the
right
method.
All
the
headers
except
headers
contacts,
all
that
if
you
use
the
SharePoint
p.m.
pjs
library,
the
only
thing
that
you
have
to
do
is
you
actually
do
this?
D
So
you
say:
PMP
I
to
get
list,
get
the
item
and
then
update
and
it's
it's
there.
So
compare
all
of
these
lines
here
and
how
many
errors
you
you
could
be
here
compared
to
just
one
function,
call
which
is
update
right.
So
it
just
ways
it
makes
things
really
easier
and
that
was
actually
their
first
time
from
for
me
to
give
it
a
try
and
I
must
admit:
I'm
really
surprised
positively
surprised
how
easy
it
was
just
to
get
it
to
work
and
SB
effects.
D
A
All
right
awesome,
all
back.
Thank
you
great
demo,
love
to
see
the
use
of
the
sharepoint
core
library
and
I.
Of
course,
very
much
agree
with
you
I
think
it's
going
to
be
a
much
easier
approach
than
trying
to
remember,
having
had
to
figure
out
how
to
make
all
those
different
bodies
and
JSON,
for
you
know
to
get
things
to
work
for
the
core
library.
I
think
it's
going
to
be
much
easier,
hopefully
helpful
and
hopefully
give
people
a
little
bit
better
experience.
A
A
A
I
think
that's
going
to
be
an
arguable
tool
for
the
whole
community
to
be
able
to
compare
the
different
ways
of
doing
things
both
on
the
data
side,
as
well
as
the
sort
of
front-end
framework
side,
because
I
know
I
get
a
lot
of
questions
just
in
general,
around
should
I
use
angular
should
I
use
react
or
any
of
the
others,
and
there
isn't
really
one
answer
to
that:
it's
it's
a
sort
of
a
complex
question
of
what
fits
for
the
project.
What
fits
for
the
team?
A
What
fits
you
know
for
what
you're
actually
trying
to
achieve?
So
that's
going
to
be
a
really
valuable
resource
and
look
forward
to
seeing
that
once
it's
available.
So
now
we
got
plenty
of
time.
This
call
for
sort
of
the
open,
Q&A
discussion.
So
this
is
great
time
if
anybody
has
questions
or
comments
or
really
just
kind
of
anything,
so
sort
of
open
forum
feel
free
to
come
off.
Mute
and
or
type
in
the
IM
window
and
and
what's
on
your
mind.
B
B
C
B
C
C
C
This
takes
the
Technical
Community
Business
I've,
requested
again
an
area
for
the
office
dev
PMP
people
I
also
the
SharePoint
framework
areas,
because
it's
it's
chaos
trying
to
find
the
you
want
and
find
out,
what's
actually
happening
with
the
PMP
and
with
the
SharePoint
framework,
where
it
includes
bundled
in
with
all
the
other
development
issues.
So
I
have
emailed
/.
C
So
I
put
the
thing
on
the
technical
community
asking
for
those
two
areas,
so
we
can
have
our
own
areas,
so
we
can
easily
keep
an
eye
on
what's
going
on
rather
than
actors
of
hunt
through
loads
and
loads
of
development,
questions
which
are
absolutely
nothing
to
do
with.
You
know
PMP
and
SharePoint
framework.
So
if
so,
we
can
have
a
chat
with
Anna
can
get
it
to
move
her
butt
and
get
this
sorted.
That
would
be
appreciated.
B
Yep,
that's
good
feedback
and
we
need
to
actually
have
that
feedback.
The
related
and
I
using
the
official
other
public
channels
as
well,
because
the
thing
is
that
they
aid
they.
For
some
reason
they
wanted
to
drop
the
bmv
groups
because
they
wanted
to
put
us
under
the
technology
and
service
groups
which
is
kind
of
fun.
We
can
call
ourself
as
the
SharePoint
the
Empire
ship
on
dev
group
as
well,
but
it
really
comes
down
on
what
the
community
wants.
A
Does
the
group
have
a
slack
channel,
we
have
a
get
ur
channel,
I,
suppose
we'll
call
it
in
lieu
of
slack
I'm
hesitant
to
open
up
another
forum
to
track,
but
if,
if
we
all
need
a
slack
channel,
we
can
do
that
right
now.
I'd
encourage
folks
to
go
to
the
get
er
and
use
that
in
this
time,
I
know
it's
not
the
same
or
on
parity
with
slack,
but
for
now
try
and
use
the
the
get
er
and
that
just
be
so
obstinate
grow
from
there.
B
And
quick
comment
around
that
one
as
well,
so
the
slack
or
pork
eater
faber
crate.
If
there
are
let's
say
a
few,
tens
of
people
who
are
active
and
the
BMP
krupin
yammer
had
four
thousand
seven
hundred
members,
and
that
meant
that
we
were
getting
a
lot
of
questions
across
different
topics
and
if
you
didn't
follow
up
on
the
croup
every
single
day
or
twice
a
day
and
you
were
unable
to
follow
up
on,
what's
actually
happening
slack
the
term
with
slack.
B
The
problem
is
that
the
discussions
or
with
cater
the
discussions
goes
so
fast
that
you
would
have
to
follow
up
on
that
all
the
time.
So
if
we
would
have
that
4,000
members
who
are
active,
so
it's
that's
one
of
the
reasons
why
we've
been
in
hesitant
with
slack
or
going
heater,
true
PMP.
So
the
killer
is
more
for
the
cello
script,
core
library
right
now
and
although
they
are
on
any
questions
around
the
related
topics,
but
the
BMB
has
so
many
followers
right
now
that
I
don't
think
that
would
scale
to
Keylong.
A
Yep,
that's
a
great
point:
I
mean
I
know
when
I
wake
up
in
the
morning.
A
lot
of
the
folks
on
the
patterns
of
practices,
core
team
are
in
Europe
and
so
then
I've
got
50
or
60
things.
I've
got
to
read
every
morning,
so
it's
tough
sometimes
to
catch
up.
But
if
we
multiply
that
out
to
4,000
it
would
be
almost
impossible
to
ryans
question.
Anyway.
We
can
push
to
get
Yammer
back
it
I
I.
D
C
A
A
B
Say
that
it's
it's
yeah,
it's
an
impossible
fight,
somebody
in
the
higher
level.
First
of
all,
there
was
a
decision
that
the
community
moves
to
network
at
office.com
and
then
somebody
that's
pretty
high
level
was
a
probably
was
like
hey.
This
is
a
great
idea:
that's
great,
a
Microsoft
communities,
and
now
it's
my
tech
community
of
microsoft.
Com
personally
I
was
asking
at
some
point,
but
why
we're
calling
that
tech
community?
What
about
the
people
who
are
not
take?
B
Why
can't
we
actually
get
them
their
own
quotes
as
well,
but
anyway,
and
somebody
somewhere
made
a
big
decision
and
they're
pushing
that
heavily
and
then
we
were
can
either
fight?
Yes,
yes,
we
were
not
consulted,
so
we
can
eat
a
fight
for
it
and
not
use
it.
But
then
the
question
is:
where
would
the
people
go
for.
B
Who
has
a
much
higher
payroll
than
we
do,
sir,
and
to
be
fair?
There
are
advantages
that
the
key
and
when
it's
off
that
net,
to
take
community
of
microsoft
com,
is
that
every
single
convent
air
gets
indexed
by
the
search
crawlers
with
Yammer.
That
wasn't
the
case,
and
if
you
have
ever
tried
to
use
the
Mercer
CH,
you
know
that
that
wasn't
really
that
functional,
so
it
this
way
and
people
can
actually
find
these
questions
and
answers,
hopefully,
even
though
they
wouldn't
be
registered,
and
that's
really
the
key
point.
A
But
it's
a
kind
of
the
general
question.
We
are
still
figuring
out
the
best
way
to
work
in
the
new,
yes,
tech
community
I
mean
I,
think
we
all
had
a
pretty
nice
rhythm
in
Yammer,
at
least
I
thought,
I
did
and
I
think
others
did
as
well.
We
don't
have
that
yet
in
the
tech
community,
it's
a
new
thing,
so
we're
still
figuring
out
a
little
bit.
It's
definitely
a
little
rough
around
the
edges.
I
feel
right
now
to
Nigel's
point
harder
to
find
things.
It's
a
little
less
focused
we'll
get
there.
A
A
B
A
A
B
Not
for
this
one
I
think,
okay
to
go
and
and
I
think
we're
in
a
corner
quorum
related
on
switching
the
pie,
weekly
bi-weekly
mode.
We
can
actually,
let's
agree,
that
we
do
next
week,
but
we
then
do
not
do
the
ignite
week.
So
after
next
week,
we'll
switch
the
biweekly
mode
and
said
so
that
we
don't
have
to
do
this
call
during
ignite
also
to
being
clever
for.
A
C
D
A
That
point
so
I
was
going
to
see
if
we
could
get
a
camera
working
or
something
we
try
not
to
be
too
fancy,
though
alright.
Well,
hey.
Thank
you.
Everybody
appreciate
everybody
joining
the
call
appreciate
waldeck.
Thank
you
so
much
for
the
demo
and
if
you
know,
let's
try
and
stay
in
touch
across
the
various
channels
and
thanks
everybody
vasive.
You
want
close
out
yeah.
B
Well,
such
as
well,
you
almost
said
it.
Thank
you,
everybody
for
joining
and
thank
you
for
following
up
on
things,
will
get
the
recording
in
the
YouTube
within
24
hours.
So
that's
always
our
pockets.
So
if
any
of
your
friends
want
to
see
what
we
denote
or
the
wild
ex-demo,
you
can
have
a
look
on
that.
So
thank
you
for
joining
and
hoping
to
see
you
again,
Cheers.