►
Description
PnP Short Guidance video on how to configure your SharePoint Framework solution package to ensure that included components (web parts and extensions) are automatically deployed across the tenant when the solution is installed to app catalog.
A
Hello,
welcome
to
the
SharePoint
page
short
video
and
in
this
video
we'll
have
a
look
on
how
you
can
deploy
your
SharePoint
framework
with
parts
or
other
components
at
10
and
wide
based
on
new
settings
which
are
available
in
a
SharePoint
framework
solution.
So
let's
actually
jump
right
into
it.
So
I'm
going
to
use
Windows
PowerShell
at
this
time
as
my
control
application
and
let's
actually
execute
at
the
you
Microsoft
SharePoint.
A
So
we
actually
started
scaffolding
process
at
using
the
yeoman
templates
and
now,
as
long
as
you're
running
the
latest
version
of
the
Microsoft
SharePoint
framework
solution
in
yeoman
templates,
there's
some
new
option
available
as
we
go
through
this
flow.
So
let's
use
the
term
deploying
as
the
solution
name
and
so,
let's
not
really
press
ENTER
there
we're
going
to
use
the
current
folder,
and
this
is
the
new
solution
or
option
which
is
available
with
the
latest
version
of
SharePoint
framework
templates.
A
So
do
you
want
to
allow
the
tenant
admin
the
choice
of
being
able
to
deploy
the
solution
to
all
sites
immediately
without
running
any
future
deployment
or
adding
apps
in
the
sides?
The
whole
point
is
that
if
you
set
this
setting,
yes
it's
going
to
actually
set
the
default
setting
in
the
solution
package
JSON
file
accordingly
and
then
the
tenant
administrator
can
control.
Is
that
solution
you're
going
to
be
deployed
at
another
point
in
this
case
I'm
going
to
intentionally
say
no
and
we're
going
to
update
that
manually
whenever
the
scaffolding
has
been
completed.
A
So
you
can
see
the
setting
in
practice
we're
going
to
create
a
whip
part,
and
let's
call
this
tenant
wide
then
and
wide
deploy
a
web
part.
So
we
can
find
it
in
the
web
part
picker
in
the
in
the
sites
and
let's
use
the
default
description
and
no
JavaScript
framework.
Now
from
this
moment
on
this
can
take
a
while
so
a
few
minutes
or
depending
on
a
machine.
So
let's
actually
speed
up
the
video
until
the
scaffolding
is
completed.
A
So
now
the
scaffolding
is
completed
and
we
can
have
a
look
on
the
solution
if
we
start
start
up
the
Visual
Studio
code
and
let
me
move
the
Wizards
to
their
code
on
the
right
window.
So
this
is
obviously
took
the
default
SharePoint
framework
solution
structure,
but
the
key
changes
with
the
latest
version
of
SharePoint
framework,
a
human
templates
packages
and
the
templates
themselves.
It's
a
new
option
in
the
package
solution
change-
and
you
actually
saw
me
answer
false
or
no
to
that
question
so
to
skip
feature
deployment.
Is
it
to
be
false?
A
So
these
solutions
or
webparts,
which
are
immediately
available
or
the
solution
which
are
configured
and
this
setting
to
be
true.
We
do
not
apply
any
future
framework
elements
from
those
solutions
as
part
of
the
deployment,
because
these
solutions
are
not
actually
available.
If
you
go
add
an
applic
add
an
app
functionality
in
the
site.
Contents
page
these
solutions,
configured
with
the
setting,
are
automatically
deployed
across
the
tenant
and
the
web
part
or
the
extensions
are
automatically
available
within
the
site
for
web
parts.
The
functionality
is
available
immediately
in
the
web
part
picker.
A
As
you
can
see
the
web
part
from
there
for
extensions.
You
still
need
to
associate
the
client
side
component
ID,
for
example,
to
field
or
use
a
custom
action,
but
you
don't
explicitly
need
to
install
the
solution
to
the
site
to
be
able
to
get
the
functionality
to
work.
So,
let's
see
this
one
in
practice,
so
I'm
going
to
move
back
on
my
console
application
and
let's
do
called
bundle.
A
So
there
we
go
the
punting
and
let's
also
the
package
solution
command,
which
will
then
prepare
SP
k,
k,
SP,
pkg
package
for
us
in
this
case,
tenant
deploy
SP
pkg
package,
which
we
can
then
deploy.
You
can
actually
see
the
files
or
the
structure
inside
of
the
SP
pkg
eight
packets,
if
you
go
down
to
the
debug
folder
and
have
a
look
on
in
this
case
the
app
manifest.
So
we
have
a
new
setting
here
in
that
manifest,
which
is
actually
skip,
feature
deployment.
A
A
So
let
me
open
up
an
explorer,
so
we
can
actually
get
it
copied
to
our
test
tenant,
so
I'm
going
to
go
in
the
ship
on
folder
solution,
folder
and
therefore
a
tenant
deploy,
SP,
p
kg
file
and
we
want
to
actually
get
that
one
deployed
within
a
tenant.
So
here
we
go
here's
our
Testament
for
this
particular
demo
and
if
I,
if
we
actually
use
or
track
and
drop
that
file
in-
and
here
we
go,
we
actually
get
it
deployed
to
the
site.
A
And
now
this
is
a
crucial
moment
with
the
tenant
administrator
or
the
person
who
has
been
delegated
permission
to
approve,
and
these
add-ins
has
to
then
check
box
or
check
this
check
box
in
the
deployment.
So
if
this
setting
is
true
in
the
package
solution
Chasen
this
option,
it
will
be
available,
but
still
the
tenant
administrator
has
to
approve
those
webparts
to
be
automatically
across
all
of
the
sites
within
this
tenant
and
by
checking
the
check
box
and
clicking
deploy.
A
That
means
that
that
solution
is,
if
it
contains
extensions
or
webparts,
will
be
immediately
automatically
available
across
the
tenants
when
people
are
using
the
web
parts
or
the
functionalities
within
the
site,
and
let's
have
a
look
on
that
one.
Here's
another
box
team
site,
let's
create
a
new
page
in
theme,
slide
and
we're
going
to
create
a
modern
page
hope
and
let's
actually
get
in
here.
That
was
actually
a
classic
page.
A
Let's
get
in
here
and
create
a
new
page,
maybe
get
let's
go
to
the
site
pages
folder,
so
double-checking
that
we're
creating
the
right
format
of
the
page
or
here
we
go
and
I
can
click
from
here.
The
functionality
over
the
works
across
the
modern
and
classic
sites,
but
I
can
create
a
wiki
page
web
page
or
site
page
and
if
I
create
a
site
page,
that's
actually
to
modern
experiences.
So
here
we
go
and
I
can
actually
go
to
the
web
park.
Picker
and
I
can
see
our
custom
tenon.
A
Why
deploy
web
part
to
be
available
in
the
picker,
even
though
I
haven't
explicitly
installed
anything
on
the
site
and
that's
because
of
all
of
this,
this
setting
in
the
package
solution
and
also
to
tenant
administrator
by
checking
the
checkbox.
Obviously
the
same
thing
applies
to
the
modern
modern
groups
I'm
on
a
team
science
or
whatever.
We
want
to
call
this
the
croup
sites.
So,
let's
create
a
new
page
and
in
here,
if
we
create
a
new
page,
we
can
actually
see
the
web
part
to
be
immediately
available
from
the
web.
A
Part
picker,
like
mentioned
extensions,
are
slightly
different
case
because
for
extensions
we
do
not
have
a
UI
to
make
them
visible
or
to
be
selected
in
the
in
the
site
or
site
collection
level.
So
for
extensions,
you
still
need
to
apply
the
client
side
component.
Id,
for
example,
for
user
custom
action
or
for
the
field
field
in
a
list
or
field
in
a
site,
collection
level,
but
you
do
not
have
to
explicitly
deploy
the
solution
package
to
every
single
site,
collection
or
every
single
site,
and
that's
it.