►
Description
Join members from the .NET teams for our community standup covering great community contributions for Visual Studio, Visual Studio Code, Visual Studio for Mac, Roslyn, Extensions, and more!
Suggest an idea for a standup: http://aka.ms/dotnet-standup-suggestion
A
Sorry,
cuz
I
already
hit
start
stream.
Okay,
now
II
think
we're
live
nice
anti-climactic
line
down
hello.
Everyone
welcome
to
the
dotnet
community,
stand
up
for
the
to
lean
the
visual
studio
tool.
In
addition,
I'm
kendra
havens
your
host,
along
with
my
co-host,
cody
layer,
blue,
you
don't
recognize
us.
I
have
a
program
manager
on
dotnet
and
visual
studio.
I
am
mostly
work
on
dotnet
tooling,
in
visual
studio,
and
I
am.
A
C
A
Sorry
if
the
title
of
the
video
still
says
triage
process,
that
was
going
to
be
the
topic,
but
instead
we're
lucky
enough
to
have
some
we'll
talk
about
that
one
later.
Oh
sorry,
thanks
for
telling
me
my
volumes
low,
okay,
so
first
off,
we
want
to
just
show
a
couple
community
news
things
I'm
going
to
switch
to
mountains,
computer
okay.
So
first
off
we
did
a
small
announcement
about
how
we're
consolidating
some
of
the
dotnet
github
repos
I
just
wanted
to
call
it
out.
A
A
Let's
see
there,
we
go
of
basically
opening
issues
on
one
repo
and
not
knowing
where
they
actually
need
to
set
up
so
and
and
having
to
see
your
tickets
moved
constantly
and
most
teams
trying
to
figure
out
where
it
goes.
That's
not
always
fun,
so
we
think
combining
them
will
be
a
little
bit
of
a
better
process
and
then
I
sent
you
one
other
link
for
the
yeah.
C
A
Guy,
oh
right:
okay,
back
to
your
screen,
so
Matt's
Christianson
I
came
up
with
a
really
interesting
blog
post
on
the
status
of
Visual
Studio
features,
suggestions,
I
think
he
I'm
a
huge
fan
of
Mads
and
I
think
he
outlined
our
process
really
well,
and
he
actually
gives
really
interesting
estimates
for
what
actually
happens
to
all
of
the
suggestions
that
people
put
in
yeah.
We
got
some
nads
fans
on
chat,
so
that's
always
really
I,
don't
know.
A
Also
the
comments
were
very
passionate
and
almost
therapeutic
to
read
because
they
we
know
dub
comm
is
absolutely
not
perfect
and
a
lot
of
it
was
I.
Guess
feedback
that
I
had
given
her
teams
for
months.
So
I
don't
know,
I
actually
just
really
appreciated
the
post
and
that
it
was
a
place
where
people
could
actually
talk
about
what
is
not
working
and
what
we
need
to
improve.
So
it
was
pretty
interesting.
B
And
you
know
Def
Con,
we
do
go
through
these
contests,
it's
not
like
it's
going
into
the
ether.
You
know
we
are
reviewing
what
what
goes
into
the
developer
community.
So
you
do
get
your
voice
heard
right.
You
know
it
might.
There
are.
There
might
be
some
issues
with
a
kind
of
the
organization
if
they're
whatnot,
but
you
do
still
get
your
voice
heard.
B
So
we
do
still
appreciate
anything
you
can
add
to
developer
community
either
on
the
problems
or
suggestions
side,
because
it
is,
it
is
viewed
by
you
know,
one
of
us
most
likely
or
you
know
another
engineer
or
program
manager
on
the
team.
So
we
did,
we
did
appreciate.
You
know
the
time
it
takes
to
to
fill
in
those
suggestions.
Yeah.
B
A
Had
some
times
users
have
commented
on
bugs
like
why?
Isn't
this
updated
and
I
know
there's
an
active
email
chain
with
like
12
different
people
on
it
and
we're
still
trying
to
figure
out
who
would
actually
fix
that
issue?
And
we
I
I,
know
I
hate
to
bring
up
like
all
of
that
I
guess:
Microsoft
internal
team
drama
trying
to
figure
out
who
owns
what
and
where
it
would
fit
on
their
backlog
but
yeah
it's.
It
is
a
task
and
it
might
take
a
while
before
we
were
able
to
give
updates,
but
yeah.
D
A
B
So
we
just
released
preview
to
the
next
version
of
Visual.
Studio
for
Mac
should
be
8.3,
yes,
I
believe
so
anyway.
So
there's
some
cool
stuff.
That's
coming
to
register
for
Mac
in
the
next
version,
one
of
the
things
I'm
most
excited
about
and
something
that
has
been
requested
by
our
community
quite
a
bit.
So
we're
happy
to
get
this
out.
I
think
this
is
when
the
top
asks
on
developer
community
is
the
ability
to
manage
nuga
packages
at
the
solution
level.
B
So
previously
in
Visual
Studio
for
Mac,
you
would
have
to
manage
the
media
package
for
each
project
independently,
updated
it
and
say
a
shared
project.
You
had
to
update
the
package
in
the
platform
project
as
well.
Now
you
can
update
them
in
one
place
and
you
can
manage
them
in
a
lot.
A
lot
more.
We
find
manage.
So
it's
a
cool
feature.
B
Please,
if
you
are
a
resistive
for
Mac
user
check
out
the
preview
by
switching
to
the
preview
channel
and
we'll
just
do
for
Mac
and
give
it
a
try,
because
it's
a
it's
gonna,
be
great,
we're
excited
about
it
and
we'd
like
to
get
to
feedback
on
on
how
it
you
know
works
for
folks
and
if
there's
anything
that
we
can
do
to
improve
it
as
we
get
nearer
to
the
final
release
of
it
so
check
it
out.
Wait.
A
B
A
B
Feels
very
similar
to
the
visual
studio
windows
side.
I,
don't
want
to
point
in
my
other
computer.
Is
this
one
I
see,
so
it
is
similar
to
that
I
needed
and
it
will
should
fill
at
home
for
hope,
so
yeah
try
it
out.
There's
an
other
great
features
in
preview
too,
as
well,
including
multi,
targeting
support
the
ability
to
choose
a
specific
browser
when
you
are
testing
the
asp.net
core
page
or
if
you
need
to
you,
know,
tested
on
browser
ABC,
you
can
launch
that
browser
so
that
default
browser.
So
there's
some
fun
stuff.
A
A
A
A
C
The
idea
is
basically
there's
a
lot
of
scenarios
where
you
know
you
have
your
local
dev
box,
but
then
you
may
have
a
remote
VM
or
some
other
kind
of
remote
compute
that
you
are
constantly
pulling
and
pushing
and
syncing
code
back
and
forth
from
and
in
all
these
scenarios
for
a
long
time,
there's
been
multiple
different
solutions.
Some
of
them
are
for
vm's.
You
can
SSH
in
use
them
use
lightweight
tools
that
are
easy
to
install
on
any
box
at
any
time.
C
Yet
your
editor
does
not
live
inside
that
environment,
and
so
all
of
these
kind
of
situations
have
been
workable
for
a
long
time
and
there's
been
a
lot
of
tools
that
have
existed
to
promote
this
development
pattern.
But
there's
little
quirks
in
edge
cases
and
it's
not
buttery
smooth
and
really
what
you
want
is
to
take
the
tools
that
you
know
and
love
and
use
them
anywhere.
Wherever
your
code
lives,
you
can.
C
You
can
connect
there
with
your
tools
and
so
basically
with
vias
code,
the
remote
extensions
and
it's
an
extension
pack,
there's
several
there's
the
SSH
containers
and
WSL
extensions,
but
effectively
what
they're
doing
is
you
have
your
local
operating
system
in
your
local
machine
running
vs
code,
but
it's
kind
of
a
thin
client.
You
only
get
the
UI
extensions.
You
only
get
the
front
end
of
this
code
and
then
you
can
connect
it
to
a
remote
vyas
code
server
which
can
be
installed
in
any
of
these
environments.
C
I've
listed
SSH
on
a
VM,
a
container
with
our
local
or
remote
or
WSL.
In
the
you
know,
WSL
linux
partition
on
Windows,
and
you
basically
communicate
back
and
forth
between
the
two,
where
you
have
a
vyas
code
version
running
in
the
same
location
in
the
same
context
as
your
code,
and
so
this
makes
it
a
lot
easier
for
vias
code
to
know
your
context
and
all
your
tools
to
work
as
expected,
like
live,
share,
kind
of
kind
of
it.
C
You
know
you're
kind
of
funneling
commands
back
and
forth
and
so
in
the
same
kind
of
spirit
you're,
just
installing
a
remote
server
which
doesn't
have
any
UI
components
of
this
code.
It's
just
all
of
you
know
the
language
services
and
the
compilers
and
the
tools
and
the
debuggers
all
of
that
stuff
lives
with
the
code.
In
that
context,.
C
C
C
C
We're
going
to
create
a
container
we're
going
to
install
vias
code
server
inside
of
it
and
then
kind
of
mount
in
our
source
code.
As
you
see
the
volume
mount,
and
all
of
this
is
going
to
happen
automatically
for
us
and
to
show
you
that
there's
no
smoke
and
mirrors
I'm
actually
going
to
grab
a
repo
from
scratch.
There
are
a
bunch
of
them.
You
can
try.
If
you
come
to
our
Doc's
code,
visual
studio,
comm,
Doc's,
remote
containers,
you
can
see
kind
of
all
the
options,
but
they
follow
the
pattern.
C
Vs
code,
remote,
try,
choose
your
language
or
technology,
and
so
there's
Python
your
java.net
and
so
on.
I'm
gonna
be
using
node
because
that's
what
I
am
personally
most
familiar
with,
but
I
can
go
ahead
and
get
cloned
this
guy
and
then
switch
into
vias
code.
Remote,
try,
node
and
then
I'm,
just
going
to
reopen
code
in
this
char
is
just
going
to
reopen
this
window
in
in
this
folder,
and
so
you'll
see
I've
kind
of
loaded.
This.
This
folder
and
I
immediately
get
this
pop-up.
C
It
says
you
know
this
folder
contains
a
dev
container
configuration.
Would
you
like
to
open
this
inside
the
container
and
I'm
gonna
say,
go
ahead
sure
and
what
this
is
gonna
start
doing?
You'll
notice,
I
have
opened
a
new
window
and
damn
that
was
really
fast.
That
kind
of
ruined
the
explanation,
but
that's
kind
of
the
point
getting.
C
Exactly
basically
what
happened
and
the
popover
in
this
dev
container,
we
have
a
dev
container
JSON,
which
describes
both
the
docker
image.
We
want
to
use
to
build
the
container,
and
so
you
see
we
reference
our
own
docker
file,
but
if
you
wanted
to,
you
could
just
reference
an
image
straight
up
and
then
you'll
notice
in
our
docker
file.
We
say
this
is
node.
We
want
to
do
some
stuff
to
get.
You
know
yarn
and
some
other
tools,
but
pretty
standard
docker
file.
And
then
we
have
a
three.
C
C
A
A
C
C
A
C
C
C
C
C
But
yeah,
so
basically,
we've
got
this
docker
container
running
locally.
We,
if
we
go
back
and
look
at
the
setup
of
this
container,
we
build
the
image.
We
run
the
image
and
if
we
pull
up
the
Andy,
let's
see
do
I
have
the
docker
extension,
no
I
don't.
But
if
we
do
docker
PS,
you
can
see
our
vias
code.
Try
remote
container
is
running,
and
so
I
didn't
have
to
start
that
from
dr.
CLI,
like
I.
C
We
reference
an
app
port,
and
so
we
do
port
forwarding
from
inside
the
docker
container
to
localhost,
and
that
is
useful,
because
now
we
can
run
the
app
from
inside
the
container
first
of
all,
install
the
dependencies
real,
quick
and
then,
when
I
hit
f5
to
launch
the
app
you'll,
see
that
it's
0
0
0
3000,
because
this
is
running
locally
inside
of
the
docker
container.
But
because
we
mapped
this
port.
I
can
just
go
to
my
browser
and
hit
localhost
3000
and
hello.
Remote.
C
About
this
right
is,
as
you
noticed,
because
I'm
in
the
docker
container,
all
of
my
dependencies
are
encapsulated.
My
whole
dev
environment
is
encapsulated.
If
I
want
to
do
things
here,
it's
not
going
to
impact
my
local
machine,
which
is
really
nice.
You
can
imagine
having
multiple
projects
with
multiple
different
dependencies
on
different
versions,
of.net
and
you
can
spin
them
all
up
in
their
own
containers
and
and
have
none
of
that
leak
out
into
your
local
machine
realm.
It
makes
it
really
easy
to
try
projects.
C
You
could
imagine
not
knowing
how
to
set
up
a
project,
not
knowing
what
versions
you
need
to
install
and
by
just
cloning,
something
with
a
dev
container.
Docker
takes
over
all
the
dependencies.
The
image
gets
built
automatically
for
you
and
you're
connected,
and
you
have
all
your
local
dependencies
and
so
there's
a
lot
of
benefits
with
docker.
C
A
C
C
Has
a
deaf
container
included,
which
is
nice
because
if
you've
never
built
angular
before
and
you
want
to
contribute
to
angular,
you
need
to
understand,
you
know
their
entire
contributing
guide
which
installed
it
virtual
Criers
installing
Java.
So
you
can
run
their
tests,
which
is
a
little
bit
unintuitive
working
on
a
web
package,
but
the
nice
part
is
with
the
dev
container.
You
can
spin
up
the
entire
project,
build
it
run.
The
test,
not
worry
about
muddying
up
your
local
environment,
make
your
contribution
and
then
teardown
the
container
when
you're
finished,
and
so
this.
C
A
C
There's
a
question
in
check:
can
you
make
persistent
changes
absolutely
because
we're
a
volume
mounting
our
local
Drive?
Any
changes
you
make
are
going
to
be
saved
back
to
disk
on
localhost,
as
I
mentioned,
we
create
this
foo
file
and
this
is,
of
course,
not
valid
JavaScript,
but
just
to
prove
the
point
we.
C
C
That's
cool,
and
so
it's
really
nice
to
be
able
to
just
develop
like
this,
but
but
the
real
benefit
comes
from
the
fact
that
this
is
full
vyas
code.
Vs
code
server
knows
how
to
run
all
of
your
extensions.
If
we
have
yes
lint,
if
we
have
any
of
our
extensions,
if
we
want
to
install
more
extensions,
we
can
do
that
we'll
notice
here
and
in
the
extensions
tab
they're
showing
me.
C
Extensions
of
course,
work
as
you'd
expect.
The
other
thing
there's
a
you
know,
a
big,
a
big
one
for
most
developers
is
the
debugger
as
you'd
expect.
We
can
just
you
know,
because
we
were
passing
the
port
through.
We
can
just
go
refresh
our
page
and
hit
breakpoints
like
you
would
expect,
because
again
the
vs
code
server
is
literally
running
in
that
docker
container,
and
so
it
connects
to
the
debug
port
locally,
as
you
would,
if
you
were
just
running
locally
and
then
passes
all
the
debug
information
through
yeah.
C
C
And
once
you
build
once
connecting
is
super
fast
and
so
I
can
I
can
reload
the
window.
It's
gonna
restart,
be
s
code,
reconnect
to
remote
and
you'll,
see
it's
setting
up
the
dev
container
again,
but
just
like
that
it
took
maybe
three
or
four
seconds
to
you
know:
stop
vias
code
server
start
it
back
up,
connect
to
the
dev
container
and
we're
back
going
again.
What's.
C
A
A
A
C
A
Got
a
ask
if
there
are
plans
to
bring
this
to
Visual
Studio
in
some
ways
we
have
been
like
making
debugging
and
container
as
possible
for
it
like
even
back
in
2017,
we
were.
We
had
docker
tools
for
Visual
Studio,
it
has
been
evolving,
but
this
is
sort
of
a
new
approach.
That's
mostly
using
live
share,
which
I
don't
think
we
had
been
using
before
so
I
can
think
up
with
that
team.
I
suppose
unless
you
have,
if,
unless
you
have
knowledge
on.
C
Of
course,
the
the
beauty
of
trying
things
in
vs
code
first
is:
we
can
work
out
all
the
kinks
and
kind
of
get
get
feedback
very
quickly
and
then
once
it's,
you
know
good
and
stable
and
we
figured
out
what
people
like
and
what
they
don't
like,
and
then
we
kind
of
expand
them
a
crowd
across
all
of
all
of
the
family
of
products
right
but
I'm,
not
I'm,
not
super
familiar
with
the
timeline
there.
Yeah.
C
A
C
C
C
So
the
next
one
I
want
to
show
you
is
the
SSH
extension
and
so
to
connect
to
that
I'm
gonna
flip
over
and
show
you
I've
got
a
VM
running
an
adjure.
It's
a
you
know
very
standard,
Ubuntu
Linux
VM,
two
gigs
of
memory,
so
it's
kind
of
a
wimpy
machine,
but
for
the
for
the
demo,
it'll
work
and
if
you
come
down
here
to
the
bottom
left
I
showed
earlier
that
this
said
connecting
when
we
were
connecting
to
the
remote
container,
and
this
is
kind
of
your
remote
status
bar.
C
A
A
C
This
shows
where
the
config
file
actually
is,
and
so
all
there
is
to
configuring
this.
This
VM
is
a
hostname
and
a
user
and,
of
course,
to
make
the
security
handshake
work.
I
had
to
copy
over
my
my
SSH
public
key
to
the
VM,
but
I
did
that
before
we
started
and
if
you're
curious
and
you're
familiar
with
Azure
the
way
you
do
that
is
just
over
here
and
password.
C
For
me,
it's
reset
password,
but
you
just
put
you
know
your
username
and
paste
in
your
public
key,
but
I
already
did
that
ahead
of
time,
and
so
at
this
point
we
can
make
our
connection
and
it's
already
done,
but
we'll
do
it
again
for
demo
sake
this
time
we'll
do
from
the
viewlet
I'm
just
gonna
click
connect
here.
Sorry.
C
A
C
You
get
the
extension,
it
walks
you
through
creating
a
VM
on
Azure
configuring,
it
generating
your
SSH
key.
If
you
don't
have
one
yet
and
then
copying
and
pasting
it
in,
and
configuring
shutdown
and
all
those
sorts
of
things
that
said
it
doesn't
it
doesn't
just
work
with
Azure
it
works
with
any
VM.
You
might
have
any
remote
machine
it.
Then
you
had
to
be
a
VM.
You
can
kind
of
connect.
C
C
By
by
just
going
to
color
theme,
dark
visual
studio,
so
yeah,
so
we
we
connected
to
a
lost
my
window,
so
I'm
going
to
do
it
again,
who
are
connecting
all
sorts
of
to
VMs,
and
you
see
it's
again
pretty
quick.
All
it's
doing
is
creating
an
SSH
connection
in
which
it's
passing
all
of
this
information
over
and
so
now
you
see
we
are
in
vm
world.
If
we
do
our
net
version
again,
you'll
see
that
I
have
no
dotnet.
If
we
do
node
version
I
think
I
installed
one
yeah.
C
Folders
on
your
VM
you'll
notice,
none
of
my
local
files
are
here
because
we're
on
a
completely
remote
via
this
time,
if
I
wanted
to
I,
could
do
some
sort
of
file
syncing,
but
how
the
beauty
of
being
on
a
VM
is
it's
completely
separate
and
so
I'll
go
ahead
and
open.
My
home
folder
create
a
C,
I,
think
I
NPM.
C
Yes,
so
I'll
go
ahead
and
generate
an
Express
project.
Let's
make
a
demo
folder
and
I'll
just
create
a
quick
Express
project
with
the
Express
generator
and
now
the
cool
thing
again
is
where
we're
completely
remote
on
this
VM,
but
vyas
code
still
works
entirely
as
you'd
expect,
so
even
from
the
terminal.
If
I
want
to
open,
see
Orion
insiders.
Yes,
we
are.
If
I
want
to
open
a
I,
am
NOT
I
want
to
open
a
new
window
from
command
line.
C
I
can
do
that
and
it
knows
that
I
was
remote,
and
so
it's
going
to
open
another
remote
connection
with
that
folder
and
so
everything
that
you've
done
everything
you're
used
to
doing
in
vs
code.
It
just
kind
of
works
right
and
so
again
we
just
opened
a
new
vs
code
folder
in
this
context,
and
so
now
I
can
install
my
dependencies
just
like
last
time.
D
A
A
C
B
C
A
C
So
yeah,
so
so
we
installed
our
dependencies.
We
can,
you
know
f5.
Oh
this.
This
app
hasn't
convinced
configured
because
I
just
generated
it,
but
we
can.
We
can
run
at
five
on
a
node
process
and
it'll
start
our
node
process.
But
this
time
we
don't
have
a
dev
container
JSON
telling
us
that
hey
we're
mapping
these
ports,
but
we
can
still
do
port
forwarding.
C
A
C
B
A
C
So
it's
been
out
for
a
little
bit,
but
it's
still
very
new
right.
We
had
we've
been
iterating
very
fast.
It's
been
one
of
these
things.
The
community
is
pretty
excited
about
because
it's
very
different.
It
changes
the
paradigm
for
how
you
do
remote
development,
especially
there
are
certain
workflows,
like
Python
developers,
doing
ml
right.
They
need
big,
beefy
machines
or
local.
C
You
know
little
laptop
with
four
gigs
of
RAM
isn't
going
to
run
your
model
very
quick,
so
you
can
spin
up
a
VM
with
120
gigs
of
RAM,
and
you
know
64
CPUs,
and
and
do
your
development
there.
We
also
see
a
lot
of
people
who
have
specific
requirements
such
that
you
cannot
connect
to
say
the
test
database
from
your
laptop.
Only
a
domain
joined
machine
and
connect
to
the
database.
C
A
A
C
B
Amazing
stuff,
that's
great
and
I.
Think
it's
the
cool
thing
also
for
you
from
a
learning
perspective.
Is
that,
as
you
showed,
with
angular,
how
easy
it
is
to
test
out
new
technologies
as
well
or
that
we're
trying
to
install
all
these
different
Corino
prerequisites
on
your
computer
and
one
I
think
that's
it's
a
huge
win
for
people
who
want
to
test
out
ain't.
You
learn,
or
you
know
that
or
anything
else
that
they
don't
necessarily
want
install
the
dependencies
for.
That's,
that's
amazing.
It.
C
Forward
there
are
certain
project
types
that
are
hard
to
set
up.
For
example,
I
had
personally
never
tried
a
rust
app
because
I
didn't
know
how
to
set
it
up
in
the
past,
but
now
you
just
go
grab
a
a
rust,
dev
container
and
boom.
Now
you
have
a
rest
environment.
Now
you
can
go
play
same
with
go
same
with
Java.
If
there's
any
of
these
technologies
even.
A
C
B
Testing
out
beta
versions
of
things
you
don't
want
to
install
your
production
environment,
you
don't
want
to
miss
it
for
the
dev
box.
You
can
really
have
beta
container
and
turns
out
these
new
versions
of
one
like
the
law
stuff,
and
you
know,
got
it
three
coming
out.
You
might
want
to
test.
Stop
you
don't
necessarily
want
installed
on
it.
Three
on
your
major
development
machine
use
the
containerized
approach.
We
use
this
as
a
approach
to
test
out
these
new
technologies
play
some
c-sharp.
Eight
we've.
C
D
C
A
A
B
A
C
Are
nice
because
they
are,
for
the
most
part
immune
to
changes
in
the
surrounding
operating
system,
which
is
one
of
the
big
draws
them
in
the
first
place?
Is
you
can
as
long
as
you
can
build
the
image
and
start
the
container?
You
don't
really
care
what
operating
system
you're
running
on?
You
could
be
Linux,
wack,
Mac
or
Windows,
you're
you're
completely
encapsulated
from
the
surrounding
environment,
and
so
usually
for
the
most
part,
you're
you're
immune
to
any
changes
in
the
in
the
environment
as
well.
Yeah.
B
C
A
A
C
C
A
couple
of
extra
things
this
first
one
is
actually
no
longer
true.
Docker
pushed
an
update
recently
where,
as
soon
as
you
try
to
mount
a
local
volume,
they
ask
for
permission
on
the
fly,
so
you
no
longer
have
to
configure
in
advance,
but
there's
little
there's
a
there's
a
handful
of
little
gotchas
there.
We
have
specific
troubleshooting
guides
just
for
Windows,
where
you
can
go
to
docker
Docs.
C
But
in
general
that
this
this
is
more
of
a
the
first
time
you
set
up
docker
regardless
of
remote
containers.
These
are
kind
of
generic
windows
and
docker
problems
that
we've
been
working
through
beyond
promote
development,
and
once
you
get
them
sorted
out
once
you
never
have
to
worry
about
it
again
once
once
you
have
docker
running
you
know,
once
you
got
your
way
like
on
generally
your
set
from
there,
you
can
check
out
repos
build
the
container
remote
to
them.
You
can
create
your
own
docker
files.
A
C
C
Around
for
for
a
long
time,
WS
L
2
is
coming
as
well,
and
it's
going
to
make
you
know
using
docker
inside
wsl
on
Windows
even
easier
as
well
as
some
other
things,
and
if
you
think
of
WSL,
as
essentially
a
Linux
VM
running
on
Windows,
then
the
remote
extension
works
in
more
or
less
the
same
way.
When
you
connect
to
WSL
from
vs
code.
You
are
inside
of
that
Linux
environment.
Everything
that's
available.
There
is
available
to
you
envious
code
and
it
just
kind
of
bridges
the
gap,
and
so
you
don't
have
to
anymore.
C
Have
your
environment
installed
boats
on
the
windows,
side
and
the
Linux
side?
You
can
just
have
it
in
the
Linux
side
as
a
as
a
more
detailed
example
NWSL,
if
you
install
Python,
and
then
you
open
up
a
Python
project,
envious
code
will
use
the
Python
running
in
WSL
to
power
your
intellisense
to
run
the
app,
whereas
normally
you
would
have
to
have
that
installed
on
the
windows
side
to
power,
the
intellisense
and
then
you'd
be
using
the
Linux
WSL
version
to
power
the
actual
running
app.
C
And
then,
if
you
have
any
version
discrepancies
there,
you
run
into
some
weird
so
weird
setups,
and
so
this
is
nice
for
double
cell
users,
because
you
just
have
the
Oscoda
ng
in
the
same
place
that
your
code
exists,
I
could
because
I'm
on
a
Mac,
the
only
way
I
could
really
show
that
is,
if
I
showed
you
WSL
installed
on
parallels.
Okay,
let's.