►
Description
PnP Webcast around using Feature Framework client-side web parts in on-premises (SharePoint 2016 Feature Pack 2). More detailed description of the webcast is available from http://dev.office.com/blogs.
A
Welcome
to
the
SharePoint
patterns
and
practices
webcast,
and
this
time
we
can
talk
about
what
does
it
mean
that
SharePoint
framework
is
hosted
and
supported
or
can't
be
hosted
and
is
supported
in
SharePoint
2016
v2
back
to
my
name
is
Osso.
You
want
a
Senior
Program
Manager
from
SharePoint
engineering
and
with
me
today,
as
my
secondary
fellow
in
the
webcast,
is
Waldeck
we'll
do
the
quick
intros
as
well
sure.
B
A
Which
is
absolutely
a
massive
deal
now
we
wanted
to
do
this
webcast
to
explain
what
does
it
actually
mean?
So
what
is
available
in
on-premises?
What
does
it
mean
for
the
yeoman
template
selection
perspective
and
what
does
it
mean
for
development
perspective
as
well
and
we'll
do
a
quick
demo
on
the
on
the
chip,
116
feedback
platform
as
well?
Now,
let's,
actually
first
do
a
few
slides,
so
let's
actually
go
through.
What
does
it
mean
so
as
far
as
to
teach
bacterial
client-side
web
parts
are
available
in
the
plastic
experience
in
SharePoint
116?
A
So
let's
be
super
clear
on
this.
One
SharePoint
framework
is
the
development
mechanism
which
supports
client-side,
big
parts
and
also
extensions
in
SharePoint
Online,
but
as
part
of
SharePoint
2016
feedback
to
and
the
client-side
web
part.
It's
the
only
piece
which
is
enabled
within
the
on-premises
and
you
might
be
thinking,
there's
wait,
wait,
wait
Wow.
Why
is
that?
Well,
the
reality
is
that
in
on-premises
the
modern
experiences
are
not
available
there.
A
Yet
obviously
they
will
land
hopefully
and
at
some
point,
maybe
to
be
honest,
that's
not
a
topic
after
of
the
webcast,
so
on-premises
in
the
future
versions,
but
they're
not
available
in
their
own
premises.
Yet
and
SharePoint
framework
extensions
have
not
been
actually
released
when
the
feedback
to
was
actually
released.
So
the
only
capability
which
we
can
ship
for
feedback
to
is
basically
the
client-side
web
parts,
and
there
is
no
modern
experiences
in
the
ship
160
in
feedback
to
so
you'll.
A
A
There
are
certain
implications
on
the
versioning
selection
when
we
can
have
a
look
on
that
one
and
upcoming
slides,
because
obviously,
if
you
take
the
latest
and
greatest
of
the
off
the
SharePoint
framework-
and
you
want
to
target
only
sharepoint
online,
you
can
actually
take
advantage
of
really
the
latest
capabilities
and
options,
and
all
of
that
like
to
share
one
framework.
Extensions,
but
you
will
have
to
use
slightly
previous
version
of
the
of
the
sharepoint
framework
if
you
use
the
sharepoint
framework
in
on
premises.
What's
that
were
like
super
clearly
defined.
B
B
Premise
is
exactly
the
same
as
we
see
in
a
cloud
extensions
only
work
with
the
mother
in
UX
yeah
right
correct
what
an
experience
o365.
If
you
want
to
build
extension
or
yeah
extension
like
solution
for
the
classic
sites,
you
have
to
fall
back
to
things
that
you've
used
in
the
past,
like
jaya,
sling,
custom
actions
correct
for
it.
That
is
correct.
Yes,
so
because
modern
new
axe
is
not
available
on
premises,
you
have
to
keep
using
the
J's
think
and
user
actions
or
instead
the
same
way
you've
done
it
in
the
past.
A
A
So
let's
actually
get
a
have
a
look
on
that
ones
and
let's
concentrate
on
the
final
bullet,
and
this
is
essentially
a
selection
which
will
be
available
when
we're
recording
webcast
this
one
country
isn't
yet
available.
It
will
be
a
mail
call
super
super
super
soon,
so
we
can
actually
show
this
one
in
practice
as
well.
But
when
you
have
the
SharePoint
framework
generator
version
1.3
available,
we
will
ask
you
that,
are
you
targeted
only?
Are
you
targeting
your
customization
only
to
SharePoint,
Online
or
also
on
premises
and
now,
depending
on
the
selection?
A
A
A
A
There's
always
a
new
build
coming
up
on
every
single
week
and
we're
pushing
updates,
and
then
we
can
enable
new
capabilities,
and
we
don't
want
to
delay
that
for
SharePoint
Online,
but
at
the
same
time
we
can
push
all
of
the
latest
greatest
and
greatest
thing
immediately
on-premises.
So
that's
why
we
have
this
selection,
which
is
essentially
then
defining.
What
is
the
platform?
What
is
the
framework
baseline?
What
you're
using
for
your
customization
did
it
make
sense
from
public.
B
Yes,
actually
I
wanted
to
clarify
is
that
we
see
numbers
on
a
screen
right.
We
see
two
times
version
1.3
and
a
one
time
version
1.1,
yes,
I
guess.
The
first
important
thing
is
to
understand
that
the
SharePoint
framework,
yeoman
generator,
has
the
version
of
itself
and
and
as
you
can
see
here,
that's
version
1.3,
correct
and
if
you
use
that
and
choose
to
create
a
SharePoint
framework
project
for
use
with
both
SharePoint
Online
and
on-premises,
it
will
create
project
that
uses
SharePoint
framework
1.1
correct.
Yes,
in.
B
So
Shepherd
framework,
yeoman
generator
version
1.3
when
you
create
a
new
project
for
both
on-premises
and
online,
will
create
a
SharePoint
framework,
1.1
project
that
will
work
there,
because
that's
the
only
version,
as
we
record
the
webcast
supported,
on-premises
correct
that
is
correct
and
and
then,
if
you
choose
projects
for
only
online,
you
will
get
the
latest
available
bits,
meaning
SharePoint
framework
version
1.3
right.
Yes,
that
is
correct.
Yes,
ok,
so
another
thing
that
I'd
like
to
add
to
it
and
to
ask
you
about
is:
what's
the
difference?
B
A
A
So
if
you
choose
the
on-premises
in
this
selection,
you
will
get
the
SharePoint
framework
1.1,
excluding
the
tenant
scope,
deployment,
support
which
hopefully
does
make
sense
in
some
level.
Yes,
what
are
the?
What
are
the
exact
internal
API
is
and
layouts
and
classes
and
properties
methods
which
are
the
differences
between
1.1
and
1.3?
That's
that's
a
really
super
specific
question.
What
sir
yeah.
B
A
We
actually
to
get
out
there.
Let's
actually
have
a
quick
discussion,
one
more
thing:
yes,
one
more
thing,
so
one
more
thing,
with
kind
of
a
considerations:
phone
premises
before
we
do
the
live
demo
on
on
that
selection.
And
what
does
it
actually
mean?
It's
the
considerations
related
on
whether
we
host
my
customization,
because
we
need
to
remember
that
spawn
of
your
SP
pkg
packets,
as
part
of
your
shape
on
framework
solution.
Right
now
is
your
Chomsky
phones
are
not
getting
deployed
to
the
phone
or
to
the
tenant.
A
So
you
need
to
there's
two
steps.
What
you
need
need
to
do
you
deploy
the
solution,
packets,
which
is
the
SP
pkg
phone,
which
is
to
SharePoint
framework
solution,
and
then
you
need
to
host
your
JavaScript
and
well
JSON
file
somewhere
and
in
your
SP
pkg
file,
your
reference
in
that
location,
where
the
JSON
file
is
located,
and
now
in
on-premises,
you
need
to
decide
the
location
where
you
want
to
do
that
and
there's
obviously
multiple
options
around
this
one
and
we
wanted
to
quickly
kind
of
go
through
all
of
these
options.
A
The
first
logical
option
is
to
host
those
assets
in
your
local
SharePoint
and
one
absolutely
supported
absolutely
viable
option,
and
but
there
are
certain
implications
of
this
one.
So,
first
of
all
the
SharePoint
2016
mind
if
you
do
does
not
like
you
to
be
able
to
plug
adjacent
file.
The
document
library,
which
is
slightly
weird
because
dot
JSON
file
doesn't
actually
I,
don't
understand
how
a
chase
on
you
can
upload
that
javascript
file,
but
not
a
JSON
file
that
I
don't
quite
grasp
the
thinking
behind
of
that.
A
But
that's
such
the
default
settings
on
the
on
the
SharePoint
at
2016
phone.
You
can
absolutely
adjust
that
now.
This
will
give
you
the
opportunity
of
hosting
your
solution
assets
in
your
shape
on
2016.
So
none
of
your
end-users
need
to
have
access
on
internet
to
connect
or
need
to
have
internet
connectivity.
They
don't
need
to
have
access
on
downloading
those
assets
from
outside
of
your
corporate
network.
A
There's
implications,
however,
on
this
one,
because
the
flexibility
isn't
really
there,
because
if
you,
if
you
have
are
let's
say
your
cloak
or
customer,
you
have
Clos
both
endpoints
and
internal
networks
within
your
club.
All
environments
and
global,
let's
a
global
network
across
the
world,
with
an
internal
access
point,
your
assets
would
be
always
coming
from
the
share
116,
with
sister
centralized
centrally
hosted
environment,
because
in
p1
2016
we
do
not
support
global,
a
disparate
dispersed
or
divided
deployments.
A
So
that's
that's
a
centralized
all
the
requests
from
different,
let's
say
region
would
be
coming
back
to
your
SharePoint
and
that
might
obviously
not
be
the
optimal
situation.
When
the
other
hand,
operational
costs
are
pretty
low
because
hey
you're
hosting
our
stuff
from
the
SharePoint
farm,
there's
no
additional
teams
to
contact,
there's
no
additional,
let's
say
subscriptions
to
manage,
and
all
of
that
now
the
second
option,
which
is
pretty
logical,
related
if
kind
of
relate
on
this
one
to
the
on-premises
shipment,
adding
model
development.
It's
that
okay,
like
adding
model.
A
So
it's
host
all
of
this
stuff
in
some
on-premises
server,
it's
called
an
iis
server
or
whatever
server,
and
then
serve
that
information
from
there.
That
does
not
require
internet
connectivity.
For
your
end
users,
which
is
good
the
clear
graphically
distributed
option
can
be
achieved
with
this
this
option.
It
really
depends
again
on
your
internal
network
setup.
There
might
be
some
internal
caching
options
within
your
network
or
they
might
not
be.
We
don't
actually
know
because
those
are
corporate,
unique
and
deployment
options.
A
The
flexibility
from
that
perspective
is
good,
but
then
that
increases
the
operational
cost,
because
now
you
have
an
additional
server
which
you
need
to
get
what
you
need
to
manage,
what
you
need
to
operate,
what
you
need
to
make
sure
that
it's
up
and
running
there's
high
availability
considerations
and
all
of
that
within
this
server
as
well.
It
might
be
that
it's
part
of
your
shipment,
adding
model
environment,
that's
an
option
and
most
likely
that's
high
available
environment
as
well.
A
We
don't
know
again
multiple
options
and
then
there's
the
let's
say
the
third
option,
which
is,
if
you're,
using
just
Microsoft
technologies.
Obviously
you
can
use
as
your
CDN
as
your
hosting
location
or
whatever
third
party
CDN
outside
of
the
of
your
corporate
network,
but
then
that
requires
the
client
connectivity
or
internet
connectivity
for
your
clients
and
which
might
or
might
not
be
suitable
for
your
for
your
deployment.
Flexibility
is
no
doubt
cute.
A
B
A
I
would
say
this
is
definitely
one
of
those
things
that
it's
so
significant,
if
you,
if
you,
if
you
have
a
one-off,
simple
deployment
in
on-premises,
no
doubt
host
your
stuff
in
SharePoint
Server,
that's
the
most
simplistic
thing.
What
I
can
do
it
for
a
demo
purposes?
Absolutely
that's
easily
doable.
A
Now,
quite
often,
customers
do
have
an
existing
shed,
let's
say
SharePoint,
adding
model
investments
in
on-premises,
so
the
on-premises
server
yeah,
that's
an
option
if
you
have
an
access
on
our
sure,
CDN,
absolutely
the
best
option,
because
and
if,
if
Internet
connectivity
is
fine,
because
it's
so
easy
to
maintain
your
assets
in
Dodger
Stadium
and
then
it
it
is
actually
sitting
in
it's
a
content
delivery
network.
So
you
get
your
assets
closer
to
the
people
regardless,
where
they're
accessing
your
endpoint
on
on-premises
and
one
again
it's
so
much
depends.
B
A
Absolutely
well
to
be
fair.
I
would
say
that
that
is
exactly
the
same
story
and
I
need
to
have
the
process
defined
for
your
company
for
all
of
these
three
different
options
and
the
process
could
be
once
again,
it
doesn't
have
to
be
a
massive
50
betas,
and
this
is
what
we
need
to
do.
When
something
happens,
it
could
be
a
1,
a
4,
where
we
agree
that
this
is
the
steps.
This
is
Dima
where
we
sent
stuff
for
approval.
A
This
is
the
people
who
are
will
approve
that
and
then
there's
a
sign-off,
and
then
we
do
a
deployment.
It's
almost
like
the
farm
solution,
deployment
in
on-premises
or
form
solution,
getting
stuff
deployed
on
premises,
form
using
the
form
solution
scenarios
exactly
the
same
thing,
there's
probably
some
sort
of
an
agreement.
How
we're
doing
that
in
on-premises
and
the
same
things
apply
here.
A
B
And,
and
and
difference
there
is
that
when
you
build
an
add-in
on
the
output,
you
will
get
a
package
right,
so
you
will
get
a
getting
and
get
a
package
that
you
that
you
can
in
install
salt
in
the
IES,
whereas
in
SP
effects
you
will
get
only
need
to
files
right.
So
if
there
is
an
admin,
they
have
to
acknowledge
the
different
deployment
approach.
If
you
will
write,
deploys
the
files
versus
installing
a
package
yeah.
B
B
A
A
Cool,
let's
actually
move
back
the
actual
code
level
and
let's
have
a
look
on
the
solution
structure.
So
how
do
we
create
a
web
part
for
SharePoint
2016
using
a
SharePoint
framework,
a
yeoman
generator
version
1.0?
So
let's
first
jump
to
our
console
so
I'm
using
I'm
using
Windows
10
machines
I'm
using
PowerShell,
as
my
console
there's
multiple
options
for
your
chosen
console
option.
Obviously,
in
my
case,
let's
actually
create
it
quickly
here
and
Waldeck
folder.
So
we
can
actually
see
how
to
yeoman.
Template
is
asking
your
target
environment.
A
So
let's
go
to
the
wall
deck
and
then
do
you
Microsoft
SharePoint,
the
immediate
first
question.
After
the
solution
creation
is,
then
what
is
your
target
environment?
So
let's
call
this
wall
deck
and
then
there's
the
new
question
which
you
haven't
seen
in
the
previous
yeoman
template
selections.
So
are
we
targeting
this
version
on
to
SharePoint
Online
only
which
is
the
latest
and
greatest
version
of
SharePoint
online
now
or
SharePoint
framework?
Do
service
line
dependences,
or
do
we
target
the
version
to
share
one
2016
onwards,
including
SharePoint
Online?
A
So
we
kind
of
use
the
later
version
of
the
of
the
SharePoint
favorite,
but
it
works
also
in
SharePoint
2016
to
those
server
side
dependencies
and
now,
depending
on
what
I
choose
here.
So,
for
example,
if
I
choose
2016
onwards,
we're
not
going
to
ask
or
you
can
create
a
a
web
part
or
an
extension,
we're
gonna,
just
move
to
the
web
part
flow
in
the
in
the
selection,
which
is
understandable.
So
we're
not
going
to
do.
Is
the
scaffolding
here,
so
I'm
gonna
actually
do
a
reset
and
let's
go
to
feature
back.
A
I've
already
done
the
scaffolding
previously,
so
we
don't
have
to
wait
the
scaffolding
to
be
completed.
So
this
is
what
you're
kidding
now
I
even
have
it
I
had
a
package.json
available
there.
So
obviously
the
basic
structure
is
exactly
the
same
as
previously
in
SharePoint
framework
solutions
on
clearly
no
differences,
because
you're
only
getting
a
different
or
previous
version
of
the
SharePoint
framework
being
scuffled
for
you
and
you
can
actually
see
dance
in
the
package.json.
So
even
though
we
were
using
a
shape,
one
framework,
one
country,
we're
scaffolding,
you
a
solution
which
is
using
SharePoint.
A
Correct
exactly
exactly
so,
we
can
quickly
do
here,
something
like
well.
Obviously
we
can
do
a
call
observe
and
we
can
see
the
web
part
being
fully
functional
in
the
local
workbench,
that's
kind
of
given
that
works
by
default
within
there
we're
gonna
ship
one
framework,
and
if
we
start
this
one
up
and
running
in
here,
we
can
clearly
say
the
web
part
being
hosted
in
1.1.
There's
our
hell
out
there.
What
part
is
getting
rendered
properly.
A
A
So
here
it
is
underneath
all
of
the
sites
and
then
we
are
able
to
work
within
the
context
of
the
site
as
well
in
the
same
way
as
which
she
went
online
for
this
particular
machine
that
I
haven't
actually
requested
that
before
today,
so
I
took
a
while
to
actually
get
it
up
and
running.
Here
we
go
here's
the
web
plan
and
then
clearly
I
can
just
do
a
package
solution
for
this
web
part.
A
And
just
for
the
sake
of
it,
we
can
no
doubt
do
this,
so
we
can
do
a
package
solution.
We
can
reference
this
reference
to
local
host
environment.
So
if
we
do
a
package
solution,
we
can
clearly
have
a
quick
look
on
on
here
that
we
are
this
classic
thing,
but
I
always
tend
to
show
because
people
are
not
super
aware
of
this.
I
can
clearly
see
that
we
are
now
still
being
pointing
to
the
local
host
the
URL.
A
So
now,
if
I
do
Explorer
or
because
this
doesn't
take
that
long,
let's
actually
quickly
walk
this
through
a
solution
and
there's
my
package:
let's
actually
go
to
the
App
Catalog.
Let's
add
that
buckets
the
App
Catalog,
the
installation
is
exactly
the
same
as
in
SharePoint
Online
tenants.
So
we
will
show
you
and
let's
say
the
mock-up
or
the
the
warnings
you
will
have
to
approve
this
one
or
the
person
who
have
permissions
in
app
catalog
will
have
to
approve
that
by
default
it's
a
tenant
administrator.
A
It
can
be
dedicated
to
anybody
who
has
access
under
on
the
FCAT
all
getting
that
one.
The
point
that's
now
getting
deployed-
you'd
probably
saw
that
was
pretty
fast-
that
we're
still
boiling
into
the
localhost
from
a
URL
perspective.
So
I
need
to
actually
get
in
here.
Do
call
observe
no
process,
so
we
have.
We
are
actually
serving
these
assets,
in
this
case
the
JavaScript
files
and
a
JSON
file
well
JavaScript
files
in
this
case
and
when
we
are
requesting
the
web
part
in
the
side.
A
So
that's
now
running
in
my
local
host
and
let
me
actually
get
back
on
the
sides.
If
I
go
to
a
clean
site,
I
need
to
install
the
solution,
because
in
SharePoint
2016
it's
back
to
version,
we
do
not
support
tenon
scope,
deployment,
so
I'll
go
to
add
an
app
in
here.
We
should
see
the
FB
to
client
solution,
I'm,
going
to
install
that
one
that's
getting
installed
again
slightly
bit
depends
on
your
farm
settings
and
environments.
How
long
this
data
step
will
take?
A
You
can
actually
see
that
from
getting
flipped
there
we
go
to
an
installed
mode.
It
really
depends
again
on
your
environment,
how
long
the
application
installation
takes,
but
when
that's
done
we
can
absolutely
create
a
page.
So,
let's
create
a
page
and
a
page
on
this
side.
Let's
call
this
webcast
and
add
that
one
to
the
page
and
now
the
web
part
is
available
within
the
classic
experience
of
the
of
the
chef
116.
B
A
We
should
see
the
web
part
underneath
the
other
if
I
click
that
one
add
and
there's
my
beautiful
beautiful
web
part
getting
served
from
on-premises
using
the
localhost
URLs
less
the
web.
Part
and
I
can
even
modify
this.
So
if
I
go
edit
web
part,
we
can
see
that
it's
exactly
the
same
as
in
shipment
online,
classic
experience,
I
can
configure
the
web
part
properties
and
if
I
do
modifications
modify
settings,
we
can
see
those
settings
keep
being
reflected
on
the
on
the
web.
Part.
B
A
That's
pretty
cool
actually,
when
I
think
events
and
there
we
go
it's
running
for
perfectly
there's
no
problems
whatsoever,
cool
and
obviously,
for
a
let's
say
for
development
experience
and
develop
in
time
thing
you
can
use
the
workbench
I
can
absolutely
go
here
and
and
stop
this
one
and
do
a
quick
modification
on
my
web
part.
So
if
I
go
back
on
the
source
and
there's
my
web
part,
let's
modify
to
hear
something:
welcome
to
SharePoint
framework
and
Casta
SharePoint
framework
in
fb2.
A
That
should
be
pretty
notice
in
the
UI
I'm,
gonna
change
to
say,
change
to
save
at
changed,
save
the
changes
and
let's
do
the
carp
server
again,
because
we're
pinpointing
from
the
local
directly
from
the
localhost
I
could
do
this
with
the
live
workbench
as
well.
But
I
can
absolutely
do
this
against
the
live
side
as
well,
because
we
install
that
SP
pkt
file
already
together,
look
it's
pointing
to
the
localhost.
A
B
A
Is
the
development
time
experienced
in
production?
You
would
have
to
upload
a
new
USB
pkg
file
to
do
add
catalog,
but
that's
a
production
time
update
of
the
of
the
assets,
so
small
differences
there
and
absolutely
getting,
and
it's
documented
and
getting
more
and
more
documented
in
the
depth
of
that
comes
last
SharePoint
location
but
I
think
that's
it
from
this
one.
A
So,
let's
flip
back
on
there
on
the
slides,
I
think
we
have
slides
here
running
and
let's
do
a
quick
summary
and
on
the
things
so
we
went
true
one
does
the
sharepoint
2016
feedback
to
support
actually
means
for
on-premises,
and
we
explained
also
what
it
means
from
a
yeoman
template
perspective.
So
the
yeoman
templates,
starting
from
one
country
version,
will
show
you
the
option
of
doing
sharepoint
online
and
slats
on-premises
as
a
choice,
choice
and
then
that's
that
is
actually
giving
you
the
package.json.
Based
on
that
particular
environment
know.
A
Somebody
might
be
immediately
thinking
what
about
sharepoint
feature
back
tree
or
whatever
future
on-premises
version.
There
will
be
then,
an
alternative
choices
and
there
will
be
absolutely
Whitson
women
who
want
to
target
your
web
part
and
this
there
is
a
server
side
dependence
on
these
things,
so
that
gets
slightly
more
complicated.
So
there
might
be
three
choices
or
four
choices
in
there
in
the
top
down
in
the
yeoman
template
selection.
But
that's
it
pretty
much
from
this
one
anything
what
we
additional
things,
what
we're
going
to
cover
warwick
questions.
B
A
And
obviously
the
key
point
being
the
fact
that
the
same
wit
part
right
now,
if
there's
a
hyper
deployment,
for
example,
it
works
in
on
premises
and
in
SharePoint
Online.
Yes,
right
now,
there's
if,
if
the
customer
is
using
a
modern
UI
in
SharePoint
Online
and
a
classic
UI
in
Chevron
2016
with
stone
option
over
there,
there
would
be
a
visible
difference,
but
the
web
part
itself
is
still
the
same.