►
Description
Office hours recording from 24th of August 2016. Topics covered.
- Office 365 Technical Network shut down in Yammer and move to http://network.office.com - http://aka.ms/SharePointPnPCommunity
- Sandbox solution transformation assets - analyses tooling and existing guidance
- SharePoint Framework - Existing, upcoming and needed tutorials
- Open Q&A on different topics
If you are interested on joining on the bi-weekly office hours, please use the following link for downloading recurrent invite - http://aka.ms/officedevpnpofficehours.
A
A
Bmp
is
owned
by
the
ship
and
engineering
nowadays,
so
we
used
to
be
an
individual
initiative,
but
nowadays
it's
owned
by
the
SharePoint
engineering,
because
shipment
engineering
ones
to
use
the
BMPs
the
tool
and
a
channel
to
provide
guidance
samples,
community
actions
for
all
of
the
new
stuff
within
SharePoint.
So
that's
for
existing
SharePoint
customizations,
including
on-premises,
even
farm
solutions.
We
can
talk
about
those
if
you
have
any
questions,
but
obviously
the
main
topics
for
the
future
is
mainly
the
SharePoint
framework
and
also
the
shipment
add-ins.
A
And
since
we
talked
about
sharepoint
online,
also,
there's
this
dependencies
or
references
too
much
soft
graph
and
all
of
the
other
office
365
a
pianist.
We
provide
code
samples,
gardens,
documentation,
monthly
community
calls
case
studies
and
all
of
that
today's
agenda
will
never
actually
gonna
with
never
change
the
agenda
slide,
but
basically,
what
we
want
to
go
to
is
true.
What
is
the
office
hours?
What
is
the
special
interest
group
and
then
what
are
we
actually
currently
working
or
if
there's
any
any
kind
of
specific
thoughts
or
bigs?
A
What
we
want
to
talk
about
so
and
that
part
is
going
to
slightly
change
in
the
future
and
also
within
this
call,
because
SharePoint
engineering
whenever
there's
something
we
want
to
ask
from
the
community,
we
kind
of
use
the
office
hours
actually
for
that
as
well.
So
we
want
to
have
your
input
if
there's
something
what
you
want
to
say
around
sharepoint
framework
or
something
is
missing
or
you
want
to.
Actually
you
have
questions
around
some
topics.
We
can
absolutely
go
down
through
during
this
one
hour.
A
A
So
the
really
the
key
point
of
the
office
hours
is
to
open
discussions
and
feedback.
So
you
can
ask-
and
we
can
answer
if
there's
any
questions,
if
there
isn't,
if
there's
something
which
we
can
answer
will
follow
up
on
those
absolutely
later
on
as
well.
So
it's
an
opportunity
for
community
to
ask
from
ship
on
the
engineering
and
the
pnp
courting
related
on
what
should
I
do.
Why
doesn't
something
work
or
what
what's
the
best
practices
for
scenario
x,
+
1,
see
when
I'm
designing
a
solution
for
my
customer?
A
I
think
the
javascript
is
working
quite
nicely
and
we're
even
more,
let's
say
re-organizing
or
targeting
that
for
the
SharePoint
framework
and
also
the
in
general,
the
JavaScript
based
customizations
within
a
SharePoint.
So
you,
as
a
community
members,
you
can
actually
choose
how
do
you
want
to
track
and
how
they
want
to
engage
within
the
PMP
initiative?
You
can
join
on
a
monthly
calls
which
is
more
around
us
explaining
for
the
community.
What
has
happened
within
the
past
month
covering
what
samples
have
been
added?
A
What
guidance
have
been
added,
and
all
of
that
we
do
have
this
bi
weekly
office
hours,
which
is
a
one
choice
you
can
join
in.
You
can
have
a
look
on
on
slightly
different
topics.
Maybe
what
we
cover
in
a
monthly
call,
a
more
practical
discussion
and
then
also
have
that
Q&A
section
within
the
call,
because
typically
no
monthly
discussions
or
monthly
calls.
A
Moving
on
on
things,
what
options
do
I
have
help
on
the
BMP
initiative
toba,
so
you
can
use
our
samples
core
component
JavaScript
core
component
dotnet
core
component
or
our
guidance
in
msdn
or
within
the
other
other
resources,
and
you
can
provide
feedback
using
a
yemek
group.
I
should
have
actually
changed
that
and
because
the
emek
group
will
be
killed
quite
soon,
which
is
slightly
unfortunate.
They
say
a
slide
coming
up
on
that
one
in
a
second
and
and
we
will
be
moving
our
discussion
to
the
network
office.
A
Calm
and
I
do
know
how
horrible
that
is,
and
all
of
that.
But
let's
talk
about
that
one
in
a
second,
but
if
you
have
a
run
into
an
issue,
if
you
run
into
problems,
you
can
always
go
to
the
github
open
up
a
case
in
an
issue
list
and
we're
working
on
on
slightly
more
active
way
of
addressing
those
issues
and
answering
on
the
issues
in
the
future.
A
You
can
extend
or
improve
existing
samples
in
the
PMP
repos.
Quite
soon
we
will
release
also
the
SharePoint
framework
repositories
under
the
SharePoint
organization,
so
there
will
be
shape
on
framework
samples
for
people
to
consume
and
all
so
contribute
back.
So
if
you
find
a
buck,
you
can
actually
put
do
a
pull
request
and
extend
or
improve
existing
example,
also
in
a
SharePoint
framework
start
and
then
you
can
fix
issues
you
encounter
and
suddenly
the
pull
request
based
on
that,
so
that's
kind
of
at
the
thinking
around
the
PMP
initiative.
A
A
We
want
to
make
sure
that
whatever
samples
will
show
anywhere
in
ignite
or
anywhere
in
the
conference's
will
be
available
as
a
sample
for
you
to
consume
our
play
around
with
or
demonstrate
to
your
customers
or
wherever
you
want
to
do
that,
and,
and
also
we're
looking
into
exposing
a
lot
of
the
SharePoint
framework
elements
as
an
open
source
elements,
at
least
the
maturity
of
that.
So
people
are
able
to
even
contribute
on
a
shipment
framework,
at
least
theoretically,
but
that's
all
of
that
plans.
What's
going
to
happen
precisely
bit
in
the
SharePoint
frame
website.
A
I
am
NOT
going
to
commit
on
any
of
these
promises
yet
and
then
we
do
have
a
plan,
but
I
cannot
actually
communicate
that
right
now,
but
anyway,
we
in
a
ship
on
the
engineering.
We
absolutely
want
to
be
more
open
source
more
transparent,
so
that
the
community
can
truly
influence
on
the
product.
On
the
development
cycles,
you
can
actually
easily
reach
out
to
the
persons
and
and
complain
because
quite
often
quite
often,
people
tend
to
be
in
in
a
way
that
they
don't
provide
positive
feedback.
A
They
provide
negative
feedback
because,
because
you
typically
that's
usually
based
on
the
fact
that
something
in
SharePoint
on
our
tooling
is
causing
challenges,
and
we
actually
want
that
feedback.
It's
really
really
important
that
we
hear
about
that.
So
we're
able
to
fix
the
issues
it's
better
to
actually
talk
out
loud
rather
than
rather
than,
let's
say
not
share
at
the
frustration
between
others.
A
Now,
let's
go
back
on
the
on
the
today's
call
and
today's
topics,
one
thing
what
we,
what
we
kind
of
mentioned
few
times
already
in
the
PMP
monthly
cost
and
in
the
past
as
well,
the
PMP
videos
are
moving
to
YouTube.
We
have
actually
launched
this
channel
already
this
week,
so
the
latest
BMP
webcast
was
linked
or
Rick
already
from
the
YouTube.
A
So
if
you
go
a
to
the
dpa
KMS
of
sharepoint,
sorry
sharepoint,
PMP
videos
or
office,
def
B&B
videos
to
learn
to
our
Channel,
nine
sorry,
youtube
section
or
a
youtube
channel
and
we've
already
uploaded
some
of
the
let's
say
classic
videos
which
might
be
useful
or
the
latest
videos
around
the
demos
around
the
web
cast
around
the
monthly
call
us
and
all
of
that
to
the
channel
in
the
future.
For
right
now
we're
all
of
the
videos.
What
we
do
they
will
be
released.
A
All
of
them
will
be
released
in
YouTube,
so,
for
example,
this
particular
recording
will
be
going
to
the
YouTube,
but
then
webcasts
will
go
to
the
channel,
9
and
YouTube.
The
reason
why
we
have
to
go
to
the
YouTube
is
that
the
channel
9
doesn't
actually
support
playlists
and
that's
a
massive
limitation,
considering
the
fact
that
we
have
special
interest
group
meetings
every
single
week.
A
We
have
this
bi
weekly
office
hours
and
if
we
would
actually
publish
all
of
these
videos
in
the
channel
9,
the
the
one
feat
which
is
showing
the
latest
videos
would
get
really
really
messy
using
the
playlists
in
channel.
In
the
YouTube
we're
able
to
kind
of
manage
all
of
the
incoming
videos.
What
are
we
releasing?
A
It's
a
change
but
I
think
it's
a
change.
It's
not
necessarily
change
for
a
verse,
I
I
think
it's
change
for
up
better.
One
of
the
advantages
of
going
to
the
YouTube
is
also
the
old
Auto
captioning,
which
is
accessibility
of
which
is
in
the
accessibility
objectives
of
the
of
the
death
toll
of
as
calm
as
an
example,
even
though
the
youtube
capture,
Auto,
captioning,
isn't
quite
bulletproof,
and
especially
when
it's
doing
Auto
captioning
for
finglas,
so
there
seems
to
be
or
not
a
native
english-speaking
person
or
another,
an
oxford
english
speaking
person.
A
That
seems
to
be
some
issues
with
their
with
their
recognition.
A
link
to
the
for
mp4
would
be
nice.
That's
actually
a
good
point.
So
from
a
YouTube,
you
cannot
download
the
videos,
that's
actually
pretty
on
point
bill
I.
Never!
Actually,
we
I
don't
think
we
actually
considered
that
the
problem
is
that
in
the
past
we've
been
releasing
the
special
interest,
interest
group
videos
and
these
bi
weekly
office
hours,
videos
in
a
Yammer,
but
because
the
Yammer
will
be
shut
down
the
office
365
network,
not
the
whole
humor.
We
don't
have
that
option
anymore.
A
So
that's
why
we've
been
kind
of
a
heading
that
you
to
YouTube
direction,
but
we
might
need
to
actually
there's
more
feedback
on
the
on
the
getting
to
mp4
to
an
offline
consumption,
and
that's
actually
a
good
point.
Maybe
we
should
think
about
how
to
address
them,
which
kind
of
I
mentioned
already
the
PMP
moving
from
miamor
the
networked
at
office.com
as
well.
So
the
office
365
in
network,
where
the
PM
am
a
groove
has
existed
and
by
the
way
we've
been
super
successful.
A
The
only
downside
has
been
that
we've
been
the
only
successfully
recruit
in
the
in
the
office.
Resist
avoid
network
pretty
much,
and
the
bmv
group
has
been
by
far
the
most
active
developer
group
in
the
india
more
network
and
they
have
megan
made
a
decision
and
that
going
to
the
Yammer
Network
is
too
difficult
for,
let's
say
random
community
members
and
that
the
fact
that
you
need
to
register
and
not
all
of
the
information
in
the
EML
discussions
are
being
indexed
by
Google
or
Bing.
A
A
It
is
a
big
change,
especially
considering
the
fact
that
the
BM
BM
occurred
had
more
than
4,600
members
and
it
was
active.
It
was
actually
working.
The
Yama
group
members
for
helping
each
others
in
the
in
the
questions
all
the
time
and
the
transition
might
be
slightly
painful,
but
we're
hoping
that
people
are
moving
with
us
to
the
network
that
Officer
calm
and
obviously
there
are
alternative
options
in
the
in
the
community.
For
people
to
contribute,
nigel
is
asking:
when
will
we
get
our
own
area?
That's
a
good
question.
A
Now
there
is
a
a
there's,
an
ongoing
discussion
on
how
would
I
put
it?
Where
does
the
PMP
belong
kind
of
it
kind
of
made
sense
when
we
started
the
BNP
initiatives
that
we
will
have
our
own
group
in
the
end
office,
racist
5
network,
because
we
wanted
to
isolate
well
or
not
isolate
the
discussion
will
not
make
sure
that
we're
able
to
track
all
of
the
discussions
related
on
the
BMA
asset.
A
Now
that
the
the
BNP
is
owned
by
SharePoint
engineering,
it
kind
of
makes
sense
that
all
of
the
bmv
discussions
are
part
of
the
sharepoint
development
group.
Now,
there's
downside
of
that
Satan,
though,
which
is
that
the
B&B
is
much
more
than
just
chirpin
we've
been.
Essentially,
our
histories
is
by
being
office,
365
developer
patterns
and
practices,
which
means
that
we
are
overlapping
now,
just
on
SharePoint,
but
also
on
Yammer.
A
Actually,
we
do
have
a
more
customizations
and
other
office
365
customizations
there
as
well,
and
so
it
would
kind
of
make
sense
that
we
would
have
our
own
proper
group
and
our
proper.
What
are
those
scopes
are
their
scopes?
I
can't
remember
what
they
are
actually
in
a
network
beginning.
We
will
have
a
look
in
a
second
but
to
be
able
to
get
that
the
demand
for
those
groups
will
have
to
be
shown
by
the
community.
So
there's
no
point
for
me
going
and
asking
that
hey.
A
We
want
to
have
our
own
croup
and
that's
not
beneficial,
even
in
internal
question,
but
if
the
customers
and
the
community,
meaning
you
guys
who
are
participating
on
the
score,
if
you
go
and
ask
from
the
network
office
con
that
that
hey,
we
want
to
have
our
own
croup-like,
we
had
in
the
Yammer
for
being
based
off
then
that
most
likely
will
actually
happen.
So
it's
waiting
for
you
to
contribute
on
your
opinions.
A
A
I
do
agree.
Actually
that
group
would
be
better
so
and
it
is
pretty
hard
to
find
all
the
bmv
related
questions
right
now
from
the
network.
But
again,
if
you
like
that,
go
on
what
there
is
actually
idea
on
that
by
already
written
by
nigel.
So
if
other
ones
like
the
same
idea,
go
on
what
that
either
up-
and
we
will
certainly
make
sure
that
we
have
our
own
group
and
then
I'll
update
that
akms
link
when
that
happens,
because
right
now
it's
well,
we
were
chatting
this
earlier
today
with
Burt
right
now.
A
It's
kind
of
an
interesting
situation.
If
we
are
as
active
as
was
we
were
in
our
existing
BNP,
a
mcrib,
we
would
actually
fill
out
the
chevron
development
group,
which
is
not
a
bad
idea.
So
if
you
have
any
questions
in
a
similar
questions,
like
you
had
any
emer
just
go
to
the
bmv,
go
to
the
SharePoint
group
as
a
chip
on
developer
group
in
network
the
office,
calm
and
start
asking
questions,
and
hopefully
we
can
rebuild
the
community
on
that
crude.
A
Whenever
the
community
owners
this
platform
owners,
we
will
I
realize
that
there's
a
lot
of
traffic
from
B&B,
they
might
or
might
not
consider
the
fact
that
we
would
have
to
have
our
our
own
quote.
We'll
see
it's
a
there's,
advantages
and
disadvantages
on
on
both
sides.
Now
on
that,
one
I'm
quickly
going
to
actually
show
you
guys.
So
we
get
it
also
record
it
in
here
I'm
going
to
share
my
screen
in
a
second
making
sure
that
I
don't
have
anything
anything
confidential
visible
in
the
screen.
A
A
A
So
what
I've
done
here
is
that
I'm
actually
going
to
just
in
case
so,
but
put
them
I'm
going
to
do
a
sign
out,
so
you
can
see
that
it's
actually
right
now,
an
anonymous
than
the
whole,
like
mention
the
whole
benefit
out
of
the
DOE
Network
total
face.
Calm,
is
the
fact
that
I
can
go
to
the
communities
I
can
scan
through
what
communities
do
we
actually
have?
For
example,
I
can
go
to
the
SharePoint
and
inside
of
the
SharePoint.
We
have
the
share
my
developer,
and
in
here
I
can
read
the
stuff.
A
A
Sometimes
our
insert
not
too
bad.
It's
pretty
significant
change,
obviously
from
Yammer,
but
we
it's
better
to
the
right.
Now
start
adjusting
to
this
one
or
what
people
can
do,
alternatively,
and
which
is
kind
of
understandable
as
well
I
was
play
messing
around.
She
won't
stack
exchange
calm,
so
I
was
here
for
a
while
today
answering
for
some
of
the
questions.
A
The
only
downside
for
the
PM
community
PMP
community
to
go
here
is
that
this
is
getting
massive
amount
of
traffic
and
material
for
things
have
questions
and
all
of
that
stuff
gets
pretty
easily
kind
of
a
hidden.
So
actually
it's
pretty
sweet
that
we
do
not
have
massive
amount
of
traffic
in
the
network
at
office.
Calm
right
now,
which
means
that
we
can
follow
up
on
the
under
discussion
slightly
more
easily.
But
it's
it's
matter
of
opinion
again.
There's
multiple
different
channels:
there,
multiple
different
locations,
but
we'll
at
least
the
B&B.
A
Boom
boom
boom
boom,
the
Q&A
format
this
and
suitable
for
general
pnp
conversation.
My
opinion,
that's
a
good
point
from
paul.
I
would
say
that
the
network
network
at
office.com
works
much
better
on
that
kind
of
a
discussion.
So
it's
not
I
you're,
not
really
looking
for
an
answer,
you're
looking
for
opinions
or
or
additional
ideas
on
the
same
topic.
A
A
Okay,
so
you're
not
access
to
even
to
use
that
for
discussions,
there's
a
good
question
from
number
number
E
and
let's
get
back
on
that
one
within
a
few
slides.
So
that's
a
good
question
we'll
follow
up
on
that
one
in
a
second
good,
that's
about
the
network
stuff!
I'm
going
to
switch
back
on
the
slides
in
a
for
a
second
and
most
likely,
I'm,
gonna,
OOP
or
I
will
cut
back
on
the
on
the
screen
in
a
second
as
well.
A
A
Good,
so
that's
about
the
network
go
office.com
and
I
dunno
actually
I
wrote
up
relatively
long
message
in
the
Yammer
thanking
everybody
for
the
a
microbe
usage
which
has
been
super
super
successful,
like
mention,
but
we're
kind
of
a
suffering
from
the
fact
that
nobody
else
could
pull
it
off
in
the
emer
and
they
really
the
surgery.
Indexing
is
the
main
thing
it
actually
it's
it's
funny.
A
It
felt
really
bad
the
right
message,
which
is
saying:
oh,
this
is
going
to
be
shut
down
and
we're
going
to
miss
you
guys,
but
realities
of
life
only
changed
this
evident
now.
Moving
back
on
the
on
the
other
topics,
that
was
already
a
good
question
from
rush
hum,
which
one
of
those
is
here
front.
First
name
and
a
last
name.
It
doesn't
actually
matter
sample
solutions,
so
we
do
have
the
sandbox
Luis
sandbox
solutions.
A
The
code
behind
has
been
already
plucked
within
a
sharepoint
online
and
let's
be
clear
on
the
on
the
messaging
on
this
one.
So
right
now
already
in
a
shipment
online,
if
you
do
have
a
code
based
sandbox
solution,
it
is
actually
executing
absolutely
fine,
but
you
are
unable
to
deploy
new
sandbox
solutions
with
code
based
customizations
or
update
any
of
the
existing
ones.
So
if
you
accidentally
go
and
deactivate
any
of
the
existing
sample
solutions,
you
cannot
reactivate
that
one
and
don't
bother
to
try
to
do
that
using
code.
A
It
doesn't
work
using
the
season
code
or
whatever
code
you
would
be
using.
So
there's
no
way
actually
going
around
that
and
there's
none
code
base.
10
/
solutions
were
deprecated
back
in
2014,
but
unfortunately
it's
pretty
clear
and
that
the
community
didn't
quite
follow
up
on
and
didn't
quite
take
it
seriously
that
it's
deprecated
deprecation
means
that
we're
no
longer
in
listening
on
that
at
some
point
it's
going
to
be
removed
and
then
I
think
it
was
13th
of
July.
A
There
was
an
announcement
that
the
the
code
base
and
acceleration
support
is
going
to
go
away
within
within
a
sharepoint
online,
now
the
official
statement
and
well
I'm
official
representative
of
the
shipment
engineering.
So
no,
no,
so
let's
not
confuse
that,
but
a
no
messaging,
we're
saying
that
there's
a
roughly
30
days
from
the
moment
when
I'm
assessed
as
announcement,
we
do
have
an
exception
process.
A
Those
will
be
then
routed
to
our
sandbox
solution,
triage,
which
is
a
daily
ended
well
detailing
daily,
meet
up
with
certain
people
me,
including
and
bert,
including
included
there,
where
we
actually
go
through
all
of
the
exception
requests
and
have
a
look
on
the
actually
inside
of
the
code
of
the
sandbox
solution.
So
we're
trying
to
figure
out
okay.
Is
this
avila
Tory
extension
request?
Is
it
a
complete,
really
complex
and
POC
solution?
A
So
we
then
give
guidance
back
on
the
on
the
support
to
actually
reroute
the
messaging
back
on
the
other
people
who
are
asking
assistance.
So
you
can
request
an
extension.
So
that's
a
good
thing
to
understand
using
the
sharepoint
online
support
channels.
We
do
have
also
a
lot
of
guidance
available
for
the
sandbox
solution
story
and
how
to
evolve
that
and
let
me
actually
jump
on
the
slides
and
walk
through
what
about
us
jump
on
the
screen
again
and
walk
to
what
we
actually
have.
A
A
Good,
the
pole
at
least
acknowledge
that.
So,
if
you
go
to
the
MSA,
if
we
go
to
our
DMP
msdn,
so
if
we
go
to
the
msdn,
where
we
have
the
solution
guidance
in
here
in
the
left
section-
and
this
is
linked
in
our
public
communications
as
well-
we
do
have
sand
box
solution,
transformation,
guidance,
and
this
was
written
two
weeks
ago,
roughly
if
I
click
that
one
it
actually
has
a
relatively
long
story
on
steps
to
perform
transformation.
A
How
to
do
the
analysis,
how
to
actually
figure
out?
What
do
you
have
within
your
tenant?
There's
two
options
on
that
I'll.
Come
back
out
that
one
that
one
in
a
second
there's
guidance
on
replacing
sample
solution,
customizations
so
depending
on
your
customization
style.
What
are
your
options
and
what
you
can
do
and
all
of
these
have
been
linking
to
an
additional
resources
and
what
does
the
removing
of
a
sandbox
code
from
your
site
actually
means?
We
also
released
quite
recently.
A
Additional
four
articles
are
related
on
wed
pots,
evans
receivers,
feature
receivers
and
infopath
that
forms
with
code
depending
on
your
sandbox
solution
content.
So
as
an
example
for
the
question
what
we
had
here-
oh
that
was
for
custom
for
claw
custom
actions.
So
I'll
come
back
on
that
one
second,
but
if
you
do
it
be
around
the
web
parts,
we
have
guidance
here
available
and
there's
a
links
to
the
additional
resources
and
I'm
just
realizing
that
we
haven't
actually
updated
this
page
to
link
to
that
example.
Solution.
Bert.
A
Do
you
mind
actually
taking
a
note
on
that?
We
need
to
update
the
link
here,
who
it
is
actually
here.
It's
the
simple
react.
Yes,
it
is
it's
that
one
which
was
which
is
actually
showing
how
to
build
a
reactor.
Script
form
based
application
using
react
with
form
validation,
web
pack
and
all
of
that
so
to
replace
existing
code
based
sandbox
solution
webparts
and
this
one
is
actually
saving
these
tickets
as
an
example
to
a
shipment
list,
it
is
using
already
kind
of
the
the
modern
way
of
doing
stuff
using
the
reactant.
A
The
reason
why
it's
doing
that
that
it's
kind
of
a
gradually
aligning
to
the
shipment
framework,
because
already
today
in
production,
you're
able
to
use
all
of
this
while
modern
frameworks
for
the
development
modern,
is
say:
well
yeah,
it's
a
debatable
world
or
a
bird.
But
this
one
is
a
relatively
nice
new
example,
which
is
explaining
how
things
are
actually
working
good
on
the
on
the
workflow
side,
so
the
user
that
you
have
custom
actions
in
the
workflow.
The
story
isn't
actually
really
that
good.
So
the
problem
with
that
one
is
that
we
don't
have.
A
Oh,
we
don't
have
anything
else
to
say
related
on
user
custom.
Workflow
actions,
then
looking
into
what
you
can
do
with
SharePoint
2013
workflows.
I
will
then
call
a
Web,
API
or
web
service
from
those
from
that
SharePoint,
2013,
workflows
and
I
do
absolutely
acknowledge,
and
we
understand
that
it's
not
an
easy
thing
to
do,
and
it's
not
a
kind
of
a
always
one
to
one
match
on
what
needs
to
be
done.
A
No
like
mentioned
the
alternative,
is
that
you
will
then
ask
for
an
extension
and
insistence
from
the
phone
shape
and
support
around
the
sample
solution
and
then
most
likely
you'll
get
some
additional
support.
Additional
guidance
on
that.
But
it's
a
good
good
point
to
notice
that
people
are
using
custom
work
for
action
still
in
a
sharepoint
2010,
very
close
in
sharepoint
online.
A
One
thing:
what
I'm
a
wanted
to
mention
in
here
is
the
the
scanning
tools
with
cysts,
and
we
can
come
back
on
the
under
discussion
in
the
sandbox
solution
in
a
second
I
just
want
to
make
sure
that
we
don't
actually
spend
the
whole
time
by
with
my
monologue.
So
we
do
have
some
additional.
We
do
have
a
powershell
script
which
can
be
used
to
understand
what
sample
solutions
do
I
actually
have
in
a
sharepoint
online.
So
this
one
is
relatively
nice.
It
is
then
outputting
the
list
of
sandbox
solutions
and
their
hash.
A
The
hashes
actually
use
difficult.
In
extension,
you
need
to
provide
the
hash
because
the
extensions
are
has
spaced,
so
you
will
get
an
extension
for
that
particular
sound
box
solution,
not
for
anybody
anything
else,
so
the
extension
is
not
based
on
a
knee
and
now
this
script
is
a
PowerShell
paste.
The
script,
however,
has
a
small
challenge.
A
It
assumes
that
the
tenant
administrator
has
permissions
for
all
of
the
site
collections
where
which
you
actually
want
to
have
access
and
which
you
want
to
scan
so
to
address
that
we
pretty
recently
released
a
additional
tool
written
by
Burt
Johnson,
a
very
own
/
Johnson
from
the
PMP
team
and
which
is
actually
code
based
tool,
which
is
using
then
additional
capabilities.
So
it's
using
the
app
only
token
to
gain
access
on
all
of
the
site
collections
within
a
tenner.
A
It
still
requires,
obviously
that
then
an
administrator
will
register
the
client
ID
and
a
secret,
but
after
that
you
will
just
configure
or
execute
the
tool
and
providing
the
client
ID
and
a
sacred
against
that
tenant,
and
you
will
get
a
full
list
of
stuff
from
the
from
from
that
particular
shape
internal
antenna.
This
tool
also
has
few
additional
advantages.
It
is
using
multi
trading,
it's
also
out
putting
stuff
in
a
more
usable
format.
A
B
A
Yes,
yes,
that's
a
good
thing
to
notice,
it's
also
scans
to
my
sides,
because
they
might
be
old.
My
sites,
which
do
have
sound
of
solutions-
and
this
also
supports
actually
on-premises
promises.
Who
does
it
mean
that
the
sample
solution
is
going
to
go
from
one
printed
premises?
No,
it
doesn't
at
least
for
now,
and
so
our
sample
solutions
are
the
code
based
sandbox
oceans,
fully
supported
in
on
premises,
and
it's
up
to
this
forum
administrator
to
decide.
Are
they
actually
use
to
none?
A
Now,
with
the
scenario
where
we
want
to
scan,
the
on-premises
is
the
typical
scenario
where
you
want
to
understand
you're
looking
into
my
creating
to
sharepoint
online,
and
you
want
to
understand
what
kind
of
customizations
I
have
in
my
own
premises,
based
on
some
solutions
and
will
those
customizations
also
work
in
a
sharepoint
online.
So,
using
this
tool,
you're
able
to
dance
country
against
the
own
premises
environment,
either
using
the
specific
account
or
again
using
the
client
ID
and
a
secret
approach
in
on-premises.
A
B
A
B
A
Good
point
fair
point,
but
anyway
that's
a
new
tool
available
in
the
PMP
and
may
be
a
small
thing
related
on
this
one,
which
relates
on
the
previous
discussion.
So
we
do
have
actually
video
explaining
and
showing
this
tool
in
the
shed
pounds
less
office,
365
def
B&B
channel
in
YouTube,
and
this
one
is
essentially
showing
all
of
the
options.
A
How
does
it
actually
work
and
all
of
that
in
practice
against
sharepoint
online
and
by
the
way,
if
I
click
from
there,
we
can
see
our
very
own
PMP
channel
in
youtube,
so
this
particular
office
hours
call
is
going
to
be
released
here
as
well.
I
think
we
have
you
office,
one
office,
our
recording
already
available
good
switch
back
on
the
slides.
A
And
Burt
is
answering
on
Reshma's
question
good
Thank
You
Bert,
for
that.
So
one
thing:
what
a
big
thing!
What
has
happened
since
last
week
is
the
SharePoint
framework
as
and
the
SharePoint
framework
Developer
Preview
since
two
weeks
ago.
So
and
that's
a
big
thing,
last
Wednesday
was
advanced
that
it
was
Wednesday.
A
Yes,
it
was
Wednesday
the
last
Wednesday
we
will
finally
published
okay
well,
actually
last
Tuesday
night
PST,
we
actually
published
our
NPM
packages
first
time,
but
nobody
knew
about
it
and
then
on
Wednesday
we
went
live
an
announcement
in
the
death
toll
of
its
calm,
with
the
SharePoint
framework
preview
to
be
available
for
others
to
start
playing
with
you,
and
this
is
obviously
a
big
thing.
It's
removed.
It's
important
about
the
stove
realized
that
this
is
a
developer
preview
and
there's
a
lot
of
stuff
which
will
be
optimized.
A
lot
of
stuff
will
well.
A
There
won't
be
that
much
stuff
which
will
be
actually
changed
within
a
coding
perspective,
but
there
might
be
a
chump
change.
This
delay
in
the
even
in
the
in
the
AP
is
which
means
that
you
shouldn't
be
running
the
SharePoint
framework
client-side
web
parts
in
production
yet,
and
we
will
move
into
the
production
mode
sooner
or
later
right.
Now
we
wanted
to
actually
start
by
having
the
tutorials
and
the
NPM
packages
available,
so
the
community
can
actually
learn
that
the
understand
hey.
This
is
how
it
works.
A
A
So
the
tutorials
and
documentation
will
be
officially
released
or
relocated,
dude,
ft.com
/
SharePoint
quite
soon,
and
there
will
be
then
additional
tutorials
additional
documentation
and
all
of
that
within
inside
of
modesto
fest
com
it
was
lifted
off
that
comes
last,
SharePoint
will
be
then
the
address
you
can
steer
and
at
that
point
you
can
actually
submit
contributions,
also
do
the
tutorials.
So
if
there's
any
challenges
or
issues
or
box
or
typos
in
those
tutorials,
you
can
always
do
a
pull
request.
A
So
that's
designed
by
me
just
to
have
a
shipment
framework
logo,
whatever
the
SX
actually
means
few
things
what
I
wanted
to
kind
of
go
through,
and
this
is
something
what
I
asked
already
in
the
Yammer
and
in
network,
that
of
calm
and
in
Facebook
and
Twitter,
and
in
all
social
media
channels,
and
at
least
in
a
networked
at
office.com.
We
actually
got
a
few
insights
on
this
one.
The
really
the
key
question
is:
what
do
you
guys
need
so
right
now
that
the
existing
tutorials
are
more
around
hey?
This
is
how
you
get
started.
A
So
this
is
how
you
actually
do
a
scaffolding
of
a
project.
This
is
how
you
start
talking
the
sharepoint.
This
is
how
I
deploy-
and
this
is
say,
a
follow-up
list
on
the
plan
tutorials,
so
we'll
work
on
the
on
the.
How
to
work
with
external
scripts?
We
need
to
get
the
story
slightly
better
clarified,
reconfigured
entries
in
with
web
parts,
because
we
do
have
a
kind
of
a
similar
experience
as
dot
webpart
files
in
the
new
client-side
web
parts
as
well.
A
They're
able
to
have
multiple
configurations
of
the
same
web
part
in
a
SharePoint
framework,
multiple
web
parts
in
one
projects,
there's
an
issue
for
that
one
right
now
there
will
be
an
update
so
obviously
coming
up
creating
custom
property,
pain,
control,
social,
app
permissions.
How
to
prepare
production
builds
my
creating
existing
JavaScript
apps
to
ship
and
framework
some
of
the
stuff.
A
Well,
if
it's
a
simple
sample,
that's
actually
really
good,
because
simple
samples
are
create
stepping
stones
to
understand.
How
would
I
then
evolve
that
sample
to
a
production,
simple
sample
doesn't
mean
that
it's
it
wouldn't
be
production
ready.
So
as
an
example
will
absolutely
pinpoint
on
the
samples
that
width
of
them
are
in
quotes,
production
ready
because
simple
crew
operations
which
react
probably
won't
pay
production
ready
or
why
not
and
the
UI
might
be
rough,
but
it's
actually
showing
how
to
cry.
A
Aight
read,
update
and
delete
items
in
a
sharepoint
list
using
react
or
using
javascript
or,
let's
say,
general
javascript,
not
without
react
or
using
angular,
also
trending
documents
inside
my
documents.
Sure
ad
implicit
flow
sample
is
in
a
plan
and
elevation
samples.
So
how
do
you
actually
elevate
within
the
permissions
in
a
SharePoint
framework
client-side
web
born
with
to
say
not
a
simple
story,
because
you
need
to
have
an
external
service
to
do
that,
but
it's
doable.
A
A
It's
not
a
production
ready
yet
so,
and
I
think
I
actually
had
oh
I
didn't
know
it's
all
in
the
one
slide.
So
here
we
go.
But
now
the
question
is
existing
tutorials
and
I
know
that
bill
and
Nigel
as
an
example
has
come
true.
This
and
Paul
probably
have
checked
and
out
and
a
few
others
in
a
call.
What
else
do
we
actually
need?
What's
missing?
What's
what's
bothering
you?
A
Why
didn't
you
guys
have
what's
actually
what's
we
need
to
have
x
and
y
and
z
before
we
can
start
actually
thinking
even
to
go
to
the
SharePoint,
go
to
the
production
with
the
stuff?
Well,
surely
we
need
to
clean
some
of
the
stuff.
We
need
to
reduce
the
development
overhead.
We
need
to
reduce
the
NPM
dependencies.
The
folder
slices
are
pretty
big
with
the
SharePoint
framework,
all
that
absolutely
no,
but
what
kind
of
guidance
and
samples
what
kind
of
samples
what's
a
great
sample,
how
to
do
stuff
solutions
to
common
problems?
B
Right
so
I
think
what
a
lot
of
the
negative
comments
have
come
about
the
size
of
the
amount
of
code
that
the
time
it
takes
to
download
all
these
dependencies
and
then
makes
an
enormous
file,
structure,
trip
and
I.
Think
one
of
the
problems
was
that
if
you
install
node
by
default,
you
get
node
package
manager,
NPM
and
that's
version
2,
and
you
really
need
to
be
using
version.
B
3
of
the
node
package
manager,
I
think
the
prop
mentation
has
been
updated
now,
but
sir,
that
was
creating
those
very
deep
path:
framework
paths
to
the
node
modules
and
creating
huge
directory
structures,
which
you
know
a
lot
of
people
recoiled
with
horror.
From
now,
once
you
get
NPM
version,
3
installed,
it
works
a
lot
better.
It's
still
quite
big,
so
I
mean
I,
think
that's
still
a
valid
complaint
about
it
and
that's
true.
The.
A
Other
but
bill
I
would
still
say
that
the
fact
that
do
we
have
150
mix
of
dependencies
or
200
or
300
it
doesn't
actually
what's
the
difference
on
the
fact
that
ok,
if
I
built
a
web
part,
it
won't
have
done
it's
only
the
development
time
experience
and
what
we're
right
now
looking
and
what
I'm
at
least
looking
to
certainly
will
fix
the
dependency,
and
we
want
to
target
that
folder
structure
to
be
minimized.
But
what
else
do
we
need?
A
B
A
B
Yeah,
so
that's
that's
path,
have
something
you
can
communicate
in
the
documentation
and
point
people.
I
don't
know
that
some
of
the
node
npm
documentation,
but
there
yeah
that's
a
that
was
a
critical
thing
was
the.
If
you
get
the
wrong
version,
the
node
package
manager,
you
will
get
certain
messages
and
warnings
and
things.
So
that's
all
I
meant
about
solutions
to
common
problems
will
be
a
good
thing
like
a
Q&A
section
in
the
documentation
say
if
you
see
this
problem
like
the
huge
directory,
this
is
probably
what's
happened
as
we
discover
these
things.
A
But
all
birth-
it
that's
kind
of
a
tooling
part.
So
let's
imagine
that
the
tooling
part
is
done.
Then
the
question
is
okay.
What
do
you
now
need
to
be
able
to
start
implementing
customizations
on
the
bus
to
share
our
client-side
web
part?
What
kind
of
tutorials
and
samples
would
be
useful,
maybe
on
top
of
what
we're
seeing
within
the
slides
or
if
you
would
have
all
of
this
stuff,
what
we're
mentioning?
What
I'm
mentioning
on
the
slide?
Would
people
be
like?
Oh,
this
is
exactly
what
I'm
need.
B
B
Fill
the
Billy
the
airspace
yeah,
yes,
I,
think
perhaps
em
examples
will
be
useful
that
are
of
practical
applications
of
this,
so
I'm,
trying
now
to
think
of
practical
web
parts
that
we
would
have
built
in
the
past
using
the
web
part
framework
in
asp
net
yeah
and
I'm
building
the
equivalence
using
this
new
model.
I
think
that
will
be
quite
useful,
particularly
if
we
can
show
that
or
show
developers
that
this
is.
B
You
know
you
can
only
need
a
few
lines
of
code
and
there's
just
one
other
point
actually
is
there
are
there's
a
tendency
to
in
trying
to
introduce
everything
into
these,
so
here
we
keep
things
as
simple
as
possible,
and
that
might
you
know
I
don't
want
to
go
on
about
the
dependencies,
but,
for
example,
if
you
look
in
the
webpart
code,
you'll
see
there's
like
an
indirection
to
where
it
gets
the
CSS
classes,
and
I
think
you've
gotta
think
you
know.
Is
that
strictly
necessary
for
the
start?
B
Maybe
that's
something
you
can
add
later
as
a
an
embellishment
of
the
starter
code,
so
they
just
got
a
single
javascript
part.
Sorry
typescript
file
to
work
with,
and
also
there's
there's
code
in
there
to
deal
with
internationalization.
But
you
know
a
lot
of
users.
Don't
have
that
problem
to
solve
when
they're
not
interested
in
it.
So
do
we
want
to
carry
the
ability
to
handle
internationalisation
in
every
single
sample
one
or
do
is
start
with
a
simpler
sample
and
then
there's
another
example
how
to
do
this
if
you've
got
multi-link.
A
B
A
But
you're
absolutely
correct
on
that,
and
actually
the
yeoman
template
is
one
of
those
things
which
will
be
well
at
least
right.
Now
it
seems
to
be
that
it
will
be
absolutely
open
sourced
within
the
under
the
sharepoint
repo.
So
that's
one
of
the
things
which
people
can
actually
contribute
back
and
say:
hey,
that's
wrong.
I
want
to
have
this
and
you
can
even
submit
a
pull
requests
on
their
own
the
process,
because
there's
no
point
for
us
kind
of
a
not
exposing
that
as
an
open
source
implementation.
Oh
yeah,.
B
A
Absolutely
agree
on
that
and
that's
something
which
is
absolutely
well
in
the
progress.
Patrick
is
actually
on
vacation
and
holidays
this
week
and
he's
been,
unfortunately,
super
busy
with
the
sample
solution
thing
something
big
on
that
one
landed
on
his
table
on
the
from
a
coordination
perspective,
I'm,
sorry
for
smiling
and
laughing.
It's
not
a
look
lucky.
B
A
A
And
there's
a
comment
from
Nigel
that
you
mean
I
ducked
when
it
came
in
your
way,
pretty
much
C&C
while
I
was
miley
really
closely
involved,
but
now
that
I'm
in
engineering
no
longer
in
cxp
I
was
able
to
duck
tunt
and
it's
fluence
landed
on
the
on
the
different
organization.
In
my
previous
role,
it
would
have
been
me
so,
but
that's
a
different
discussion.
A
A
That's
going
to
be
yeah,
I
was
actually
just
in
pointing
on
those
suggestions
as
well.
So
sorry,
having
a
know,
various
no
worries
so
technically
right
now
in
the
classic,
you
should
be
able
to
have
multiple
client-side
web
parts
in
a
single
page
and
the
classic
pages,
as
long
as
to
deploy
your
web
parts
using
the
production
mode
so
using
the
CDN.
A
And
obviously
the
webpart
connections
was
mentioned
by
Paul
I
got
that
one
up
as
well
and
it's
it
is
in
our
extended
list
of
tutorials,
so
it
was
on
the
list
right
now.
The
webpart
connections
is
right.
Now
it's
not
natively
supported
in
SharePoint
framework
for
the
client-side
web,
but
it
is
actually
in
the
queue
to
get
natively
supported.
But
technically
you
can
do
the
connections
already
today,
using
using
your
own
code.
It's
not
an
optimal
setup,
but
hey.
We
can
absolutely
build
a
story
around
that
as
well,
but
let's
put
it
this
way.
A
If
we
would
get
have
to
do,
is
I
have
to
do
something
like
signal
or
yeah.
Well,
no,
no,
no!
Actually
in
the
client-side
web
parts
it
would
be
slightly
different.
The
signal
are
reverse
to
the
refers
more
on
the
iframe
based
client-side
web
part,
so
at
parts
and
that's
when
you
cannot
use
the
browser
or
the
page
as
your
channel
to
dock
between
the
iframes.
That's
when
you
have
to
go,
let's
say
back
back
inside
and
that's
when
you
go
to
signal
our
that's
an
old
example
which
I
think.
A
B
A
Couch
now
the
question
which
I
almost
got
there
was,
if
we
would
have
all
of
this
plus
the
things
what
was
mentioned
in
the
in
the
discussions
together
with
Bill
and
all
of
that,
but
pretty
much
it's
this
stuff.
What
we
have
on
this
slide
and
that
few
additional
things
if
we
would
have
this
by
ignite
or
by
mid-september
or
by
before
we
actually
open
up
the
SharePoint
framework
for
first
release.
Would
that
be
like
who
awesome
now
I
can
actually
start
working
on
stuff
or
would
you
be
like
hey
we're
missing?
A
Then
the
question
is
what
would
be
mission?
Obviously
there's
a
lot
of
stuff
like
ALM
testing
details
on
the
web
parts
and
all
of
that
which
we
need
to
work
next,
but
now
the
doing
immediate
question
is
more
around
okay.
How
do
we
get
people
to
write
the
client-side
web
parts
what's
actually
needed
to
help
them
to
get
started?
B
At
least
happy
okay,
well,
I
think
you
have
to
it's
like
to
take
the
temperature
of
the
of
your
audience,
and
you
can
see
the
reaction
now
that
you've
released
what
you've
released
and
you
got
to
take
a
view.
I
guess
as
to
what
point
is
the
advantage
of
making
it
properly
released?
True,
our
way,
the
disadvantage
of
people
saying
this,
this
is
missing.
That's
missing.
This
is
terrible,
and
so
on
and
I'm
not
sure
my
gut
feel
is
we're
not
there
yet
true,
no.
A
Doubt
no
doubt
we
need
to
do
additional
builds.
We
need
to
do
additional
topics,
but
again,
if
we
would
get
the
basics
and
techniques
and
the
NPM
dependency
numbers
down,
then
the
tooling,
in
a
better
Foreman
again
the
guidance
which
would
be
needed
for
you
to
get
started.
I
think
we're
pretty
well
covered
with
the
with
the
setup
what
we
have
on
the
slide
right
working
with
search,
yes,
the
world
night,
that's
kind
of
a
covered
in
my
documents
or
or
trending
documents
in
a
site.
A
B
A
Doubt-
and
we
need
to
make
sure
that
whenever
the
white
version
1.0
comes
out,
it's,
it
is
no
doubt
a
stable
enough
and
that
our
own
engineering
understands
the
impact
of
protein-protein
changes
within
the
platform
in
the
same
way
as
we
don't
actually
release
protein
breaking
changes
within
the
season.
Maybe
I
sore
wrist
ideas,
because
we
can't
it
we
would
actually
kill
our
eco
eco
system.
If
we
would
do
that.
A
Which
way
on
SharePoint
does
he
open
framework
supports
a
SharePoint
framework
is
only
for
sharepoint
online
from
now
so
not
for
on-premises.
It
will
be
landing
on
a
SharePoint
2016
during
next
year
as
part
of
the
2016
updates
and
it,
but
it
will
never
ever
land
on
the
SharePoint,
2013
good
question
and
good
clarification.
A
Well,
Never
Say
Never.
If
we,
if
maturity
of
our
own
premises,
customers
in
SharePoint
2013
would
start
yelling
and
demanding,
shape
and
framework
the
land
on
a
ship,
1
2013
or
they
would
actually
leave
Microsoft
and
move
the
competitors,
then
maybe
that
might
happen
for
Chevron
2013
as
well
pretty
far-fetched,
but
the
community
input.
Customer
input
is
really
really
the
way
how
we
design
our
following
roadmap
as
well.
So
your
input
actually
does
matter,
go
to
the
user.
Vols
go
to
the
issue
list
go
to
do
whatever
don't
complain
at
home.
A
Make
voice
make
noise
out
of
your
opinions.
They
do
matter,
make
some
noise
cool
we're
two
minutes
of
the
eye
on
top
of
the
hour.
Maybe
I
talk
too
much
actually,
when
we've
done
it
on
the
other
topics,
but
at
least
we
got
some
stuff
covered
on
the
undead.
Someone
as
well
I
know
that
you
guys
have
other
meetings
to
attend.
I
do
as
well,
so
let's
actually
closed
up
for
four
today
for
the
pnp
by
weekly
office
hours,
and
today
is
the
to
do
this
week.
We
still
have
the
JavaScript
special
interest
group
tomorrow.
A
Now
we're
going
to
talk
about
more
on
the
ship
on
framework
and
probably
going
to
touch
the
tutorial
discussion
tomorrow,
as
well,
so
for
those
who
will
join
tomorrow
and
on
the
special
interest
group
think
about
what's
needed.
Think
about
the
feedback.
I
want
to
get
that
collected
as
well,
and
then
we
will
have
the
bi-weekly
BNB
office
hours
again
in
two
weeks
and
pretty
close
to
that
we
will
actually
have
our
monthly
community
call
for
the
September.
A
Actually
it's
week
before
so
most
likely
September
must
emerge
will
happen
on
the
9th
of
sep
tember
and
the
monthly
community
call
is
on
thirteenth
of
September.
Yes,
it
is,
and
then
we
are
heading
to
the
ignite
schedules,
but
anyway,
thank
you.
Everybody
for
joining,
please
go
to
network
dude
office
come
for
input.
Questions
will
follow
up
on
those
lists.
Gemma
is
still
a
few
days
and-
and
we
so
will
absolutely
follow
up
on.