►
Description
PnP Webcast around how to use the Office 365 CLI to upgrade your SharePoint Framework solutions to use the latest version of the SharePoint Framework.
Demo on how to upgrade existing custom solution built using SharePoint Framework version 1.4.1 to version 1.5.
A
Welcome
everybody:
this
is
chiffon
Patterson
practices
webcast
and
this
time
we're
going
to
talk
about
how
you
can
use
to
office365
CLI
command
line
tool
to
up
create
your
shipment
framework
solution.
My
name
is
SR.
You
wanna
I'm,
a
Senior
Program
Manager
from
shipment
engineering
and
with
me
today
is
waldek
mastercards
wall
tech.
Will
they
do
the
quick,
intro,
so
small
sure.
A
So,
but
let's
actually
there
might
be
some
terms
here
there,
which
people
are
not
that
familiar.
So,
let's
make
sure
that
you
are
actually
familiar.
What
is
an
office
register
five
CLI,
and
then
we
can
talk
about
how
we
can
use
that
tool
to
upgrade
your
SharePoint
framework
solution
to
the
latest
version
or
whatever
version.
Actually,
you
can
define
what
version
you
want
to
upgrade
your
solutions
to
now.
First
of
all,
office365
stay
aligned,
that
is
a
cross-platform
command
line
tool
to
manage
office,
365
settings
and
SharePoint
framework
projects.
A
So
if
you
think
about
the
classic
ways
of
managing
office,
365
settings
or
tenant
settings,
you
have
been
using
PowerShell.
The
challenge
with
PowerShell
for
the
time
of
the
recording
of
this
video
is
that
it's
not
a
cross-platform.
It's
not
that
it's
not
available
in
a
Mac,
and
you
would
have
to
then
start
up
windows,
VM
and
whatever
to
manager,
Office
traces
to
factory
settings.
A
In
a
second
now
of
creating
a
ship
one
framework
solution
and
the
latest
version
of
your
choice
or
your
chosen
version,
the
CLI
is
being
built,
are
using
no
chance
and
using
it
too,
because
the
ill
I
approach
so
you're,
basically
using
a
command-line
UI
to
manage
settings.
This
is
a
community-driven,
so
ideas
and
questions
and
pull
requests
and
suggestions
are
absolutely
more
than
welcome
to
evolve.
The
history
justify
CLI
in
the
future.
Anything
what
you
want.
A
Absolutely
cool
so
now
we
know
what
is
an
office
365
CLI,
hopefully,
and
please
have
a
look
on
and
the
documentation
again
as
office.
365
stay
like
that,
will
actually
redirect
you
to
the
documentation
and
how
to
get
started
in
all
of
that.
But
today's
topic
was
around.
How
do
we
upgrade
a
SharePoint
framework
solutions?
So
how
do
I
upgrade
the
actual
solution
using
the
office?
Razor?
Sorry
Emma?
So
obviously
you
need
to
first
instance
Eli.
Then
you
are
running
SPF
X
project
upgrade,
and
this
is
something
which
you
need
to
run
in
the
solution.
A
So
you
basically
go
in
the
command
line.
You
go
to
the
solution,
folder
in
the
where
it
is
in
your
file
system,
and
then
you
run
the
SPF
X
and
project
upgrade
command
in
the
solution.
Folder
you're
able
to
also
get
the
output
of
that
to
a
MD
or
Mac
down
format,
so
you're
able
to
more
easily
kind
of
see,
what's
actually
happening,
and
that's
mainly
because
the
solution
upgrading
isn't
really
actually
upgrading
stuff
right.
A
B
So
currently,
when
we
record
the
video,
the
idea
is
that
that
CLI
offers
you
a
report
describing
step
by
step
what
you
have
to
change
in
side-side-side
the
project
to
what.
But
you
have
to
apply
changes
by
yourself
and
that's
a
conscious
choice
for
now,
because
if
you
can
imagine
changing
product
or
changing
files
in
projects
in
an
automated
way,
it's
complex
and
it
might
get
challenging,
especially
when
a
part
of
the
upgrade
is
all
means.
Also
adjusting
your
code
right.
B
A
Which,
which
kind
of
makes
sense
I'm
gonna,
do
a
pad
Microsoft
joke
here,
because
I
think
many
of
the
the
Watchers
of
this
video
and
people
who
are
listening.
This
talks
are
aware
of
some
of
the
tools
with
Microsoft
have
been
having
in
a
past
which
do
modify
your
code
because
they
the
tool,
thinks
that
it
can
make
a
better
decision
than
a
you
for
adjusting
your
code
without
asking
any
any
kind
of
approval
on
that,
and
we
quite
often
have
seen
that
that
those
chosen
models
are
not
actually
also
always
so
optimal.
A
B
Right
so
here
I
have
a
SharePoint
framework.
One
point
four
point:
one
project,
a
with
a
react
web
part
and
how
about
we
go
through
the
process
of
upgrading
that
to
version
1.5.2
office365,
see
see,
see
right.
So
first
we
go
back
to
command
line
and
I
have
already
the
office
5c
like
installed.
So
with
that
and
I
and
I'm
in
command
line.
Now
so
the
command
Ron
is
all
365.
B
To
the
latest
version
supported
in
CLI,
which
is
at
the
moment
of
of
the
recording
version
1.5.2,
so
I
run
that,
and
here
you
will
see
an
overview
and,
as
you
can
see,
there
are
quite
a
few
things
to
change
and
that's
that
might
be
good
for
overview.
But
if
you
want
to
really
consume
it
might
be
not
the
easiest
way.
So
that's
why
we
thought
that
how
about
if
we
offered
the
same
output
but
then
in
it
mardow.
B
So
in
here
you
can,
you
can
add
output
MD
and
we
can
start
it
inside
a
file.
So
let's
call
the
file
report
MD
and
the
file
will
be
stored
in
the
current
directory,
which
is
the
directory
of
of
the
project,
and
if
we
go
back
to
vs
code,
we
can
now
see
a
new
file
called
report
Andy
and
in
here
we
have
all
the
findings
that
CLI
discovered
that
has
to
be.
That
has
to
be
adjusted
in
in
the
project
to
upgrade
it
to
SPF
x-15.
B
So
if
we
open
the
file
in
preview
mode,
which
is
easier
to
read,
we
can
go
through
the
findings,
like
ok,
upgrade
our
project
to
version
1
500,
and
then
we
can
go
through
the
truth
with
them.
The
findings
that
we
have
consists
of
a
few
parts
right,
so
there
is
first
an
ID
there's
a
title
and
for
each
one
we
say
whether
it's
required
or
recommended
it
required.
Are
things
that
you
have
to
change?
If
you
don't,
your
project
will
break
recommend.
That
is
like
we
say
you
should
do
that.
B
B
So
each
one
consists
of
an
ID,
a
idle
severity
if
you
like,
required
or
recommended
description
and
then
the
command
to
run
or
even
the
piece
of
code
to
apply
right.
So
if
we
scroll
scroll
down
well,
one
of
the
things
that
change
from
one
for
one
to
one
final,
five
and
five
OSPF
X
is
URL
of
a
schema
right.
So
here,
if
you
would
go
to
config
you
will
see,
is
that
schema
originally
was
def.
B
That
office.com
and
in
1:500
its
developer
demise
of
comm
right
so
in
here
you
will
get
snippet
and
you
can
just
merge
that
code
with
your
original
code
right.
So
we
don't
show
you
the
full
of
style,
but
only
the
piece
that
has
changed,
and
that
applies
to
everything
that
that
we
discovered
that
that
has
changed
in
order
for
you
to
upgrade
to
version
that
you
chose
right.
B
So
if
you
look
at
what
what
else
you
could
do
in
CLI
like
currently,
we
support
only
the
upgrade
from
one
four
one:
two
one:
five
Oh,
but
eventually
when
there
will
be
version,
1,
v,
1
or
wow
wow
1.6,
you
might
not
want
to
upgrade
to
the
latest
one
supported
in
CLI.
Instead,
you
might
want
to
go
from
one
four
one,
two
one
five
out.
So
with
that
you
would
say.
B
Version-
and
in
here
you
can
say
one
five,
oh,
and
that
would
explicitly
upgrade
the
project
that
you
are
currently
in
in
command,
like
which
you
can
see
here
diversion
you
explicitly
give,
because
if
you
don't
CLI
will
automatically
pick
the
latest
version
of
SPF
X
it
supports.
If
you
want
to
know
more
about
the
command,
how
it
works
the
and
get
examples
you
can
run
help
and
that
will
give
you
a
detailed
description
of
supported
version.
B
A
B
A
A
Excellent
but
I
think
that's
it's
around
this
one
really
cool
stuff,
but
let's
flip
back
on
the
slides
and
and
close
up
to
broadcast
excellent
good
demo
could
set
up-
and,
like
mentioned
already,
and
so
in
wild
x
case,
what
like
is
using
a
Mac,
but
this
tool
does
working
in
the
Windows
machine
as
well.
It
is
super
easy
to
install
directly
by
running
NPM.
Is
the
NPM
co-op,
no
know
what
install
NPM
install
the
stuff
typically
to
your
machine?
B
Share
is
that
the
future
is
pretty
new
and
I
would
encourage
everybody
to
give
it
a
try
on
the
projects
that
that
that
you
have
build
and
tell
us
what
you
think
yeah.
If
you
like
the
idea,
or
do
you
miss
something,
would
you
like
to
see
songs
on
something
else?
When
we
record
the
video,
the
only
versions
that
you
can
update
from
is
one
for
one-to-one
500.
B
Now
we
have
quite
a
few
PRS
outstanding
that
will
allow
you
to
upgrade
versions
that
are
older
as
well,
and
you
can
imagine
or
you
could
you
could
even
assume
that
as
new
SharePoint
frame
frame
and
versions
become
available,
we
will
also
add
the
ability
to
upgrade
them
right.
So
with
that
you
will
be
able
to
choose
from
which
version
to
which
or
the
latest
you
want
to
upgrade
you
so
again.
I
would
encourage
everybody
to
give
it
a
try
and
tell
us
what
you
think
yeah
absolutely.
A
And
this
is
really
interesting.
One
of
the
things
what
we're
seeing
in
the
indicator
in
the
SPD
of
Dogg's
issue
list
or
in
social
media
is
that
people
are
clearly
struggling
on
this
upgrade
so
they're
not
really
super
familiar
on
all
of
the
native
changes.
When
you
move
to
one
version
to
another,
which
is
fair,
we
as
a
Microsoft
should
be
doing
a
better
job
on
that,
but
this
tool
really
helps
to
make
that
upgrade
possible.