►
Description
PnP Webcast around the asset packaging feature, which is default experience starting from the SharePoint Framework 1.4 version. By default JavaScript files generated from the solution are being packaged inside of the sppkg package and served from the app catalog site collection. If Office 365 Public CDN is enabled, it will be automatically used for these assets. More details on covered topics and other assets from http://dev.office.com/blogs.
A
Welcome
to
the
SharePoint
Patterson
practices,
wet
cast
and
system
and
we're
gonna
talk
about
and
something
with
respondent.
The
shipment
framework
1.4
release
the
movie
released
significant
chains
with
this
around,
including
the
assets
on
a
shipment
framework
solution
packages.
My
name
is
Lisa
Irwin
and
I'm.
A
senior
program
manager
from
Microsoft
and
in
the
shipment,
engineering
and
Witney
today
from
the
community
sign
is
wall
tech,
mastercards
hello,
while
they
equally
do
the
quick
intros
as
well
sure.
B
A
Indeed-
and
this
is
a
really
really
big
change-
actually
we
are
considering
how
the
SharePoint
framework
us
working
in
past.
So
this
is
a
really
great
improvement
for
the
developers
and
also
for
admin.
So
let's
have
a
look
on
this
one.
What
does
it
mean
in
practice?
Looking
in
the
distal,
aaja
call
architecture
and
then
we'll
do
a
live
demo
together
with
well
I?
Guess
well.
A
If
the
CDNs
enable,
if
the
CDN
is
not
enabled,
will
dynamically
update
the
urls
point
directly
to
the
assets
in
the
tenant,
app
catalog
site
collection,
then
the
whole
thing
is
happening
automatically
depending
on
the
tenant
level
settings.
So,
as
you
as
a
developer,
know
just
package
your
solution
and
they
say,
if
you
don't
change
the
default
settings,
the
the
assets
are
getting
packets
inside
of
this
biggity.
A
Well,
you
deploy
the
solution
to
your
tenants
and,
depending
on
a
tenant
administrative
settings,
your
assets
are
billing
getting
served
either
from
the
office
traces
to
a
CDN
or
from
the
application
catalog
in
a
tenant
level,
so
quite
quick
rate
capability,
because
this
will
reduce
the
complexity
of
the
killing
stuff
deploy.
So
you
don't
have
to
worry
about
getting
those
assets
deployed
from
the
from
let's
say
a
third
party
Stadium
or
in
a
different
location.
All
of
that
is
getting
automatically
by
default.
A
It
done
for
you
now
just
a
pin
point
and
also
that,
if
you
still
want
to
use,
for
example,
sure
CDN
or
whatever
senior
service,
so
you
would
will
need
to
have
more
control,
for
example,
for
city
and
expiration
or
cm
configuration.
You
can
absolutely
do
that
in
the
future
as
well.
So
this
is
the
saving
in
the
package
solution
JSON
file,
which
which
controls,
if
desserts,
are
getting
actually
packets.
Inside
of
this
paper,
ktf
well
or
not,
why
does
it?
A
Why
does
that
packaging
is
a
great
improvement
for
SPF
X
solution,
so,
like
mentioned
no
additional
asset
hosting
location
needed,
so
everything
is
getting
done
automatically
for
you.
It's
just
point
adding
that
this
PPK
chief,
while
the
app
catalog
organization
in
control
for
the
solution
assets-
and
this
is
a
good
thing
as
well,
because
theoretically,
if
you're
using
a
let's
say
an
SPF
X
solution
provided
to
you,
PI
an
ISV
or
a
render
partner,
death
solution
is
referencing
assets
from
a
random
city
and
random
URL
in
the
internet.
A
You
as
an
organization,
you
don't
know
if
those
Java
scripts
are
getting
update
or
not.
Now
that
we
are
actually
getting
the
JavaScript's
inside
of
the
assets
files,
you
actually
control
the
solution
asset,
so
you
know
exactly
where
and
when
these
files
are
getting
updated.
So
that
will
give
you
more
security
and
more
reliance
on
what's
actually
happening
within
your
tuna
and
then
possibility
to
promote
the
same
packets
to
dev,
UAT
and
approach.
So
obviously,
depending
on
your
ALM
process,
you
might
have
separate
people
doing
a
development.
A
You
might
have
a
separate
test-
tenant,
potentially,
not
obviously
required,
but
you
might
have
done
and
and
you
might
have
a
production
tenant
so
using
this
model
that
the
assets
are
getting
packets
inside
of
the
package,
you
don't
have
to
worry
about
the
URL
in
the
inside
of
the
SPP
kg
file,
because
everything
is
automatically
updated
for
you.
So
as
a
developer,
you
just
package
everything
into
the
SP
pkg
oil
and
the
URLs
are
getting
up
automatically
updated
based
on
the
environmental
settings
or
lieutenant
setting
anything.
What
I'm
missing
here,
Baltic,
which
comes
yeah.
B
B
Effective,
yes,
so
the
one
thing
you
mentioned
is
that
by
default
everything
will
be
packaged
inside
the
package.
So,
let's
say,
would
you
say
that
deployment
to
Azure
of
assets
or
treasure
blob
is
in
a
way
obsolete
and
that
we
should
always
use
that
and
I'm
aware
that
I'm
here
moving
on
a
dangerous
ground,
because
it's
like
basically
asking
for
advice,
would
you
say
people?
Should
people
always
do
this,
or
can
you
say
there
are
some
particular
scenarios
in
which
it
would
make
sense
to
use
Azure
or
your
own
location
to
store
the
assets?
Well,.
A
This
is
once
again
one
of
those
things
that
it
absolutely
depends
so
I
would
say
pointy
fingers
yes,
by
default,
absolutely
you
should
be
using
this
automatic
asset
packaging.
Now
we,
the
dofus
resist
of
our
CDN,
is
an
automatic
CDN
which
we
provide
you
for
free
through
office
365.
Now
it
might
be
that
you
have
specific
requirements
for
your
CDN
control.
You
might
have
specific
configuration
requirement,
which
I
can't
really
invent
anything.
Maybe
you
can
welding,
and
but
we
want
to
control
how
to
CDNs
behaved.
A
You
can't
do
that
with
office365
see
there,
but
you
can
do
that
with
the
National
Stadium.
So
if
you
have
those
requirements,
you
can
still
use
your
option.
You
can
still
use
to
deploy
the
storage
storage.
Blob
asteroids
account
plops
option
as
a
cop
tasks
in
the
future
as
well,
we're
not
going
to
remove
them
and
but
by
default,
probably
that's
not
the
chosen
path
and
all
of
our
tutorials
might
have
seen
that
we
updated
all
of
our
tutorials
to
offer
us
a
fall
back
and
not
fall
back
to
use
this.
B
Yeah
and
I
guess
there
are
still
still
two
options,
so
tutorials
that
we
have
some
of
them
will
or
actually
we
will
have
one
tutorial
or
we
have
one
tutorial.
That
shows
exactly
if
you
chose
to
deploy
to
Azure.
This
is
the
way
to
do
it
bar,
but
I
default.
As
I
said,
we
use
the
default
approach
that
everybody
will
see
when
they
create
new
project.
B
To
ask
that
I
wonder
about
really
it's
like
in
the
past.
Before
you
actually
created
the
package,
you
had
to
include
the
URL
where
the
files
would
be
stored
yeah.
So
how
does
that
work
here?
Because
you
said
that
the
URL
will
be
automatically
adjusted
across
environment,
but
so
how?
What
do
I
include
in
the
code?
What
you
were
all
do
I
said
initially,
and
how
does
that
work.
A
B
A
Will
happen
is
that
if
you
have
the
setting
in
the
solution,
packaging
enabled
true,
which
is
the
default
setting
indicating
that
solute
assets
should
be
packaged.
The
solution
begins
will
replace
that
you
were
well
automatically
as
part
of
the
packaging
as
a
tack.
It's
in
I
think
it
says
the
dps
client
library,
the
tag
name,
if
I
remember
correctly
and
but
yeah,
and
it
actually
doesn't
matter.
A
We
replace
the
URL
as
a
dynamic
tag
and
so
that
whenever
the
assets
are
being
used
in
ship
on
ship
and
actually
recognizes
hey,
this
is
actually
indicating
that
it's
as
dynamically
packaged
in
the
solution
and
the
URL
s
getting
replaced
automatically.
So
you
as
a
developer,
you
don't
need
to
worry
about
the
URL
and
because
that's
getting
taken
care
of
by
us
in
the
inter
SharePoint
site,
right.
B
So
if
I
understand
that
correctly,
no
matter
what
URL
you
set
it
to
you,
when
you
create
the
package,
it
will
be
replaced
by
a
token,
and
that
token
indicates
during
deployment
to
SharePoint
Online
that
it
that
the
assets
are
included
in
package
and
they
should
be
deployed
to
the
location
meant
to
hold
the
assets
in
SharePoint.
Correct,
correct.
That
is
correct,
yeah
cool
yeah.
So
how?
How
about
we
see
it
in
practice?.
A
B
B
Another
think
that
let's
have
a
look
at
is
the
URL.
So
here
in
right
at
FSU,
you
can
see
that
I
haven't
changed,
it
URL,
so
I
just
let
it
be
the
way
it
is
so
now.
Let
me
build
the
project
in
release
mode,
so
here
I
will
run
gob
bundle.
That's
that
ship
right,
because
if
you
would
build
it
in
in
a
debug
mode,
it
would
just
point
to
localhost
and
we
actually
want
to
see
how
it's
going
to
be
deployed
to
SharePoint
course.
So
here
we
have
the
three
to
one.
B
There
will
be
the
bundle
there
is.
It
took
a
bit
longer
than
we
thought,
but
and
now
let's
generate
the
package.
So
here
was
a
drop
package
solution.
There's
the
ship
and
that
should
go
relatively
fast.
There
you
go
is
done
before
we
actually
add
the
package
to
the
SharePoint.
Let's
have
a
look
at
the
manifest
and
URL.
B
So
if
we
open
that
the
one
thing
that
we
can
see
here
is
that
there
is
new
folder
named
client-side
assets,
which
is
here
and
if
we
open
that
we
can
actually
see
the
strings
and
the
bundle
that
we
have
in
project
because
they're
exactly
the
same
as
available
here
in
this
I
are
actually
not
in
this
in
temp
deploy.
So
they
are
here,
and
these
are
exactly
the
same
things
that
are
available
here
that
are
available
here.
So
yes,
they're,
included
in
package
now.
B
Another
interesting
thing
is
what
about
the
URL,
because
initially
we
didn't
set
that
right.
We
left
that
empty.
So
what
is
the
URL
now
and
if
I
wrap
it
here,
you
can
see
the
token
that
the
tooling
includes
to
indicate
to
sharepoint
that
these
assets
are
included
in
package
and
the
sharepoint
should
deploy
them
inside
sharepoint.
So
that's
a
token
that
does
that.
So,
let's
see
it
in
practice.
How
sharepoint
will
handle
the
package
when
we
edit
to
catalog,
let's
switch
to
our
site
and
let's
switch
to
the
package.
B
B
Now,
there's
an
interesting
part
in
a
past
if
you
recall
that
we
would
see
it
a
URL
that
that
shows
where
the
files
are
stored,
but
now
it
says
SharePoint
Online,
it's
exactly
because
of
the
fact
that
we
chose
to
include
assets
inside
the
package
and
that
we
won't
SharePoint
to
house
them
for
us.
So
that's
why
it
says
the
files
will
come
from
your
tenant.
You
host
them.
So
now
we
choose,
let's
say:
make
this
available
to
all
sides
deploy
that,
and
that
should
be
done.
B
Let's
verify
that
it
has
been
deployed,
no
errors
now,
let's
switch
to
our
sites
and
let
me
refresh
the
page
so
that
it
will
load
the
manifest
available
in
the
tenant.
Let
me
edit
the
page
and
add
the
weapon
to
the
page,
because
the
package
that
we've
built
has
a
web
part
which
we
can
add
to
the
site.
So
here
we
look
for
cells,
which
is
our
web
part.
We
had
that
and
now
we
can
already
see
that
it
works
right.
So
let's
quickly
configure
that,
so
we
can
see
some
nice
data.
B
And
we
can
already
see
that
it
works
right
and
if
we
publish
the
page
and
load
developer
tools,
let
me
zoom
in
on
that
switch
to
the
network
tab
filter
on
contoso,
which
is
the
name
of
the
web
part,
and
then
we
reload
the
page
we
should
be
able
to
see
from
which
URL
this
web
part
is
being
served
soon.
So
now
we
see
it
here
and
if
you
look
at
the
URL
it
points
to
public
CDN,
SharePoint,
Online
comm.
B
The
reason
for
that
is
is
that
this
tenant
has
the
public
CDN
enabled
right,
and
if
you
recall
it,
we
didn't
set
this.
You
were
ourselves.
We
only
set
the
token
and
SharePoint
framework
picked
it
up
on
itself
right.
It
did
it
by
itself.
It
replays
token
with
the
right
URL
based
on
the
fact
that
CDN
is
enabled
here.
If
it
wasn't,
it
would
use
the
catalog
URL
and
where
the
package
is
stored.
A
It
has
to
be
super
super
clear
if
the
CDN
is
not
enabled
like
well
dick
mentioned,
and
you
can
actually
see
what
would
be
the
URL,
so
the
URL
would
be
the
tenancy,
a
URL,
slash
sites,
less
apps,
less
client-side
assets
last
that
good,
and
also
that
the
point
of
from
here
so
the
if
the
CDN
is
enabled
it's
gonna
use
the
HTTP
public
CDN
URL.
If
it's
not
enabled
it's
gonna
pinpoint
directly
to
the
bundle
directly
from
the
app
catalog.
So
it's
completely
seamless
experience
but
sister,
but
right.
A
Sounds
good
thanks,
Robbie
cool,
so
thank
you
well
like
for
that.
One
I
think
we
work
nicely
walkthrough.
Let's
say
the
difference
is
between
the
URLs
and
and
maybe
not
to
not
the
most
success
demo
so
to
say,
but
I
think
this
has
a
massive
deal
from
a
simplifying
the
chiffon
framework
solution,
development
experience
and
also
deployment
experience,
and
this
has
a
massive
massive
impact,
also
from
hosting
experience
and
perspective.
So
the
the
tenant
admins
or
the
persons
who've
been
delegated
the
permissions
to
manage
that
catalog.
A
Don't
have
to
worry
about
the
second
dimension,
we're
way
to
actually
host
assets
and
and
also
considering
the
fact
that,
quite
often,
if
you
think
about
the
usher,
CDN
host
and
quite
often
in
enterprises,
the
usher
is
being
managed
by
a
different
people
in
the
office
365
people.
So
this
way
you
don't
have
to
worry
about
that
asset
hosting
in
Azure
side.
You,
let's
just
concentrate
on
when
making
sure
that
your
solution
is
going
to
deploy
your
based
on
settings
and
then
I
that
mean
controlled
settings.
Everything
is
dynamically
happen.
Anything.
B
Yeah,
yes,
sure,
yeah
and
I
do
sum
it
up.
It's
all
about
simplicity,
its
simplicity
in
your
deployment
in
your
ALM
and
the
fact
that
you
have
one
thing
less
to
worry
like
who's
managing
the
assets.
It's
a
period
you
determine
when
and
when
they
they
they
change.
So
it's
a
big
changer
in
the
whole
game
of
SPFs
deploy
and
all
that.
It
really
simplifies
things.
A
lot
absolutely.
A
That's
great
great
I
think
if
you're
not
super
familiar
with
SharePoint
framework
until
I
say
in
this
video,
you
probably
don't
even
understand
the
the
meaningless
of
the
magnet
of
of
this
chains.
I
think
this
will
have
a
significant
impact
like
you
like
what
I
said
on
the
simplicity
of
getting
things
done,
which
is
superb,
so
cool,
but
I
think
that's
it
for
this
one.
So
what
does
thank
you
one
like
for
a
great
demo,
Thank
You
Baltic
for
the
great
discussion
and
we'll
come
up
with
a
new
webcast
sooner
or
later.
Thank
you.