►
From YouTube: PnP Monthly Community Call - January 2017
Description
Recording for the SharePoint / Office 365 Dev Patterns and Practices (PnP) January 2017 monthly community call from 10th of January.
More details on the content and direct links to specific topics can be found from following location - https://techcommunity.microsoft.com/t5/SharePoint-Developer/SharePoint-Office-Dev-Patterns-and-Practices-PnP-January-2017/m-p/38742#M1201.
You can also download the used presentation from https://doc.co/yHaCD2.
A
Gute
so
welcome
everybody.
This
is
the
monthly
community
called
January
20th
17th
edition.
My
presentation
name
was
actually
originally
2016,
January
2016,
but
it
is
actually
2017
it's
one
of
those
things
it
takes
a
while
to
again
to
remember
that
the
years
are
changing.
So
this
is
the
multi
community
call
for
sharepoint
patterns
and
practices,
also
known
as
office
def
patterns
and
practices,
and
more
but
more
and
more,
we've
been
concentrating
on
a
SharePoint
site,
even
though
we
do
cover
other
areas
as
well.
A
The
record
the
community
code
will
be
recorded,
it
will
be
available
in
the
BMP,
a
YouTube
channel
within
24
hours
after
the
recording,
and
the
whole
idea
of
this
course
is
to
go
through
what
has
happened
within
the
past
month
and
what
are
we
planning
to
do
in
the
future
and
give
credits
for
the
people
who've
been
doing
contributions?
We
also
have
live
demos.
A
Today
we
have
two
demos,
one
around
the
SharePoint
framework
and
I
put
in
the
creation
for
creating
classic
sites
and
a
team
sites
or
sub
sites,
and
that's
a
community
demonstration
or
community
contribution.
And
then
we
do
have
a
demo
around
on-premises
development
using
the
modern
web
stack
and
I'm
gonna
do
that
by
myself
and
for
this
time,
but
let's
actually
get
started
on
slides
and
if
you
have
any
questions,
feel
free
to
use
time
window.
A
These
are
the
monthly
community
calls,
so
we're
pretty
busy
always
for
this
particular
hour,
and
there
might
be
some
time
for
Q&A
in
the
end.
Hopefully,
we'll
see
how
the
how
the
speed
goes
with
the
with
the
demos
and
everything
else,
and
if
you
have
any
specific
questions
or
concerns
or
feedback,
there's
some
more
than
welcome.
But
we
would
prefer
that
those
two
actually
have
in
the
special
interest
group
calls,
and
we
kind
of
talk
about
that
one
in
a
second
as
well.
A
The
next
special
interest
will
call
for
the
BMP
provisioning
powershell
and
the
season
core
is
tomorrow.
Actually,
tomorrow,
at
7
a.m.
PST
or
5
p.m.
at
central
european
time
or
wherever
you're
located
around
those
time
frames,
but
let's
actually
get
done
going
on
the
slides.
If
I
activate
that
in
that
Skype
window-
and
we
should
be
good,
so
we
have
a
tubing
on
agenda.
Are
we
going
to
go
through
the
monthly
highlights?
So
what
has
happened
within
a
month
and
what
are
the
contributions
and
what
are
the
other
topics
around
the
B&B?
A
So
what's
coming,
what
has
been
contributed?
What
other
changes
and
then
we'll
have
two
demos
today
to
go
through
so
I'm,
estimating
that
the
presentation
will
take
roughly
25
minutes
and
then,
after
that,
we'll
go
to
demos
and
most
likely
we
will
have
some
time
for
the
Q&A
in
the
end,
as
well
really
depends
on
how
much
input
you
guys
are
giving
us
in
the
ion
window
as
well.
A
So,
first
of
all,
if
there's
any
new
persons
coming
in
on
this
and
this
course
sharepoint
patterns
and
practices,
is
a
initiative
community
driven
initiative,
coordinated
by
shape
and
engineering.
So
we
within
the
sharepoint
engineering
from
Redmond,
we
are
owning
the
BMP
and
we
are
using
the
BMP
as
the
primary
channel
for
anything
related
on
a
SharePoint
customization
for
on-premises
for
sharepoint
online,
giving
guidance,
giving
community
inputs
and
kidding
on
community
input
as
well.
A
You're,
probably
seen
us
asking
a
lot
of
feedback
around
the
SharePoint
framework
around
the
provision
of
things
and
all
of
that
and
those
are
more
than
welcome
because
that's
what
we
actually
want
to
use
the
PNP
as
well.
That
feedback
goes
directly
to
engineering
because,
as
an
example,
I
work
within
the
team
reporting
directly
underneath
Jeff
deeper
and
my
team
is
responsible
of
all
of
the
api's
within
a
SharePoint
and
including
the
documentation.
So
if
something
is
missing,
just
let
us
know
and
we'll
try
to
address
that.
A
We
do
have,
however,
also
limited
resources,
like
you
guys
have
when
you're
implementing
your
projects.
So
we
need
to
prioritize
our
time
as
well,
but
feedback
more
than
welcome
good
moving
on
on
things
and
yes
on
the
Nigel's
comment:
we're
going
to
talk
about
those
ones,
absolutely
as
well.
First
of
all
big
announcement.
Yesterday,
the
shipment
framework
is
moving
into
released
candidate,
so
yesterday
we
released
a
release
candidate
version
of
SharePoint
framework
and,
as
part
of
this
announcements
and
release,
we
also
updated
our
existing
tutorials
in
the
dead
of
calm
/
upon.
A
So,
if
you
go
there
and
start
working
true,
the
individual
tutorials,
those
are
already
up
to
date
as
well,
and
if
you
go
the
lifted
of
sterkens
last
blocks,
you'll
find
an
announcement
from
yesterday
actually
from
our
marketing
people.
Well,
it
hasn't
been
signed,
but
anyway
for
mics
of
people
where
we
have
been
pointing
the
release,
notes
where
we
were
explaining
what
other
changes
comparing
to
the
previous
shops
around
the
SharePoint
framework
and
what's
coming
up,
the
release.
Sharepoint
framework
is
relatively
close.
The
release
candidate
is
relatively
close
already
to
GA.
A
This
one
is
a
breaking
change
and
we
do
apologize
on
that
and
the
previous
drops
were
more,
let's
say
backward
unbootable,
and
this
was
a
breaking
change
so
that
whenever
we
go
to
the
GA
we
can
actually
we
can
actually
avoid
any
breaking
changes
at
that
point.
Sorry,
for
not
my
stuff,
is
starting
the
ring
on
my
table
now.
A
So
release
candidate
super
close
to
the
g8,
so
if
you
can
technically
start
implementing
your
stuff
already
at
this
point
might
be
some
changes,
but
this
will
be
a
relatively
minor
when
we
go
to
the
GA
and
ta
then
means
that
it's
actually
production
already.
The
release
candidate
means
that
it's
now
available
in
the
developer,
tenants
and
in
first
release
tenants,
but
it's
not
yet
production
ready.
A
We
have
super
close,
but
not
quite
there
yet
so
we're
getting
there
on
a
relatively
fast,
though
super
super
exciting
from
site,
because
also
means
that
pretty
soon
you
can
start
implementing
client-side
with
parts
in
production
for
classic
pages
and
classic
sites,
and
also
for
modern
science,
so
for
sharepoint
online
super
exciting
news
now
other
stuff
just
quickly
in
pinpoint,
because
people
are
not
aware
of
these
things
and
we
need
to
keep
on
repeating
this
and
so
how
to
find
PMP
examples
or
guidance.
This
is
a
classic
question.
A
A
So
this
is
absolutely
a
great
tool
for
you
to
find
what's
relevant
for
you,
but
when
you're
starting
your
projects
for
implementing-
let's
say
user
profiles,
the
criminal
provisioning
printing
in
sharepoint
online
or
in
on-premises
using
a
data
model,
so
absolutely
use
this
one.
We've
been
evolving
this
slightly.
We
do
have
nowadays
filters,
for
example,
for
SharePoint
framework
samples
and
all
of
that,
so
you
can
easily
find
what's
relevant
for
you
when
you're
working
and
trying
to
find
the
samples.
We
are
also
working
on
a
slightly
newer
version
of
the
sample
corals.
A
So
in
the
future
there
will
be
evolvement
and-
and
this
will
evolve
to
a
better
looking
portal
where
people
are
able
to
then
find
information
even
more
efficiently,
other
stuff,
BMP,
webcast
and
videos.
For
the
past
month,
we
released
technically
well
five,
four
or
five
weekly
podcasts,
and
these
are
at
once
again
on
a
different
topics.
Typically,
these
are
15
to
30
minute
webcasts,
which
are
concentrating
on
sharepoint
development
topics.
A
Many
of
them
are
nowadays
have
been
on
the
sharepoint
framework,
and
then
we
did
a
webcast
on
using
the
modern
web
stack
on
a
sharepoint
on-premises
deployment,
but
because
that
was
on
26th
of
December,
your
during
the
Christmas
time
period.
I
wanted
to
have
that
demo
included
in
this
monthly
call
as
well,
and
then
we
did
pretty
recently
this
Monday
that
was
yesterday.
Today's
Tuesday's,
we
released
the
the
webcast
run,
the
customization
options
which
opened
on
my
modern
experiences.
That's
not
15!
A
30
minutes,
that's
actually
more
than
50
minutes,
so
we're
pretty
close
to
one
hour
of
it
that
one
it's
more
like
an
ignite
session
or
whatever.
But
if
you
go
to
the
dev
two
doors,
come
you'll
find
a
plot
post
for
all
of
these
in
the
blog
post,
if
you're
only
interested
on
a
demo,
you
don't
want
to
have
look
on
the
slides
in
the
blog
post.
A
We
always
have
a
links
to
the
exact
demo
timings
as
well,
so
you're
able
to
jump
to
the
demo
and
concentrate
on
on
the
demo
section
from
that
perspective,
which
is
good
couch.
What
else
monthly?
Is
it
more
some
monthly
metrics,
so
the
December
2016?
As
expected,
we
know
that
this
always
happens.
We've
seen
this
in
the
past
as
well.
A
A
Because
that
mean
if
people
are
using
this
stuff,
it
means
that
we
can
actually
more
invest
on
the
stuff
as
well.
The
most-used
capability
was
once
again
the
provisioning
engine.
That's
no
doubt
the
number
one,
let's
say
bigger
capability
within
the
PNP,
and
that
was
used
in
825
tenants
and
in
a
bigger
scale
of
tenants.
A
There's
more
than
10
million
tenants
out
there
in
the
SharePoint,
Online
825
isn't
a
human
number,
but
then
again
quite
often
this
are
bigger
enterprises
and
and
bigger
customers
who
are
using
this
for
automating
their
provisioning
automating
their
site,
things
automating,
a
lot
of
audits.
You
know
stuff
in
a
SharePoint
Online
top
countries
didn't
change
at
all,
which
is
kind
of
interesting,
so
the
top
five
countries
is
exactly
the
same
list
as
within
the
previous
month
in
November
and
topic
from
a
tenant
number
perspective.
A
Top
five
countries
based
on
requests,
United
Kingdom
came
across
Denmark
they're,
pretty
close
and
Germany
is
just
following
behind
of
that.
United
States
is
leading
by
far
because
we
have
this
room
maturity,
well,
not
maturity,
but
significantly
more
tenants
are
based
on
in
the
US
and
then
Netherlands
is
pretty
high
on
the
consumption
perspective
as
well.
A
So
from
that
perspective,
it's
a
really
really
close
usage,
good
thanks
Freddy
for
that
comment,
top
15
samples
in
December
2016
kind
of
an
interesting
from
at
least
for
us,
because
these
are
two
country
samples
which
the
community
has
contributed,
or
we
work
together
with
the
community
and
VPS
and
non
invitees
to
make
this
happen.
The
number
one
sample
from
a
unique
page
view
perspective,
so
we're
tracking
individual
readme
file
accesses
in
the
Quito
is
the
SharePoint.
A
You
are
responsive
package
for
classic
sites
which
works
in
the
SharePoint
2013
Chevron,
2016
and
SharePoint
Online,
and
obviously
the
modern
expiry
in
SharePoint
they're
fully
responsive
natively.
So
you
don't
have
to
worry
about
that,
but
classic
pages
and
classic
sites
are
none,
and
this
is
a
SharePoint
UI
package
which
is
adapting
pretty
well
the
sites
to
be
responsive.
It's
not
a
100%
reliable
because
there
are
certain
special
web
parts
and
and
some
classic
bodies
of
how
SharePoint
classic
is
rendered
using
tables.
So
we
can't
actually
make
everything
responsive,
but
it's
pretty.
A
Ok,
it's
actually
superb
working
superbly.
Well,
and
it's
been
quite
widely
used
as
well.
The
core
component
is
pretty
high
as
well.
That's
us
expected,
so
people
are
looking
into
the
code
of
the
core
component
and
to
understand
what's
actually
happening,
and
yes,
we
know
that
we
should
have
a
much
better
documentation
on
that
one
as
well.
Then
the
PMP
parking
back
number
tree,
that's
good,
to
see
as
well,
because
that's
meant
to
be
a
starter
kit
for
partners
and
customers
how
to
implement
this
stuff.
A
In
a
shipment
online,
though,
the
business
dot
office
traces
to
faster
internet
from
Frank
corner,
it's
pretty
high
as
well
immediate,
and
it
has
been
really
high
after
it
was
released
because
it
shows
how
to
do
publishing
sites
using
modern
web
stack
in
SharePoint
Online
using
classic
publishing
the
modern
publishing
is
in
the
roadmap.
It's
in
the
queue
it's
going
to
be
released
or
first
version.
It's
going
to
be
released
at
some
point
and
I
can't
comment
on
the
timing
of
that
one.
A
At
this
point,
what's
kind
of
an
interesting
on
day
on
here,
there's
few
things
which
were
kind
of
a
super-clean
interest.
Then
there's
the
core
data
meant
receivers,
and
this
is
remote
and
intrusive
as
demo,
which
is
super
super
high,
so
people
seem
to
be
implementing
a
lot
of
remote
image
receivers
or
there
at
least
interested
of
seeing
how
to
promote
their
interests.
A
Now
that
we
are
heading
closer
to
the
GA,
we
can
kind
of
predict
that
the
SharePoint,
for
example,
access
and
usage,
will
be
crowing
as
well,
and
quick
comment
really
may
be
related
on
that
one
I
think
it
was
mentioned
in
some
of
the
slides
as
well
we're
working
from
this
week
and
probably
next
week
as
well,
getting
all
of
the
existing
samples.
What
we
have
on
a
SharePoint
framework.
I've
created
two,
the
release
candidate
level.
A
So
right
now
those
some
of
those
samples
will
have
issues
whenever
your
tenant
is
upgraded
to
the
latest
version,
which
is
to
release
candidate
version,
which
quick
clarification
again.
This
kind
of
classic
slide
I
know
some
of
you
have
seen
there's
so
many
times,
but
this
is
how
we
think
about
BMP.
We
have
the
core
team.
Then
we
have
the
special
interest
groups.
The
core
team
is
a
relatively
small
group
of
people.
They're
crippled
hook
people
who
coordinate
to
be
MP
stuff,
ndb's
internal
Microsoft
people.
A
Then
we
have
the
special
interest
groups,
which
are
more
concentrated
on
a
specific
areas
like
the
shape
and
framework
JavaScript
special
interest
group,
which
is
meeting
next
time
on
a
test
or
a
Thursday
19th
of
January,
and
that's
really
where
we
could
tell
always
the
latest
on
SharePoint
framework
and
the
BMP
Chaves
with
core
usage
and
there's
always
time
for
Q&A
as
well.
And
then
we
have
the
bi-weekly
PMP
Core
PowerShell
special
interest
group
which
we
will
meet
tomorrow.
A
So
if
you're
only
interested
on
on
those
topics-
and
you
have
questions
feedback
or
whatever,
then
you're
gonna
join
on
that
call
and
give
us
the
input
around
that
one.
But
that's
really
around
the
provisioning
engine.
Powershell
use.
It's
and
PM
pages
see
some
core
on
that
one,
and
then
we
have
this
monthly
community
calls,
and
these
are
more
around
us
telling
what
has
happened
within
a
month
and
who
are
the
people
who've
contributed
and
what
does
what
we're
gonna
do
in
the
future
as
well?
A
January
2017
released,
share
pod
framework
site.
We
have
two
explicit
and
new
samples
on
the
SharePoint
framework
site
in
November.
We
had
like
sixteen
or
eighteen
in
this
particular
release.
Only
two,
because
it's
the
holiday
season-
that's
absolutely
understandable,
so
there's
the
angular
aad
Web
API,
is
showing
how
to
call
a
custom
web
api
security.
There
are
ad
share
more
from
a
SharePoint
framework
web
part.
The
that's
a
slightly
problematic
situation
right
now,
because
the
SharePoint
has
a
different
goal
in
the
case
of
scheme
then
sure
ad.
In
the
future.
A
We
are
looking
in
the
aligning
those
the
authentication
model,
so
you
are
able
to
then
call
from
a
ship
on
framework
web
part
and
directly
stuff,
which
has
been
secured
using
Web
API
like
or
security
Web,
API
or
Microsoft
graph
as
an
example,
without
expedition
alone,
indication-
and
that
will
be
huge-
and
we
understand
that-
and
that's
that's
why
we're
working
on
that
one
as
well.
The
second
sample
is
at
a
spot
framework,
which
is
a
that's
actually
second.
A
So
he
can
actually
share
that
one
and
show
that
one
on
live
as
well,
and
then
we
released
four
different
guide
as
documentation
to
the
dev
tariffs
that
comes
last
SharePoint,
explaining
different
topics
explaining
different
areas
around
developing
stuff
on
the
SharePoint
framework,
but
looking
into
upgrading
days
to
release
candidate
a
level
quite
soon
as
well,
on
the
samples
and
guidance
perspective
kind
of
a
generic,
not
in
the
SharePoint
framework
side,
in
more
on
the
BMV
site
or
in
the
general
usage
site
we
released.
This
react.
Generic
app,
which
we're
going
to
show
today.
A
A
I'm
getting
a
lot
of
individual
emails,
which
I
hate
that
when
people
have
sent
me
an
individual
email
asking,
hey
I
have
this
and
this
customer
and
on
its
dissing.
This
critical
situation
and
I
need
to
have
this
answer
now.
The
reality
is
that
we
don't
scale
and
that's
why
we
want
to
have
this
all
of
this
guidance
out
there,
which
is,
for
example,
from
a
modern
experience.
A
Customization
perspective,
the
story
around
that
one
relatively
limited
for
time
being,
but
we're
looking
into
adding
additional
capabilities
from
an
engineering
perspective
and
enabling
additional
things
in
the
future
right
now,
the
guidance
is
showing
all
of
the
different
capabilities:
how
to
customize
the
modern
experiences
and
calling
out
those
in
practice
each
what
else?
Corsi
some
ancient
a
lot
of
overall,
both
some
overall
quality
and
performance
improvements,
a
lot
of
pull
requests
being
processed
a
lot
of
issues
being
closed
from
the
key
table.
There's
still
quite
a
few
of
them.
A
The
same
time
as
release
candidate
for
SPF
X,
because
we
will
introduce
a
lot
of
capabilities
and
a
lot
of
additional
things
on
the
core
KS
core
component
when
a
PowerShell
side
a
lot
of
a
lot
of
new
comment.
Let's
we
are
in
the
199
command,
let's
level
so
hopefully
after
January,
we
will
hit
the
200
command
lets
in
the
PNP
PowerShell,
and
these
are
really
around
operating.
For
example,
maturity
of
these
are
around
operating
stuff
in
the
recycle
bin.
The
renaming
a
PNP
folder
moving
TMP
folder,
adding
p.m.
A
A
A
lot
of
people
contributed
during
last
month
as
well.
So
these
are
the
people
who've
contributed
in
the
past
month,
based
on
our
github
statistics
and
other
other
channels
as
well.
I'm,
not
gonna
mention
all
of
you
guys
by
name
I
do
apologize
on
that,
but
the
numbers
are
so
cute
are
so
big
and
that
we
don't
really
want
to
have
spent
time
on
answering
and
telling
what
all
of
you
have
done
individually.
So
I
have
to
change.
This
were
small.
A
Some
of
the
changes
were
significant,
but
for
really
the
key
point
is
that
people
want
to
help
each
other
by
first
of
all
telling
maybe
finding
a
buck
and
second
of
all,
what
by
fixing
that
buck
and
pushing
that
back
on
the
engine
or
back
on
the
samples
and
helping
the
others
to
succeed
as
well.
Because
this
way
we
will
be
much
more
efficient
together
because
we
are
building
on
the
common
knowledge
of
the
community
rather
being
individual,
independent
I'm.
A
Here
not
going
to
share
anything
anyone,
nothing
my
pressures,
so
it's
much
more
easier
and
fun
to
work
together
and
try
to
resolve
the
typical
issues
and
share
your
knowledge
for
the
others
as
well,
for
Microsoft
from
a
company
perspective,
there's
quite
a
few.
Quite
a
few
companies
who
gave
us
their
permission
to
use
the
locals
or
have
given
the
permission
to
use
the
logos
as
well,
so
the
people
from
the
previous
slides
are
coming
from
these
companies
as
an
example
and
the
and
some
of
these
companies.
A
They
actually
have
a
dedicated
time
for
community
work
so
that
their
employees
can
actually
work
and
contribute
back
on
the
on
the
B&B
because
they
are
using
community
tooling
in
their
deliverables.
So
they
feel
that
it
would
be
nice
to
contribute
back
as
well.
Superb
and
absolutely
powerful
ones
happen
in
the
future,
as
well
from
Microsoft
side.
We
have
a
typical
set
of
people
on
the
left
side
and
own
a
person
who's,
not
let's
say
in
the
in
the
typical
crew
of
the
BMV
core
team.
A
A
Couch,
what's
in
the
queue
quickly
on
this
one
and
we're
gonna
move
on
the
demos
in
in
a
second
ship,
one
framework
is
absolutely
our
priority.
Still
we
are
looking
into
about
not
release
candidate
assault.
Upgrading
all
of
the
content
to
release
candidate
level
is
the
number
one
thing
and
then
hearing
the
DGA
after
them.
Your
contributions
are
absolutely
welcome
on
the
our
samples
in
a
kit
hub
as
well,
and
then
we
keep
on
evolving
the
provisioning
engine.
We
keep
on
evolving
the
core
component
chase
core
components.
A
The
2.0
is
going
to
be
released
relatively
soon
I'm,
just
waiting
for
final
go
from
Patrick
on
that
one
PowerShell
general
improvements,
absolutely
B&B
parting
back
evolving
and
samples
and
solutions.
We
keep
on
evolving
this
based
on
the
community
contributions.
Nothing
really
super
super
specific
for
this
month
in
the
queue
except
to
SharePoint
framework
and
we're
super
excited
on
on
the
level
of
that
one,
but
going
to
the
demos
so
we'll
start
with
Joseph.
If
I
can
find
Joseph
in
wine,
Joseph
I
it
there.
A
Yes
excellent,
are
you
already
be?
Have
you
been
upgraded
already,
as
a
presenter?
Nope
I
need
to
find
you
there's
too
many
people
online,
we're
second
from
the
last
second
from
the
last.
Oh
there
you
are,
you
have
your
last
name
and
first
name
in
a
slightly
different
format.
That's
right
now
you
should
be
presenter,
so
Joseph
is
gonna,
show
the
SB
effects
and
a
marks
of
framework,
but
what
framework
integration
and
then
we'll
move
to
that
on
premises.
A
B
Okay,
so
today,
what
I'm
going
to
show
you
is
a
very
basic
conversational
board
that
can
be
displayed
in
chef
and
framework
web
part.
Okay.
So,
as
you
all
know,
chef
and
framework
bot
framework
is
a
Microsoft
operated
service
and
the
SDK,
so
we
can
build
our
parts
and
integrate
with
SharePoint
and
other
channels
as
well.
So,
in
addition
to
the
bot
framework,
SDK
Microsoft
also
offers
the
other
services
like
lowest.
That
is
the
language,
understanding,
service
and
speech
API,
so
to
build
great
BOTS.
B
Basically,
so
the
pod
connector
is
kind
of
a
service
which
will
connect
our
bot
with
the
users
by
a
different
channel
such
as
the
chat,
email,
SMS,
Skype
and
etc.
So
this
connector,
that
is
a
connector.
It
provides
store,
ste
transition
and
telemetry
mechanism
also
to
analyze
how
our
bodies
behaving
and
responding.
So
in
this
demo,
what
I
am
going
to
show
you
is
a
visual
studio
template
which
is
provided
by
Microsoft
Project
template
for
to
build
our
bot
and
then
add,
dialogues
to
that
part
and
then
publish
that
part.
B
Oh,
are
you
and
then
register
and
use
it
in
sharing
framework,
so
that
is
I'm
going
to
show
you.
So
if
you
are
new
to
part
framework,
this
is
the
link
you
have
to
start
with,
so
you
can
download
the
project
templates
from
here
and
you
can
once
you
update
this
project
templates.
So
men
ever
you
create
a
new
import
project.
B
You
can
start
building
your
new
import
with
this
template.
Basically,
so
this
is
how
you
will
create
a
new
part
so
from
Shenzhen
yo,
its
2015
I'm,
selecting
this
template.
So
first
I
will
show
you
what
are
all
the
files
bought,
project,
template
and
things,
and
then
I
will
show
you
how
we
can
add
fields
to
the
bot
and
then
how
we
can
validate
the
fees
at
one
time
on
the
fly
and
then
finally
process
the
request,
what
is
submitted
by
V
user.
B
So
this
is
where
you
will
describe
and
explain
about
your
bot
operations,
and
you
can
put
your
legal
and
stuff
in
this
terms
and
conditions
and
everything,
because
you
can
host
your
part
in
public
and
then
the
second
one
is
to
secure,
but
you
should
have
a
password
and
this
will
be
generated
from
the
apart
framework
website,
and
once
you
update
that
you
can
secure
the
path
if
you
publish
it
in
online
and
then
this
is
the
controller
API.
This
is
where
you
will
write
the
logic
how
to,
in
fact,
with
your
part.
B
So
what
it
is
doing
is
it
is
accepting
the
messages
from
the
user,
and
then
it
will
do
some
logic.
So
in
this
sample
the
free
template,
what
it
is
doing
is
it
is
receiving
the
message
from
the
user,
and
it
is
just
calculating
the
length
of
the
string
what
you
entered
and
it
is
responding
so
other
than
the
message
type
activity
message
type.
You
have
some
other
messages,
activity
types
also
that
you
can
handle
separately
in
your
path.
So
in
the
example
which
I
submitted
here
right,
so
what
it
is
basically
doing
is
so.
B
This
is
how
it
is
doing
so.
This
is
our
bot,
and
then
this
is
the
butt
connector
where
we
will
register
what
it
is.
It
can
be
built
in
any
technology,
and
here
we
will
integrate
our,
but
with
this
connector
and
this
connector
can
talk
to
any
channels
and
user
can
in
fact
wear
this
channel.
This
is
what
I
was
explaining
film
names
back.
Ok,
so
this
is
the
example
which
I
submitted
in
the
github.
So
what
it
is
doing
is
so
what
we
are
doing
is
here.
We
are
going
to
define
some
fields.
B
It
is
a
basic
conversation
part
so
using
Luis.
That
is,
the
language
understanding,
a
service
where
we
can
put
natural
language
questions
and
train
the
Louis
system
so
that
when
our
user
types-
and
we
can
take
that
request
and
process
that
request
so
here,
I
am
not
doing
anything
with
Luis.
So
here
I
just
created
a
basic
fields
which
is
required
to
process
the
site
request,
which
is
nothing
but
the
title,
description
and
URL
name
and
the
template
name.
B
So
once
the
conversation
is
started
right,
so
what
we
are
doing
is
we
are
building
a
dialogue
that
is
nothing
but
a
form.
So
that
is
what
I
am
showing
here.
So
in
the
form,
there
are
a
couple
of
things
involved
in
this,
so
to
build
a
form.
First,
we
need
to
define
the
fields.
So
these
are
all
the
fields
you
can
make
it
optional
mandatory.
Something
like
this.
So
once
you
have
the
fields
in
place
and
then
you
can
build
the
form
so
in
the
build
form
method.
B
This
is
just
a
very
simple
example,
so
you
can
put
any
logics
in
this
through
process
your
site
request,
so
once
it
is,
then
so
I
am
just
wrapping
up
my
request,
because
I
completed
capturing
all
the
fields,
whatever
necessary,
for
this
particular
site
like
to
start
it
and
then
I
can
process
the
request
and
then
finally
send
the
final
message
back
to
the
user
saying
I
have
created,
and
this
sake
for
you
with
this
URL.
So
this
is
how
the
logic
words.
B
So
once
you
are
done
with
the
bot
development,
you
can
publish
this
true
and,
as
you
web
app,
so
once
it
is
done,
what
do
we
need
to
do?
Is
we
just
need
to
go
to
pot
bot
framework
website
and
register
your
part?
So
whenever
you
register
a
part,
you
have
to
enter
few
details.
Like
this
name
robot
handler
and
description-
and
this
is
the
place
where
you
will
update
your
endpoint-
that
is
nothing
but
your
as
your
website,
API
URL
and
from
here
you
will
generate
the
app
ID
and
password.
B
So
this
app
ID
and
password
is
the
one
you
will
run
figure
in
the
config
file
to
secure
our
bot.
So
once
it
is
done,
your
part
is
ready,
so
here
I
have
registered
my
part,
this
is
ask
Espeon
either.
This
is
my
bot,
so
here
you
can
test
your
part
directly
and
you
can
enable
the
list
of
channels
or
where
you
want
to
enable
this
particular
part.
So
what
I
am
doing
in
this
demo
is
I
am
just
showing
the
web
chat.
That
is
nothing
but
a
iframe
using
which
we
can
enable
the
part.
B
So
something
like
this,
so
this
is
how
we
can
enable.
So
if
you
look
at
this,
this
is
how
we
can
enable
this.
This
is
your
secret
and
then
your
pardoning,
so
these
two
values
I,
am
taking
it
in
the
Shelf
and
framework
as
a
property
and
then
enabling
it.
So
once
you
have
these
details
and
again
publish
the
same
to
as
your
website,
what
we
can
do
is
we
can
connect
it
in
different
ways.
For
example,
if
you
want
to
add
it
as
a
Content
area,
third
party
can
do
something
like
this.
B
So
then
it
is
starting,
so
I
will
show
you
the
conversation
how
it
works.
So
once
you
have
the
part
and
Ed
in
the
page,
you
just
need
to
start
the
conversation
by
saying
some
message,
so
the
part
is
going
to
show
you
the
welcome
message
and
then
it
is
going
through
process,
the
fields
basically
so
yeah.
This
is
so
what
I
am
doing
is
here
I'm,
just
adding
some
secret
key
and
what
botany
as
an
input
to
process.
So
here
I
can
say
hello.
B
So
it
is
going
to
ask
you
the
list
of
fields
I
defined
in
my
part,
so
in
the
conversation
especially
so
if
you
look
at
the
status
right
so
right
now
there
is
no
of
fields
or
inputs.
I
entered
in
this,
but
so
these
are
all
the
fields.
This
part
is
expecting,
so
the
values
are
not
intact.
So
the
first
question
it
is
asking
is
to
enter
the
PLM
site
URL.
B
B
So
then
it
is
asking
me
to
select
a
template,
so
this
is
kind
of
an
option
for
us,
so
we
can
select
so
instead
of
saying
1,
we
can
also
display
the
template
name
directly
in
the
conversation.
So
here
it
is
asking
you
confirmation,
so
you
can
say
yes,
then
it
is
going
to
process
that.
So
this
is
the
confirmation
message
which
we
got
from
the
bat
and
then
currently
it
is
processing
the
request.
So
once
it
is
done,
it
is
going
through.
B
Tell
me
the
URL,
so
here
what
I
am
doing
is
in
the
in
this
particular
part
which
I
built.
So
here
the
prompt
and
other
things
which
I
define
with
this
static
questions
right
so
using
Louis
right,
you
can
define
your
intense
and
the
entities.
For
example,
you
can
build
one
bar
to
create
a
site
at
the
later
side,
update
something
in
the
side.
All
these
things
you
can
create,
as
one
part,
so
each
operation
is
kind
of
intent,
so
create
site
is
an
intent.
B
They
leak
site
is
an
intern,
so
you
can
define
all
your
intense
here
and
then
for
that
particular
intent.
What
is
the
input
entity
you
need?
That
is
something
you
can
define
in
the
fit
set
so
far,
for
example.
So
this
is
a
parent
site,
URL,
so
Prieta,
side,
parent
site
URL
is
a
mandatory.
So
you
can
here
you
can
define
your
entities
here.
So
that
way
you
can
frame
your
lowest
model
and
you
can
make
it
kind
of
a
natural
language
conversation
so
coming
back
to
this
fine
set
apart.
B
So,
as
you
can
see
here,
the
vectors
which
is
submitted
to
create
this
particular
site
got
created
and
we
got
the
URL
back
from
the
bot.
So
this
is
how
we
can
create
a
part,
so
I
asked
based
on
mention,
so
we
have
one
other
part
in
the
in
our
sample
of
parts.
So
here
it
is
not
containing
something
related
to
conversation
and
rich
cops.
So
if
you
want
to
define
your
colors
and
the
title
of
the
chat
and
all
those
things,
I
guess
this
is
this
will
be
a
very
good
start
for
you.
B
So
you
can
refer
this
particular
sample
as
well
to
customize
your
own
color,
another
thing
so
whatever
we
saw
just
now.
This
is
with
a
default
value,
color
value
and
other
things.
So
in
this
example,
the
community
member
explained
the
different
options.
What
we
can
enable
for
the
part
like
color
coding
and
another
other
things,
so
that's
all
about
the
part
framework
which
I
built
so
hope
you
liked
it.
If
you
have
any
questions,
please
feel
free
to
message
me
before.
A
B
A
And
to
be
fair,
I'm
gonna
interrupt
you
on
there.
That's
debatable.
Both
things
are
absolutely
fine,
because
I
think
in
your
case,
the
integration
with
the
bot
is
super
simple.
Yes,
you
are
just
using
an
iframe
within
this
client
side
web
part
and
you
are
passing
those
properties
whatever
I
have
ever
seen.
So
this
is
simple.
A
way
of
India.
B
So
what
I'm
doing
is
this
is
all
supported
in
the
bot
frame.
That
is
how
I
am
doing
so
here.
The
one
which
is
in
the
other
sample
is
static
line.
I
am
using
web
chat.
So
if
you
go
to
the
web
chat,
you
can
click
Edit
and
find
out
your
details.
You
can
generate
your
own
secret
keys
here
and
once
you
are
done
with
that,
you
can
embed
that
code
basically
get
bought
embed
code.
So
the
moment
when
you
click
on
this,
you
will
see
options.
B
A
Make
sense?
Oh
that's!
That's
a
really
nice
sample
and
I
like
this
implicit,
a
because
I
using
that
and
there's
some
advantages
because
you're
using
that
web
chat
with
an
iframe,
you
actually
get
all
of
the
benefits.
What
Microsoft
has
been
implemented
in
a
web?
A
web
chat.
The
artist
sample,
doesn't
actually
understand
as
an
example
that
some
of
the
template
selection,
which
you
had
as
juice
this
tree
I
say.
Is
it
the
dialogue?
I
can't
remember
the
right
terminology
right
now,
so
that
particular
sample
doesn't
understand
that.
Yet
so
it's
debatable.
A
B
Yes,
so
one
other
thing,
what
we
can
do
is
suppose
in
the
simple
conversation
about
what
I
built
is
straightforward
question
right,
for
example,
when
you
create
a
sub
site,
you
can
put
in
a
question
like
if
you
want
to
inherit
from
the
inside.
So
if
you
say
no,
you
have
to
get
the
group
names
for
that
particular
sub
site
right,
so
you
can
use
a
cascading
form
inside
so
these
features
we
can
add
it
as
per
our
business
logic,
but
definitely
these
are
all
possible
with
the
pod
framework.
So.
A
And
let's
say
even
the
slightly
more
interesting
scenario
would
be
the
one
where
we
actually
provision
site
collections,
but
I
think
the
the
sample
itself
is
showing
how
to
make
that
happen
and
how
to
make
the
discussion
happen,
how
to
collect
the
things
then
provision
and
a
site
collection
that
would
be
just
and
using
an
app
only
tokens,
and
all
of
that,
so
that's
a
traditional
complexity
on
the
sample,
so
really
great
implementation,
so
nice
to
see
this
one
in
practice
as
well
cool.
Thank
you,
sir.
A
A
This
was
around
the
own
premises.
How
to
do
modern
web
stack
development
in
on-premises,
and
this
is
a
relatively
rough
status
at
this
point,
but
because
we
showed
this
one
in
the
European
SharePoint
conference
keynote,
we
wanted
to
actually
share
the
code
as
a
starting
point
and
yes,
we
can
further
enhance
this
one
in
the
future
as
well.
Can
you
guys
see
what
I'm
sharing
just
double
checking
got?
My
screen
is
fine,
yes,
excellent
thanks
Ralph,
so
the
sample
itself
is
available
from
the
underneath.
A
The
ship,
github,
SharePoint,
SPF
samples,
and
in
here
we
have
few
samples.
We
have
the
web
few
examples
for
nodejs
and
asp.net,
and
the
reaction
recap,
because
this
is
not
a
SPF
fix.
This
is
not
a
SharePoint
framework
implementation.
So
that's
why
it's
actually
in
the
SPF
samples-
and
this
one
is
actually
pretty
clearly
explaining.
This
is
super
simple
sample,
but
it's
super
simple
to
actually
set
up
as
well,
so
nothing.
What
you
need
to
do
is
clone
the
repo
move
to
the
sample,
folder
run
and
being
installed.
A
If
you
have
installed
the
NPM
long-term
version
and
then
run
cop
sir
and
then
you're
good
to
go,
it's
gonna
actually,
I'm
gonna
show
what
happens
practice
with
that
one,
so
I.
What
I've
done
here
just
to
show
how
to
get
started
so
I've
cloned
that
repo
I'm
gonna,
go
to
the
samples
folder
I'm
gonna
go
to
react,
generic
app,
folder
and
then
something
which
this
is
pretty
awkward,
something
what
I
learned
pretty
recently
I
can
actually
start
PowerShell
from
the
Windows
Explorer.
A
Just
by
writing
PowerShell
there,
then
it
will
open
on
that
one
in
the
right.
Folder
I
should
have
known
about
this
one
way
before,
but
I
wasn't
aware
of
that.
So
let
me
slightly
adjust
the
size
of
that
one
thanks
Ross.
So
so
in
here
we
can
say
that
we
are
in
sample
folder
and
then
what
I've
done
is
that
I've
executed
I've
installed
the
NPM
and
no
chests
at
the
basic
noches
setup,
which
is
available
for
noches
work
and
then,
after
that,
I'm
able
to
start
this
one
to
work
or
get
off.
A
The
demand
assess
on
my
machine
running
the
MP
Minister
I'm
not
going
to
do
that.
One
right
now,
because
I've
already
done
that
immediately
when
I've
done,
that
I
would
be
able
to
run
called
serve.
But
let
me
first
open
up
a
visual
studio
code
and
then
I'm
gonna
show
how
the
sample
looks
in
practice.
So
I'm
gonna,
just
run
gulp
serve
in
the
same
way
as
we
do
in
US
and
the
client
side
in
the
SharePoint
framework.
But
again
just
super
super
clear.
This
is
not
SharePoint
framework.
A
This
is
using
the
morons
web
stack
development.
Tooling,
within
the
own
premises,
without
a
SharePoint
framework,
and
even
though
it
looks
even
the
UI
looks
pretty
much
the
same
as
the
client-side
web
parts
work.
The
default
clients
are
we're,
passing
what
we
have
so
for
what
you're
seeing
here
is
essentially
my
own
premises,
hosted
and
noches
is
now
hosting
my
local
hosts
in
four
three
two
one
index.html
and
all
of
the
things.
What
we,
whatever
needed
to
get
me
started
ever
installed
using
the
npm
install
command.
A
My
actual
code
is
typescript,
so
that's
my
individual
web
part
code
or
actually,
let's
open
up
this
one.
That's
that's
the
individual
web
part
code
or
in
quotes
web
part
code.
The
implementation
works
in
a
way
that,
when
I
reference,
my
code
we're
trying
to
find
divs
which
have
this
particular
ID,
and
we,
if
we
have
a
div
on
the
page
with
that
particular
ID
we
eat.
Today
we
read
the
data
scripture
description
and
give
it
a
say,
a
property
for
the
react
component.
A
So
this
way
I
can
actually
parameter
size,
the
instance
and
that's
the
reason
why
I
was
saying
in
quotes
two
different
instances
of
a
web
part
and
they
have
a
slightly
different
parameterization
on
here
and
it
might
be
still
like
okay,
but
tell
me
what
it
means
in
SharePoint
and
I
will
come
back
on
that
one
in
a
second
now
the
implementation
itself
is
just
a
simple
react
component,
so
in
here
we
are
actually
passing
through
that.
The
description
property
now
follow
a
folder.
A
Let's
say
in
quotes
web
part
instance
or
let's
call
them
Apps,
Script
parts
or
whatever.
We
want
to
call
them
script,
parts
I,
don't
know,
and
in
here
this
is
the
actual
implementation.
So
this
is
super
simple
react
component,
which
is
then
eating
up
the
properties,
description
and
our
outputting
that
one
in
as
part
of
the
HTML.
A
So
essentially
it's
rendering
that
UI
it's
using
the
styles
from
the
UI
fabric,
so
it's
actually
giving
that
look
and
feel
which
is
pretty
close
to
clients
a
SharePoint
framework,
but
we
intentionally
switched,
for
example,
the
background
color
from
a
Pluto
teal
to
make
sure
that
it's
not
blue.
So
it's
not
actually
looking
like
Shere
Khan
framework.
A
The
problem
with
SharePoint
2010,
however,
is
that
there's
no
proper
REST
API
is
in
SharePoint,
2010,
so
or
well,
technically,
even
SharePoint
2007,
but
a
remote
API
is
with
2007
as
an
example
and
in
2010
were
highly
limited,
so
you
would
have
to
then
call
Web
Services.
Those
classic
is
a
SMX
files.
A
SMX
web
services
to
get
the
data
from
SharePoint
and
operator
comes
to
SharePoint,
but
you
could
actually
make
it
work
with
a
content.
Editor
webpart,
pointing
that
to
a
file
where
we
have
the
script
and
then
it
makes
work.
A
A
So
let
me
double
check
OOP
actually,
before
I
go
there,
so
I'm
missing
a
one
thing
and
what's
really
kind
of
a
nice
in
my
local
development
experience
in
here,
there's
my
local
development
experience.
If
I
put
this
one,
that's
my
console:
it's
working
there,
we
can
say
the
console
on
that
side
and
what
I
can
do
is
that
I
can
actually
do
modifications
on
my
layout.
A
A
There
we
go
and
we
can
actually
say
the
chance
in
the
same
way,
if
you
would
do
much
more
complex
modifications,
if
you
would
be
talking
to
an
external
system-
and
you
do
the
modifications
you
would
see
those
changes
when
I'm
doing
development
know
now,
I
need
to
actually
I
need
to
move
into
the
SharePoint.
How
do
I
get
this
one
to
work
in
the
SharePoint?
So
let's
go
to
the
SharePoint
site
and
let's
make
the
page
in
edit
mode
I.
A
This
is
out-of-the-box
team
site.
I
haven't
done
anything
more
than
get
rid
of
the
getting
started
web
part
in
here.
I'm
gonna
put
an
insert
a
web
part
and
midian
content.
Script
editor
web
part
was
the
one
which
we
introduced
in
SharePoint
2013,
which
is
involved.
It
actually
supports
scripts
natively
within
the
web
part
rather
than
content
editor
web
part
as
this
limitation.
So
you
cannot
actually
reference
scripts
directly,
but
you
can
reference
a
file
and
txt
file
within
references
script
as
an
example.
A
It's
an
awkward
story,
I
know,
but
let's
not
even
talk
about
that.
One
too
much
script
editor
web
part
edit
web
part
edit
snippet
and
then
the
question
is
what
do
I
actually
get
on
this
particular
configuration
so
in
our
sample
I'm
gonna
open
up
that
one
we
do
have
the
readme
file.
Obviously
you
can
go
to
the
github.
You
can
copy
that
from
the
visual
studio
code
or
from
the
key
top
I'm
gonna
actually
copy
that
directly
from
here,
and
it
has
been
initially
already
configured
for
that
particular
demo.
A
Let
me
scroll
down
it's
using
HTTP
and
this
particular
on-premises
deployment
is
using
HTTPS,
but
let's
actually
get
that
one
fixed
in
the
process.
Settings
done
clicking.
Ok,
there
we
go
and
one
more
time
clicking
safe
and
most
likely
if
our
processor
is
working
properly.
No,
it's
not
it's
giving
me
that.
Okay,
let
me
do
this.
I'm
gonna
actually
I
know
that
this
one
work
I
was
expecting
this
one
don't
to
happen.
So
let
me
flip
in
here
and
I'm
gonna
request
the
same
page
and
I
Internet
Explorer.
A
A
A
Now
I
need
to
actually
go
and
double-check
my
settings.
So
let's
go
one
more
time.
Edit
page
I
still
have
two
minutes
to
make
this
work.
Oh
there
we
go.
Only
secure
content
is
displayed
there.
It
is
I'll
click
show
our
content.
We
try
that's
what
I'm
looking
for
and
then
go
save
there.
We
go
after
two
minutes
of
messing
up
things
and
did
I
actually
get
that
one
to
work.
No
I
didn't
one
more
time
edit.
A
It's
not
showing
that
when
I'm
in
the
rate
mode
interesting,
never
mind,
we
have
this
one
recorded
as
a
webcast
as
well
and
together
with
Waldeck,
where
we
showed
the
whole
sim.
So
sorry
for
my
demo
problem,
but
you
can
actually
see
the
same
text
and
the
same
challenge,
and
this
is
really
because
we're
referencing
HTTP
served
content
from
our
local
box
and
we're
running
in
HTTP
in
my
SharePoint
on
on-premises
deployment,
and
that's
really
the
reason
why
we're
getting
this
small
challenge.
A
Theoretically,
in
the
same
way
a
shape
on
framework,
you
could
actually
in
Star,
install
a
dev
if
certificate
to
noches
and
you
would
be
able
to
serve
your
stuff
using
it.
It
appears
that
guidance
and
everything
else
is
not
yet
available,
we're
running
out
of
time,
so
we're
not
going
to
actually
start
debugging
this
life
on.
This
call
thanks
for
that.
A
Thanks
for
the
suggestion,
but
essentially
what
I'm
seeing
here
is
exactly
the
same
thing
and
and
I
can
still
go
to
my
web
part,
and
let's
do
a
small
modification,
let's
actually
clean
that
one,
and
do
it
just
and
should
I
welcome
to
SharePoint
2016,
because
we're
hosting
from
SharePoint
sound
we're
not
actually
getting
reflected
by
default.
So
I
need
to
do
a
refresh
on
a
page
and
after
that
we
can
actually
see
the
chains
being
reflected
on
the
UI
as
well.
A
In
a
sharepoint
online
you
would
pay
pal,
then
nothing
sharepoint
online
in
sharepoint
in
on-premises,
you
would
be
able
to
then
use
the
REST
API
in
SharePoint
2016
tape,
1
2013,
to
get
access
on
SharePoint
data
and
do
whatever
you
want
to
in
the
setup,
but
again
I'm
gonna
call
back.
You
are
running
out
of
slightly
out
of
time
in
talking
too
much,
which
is
pretty
typical.
For
me,
it's
a
start
for
the
initial
guidance
for
the
on-premises
on
premises.
A
We
do
have
a
webcasts
like
mentioned.
That
was
released
on
26th
of
December
around
this
one,
where
we
actually
talk
about
that
one,
slightly
more
detailed,
that
recording
is
available
from
the
YouTube.
So
if
you
go
to
the
after
of
Scone,
slash
blocks
and
Scrolls
write
it
down.
One
of
the
webcast
here
is
using
modern
web
stack,
which
happened
on
premises
deployments
where
we
then
have
few
slides,
and
we
talk
about
the
demo
and
the
recording
is
available
from
YouTube
as
well,
but
that's
it
for
the
demo
perspective.
A
And
switching
back
on
the
slides
never
go
good.
We
are
pretty
much
out
of
time.
Only
a
few
minutes
already
above
the
timings
I
mean
didn't
have
a
time
for
proper
Q&A.
If
you
have
any
questions,
please
use
the
community
tech
community
sections
we're
trying
to
follow
up
on
those
questions
over
there
as
well.
A
Well,
then,
use
the
issue
list
in
a
key
type,
we're
trying
to
follow
up
on
those
as
well
and
tomorrow
we
will
have
a
special
interest
group
called
for
PNP
J
scores,
chasin
client-side
object,
model
core
and
the
classic
core
and
the
PMP
powershell
and
the
PNP
provisioning
engine,
and
then
a
week
from
there
we'll
come
back.
We
have
a
special
interest
group
for
call
for
the
shipment
framework
and
the
JavaScript
development
stuff.
A
So
those
are
really
great
cause
also
to
participate
to
have
an
open
discussion,
because
typically,
these
monthly
calls
are
quite
a
lot
of
information,
and
you
hear
quite
a
lot
of
me
talking
and
explaining
stuff
as
well,
but
I
think
that's
it
a
lot
of
stuff
available.
Please
give
us
feedback
and
give
us
in
boot,
and
thank
you
for
your
contributions.
For
last
month,
let's
continue
doing
what
we're
doing,
and
this
is
seems
to
be
working
quite
well
for
the
SharePoint
community.