►
Description
In this video Vesa Juvonen (Microsoft) is showing how to get started on creating SharePoint Framework solutions for SharePoint 2019. SharePoint 2019 supports SPFx web parts and extensions created with the specific environmental switch in the Yeoman generator. This video shows the required steps on creating a solution and also what are the requirements in the SharePoint 2019 farm configuration to use SharePoint Framework solutions.
Presenter - Vesa Juvonen (Microsoft) - @vesajuvonen
See more details on the SharePoint 2019 developer capabilities from official SharePoint documentation - https://docs.microsoft.com/en-us/sharepoint/dev/general-development/sharepoint-2019-development-platform
More details on the SharePoint developer community from http://aka.ms/sppnp.
A
Hello
in
this
video
we'll
have
a
look
on
how
to
get
started
on
creating
shape
and
framework
solutions
for
SharePoint
2019.
So
if
you're
targeting
and
still
running
SharePoint
in
on-premises,
your
hopefully
running
the
ship
on
2019
version
with
the
latest
version
currently,
which
supports
also
modern
pages
and
modern
experiences
and
also
SharePoint
framework
solutions.
So
how
do
we
get
started
on
this
one
and
getting
started
on
creating
those
share?
One
frame
resolutions
on
20:19?
A
First
of
all,
you
need
to
follow
up
on
the
guidance
to
install
in
your
development
environment,
which
is
available
from
the
SharePoint
development
documentation.
You
can
actually
go
to
the
setup,
your
development
environment
from
here
or
you
can
extend
the
SharePoint
framework
from
menu
items
from
the
Left
menu
and
then
go
to
the
setup
development
environment.
So
the
steps
for
setting
up
to
your
2019
SharePoint
framework
and
development
environment
is
exactly
the
same
as
defined
within
this
and
one
and
within
this
documentation.
A
A
A
So
this
is
my
development
machine
for
SharePoint
2019,
and
this
is
really
important
thing
to
remember-
always
install
the
latest
version
of
the
SharePoint
framework
generator
and
that
we'll
make
sure
that
everything
is
fine-tuned
and
polished
and
tested
with
the
latest
possible
capabilities
for
just
share
one
2019
development
as
well.
Now,
okay,
so
now
we
have
the
everything
installed.
We
follow
up
on
the
guidance
and
set
up
the
no
chase
and
everything
else
on
this
machine.
This
is
my
development
books
and
then,
let's
actually
create
here
at
2019.
A
It's
called
it's
just
web
part
and
let's
go
to
that
web
part
folder,
which,
where
I'm
gonna
actually
scuffled
and
create
my
shape
our
framework
solution.
So,
let's
clear
up
some
space-
and
let's
do
you-
Microsoft-
has
a
SharePoint
and
that's
going
to
start.
Then
the
yeoman
generator
for
SharePoint
framework,
like
we
do
all
those
LEM
for
sharepoint
online
as
well.
Now,
there's
the
generator
it's
going
to
ask
a
set
of
questions,
which
is
quite
typically,
if
you
follow
it
up
on
any
of
our
guidance.
A
We
will
call
this
our
web
part
solution
and
a
really
really
important
question
that
may
slightly
adjust
the
size,
so
it
is
actually
adjusting
the
spacing,
probably
in
the
window.
Now.
This
is
the
key
question
when
which
is
the
environment,
a
question
so
wits
and
one
and
we're
going
to
target
our
solution
and
in
here
the
important
thing
to
select
this
shipment
2019
if
you're
only
targeted
on
a
ship
on
2019
and
forward.
A
So
any
of
these
solutions
which
we
create
for
SharePoint
2019,
will
work
and
share
the
SharePoint
2019
and
also
in
SharePoint
Online,
because
it's
a
we
have
a
backward
compatible
support
in
SharePoint
Online
as
well.
Now,
if
you
want
to
target
SharePoint
framework
2016
feature
back
to
forward,
we
do
support
SharePoint
framework
and
SharePoint
2016.
A
Only
web
parts
do
you
can
select
this
option
or
if
you
want
to
use
something
latest
and
greatest
night
to
craf,
API,
access
or
library,
components
and
so
on,
then
you're
gonna
use
SharePoint
Online
only
and
your
solution
only
works
in
a
SharePoint
Online.
So
in
this
case
the
video
was
getting
started
in
ship
on
2019.
So
let's
actually
select
that
one
and
because
we
are
in
a
SharePoint
2019,
it's
going
to
ask
the
components
of
time
before
they
actually
go
there.
A
What
we're
going
to
use
well
to
be
called
a
creation
of
the
solution.
Absolutely
and
the
web
parts
are
the
ones
which
people
are
quite
common
command
and
used
to
use
in
SharePoint.
So
what
are
we
going
to
call
our
web
fonts?
Let's
call
this
a
spade.
2019
demo
just
make
sure
that
it's
a
unique
name
description
doesn't
really
matter
on
this
case.
We
can
find
it
using
SharePoint
when
a
19
demo,
then
in
the
web,
part
picker
and
then
the
question
related
on
the
framework.
So
we
kind
of
choose
no
JavaScript
framework.
A
Technically,
you
can
absolutely
still
use
to
react.
If
you
choose
to
no
JavaScript
framework
and
then
you
adjust
the
solution
against
angular,
you
can
use
view
j/s.
You
can
use
whatever
framework
you
want
within
the
SharePoint
framework,
so
anything
is
supported
by
default.
We
all
know
support
and
provide
these
three
options.
But
again
you
can
associate
or
use
any
JavaScript
framework
with
your
solution
by
starting
no
JavaScript
framework
and
then
adjusting
the
solution
based
on
the
framework
you've
chosen
two
years
now,
that's
going
to
then
scuffle
the
solution.
This
is
going
to
take
a
while.
A
A
And
they
begin
our
solution
has
been
performed
and
let's
have
a
look
on
the
solution,
quickly
and
kind
of
a
pinpoint.
What
is
the
differences
here
as
with
selected
target
environment,
to
be
SharePoint
2019?
So
if
we
have
a
look
on
the
package
situation
file
so
looking
at
the
ant
on
this
one
and
the
updates,
so
let's
zoom
it
make
sure
to
close,
does
so
and
in
the
package
Jason,
and
we
can
actually
see
that
our
dependencies
are
using
SharePoint
22
shipment
framework.
A
One
point
four
or
one
point
four
point
one
so
slightly
depending
on
on
a
tandem
and
that's
why,
in
our
public
documentation
or
in
our
messaging,
we're
saying
that
shipment
for
nineteen
issues
in
SharePoint
framework?
One
point
one
point
four
point:
X,
because
it's
a
combination
of
some
packages
for
one
point,
four
point:
one
and
Sam
Perkins
waves
from
one
point:
four
point
zero.
Now
this
is
basically
then
the
difference
between,
let's
say
the
latest
SharePoint
Online
packages
or
solutions
versus
shipment.
A
When
a
nineteen
solution
same
applies,
if
you
select
a
solution
to
be
targeted
on
shipment
2016
in
that
yeoman
generator
a
question
and
then
these
versions
will
be
one
point
one.
But
to
keep
on
to
understand
here,
you
do
not
have
to
install
an
older
version
of
the
yeoman
generator,
because
yeoman
generator
is
aware
or
scuffles
you,
the
right
version
of
the
after
of
the
packages
as
part
of
your
solution
based
on
your
selection.
A
Now,
let's
do
a
small
modification
and
in
the
UI,
so
we
can
actually
say
that
our
web
part
is
working
properly
and
it
is
that
particular
web
part
which
were
actually
using
so
I'm
going
to
add
there
welcome
to
SharePoint,
2019
and
marker,
and
let's
save
that
one
so
now
we're
kind
of
a
good
to
go
of
getting
stuff
deployed.
So
let
me
go
in
the
command
line
and
let's
do
a
cop
bundle
under
starship.
A
This
is
preparing
or
trans
compiling
the
typescript
to
the
JavaScript,
so
it
is
ready
to
be
packaged
as
a
SharePoint
framework
solution.
That's
not
going
to
take
it
too
long,
slightly,
depending
again
on
the
environment
and
the
complexity
of
your
solution,
and
then
we're
going
to
do
call
up
I'll
package
solution
and
that's
the
ship
which
will
prepare
or
create
actual
package
SP
pkg
phone
which
were
able
to
deploy
then
to
the
ship,
1,
2019,
environment
and
use
this
weapon
now.
A
What's
really
important
to
also
understand
here
is
that
ship
1
2019
does
support
as
it
packaging.
So
if
I
go
back
in
here
in
the
packet
solution,
we
can
actually
see
that
our
include
client
side
assets
is
by
default.
True,
so
I
do
not
have
to
care
where
I'm
actually
hosting
these
JavaScript
files.
Everything
is
hosted
automatically
for
me
inside
of
the
form.
A
As
long
as
this
setting
is
true
now
you
can,
alternatively,
host
your
JavaScript
files
in
a
separate
CDN
in
your
corporate
network,
but
that
adds
additional
complexity,
which
is
not
necessarily
and
the
right
option.
So,
if
possible,
and
unless
you
have
a
valid
reasons,
we
would
recommend
to
use
the
asset
packaging
because
that
will
take
care
of
than
the
hosting
for
you.
A
So
now
we
have
this
webpart
SP
pkg
file,
actually
in
the
SharePoint
folder
here
we
can
see
it
and
it's
basically
containing
all
of
the
assets
and
I
can
send
that
to
anybody
and
it
will
work
in
their
SharePoint
2019
phone
because
it
contains
all
of
the
assets.
So
it's
not
about
city
and
configuration
there's,
no
additional
complexity
of
making
things
happen.
Now.
The
second
option
here
by
the
way,
was
the
question
in
the
yeoman
generator
which
force
them
to
be
allowed.
A
The
solution
be
to
be
deployed
automatically
to
all
of
the
sites
and
that's
the
skipped
feature
deployment
question.
We
said
true
to
that,
and
that
means
that
the
web
part
is
automatically
available
across
the
forum
when
it's
getting
deployed
on
App
Catalog.
Now
we
can
again
say
that
this
is
false,
and
that
means
that
the
solution
has
to
be
explicitly
installed
to
those
site
collections
or
sites
where
you
want
to
actually
use
that
again,
depending
on
your
solution,
design
that
might
be
an
option
for
you
now
we
can
see
the
file
actually
getting
created.
A
So
let
me
actually
open
up
data
in
file
explorer,
so
we
can
actually
see
the
file
in
here
and
we
need
to
get
it
now
deployed
to
the
SharePoint
2019.
If
on
so,
we
actually
want
to
go
to
the
forum
and
if
there's
few
things
in
the
forum
which
we
need
to
actually
configure
so
in
the
Central
Admin,
you
need
to
make
sure
that
whoever
is
the
farm
administrator.
Is
it
you
or
not
and
doesn't
really
matter?
You
need
to
make
sure
that
you
have
actually
the
apps
capabilities
and
Ivan
capabilities
enable.
A
So
you
need
to
have
an
app
catalog
existing
in
the
form,
because
that
is
the
mechanism.
How
do
we
deploy
SharePoint
framework
solutions
to
smell?
You
also
need
to
have
an
app
configurations,
a
point,
and
that
configurations
basically
mean
that
you
need
to
have
an
app
URL
defined
for
your
apps,
but
actually
technically
we're
not
using
this.
So
this
is
kind
of
a
unfortunate
leftovers
and
do
dependencies
on
the
app
adding
an
app
infrastructure
that
you
need
to
define
this
app
domain,
even
though,
which
opens
framework.
We
do
not
actually
use
that.
A
So
it's
a
configuration
of
requirement,
but
on
runtime,
as
long
as
it
has
any
value,
it
is
good
to
go,
so
you
don't
actually
need
to
think
about
the
routing
or
any
DNS
a
their
settings
or
anything
like
that
to
make
ship
on
favorite
solutions
work.
Now,
if
you
want
to
use
SharePoint
add-ins
in
your
forms,
then
definitely
you
need
to
have
follow-up
on
the
ad
domain
and
make
sure
that
that's
ruling
properly
within
their
corporate
network
now.
A
So
that's
the
app
side
of
the
things
and
then
we
need
to
make
sure
that
we
have
two
specific
service
applications
created
which
are
needed
for
adding
infrastructure
and
adding
infrastructure.
Basically,
requirements
are
the
app
and
management
service,
which
is
this
one
in
here,
which
isn't
created
by
default
in
the
form.
So
we
need
to
create
that
using
the
guidance
which
we
have
documented
for
SharePoint
guidance,
and
the
second
thing
is
the
subscription
settings
service
application
or
sorry,
the
state
service
application
server,
which
is
actually
being
used
by
the
app
infrastructure
as
well.
A
So
these
two
are
basically
required
to
make
everything
work
properly
within
your
phone
and
if
you
don't
have
those
running
in
your
phone,
the
SharePoint
framework
solutions
do
not
work
again
because
they
take
advantage
of
the
SharePoint
add
in
infrastructure.
Now,
in
my
case,
and
those
are
all
running
as
so,
I
can
actually
go
now
to
my
app
catalog
in
the
form
and
we
can
say
that
I
don't
have
applications
available
here.
So
let's
actually
install
our
web
port
and
track
and
shop
that
web
work
into
the
ham.
A
Catalog
that's
going
to
validate
a
to
pre
validation
of
the
solution,
and
then
it's
going
to
request
that
are
we
trusting
the
solution
and
do
we
want
to
make
the
solution
available
in
all
sides
of
the
organisation?
Again,
this
is
the
tenant
deployment
option
and
we're
going
to
say
yes
to
dance,
so
I
have
the
web
part
available
across
all
of
the
site,
collections,
classic
site
collections
and
classic
experience
is
a
modern
experiences
in
this
form.
A
Now
it's
important
to
realize
that
the
web
portability
works
in
classic
and
modern
experiences
and
then
the
extensions
only
work
in
the
modern
experiences.
So,
in
the
modern
pages
and
with
modern
pages
we
mean
the
modern
experience
is
with
SharePoint,
which
are
supported
by
ship
one
2019.
So
this
is
the
default
default
team
site
which
has
some
content
and
but
in
our
case
let's
actually
go
and
create
a
new
communication
aside.
So
let's
go
to
the
SharePoint
root,
Start
page
and
then
in
here
let's
create
a
site.
A
You
can
actually
see
the
modern
site,
creation,
capabilities
and
functionality
here,
I'm
going
to
choose
the
communication
site
or
a
design
for
the
communication
side.
So
let's
use
the
Showcase
and
let's
do
this
demo
and
call
that
as
a
demo
site
create
a
create
a
site
collection
and
because
these
are
more
on
site
collections,
they
are
really
fast
to
get
created.
So
creating
one
doesn't
take
actually
that
long.
So
it's
a
matter
of
few
seconds
and
the
site
collection
is
created
in
database.
A
The
site
collection
are
available
and
now
we're
able
to
actually
start
modifying
the
content.
Because
again
it's
modern
experiences,
modern
page
with
the
modern
based
experience
as
well.
Now,
in
our
case,
we
we
basically
wanted
to
test
our
web
born.
So
the
web
part
is
now
in
app
catalog,
so
it's
available
in
every
single
site,
the
existing
sites,
older
sites
and
also
on
new
sites.
So
if
I
create
a
new
page
here,
I
can,
let's
get
rid
of
the
hitter.
A
I
can
add
here
anyway,
part
which
out
of
the
box
with
port
or
I,
can
actually
search
for
ship
1
2019,
which
we
gave
it
the
name
as
the
ship
1
2019
demo
for
our
web
part
in
the
scaffolding.
So
let's
add
about
that
one
there
and
we
can
actually
see
there
is
to
ship
1
20
19
texts
which
we
modified
in
the
code.
A
So
this
one
is
now
getting
served
automatically
and
hosted
automatically
by
the
sharepoint
form
without
any
stadium
settings
without
any
additional
complexity,
and
you
can
create
or
use
this
web
part
in
a
classic
basis
or
in
modern
pages
in
any
of
the
site
collections
within
this
channel.
Within
this
form,
to
be
precise,
this
is
not
about
tenant.
Well,
technically,
a
one
form
could
be
called
as
a
one
tenant
as
well,
because
that's
the
behavior
from
that
perspective,
but
that's
it
from
this
one.
So
keep
the
key
things
to
remember.