►
Description
In this 4 minute developer-focused demo, Hugo walks through how to install the Remote Development extension pack for Visual Studio Code and then uses Docker for desktop to connect to the remote container so that you can easily switch between development environments reflecting that you need different development dependencies for Teams, SPFx, Power Platform etc.
Presenter: Hugo Bernier (Microsoft) | @bernierh
Resources:
https://code.visualstudio.com/docs/remote/remote-overview
https://aka.ms/m365pnp
https://pnp.github.io/blog
A
Hi
everyone,
my
name
is
hugo
bernier
and
I'm
a
cloud
solution
architect
at
microsoft,
as
the
microsoft
365
developer
ecosystem
keeps
on
evolving,
you
might
find
it
difficult
to
keep
up
with
all
the
environments
that
you
need.
Maybe
you
need
to
set
up
a
an
environment
for
web
part
development
or
one
for
adaptive
card
extensions
for
viva,
or
maybe
you
want
to
build
teams
apps
or
you
want
to
build
tools
to
work
with
the
power
platform.
A
A
A
A
A
Okay,
so
here
I
have
a
sharepoint
framework
solution
that
was
built
a
long
time
ago
and
it's
actually
not
even
using
a
version
of
sharepoint
framework
that
is
compatible
with
my
environment.
In
fact,
let
me
just
put
these
things
away
here.
If
I
actually
use
my
terminal-
and
I
look
at
the
version
of
node-
that's
currently
installed
on
my
machine
you'll
see
that
I'm
currently
running
node
1222..
A
Unfortunately,
the
version
of
sharepoint
framework
that
this
was
built
in
only
works
with
node
version
8..
Now,
if
all
I
was
doing,
was
working
on
spfx170
or
older
versions
of
spfx,
then
I
could
probably
configure
my
workstation
to
only
have
node
8.
But
in
my
particular
case
I
like
to
work
with
multiple
solutions
across
multiple
versions
of
of
sharepoint
framework,
or
I
like
to
build
teams,
applications
or
viva
adaptive
card
extensions.
A
So
that's
not
going
to
work
for
me,
but
because
I
have
the
extension
for
remote
containers
and
I
have
docker
desktop
installed
on
my
machine.
I
can
actually
use
this
cool
feature
here,
so
I
have
a
folder
called
dev
container
and
the
folder
contains
a
dev
container
json
that
actually
points
to
the
image
that
I
want
to
use
to
be
able
to
run.
A
This
sharepoint
framework
happens
to
have
docker
container
images
for
every
single
version
of
the
sharepoint
framework
created,
so
it
makes
it
easy
for
you
to
be
able
to
create
an
environment,
that's
compatible
with
whatever
version
of
sharepoint
framework,
and
that's
what
you
see
here.
I
have
an
image
that's
created
for
spfx170,
so
all
I
need
to
do
because
I
have
this
dev
container
folder
and
this
dev
container
json
created.
A
A
So
here
I
have
a
solution
that
contains
the
power
platform
center
of
excellence
toolkit
as
a
command
line
interface.
In
order
for
me
to
run
this,
I
need
to
have
a
different
version
of
node.
I
need
to
have
all
sorts
of
different
requirements
that
you
may
or
may
not
have
in
your
environment,
but
thankfully
the
solution
has
a
dev
container.
That
means
that
I
can
just
reopen
the
solution
again
in
a
container
using
the
extension.
That's
built
into
visual
studio
code.
A
A
But
I
can
actually
just
get
started
so
if
I
type
coe
h,
for
example,
to
just
get
the
help,
I
get
the
help
for
the
center
of
excellence,
command
line
interface
right
away,
so
you
might
say,
hey
hugo.
I
don't
know
how
to
set
up
these
containers.
Don't
worry
about
it.
One
of
the
things
that
we've
started.
A
It'll
make
it
easy
for
you
to
switch
back
and
forth
between
various
development
environments,
but
also
make
it
easy
for
you
to
share
your
code
with
your
team
members,
because
they
don't
have
to
worry
about
whether
they
have
the
right
environment
set
up
or
not.
The
dependencies
are
built
in
and
described
within
the
remote
container
itself.