►
Description
SharePoint PnP Webcast around introduction to new community driven initiative to built Visual Studio 2015/2017 extension for SharePoint Framework. More details around the covered topics and VS extension from http://dev.office.com/blogs
A
Welcome
to
SharePoint
patterns
and
practices
webcast,
and
this
one
and
we
have
again
something
really
really
cool
to
shell.
With
the
same
open-source
community
initiative
around
a
visual
studio,
extension
for
SharePoint
framework
and
the
people
who've
been
actually
spotted,
this
work,
our
Eric
chops
and
Paul
Schieffelin
and
who
are
in
the
call
as
well.
My
name
is
Erin
and
I'm.
A
senior
program
manager
from
SharePoint
engineering
and
like
mentioned
Eric
and
Paul,
are
the
main
presenters
of
off
today.
A
B
C
Yes,
I've
been
around
quite
a
long
time
as
well
main
office
server
and
services
MVP
based
in
Chicago
do
a
lot
of
the
architecture,
work,
solution,
architecture,
work,
meaning
talk
with
the
developer
teams
about
what's
the
best
approach
to
do
things
in
the
SharePoint
office
365
platform,
and
why
should
we
do
this
versus
that?
So
a
lot
of
interaction
with
them
and
a
lot
of
questions
about
hey,
do
I
have
to
learn
all
this
new
stuff,
so
the
visual
studio
extension
fits
into
that
deck
crowd
very
well.
Absolutely.
A
C
A
Fair,
that's
right,
I
think
it's
more
official
solution,
but
anyway,
so
I'll,
let
Eric
and
Paul
through
the
presentations
and
walks
through
the
slides
and
we'll
do
this
live
demo
I'll
jump
in
every
now
and
then
for
asking
any
questions
which
pop
up
on
my
well
but
I.
Think
Eric
will
take
it
away
from
here
and
let's
see
what
this
process
is
all
about.
Right.
C
So
the
as
I
mentioned
before
it
there's
been
a
lot
of
confusion.
People
who
have
done
SharePoint
development
for
a
while
I
have
to
learn
this
new
tool
chain
and
and
the
benefits
of
the
tool
chain
are
well-documented,
and
so
you
can
learn
more
about
it.
But
again,
if
I'm
trying
to
get
my
job
done,
learning
that
new
tool
chain
can
be
helped
right.
So
so
the
idea
around
here
is
that
we
have
an
IDE.
This
Visual
Studio
does
JavaScript
development.
C
Visual
Studio
can
run
all
these
extensions,
and
so
the
idea
was
to
help
get
something
more
familiar
to
people
and
and-
and
the
idea
here
is
that,
since
the
framework
or
Visual
Studio
is
extensible,
why
not
snap
into
that
and
there's
actually
some
prior
art?
There
was
a
cks
dev
initiative
that
both
Eric
and
I
dabbled
within
and
the
SharePoint
2010
time
frame,
so
there's
really
kind
of
a
common
paradigm
here
for
what
people
are
doing
and
then
the
other
goals
that
we
wanted
to
do
here
is
write
this.
C
This
yeoman
command
line
does
have
some
a
lot
of
things
that
have
to
be
typed
a
lot
of
things.
Yet
to
get
right,
and
so
we
can
certainly
extract
that
away
and
take
care
of
that
by
providing
the
typical
wizard
interface
right
and
then,
lastly,
you
can
see
we
have.
We
have
a
goal
to
support
Visual
Studio
2015
as
well
as
2017.
So,
although
the
demos
today
are
in
2017,
we
certainly
are
targeting
the
Visual
Studio
2015
as
we
go
forward.
Yeah.
B
Part
of
what
I've
been
hearing
a
lot
of
feedback
from
enterprise
customers,
as
I'm
sure
you
have
as
well
is
is
the
framework
looks
interesting.
It's
neat
the
stuff
we
can
do
but
we're
an
enterprise
organization,
and
we
have
a
very
structured
ALM
processes
and
we
have
to
use
Visual
Studio
as
our
IDE,
and
this
needs
to
fit
in
with
our
other
SharePoint
solutions
that
we're
building
or
it
has
to
go
into
our
ms
build
process.
B
We
have
to
use
TFS,
etc,
etc,
and
the
open
source
kind
of
modern
web
development
tools
don't
fit
well
into
these
very
structure,
enterprise
environment.
It's
all
well
and
good
to
say:
well,
let's
learn
something
new
and-
and
that
is
a
great
thing,
but
when
you
have
30
or
40
or
50
devs
in
an
enterprise,
you
have
to
have
standardized
practices.
B
You
can't
people
can't
just
be
going
off
and
doing
their
own
thing
as
part
of
those
environments
and
they
spend
a
lot
of
money
and
time
and
effort
creating
these
processes
and
procedures
and
and
we
giving
them
sort
of
a
oddball
out
of
left
field
here
it
to
create
something
new
really.
Is
it
it's
not
a
comfortable
fit,
it
doesn't
work
well,
and
so
there
was
a
lot
of
friction
there
around
implementation
and
details
of
how
we
make
this
stuff
happen.
B
I
think
everybody's
excited,
or
at
least
everybody
I've
talked
to-
is
excited
about
what
we
can
do
with
the
framework
and
the
webparts
and
things
that
we
can
build
and,
and
they
don't
mind
using
the
javascript
and
HTML,
is
there
all
UI
and
client-side
driven
stuff?
It
was
just
the
tool
chain
that
was
causing
a
lot
of
difficulty
and
as
Paul
mentioned,
because
Visual
Studio
is
extensible,
there's
really
no
reason,
especially
in
2017,
with
its
improved
support
for
node.js
and
and
NPM
and
gulp,
and
all
those
web
extensions.
There's
really
no
reason.
A
Anna,
maybe
one
things
more
than
that,
one
as
well
that
obviously,
from
an
engineering
perspective,
we
do
understand
that
the
learning
curve
around
the
yeoman
templates
and
the
modern
web
stack
development
and
everything
else,
and
this
is
a
great
tool
to
ease
up
the
transition.
So
you
will
be
still
in
the
in
the
familiar
visitors
to
the
ID
as
well.
So
it's
an
option
to
use
and
are
creating
about
this
one
we'll
go
through
that
in
a
detail.
A
This
still
works,
or
it
has
been
implemented
in
a
way
that
it's
always
still
using
the
latest
and
greatest
in
a
yeoman
template
perspective,
so
you're
still
using
the
exact
same
engines
as
you
would
be
using
if
you
were
to
use
in,
for
example,
Visual
Studio
code,
so
great
crazy
implementation.
From
that
perspective,
I.
C
Another
thing
that
I
like
about
this
when
I
run
when
I
run
the
yeoman
generator
and
I
get
this
folder
and
I
get
lots
of
files.
The
node
packages,
folder
gets
very
large.
A
lot
of
those
files
are
to
support
the
development
environment
locally
on
your
machine,
the
actual
code
that
you
need
to
focus
on
to
deliver
your
solution
is
a
subset
of
that
and
by
hiding
that
into
this
video
Explorer,
it
kind
of
focuses
on
what
I
need
not
so
much
on
the
infrastructure.
C
C
One
thing
that
we
we
didn't
necessarily
talk
to
yet
is
the
bottom
bullet
point
here
and
that
as
I'm
as
I'm
writing
code,
it's
common
that
I'm
going
to
be
doing
JavaScript
and
SharePoint
I
need
to
call
to
some
service
so
that
service
might
be
part
of
the
same
application,
I'm
building
and
so
I
might
want
to
have
the
SharePoint
web
part
in
the
same
visual
studio
solution.
As
my
web
service
that
I'm
calling
so
they're
kind
of
enables
that
happens
well,.
B
One
of
the
big
use
cases
that
I'm
seeing
is
as
your
deployment
Visual
Studio,
has
the
very
best
as
your
integration
tools
that
are
out
there
and
it's
it's
super
simple
to
right-click
and
deploy
new
as
your
web
app.
You
can
even
integrate
with
Azure
ad
and
and
do
all
that
good
as
your
stuff
from
within
ninety.
But
it
requires
that
you're
building,
traditional
Visual
Studio
and
Web
API
or
MVC
type
of
solutions
into
Azure.
B
For
the
most
part,
you
can
use
other
stacks
as
well,
but
that's
where
the
tool
change
fits
best
and
it's
a
struggle
when
I
sat
down
and
started
working
with
the
framework,
I
tried
to
say:
okay
I'm,
going
to
deploy
this
to
a
sure.
I
want
to
spend
this
up
on
an
on
an
azure,
endpoint,
well,
I,
couldn't
because
or
not
easily,
because
I
was
going
to
visual
studio
to
do
my
stuff,
rather
than
switching
back
over
to
vs
code.
To
do
my
stuff
for
the
framework.
B
It
was
not
a
comfortable
development
experience
for
me
and
it
definitely
wasn't
a
good
ALM
story,
because
my
code
was
in
multiple
places.
By
being
able
to
combine
that
into
a
single
solution,
framework
I
now
have
everything
where
I
need
it
to
be.
I
can
check
it
into
TFS.
I
can
manage
my
work
items
and
tasks
that
I
need
to
do
with
the
team,
and
so
it's
much
more
that
that
traditional
process
that
we
become
used
to
that
works
across
multiple
project
types.
Absolutely.
A
B
A
A
C
So
again,
we're
we
don't
want
to
say
who
has
to
use
this
or
who?
Why,
right
again,
if
you
are
more
familiar
with
the
c-sharp
asp.net
visual
studio
paradigm,
this
could
help
you
write.
If
you
have,
is
it
Eric,
as
mentioned?
If
you
deal
with
all
types
of
enterprise
ALM
process
that
you
already
have,
and
you
can
do
all
that
work
inside
Visual
Studio,
we
want
to
help
enable
you
to
develop
for
the
new
SharePoint
framework,
in
addition
to
that
right
and
again
not
trying
to
replace
anything.
B
Important
to
point
out,
I
think
that
we're
not
with
this
initiative
trying
to
replace
the
existing
tool
chain.
That's
there
we're
not
trying
to
get
you
to
use
Visual
Studio
instead
of
es
code
or
not
use
the
yeoman
generators
from
the
command
line.
You
can
continue
to
do
so.
This
is
simply
an
extensible
layer
that,
if
you're
more
comfortable
with
Visual
Studio
is
an
ID
as
I
am
as
I
know.
A
lot
of
other
people
are,
if
you
need
those
additional
components
we
allow
this
to
plug
into
it.
B
Once
you've
generated
one
of
these
projects,
you
can
still
jump
in
with
vs
code.
If
you
want
and
modify
the
project,
you
can
still
run
from
your
command
line.
It's
not
preventing
you
from
doing
any
of
those
things.
That's
interchangeable
with
that,
and
it's
really
just
designed
for
people
who,
like
living
in
the
heavy
weight,
client-side
IDE
for
all
the
other
things
that
Visual
Studio,
brings
you
that
you're
comfortable
with
or
for
those
who
must
do,
because,
as
part
of
their
prescribed,
toolchain
yeah.
A
Absolutely
and
personally,
that's
really
the
key
reason
why
I
really
like
this
we're
architecture
of
this
extension,
because
it's
not
a
yes
or
no,
it's
like.
If
you
want
to
use
it,
it's
going
to
help
you.
If
you
don't
want
to
use
it,
that's
fine
as
well,
because,
although
in
larger
projects,
there
are
different
kind
of
people
and
developers
as
well,
some
might
feel
that
they
want
to
use
this.
Some
might
feel
that
they
want
to
use
Visual
Studio
code
or
whatever
alternative
editors,
so
absolutely
make
sense.
B
B
The
way
that
we
built
it
was
specifically
designed
to
run
in
conjunction
with
the
existing
toolset
Visual
Studio
has
an
extensive
ility
framework
in
the
term
of
physics
that
allows
you
to
create
custom
project
types
and
item
templates
and
there's
a
whole
managed
extensibility
framework
for
those
who
remember
theirs.
Back
in
the
SharePoint
2010
days,
you
could
extend
the
out-of-the-box
development
tool
chain
for
doing
f5
deployment
with
your
own
custom
types
and
whatnot.
B
That
was
also
developed
as
physics
solutions,
so
we've
taken
the
existing
Visual
Studio
extensibility
framework
and
extended
it
into
the
SharePoint
framework
projects
when
you
run
a
framework
project
from
the
command
line.
The
first
thing
that
you
get
in
the
yeoman
generator
is
a
set
of
questions
about
how
you
want
your
project
to
be
built.
What
should
be
the
solution?
Name?
What
should
you
name
the
components?
What
type
of
framework
are
you
using,
etc?
B
We've
added
a
Windows
forms
layer
to
that,
so
that
you
can
see
those
options
in
a
visual
interface
and
also
to
also
give
you
some
additional
capabilities
that
we'll
show
you
in
the
demo,
such
as
adding
common
strings
like
skip
install
for
do
rapid
project
scaffolding
whatnot.
This
does
not
in
any
way
replace
the
yeoman
generator
it
doesn't
it's
not
a
customized
or
proprietary
method
of
building
out
the
framework
we
didn't
take.
What
was
in
the
generator
or
break
it
apart
and
do
something
different
behind
the
scenes?
B
Still,
the
Gilman
generator
running,
in
fact,
there's
a
switch
option
in
the
forum
where
you
can
run
the
command
line
and
see
it
actually
running
in
the
command
window
space,
if
you
like
change
the
command
string
and
all
that,
so
we've
tried
to
facilitate.
Whichever
way
you
would
like
to
use
that,
if
you're
more
custom,
if
you're
more
comfortable,
seeing
the
command
line
run
and
watching
it
draw
out
the
big
yeoman
and
do
that
stuff,
you
can
absolutely
do
it
inside
of
this
extension.
B
In
addition
to
the
build,
the
project
can
get
the
project
going.
We
also
wanted
to
make
it
easier
for
folks
who
are
familiar
with
the
f5
debug
experience.
To
do
that.
One
click
my
project
is
built.
Let
me
f5
it
launch
gulp
serve.
Take
you
into
your
browser
where
you
can
start
working
with
the
workbench,
and
so
we've
included
as
part
of
the
templates.
A
default
launch
command
line
for
gulp
serve.
That
will
have
the
same
experience
as
if
you
type
gulp
serve
from
the
command
line.
B
Runner
Explorer
and
launch
it
from
there
to
get
that
same
work
back
experience,
there's
a
couple
of
different
ways
that
you
can
interface
with
the
tool
on
a
go-forward
basis,
whatever
the
advantage
and
one
of
the
main
reasons
we
wanted
to
extend
what
was
happening
in
the
yeoman
generator
and
not
do
any
replacement
is
whenever
the
product
team
makes
a
change
or
introduces
a
new
feature
into
the
framework.
Shortly
thereafter,
we
will
update
the
extension
so
that
those
capabilities
will
also
come
into
visual
studio.
C
A
A
We
absolutely
will
make
sure
that
we
keep
this
up
to
date
and
we'll
make
sure
that
they
are
a
kampol
are
up
to
date
on
on
things
what's
happening
and
the
additional
people
who
are
hopefully
turning
on
this
initiative
as
well,
because
I
think,
there's
massive
potential
on
this
extension-
the
CRO
as
a
de
facto
model
and
extension
for
those
who
want
to
use
the
visitors
to
the
idea,
which
happened
framework
so
massive
massive
potential
on
the
planet.
Yeah.
B
That's
a
good
point.
Actually,
we
should
make
it
clear
that
this
is
just
an
initial
effort.
We,
this
is
just
a
basic
extension
capabilities
here
for
what
comes
out
of
the
box.
There's
a
lot
of
things
that
people
could
do
with
this.
I
can
envision
that
for
folks
who
have
really
involved
ALM
processes
that
they
may
want
to
branch
this
and
do
a
customized
version
of
it
for
their
own
needs
and
that's
a
perfectly
fine.
B
We
would
also
love
to
hear
feedback
from
people
on
how
you
know
how
they're,
using
it
and
ways
that
they're
making
it
extensible.
So
this
is
in
the
spirit
of
PNP
we're
getting
it
started
and
sort
of
pushing
the
boulder
up
the
hill
to
start
making
this
happen,
we'd
love
to
see
people
jump
in
and
keep
it
rolling.
Yep.
C
And
we
have
a
slide
on
us
later,
but
I
would
just
point
out.
I
can
envision
I
want
to
right-click
to
add
new
item
and
I
want
to
add
a
react
component,
and
so
what
kind
of
scaffolding
or
what
kind
of
boilerplate
the
react
component
can
I
use.
I
know
that
fishwife
fabric
has
got
some
samples,
so
we
would
love
to
help
the
people
who
can
grab
some
of
those
sample
components,
maybe
bundle.
It
is
an
item
template
just
to
help
bootstrap
developers
who
are
new
to
the
the
react
world
instead
of
asp.net
yep.
A
Absolutely
and
one
long-term
dimension
could
be
just
as
well
that
we're
looking
into
actually
open
sourcing
the
yeoman
templates
as
well.
So
at
that
point
the
extension
and
the
yeoman
templates
are
open,
sourced
and
coordinated
by
the
same
people,
so
that
gives
again
additional
options
for
the
future,
but
and
we'll
move
in
this
on
this
journey
step-by-step
by
enabling
these
things,
and
hopefully
sooner
or
later
we
have
a
massive
leak
rate
set
up
in
both
sides.
B
So,
let's
look
at
just
visually
what
we're
doing
in
the
tool
here.
We
want
this
to
be
a
familiar
file,
new
experience
for
visual
studio
developers,
and
you
could
certainly
do
that.
We've
added
a
new
project,
category
called
SharePoint
framework
for
the
web
part
project
and
additional
project
types
should
they
ever
be
included
in
the
yeoman
templates
will
show
up
here
as
you
step
through
the
wizard.
We
give
you
a
tabbed
control
here
where
you
can
set
up
your
inputs,
as
you
can
see
here,
the
for
standard
inputs
for
building
a
solution.
B
We've
added
a
couple
of
additional
options,
as
I
mentioned,
like
the
the
Skip
install
command
line
flag,
which
you
can
add
here
by
ticking
this
check
box,
which
you
may
or
may
not
be
familiar
with.
But
what
that
does?
Is
it
skips
running
the
NPM
install
which
really
takes
the
longest
amount
of
time
in
doing
your
new
project
setup,
because
it
has
to
download
all
of
those
onto
local
machines?
B
So
you
can
run
the
Skip
install
for
rapid
scaffolding
and
then
there's
an
Advanced
tab
that
allows
you
to
modify
the
command
string
and-
and
this
is
where
it
becomes
really
impaired-
working
with
the
native
toolset,
because
we're
calling
yo,
Microsoft
SharePoint
and
passing
in
the
parameters
to
the
command
line
for
it,
along
with
any
additional
command.
So
if
you
want
to
do
things
like
yarn,
for
example,
as
part
of
your
process,
you
could
do
skip
install
and
an
yarn
and
have
a
custom
command
string
for
whatever
it
is.
B
You
want
to
include
in
here
by
default,
it
will
run
behind
the
scenes.
You'll
just
see
the
visual
studio
project,
setup
green
bar
running
from
left
to
right
until
it's
done
or
if
you'd
like
to
actually
see
it.
As
you
would
in
the
command
line,
you
can
tick
the
show
command
window
and
generate,
and
you
can
it'll
actually
launch
the
window
for
you
to
see
it
running
in
real
time.
A
Cool,
pretty
cool
stuff,
so
I
think
the
best
way
to
actually
see
that
one.
It's
no
doubt
doing
this
in
practice
as
a
live.
We
wanted
to
have
those
screenshots
in
the
in
the
presentation
for
reusability
best
perspective
as
well,
but
I
think
it's
good.
This
flip
on
the
business
to
the
end
state
this
morning.
Practice
yes,.
B
B
So
when
you're
naming
it
here,
pay
attention
to
what
you're
naming
the
solution
name
because
as
you'll
see
on
the
next
screen,
we
add
that
in
automatically
and
grade
that
panel
out
and
that
so
it
properly
wires
up
the
whole
folder
structure
with
the
way
the
visual
studio
creates
it
on
the
system,
with
the
way
that
the
generator
works
so
I'm
just
going
to
choose
the
defaults
that
I
have
here
and
click
OK.
The
next
screen
that
you'll
see
here
is
our
wizard
box.
Here's
the
solution,
name
that
we've
applied.
We
could
pick
our
framework.
B
These
are
the
default
ones
that
are
supported
by
the
generator.
If
and
when
new
ones
get
added,
we'll
update
them
here
as
well
and
we
can
give
it
a
component
name
part
or,
let's
just
call
it
web
part.
4
and
we'll
add
a
description.
My
custom
web
part.
Now
this
is
the
option
to
run
the
skip,
install
I'm,
going
to
check
it
for
what
we're
doing
here.
So
we
can
do
a
rapid
scaffolding,
because
the
fold
thing
takes
about
10
minutes
or
so
for
it
to
run
and
download
everything
to
create
our
project.
B
So
we're
just
going
to
do
a
basic
scaffolding
and,
as
I
mentioned,
that
all
that
does
is
skip
the
npm
install
of
the
node
modules.
When
it's
creating
your
solution,
you
can
still
go
to
the
command
line
afterwards
run
npm
install
in
that
directory,
and
it
will
bring
down
everything
that
you
need
for
the
node
modules
looking
over
on
the
advanced.
Have
here
is
the
command-line
string
that
it's
generating,
so
you
can
see
our
solution
name,
the
framework
that
we
picked
our
component
name
and
description,
and
then
it's
automatically
added
the
Skip
install
for
us.
B
If
I
want
to
see
it
running
in
the
window,
I
can
launch
that
up
there.
What
the
project
will
do
on
the
back
end,
if
we
don't
run
that
is,
it
will
generate
a
log
file
with
everything
that
happened
in
the
command
window
for
you,
so
I'm
going
to
go
ahead
and
click
generate.
So
we
can
start
scaffolding
out
our
project
and
without.
C
Sorry,
Erik
I
would
append
for
those
who
are
new
to
this
right,
the
the
NPM,
if
I
skipped
install
now
when
I
press
f5,
it's
similar
to
the
new
get
package
thing
where
it'll
download
on
build,
you
can
still
get
that
command
to
run,
to
do
the
actual
downloading
at
the
bug.
Teignmouth.
If
you
want
yeah.
B
You
absolutely
can
okay,
so
it's
already
done
here.
You
can
see
our
log
file
where
it's
printed
out
the
everything
that
it
did
in
the
yeoman
generator
note.
This
is
exactly
how
it
looks
if
you
ran
it
from
the
command
line,
so
it's
created
everything
for
us
in
our
project.
Here
is
my
web
part
over
under
my
source
directory
and
if
I
want
to
see
the
pre
generated
code,
I
can
just
click
on
the
typescript
file,
and
here
it
is
so.
B
B
Once
you
have
this
in
place,
there's
a
couple
of
different
ways
that
you
can
work
with
it
and
get
it
to
launch
your
project
for
the
for
testing
and
in
the
workbench
I'm
going
to
skip
over
here
to
a
one
that
I've
already
created
this
one
I
ran
through
the
full,
install
and
you'll
see
the
node
modules
folder.
Is
there
now
I,
don't
have
it
included
in
the
project
and
you
typically
wouldn't,
if
you're
checking
this
into
source
control,
for
example,
you
would
make
running
the
NPM
install
part
of
your
build
process.
B
Ams
build
on
your
TFS
server
to
pull
everything
down.
There's
no
reason
to
have
those.
You
know
20,000
odd
as
part
of
your
base
solution
structure,
so
to
run
it
it's
as
simple
as
just
clicking
start,
because
in
the
configuration
for
the
project,
we
automatically
include
the
start
external
program
with
the
command-line
options
that
we
need
to
run.
Gulp
serve
so
from
here.
Just
clicking
start
will
launch
the
web
browser
and
should
take
me
directly
into
the
workbench
here.
You
can
see
it
running
the
commands.
Do
the
gulp
serve.
B
C
B
All
right,
so
there
goes
it
wires.
It
up.
I
should
get
a
certificate
error
saying
it
doesn't
trust
my
developer
certificate
here
there
goes
so
if
I
click
details
here
and
I
can
just
go
on
to
the
web
page-
there's
a
command
and
you
can
run
to
trust
that
certificate
automatically.
So
you
don't
run
into
that
every
time
and
tears
web
part
1.
I
can
added
it
into
my
workbench
and
now
I
have
it
in
my
test
environment.
B
If
I
have
any
tests
for
mock
data
or
whatnot
that
will
show
up
in
here
as
well
as
well
as
any,
if
I
have
any
options
over
here
in
the
Edit
panel,
so
all
of
that
is
working
properly
as
it
should
in
the
web.
Browser
now
there's
another
option
for
launching
this,
and
that
is
to
use
the
tasks
runner
Explorer
in
visual
studio.
So
let
me
get
rid
of
the
external
program
bit
here.
I'll
save
that
and
now
back
into
my
webparts
solution.
If
I
go
to
view,
other
windows
I
can
bring
up
the
task.
B
Runner
Explorer,
if
you're
not
familiar
with
this.
This
is
designed
specifically
for
these
type
of
modern
web
experiences
that
have
node
and
gulp
and
all
that
stuff
in
the
background,
it'll
work
with
different
packaging
managers,
but
what
it's
going
to
do
is
it's
going
to
analyze.
What's
in
our
gulp
file
to
see
what
tasks
we
have
included
and
out
of
the
box,
as
you
can
see
here
down
at
the
bottom,
we
have
the
standards,
the
build
clean,
there's,
even
one
to
deploy
to
Azure
storage.
We
come
down
here
to
gulp
serve.
B
We
can
right-click
bind
to
that
which
makes
a
slight
modification
to
our
gulp
file
for
serve
so
that
it
automatically
binds.
If
you
want
to
run
these
from
the
command
line,
I
can
also
do
a
run.
It'll
launch
the
window
here.
You
can
see
that
it's
running
the
serve
command
runs
through
the
same
set
of
operations
that
we
did
just
a
minute
ago
and
that
will
launch.
There
goes
launching
our
web
browser
and
right
into
the
workbench.
A
Really,
cool,
really
cool
stuff
and
I
really
really
like
the
way
it's
in
the
credit,
experience
and
visitors
to
the
as
well.
So
if
you
prefer
to
do
SharePoint
framework
development
using
this
kind
of
a
model,
absolutely
this
is
a
suitable
way
of
doing
that.
If
you
prefer
to
stay
in
Visual,
Studio
code
or
whatever
alternative
editors.
That's
absolutely
fine
as
well,
but
this
is
a
great
resource.
Today
is
really
improving
on
this
side
as
well.
I
think
2015,
wasn't
dis,
capable
2017
is
clearly
much
more
flexible.
From
this
perspective,.
B
B
And
that
will
allow
you
to
add
a
webpart
here.
So
here's
my
SPF
X
web
part
template
and
I
can
choose
web
part,
3,
I'll
name
it
here.
It
pops
our
generator
window
again
but
notice.
This
time
we
don't
have
as
many
options,
because
we're
not
scaffolding
up
a
full
project,
so
I
can
say
web
part
5
another
web
part,
whatever
I
want
to
call
it
here,
same
advanced
option
to
control
the
command
line
and
the
command
window
skip
install
is
missing
because
that's
not
necessary
when
you're
doing
an
item.
This
one
runs
pretty
quickly.
B
B
A
And
then,
obviously
in
the
future,
when
we're
introducing
additional
components
and
capabilities
in
SharePoint
framework
we'll
keep
on
evolving
this
extension
as
well
having
those
additional
file,
types
or
item
types
in
the
extension
as
well,
so
create
great
starting
point
for
a
create
journey
on
the
business
to
destination.
Sound.
A
C
That
would
be,
it
would
be
great
right.
So
obviously
we
have
our
first
initial
start
here.
There's
lots
of
things
that
can
be
done.
That
will
talk
about
enhancements,
that
a
product
group
might
be
considering.
I've
already
mentioned,
help
me
to
react
components.
What
else
is
there?
What
other
things
do
you
need?
C
B
C
A
C
Yes,
and
and
of
course,
you
know
spread
the
word
use
this
within
your
team
mm,
gives
your
team,
obviously
showing
them.
This
recording
is,
would
be
a
wonderful
first
start
and
we're
certainly
open
to
a
being
out
there.
I'll
be
talking
about
to
set
up
coming
conferences
and
SharePoint
Saturday.
The
round
2
will
get,
will
certainly
get
the
word
out.
We
would
look
for
for
you
to
do
that
with
us
as
well.
Well,.
B
We'd
also
like
to
thank
Besson
and
the
team
there
for
allowing
us
to
put
this
into
the
P
and
P
initiative
so
that
it
gets
wider
exposure.
You
know
that
is
a
community
effort.
I
talk
to
a
lot
of
folks
who
don't
realize
that
they
can
contribute
to
P
and
P
and
all
the
various
branches
and
things
that
are
out
there
and
available
for
that,
and
so
we
welcome
that
same
level,
participation
here
and
because
we're
working
closely
with
that
team
going
forward.
B
We
will
continue
to
update
this
for
things
coming
from
that
side,
but
we'd
also
love
to
see
contributions
from
the
community
side
on
ways
that
you're
using
this
things
that
you
can
integrate
in
as
Paul
mentioned
things
like
react,
components
and
and
various
other
plugins
that
we
can
see
adding
to
these
utilities
so
by
all
means
communicate
with
us
put
in
drop
issues
in
if
you
find
problems
update
the
wiki.
Let
us
know
where
you
find
issues
and
opportunities
for
enhancements.
We'd
love
to
hear
from
the
community.
A
Absolutely
absolutely
our
business
like
mention
this
is
a
great
great
great
start
for
the
extension,
but
it's
only
a
start.
There's
a
interesting
there's,
an
interesting
scenarios
which
we
can
already
visualize
or
vision
for
the
future.
For
this
one
and
if
there's
a
high
usage
on
this
one
and
then
then
there's
high
interest
of
evolving
that
as
well.
So
absolutely
we
absolutely
welcome
people
to
contribute
on
this
one,
but
I
think
that
sums
up
the
the
webcast.
For
this
time.
We
didn't
have
anything
extra
to
talk
about
right,
not.
A
So
then,
cue
Eric
and
poll
absolutely
on
the
on
the
create
start
on
the
extension
and
thanks
for
joining
on
the
webcast
as
well,
and
it
is
a
great
great
tool-
super
excited
on
this
one
and
so,
and
we
hopefully
see
additional
community
members
contributing
and
participating
on
this
journey.
Any
last
words
words
from
you
guys.
B
Then
I
was
kind
of
going
to
say
the
same
thing
in
a
lot
more
words
but
but
yeah.
We
I'm
really
interested
to
see
how
people
react
to
this
and
what
type
of
feedback
we
get
we'd
love
to
hear
at
all,
positive
and
negative
and
so
feel
free
to
reach
out
I.
Think
everyone
probably
knows
how
to
get
a
hold
of
us
by
now,
but
reach
out
to
myself
or
Paul
or
VESA
will
be
it
all
the
normal
conferences
and
things
where
you
would
expect
to
see
us.