►
Description
Join members from the ASP.NET teams for our community standup covering great community contributions for ASP.NET, ASP.NET Core, and more.
Community links for this week: https://www.theurlist.com/aspnet-standup-2020-07-21
A
B
A
Well,
cool,
okay!
Well,
so
you're
going
to
be
showing
us
some
fun
new
stuff
with
with,
like
you
said,
web
tooling,
so
that's
awesome.
Let's
jump
in
I've
got
js
out
in
the
description
and
in
the
chat.
If
you're
watching
on
youtube
or
twitch,
so
don't
worry,
I
will
send
them
on
over,
and
so
here
we
go.
A
The
first
one
is
there's
a
new
release
of
b
unit
out.
This
is
really
cool
b
unit,
just
in
general,
is,
is
a
cool
project
that
makes
it
easier
to
do
testing
and
some
kind
of
more
advanced,
specific
testing
for
blazer.
So
I
mean,
of
course
you
can
always
write
your
standard
unit
tests,
but
but
this
is
specific
and
built.
A
You
know
to
work
well
with
blazer,
so
it's
cool
so,
for
instance,
things
like
working
with
js,
js,
interop
and
stuff,
also
cool
to
see
like
there's
some
cool
interaction,
simon
crop
has
been
working
and
contributing
to
some
of
these
unit
testing
frameworks
with
interaction,
and
so
that's
really
cool
too.
So
excellent
news,
and
thanks
thanks
ego
for
sending
me
the
link
to
that
all
right.
So
this
is
a
fun
one.
So
marin
sent
me
this
link.
This
is
for
blazer
monaco,
so
monaco
is
monaco.
A
Editor
is
the
editor
that
powers
vs
code.
It's
also
it's
a
web-based.
It's
a
web-based
editor
and
you
know
I've
played
with
it
over
the
years
and
one
thing
is
over
time:
it's
gotten
pretty
involved
to
set
up
and
get
running
to
actually
like
get
the
javascript
and
to
get
everything
integrated.
I
played
with
this
over
time
and
it
was.
It
was
more
difficult
than
I
thought
so
this
is
really
cool
to
see
this
built
in
a
way
that
can
be
plugged
right
in
via
laser.
A
So
you
get
this
cool
blazer
and
I'll.
Just
pop
over
he's
got
a
live
working
demo
here,
and
so
I
mean
you
know
like
it's:
it's
got,
you
know
it's
got
intellisense,
you
know
pretty
pretty
neat
stuff,
so
so
this
is
and
you'll
see
even
over
on
the
right.
We've
got
the
I
forget
what
this
is
called,
but
it's
got
the
zoom
thing
where
it
shows
the
you
know
the
thumbnail
version
of
the
code.
You
can
add
values
and
get
values.
A
It's
got
different
theme
support,
so
I
I'm
pretty
excited
to
see
this.
This
is
this
is
really
neat
and
if
you
need
to
use
any
kind
of
integration
with
a
code
editor,
this
seems
like
a
really
cool
thing
to
to
start
with
excellent.
So
thanks
for
sending
that
one
over
okay,
so
this
this
is
kind
of
neat.
This
is
asp.net
team.
A
Specifically,
the
blazer
team
did
a
sprint
last
week,
and
this
was
designed
for
people
to
get
involved
and
work
on
pull
requests
and
they
would
work
directly
with
somebody
on
the
team
that
would
help
them
with
it.
So
I'm
starting
by
linking
to
the
asp.net
on
twitter,
if
you're
on
twitter
you're,
not
following
asp.net.
What
are
you
doing?
You
got
to
follow,
follow
asp.net
on
twitter,
that's
also
where
we
share
out
community
links
and
things
like
that.
But
this
is
this
is
how
it
was
announced
and
here's
the
information
for
the
sprint.
A
So
this
this
was
their
first
one.
I'm
sure
they'll
be
tweaking
things
over
time,
but
they
had
a
forum
where
you
could
sign
up
to
join.
They
had
you
know,
here's
how
you
can
get
prepared
for
it,
so
that
people
could
jump
in
and
be
already.
You
know
ready
to
go
and
then
here's
the
things
pretty
well
documented
how
to
submit
a
pull
request,
and
here
are
some
of
the
issues
that
they
had
available
as
well
as
mentors
to
help
work
with
them.
A
A
Okay,
so
rick
shared
this,
and
I
thought
this
is
interesting.
I
actually
hadn't
seen
this
before.
I
saw
this
post
so
there's
azure
static
web
apps.
So
there's
you
know,
there's
there's
the
azure
web
apps
support
or
azure
app
service.
That's
that's
been
available
for
a
while,
then
there's
static
website
hosting
in
azure
storage
and
that's
where
you're
just
storing
static
files-
and
this
was
you-
know,
semi-recently
released
where
they
added
in
support
for
like
actually
serving
files
and
functioning
as
a
static
server.
A
However,
there
are
some
things
that
it
does
not
support.
So
it's
it
is
literally
like
just
serving
static
files,
and
so
this
new
support
for
static
web
apps
is
kind
of
an
integration
of
several
different
things,
so
integration
with
better
ci
cd
integration
with
support
for
azure
functions,
and
so
the
idea
is
it's,
it
is
still
you
know
it's
not
full
on
web
server
support,
but
it
is
a
slightly
more
advanced
static
web
app.
A
So
this
is
something
I'm
going
to
need
to
play
with
it,
but
it
does
look
like
something
where,
if
you
have
wanted
to
do
something-
and
you
need
a
little
bit
more
support
like
support
for
https
or
cores
or
something
like
that
or
you
want
better
integration
with
functions,
this
seems
pretty
exciting
to
take
a
look
at
so
all
right.
This
is
just
you
know,
to
check
back
in
on
this
few
weeks
ago.
A
We
had
sebastian
ross
on
and
he
showed
a
lot
of
demos
with
crank
and
cranks
the
infrastructure
that
they
use
for
testing
performance
and
all
the
benchmarking
and
all
that
kind
of
stuff.
So
he
showed
off
a
lot
of
examples
of
it
and
it
wasn't
yet
open
sourced
out
on
github,
and
now
it
is
so.
You
can
take
a
look
at
this.
A
There's
also
some
really
good
support
in
here
and-
and
he
talked
through
this
during
the
during
his
demos-
that
you
could
use
this
for
benchmarking,
your
own
applications
and
you
could
set,
you
know,
triggers
and
all
kinds
of
things
where
you
could.
You
could
observe
your
applications
running
in
a
test
benchmark.
You
know
environment,
and
so
this
this
seems
really
exciting
for
that
sort
of
stuff.
As
well
and
neat
that
you
can
deploy
it
all.
A
A
You
know
it's
very
kind
of
one-off
and
very
kind
of
learning
how
to
make
how
to
build
these
high-performance
networking
things
in
net,
and
so
now
this
is
kind
of
codified
into
these
abstractions.
So
this
is.
This
is
a
you
know
the
published
thing
out
on
github
and
and
it's
exciting
to
see
this-
you
know
see
this
out
there
so
stuff
all
right.
A
Now
we
get
into
web
dev
features
and
we'll
probably
dig
deeper
into
these
when
we
talk
to
you
syed,
but
here's
here's
some
of
the
stuff,
so
a
new
post
out
last
week
on
enabling
experimental,
razer,
editor
and
visual
studio.
So
this
is,
this
is
a
feature
where
you
can
go
and
turn
this
on
in
visual
studio
windows,
16,
7
preview
for
and
later
so
going
into
the
preview
features.
I'm
I'm
a
nut
for
this
stuff.
I
go
and
turn
them
all
on.
A
You
know,
but
it's
cool,
and
so
this
is
some
interesting
stuff
about
the
razer
editor
and
you
know
how
the
how
they've
worked
to
get
this
set
up
and
integrate
with
the
razer
language,
server,
etc,
and
I
think
we're
going
to
try
and
show
some
of
this
when
we
bring
you
on.
So
I'm
not
going
to
go
deeper
than
that,
and
then
these
are
two
other
links
that
you
sent
me.
A
B
A
B
A
B
And
you
know
I
am
running
some
kind
of
daily
builds
here,
so
if
we
do
run
into
any
issues,
you
know
I'm
definitely
gonna
blame
it
on
that.
So
yeah
so
john
already
talked
about
the
the
link
for
web
live
preview.
Here
for
the
v6,
let
me
just
let
me
open
up
a
new
browser,
tab
I'll
navigate
to
that
link.
Let's
go
take
a
look
at
this.
B
B
B
You
know,
even
in
you
know,
for
some
cases,
users
may
have
you
know
either
permanent
or
temporary
disabilities,
but
you
know
we
want
to
make
our
product
where
everybody
can
use
it,
no
matter
what
their
situation
is
right
and
with
web
forms.
In
particular,
we
did
have
a
really
big
problem
with
accessibility
with
respect
to
the
web
forms
designer,
so
so
so
web
live
preview
is,
is
our
attempt
to
basically
kind
of
replace
the
web
forms
designer,
but
we're
also
we're.
B
That's
called
browser
link
there
and,
and
also
page
inspector
really
so
for
for
people
who
remember
browser,
lick
and
page
inspector
web
live
preview
is
kind
of
a
combination
of
those
two
things
currently,
but
then
we're
going
to
kind
of
beef
it
up
to
to
add
a
bunch
more
support
there
and-
and
you
know,
I
do
have
some
some
kind
of
mock-ups-
that
I
wanted
to
show
too.
If,
if,
if,
if
that's
interesting
for
the
viewers
here.
A
B
But
yeah,
why
don't
we
get
through
the
the
web
live
preview
and
I'll
give
kind
of
a
demo
of
what
we
have
and
then
we
can
go
through
the
the
mock-ups
and
whatnot,
but
I
was
gonna
point
out
that
you
know
after
you
download,
there's
also
more
information
at
this
link
here.
Basically,
this
is
a
blog
post
that
we
put
together
when
we
released
the
web
live
preview.
B
B
I
think
so
let
me
go
into
views,
and
so
now
we
can
see
that
I've
got
my
views
here
and
actually
you
know
what
let
me,
let
me
go
back,
I'm
going
to
create
a
new
I'm
going
to
create
a
new
mvc
project
here.
Now
that
I
remember,
I
think
there
might
be
an
issue
with
this
particular
project
that
I
created
so
yeah.
Let
me
go
through
and
create
one
mvc
project
here
as
well.
B
Just
one
second
here:
okay
just
need
to
make
sure
I
pick
the
right
one
there
we
go
great
so
yeah.
If
you
have
any
problems
with
it
or
any
issues,
definitely
do
let
us
know
about
that,
because
we
want
to
make
sure
that
we
we
get
a
nice
solid
release
before
we
go
ga
here,
but
we
definitely
have
a
lot
of
plans
to
add
a
bunch
more
functionality
to
this
as
well-
and
you
know,
like
I
said,
we're
going
to
get
into
that
so
yeah.
B
But
I'll
show
you
how
we're
planning
on
streamlining
that
in
the
future
as
well,
when
we
get
to
the
mock-ups
portion
of
this
okay,
so
I've
got
my
mvc
project
created
here,
I'm
just
going
to
go
to
the
to
the
about
page
here.
So
what
I'll
do
is
I'm
going
to
right
click
on
this
about
page
we
can
see
oops.
I
think
it's
still
kind
of
initializing.
B
B
A
B
B
So
we
can
see.
I've
got
edit
and
browser
here.
So
I'm
going
to
select
that-
and
this
should
fire
up
a
browser
window
for
me,
hopefully
on
the
same
screen
that
we're
looking
at
otherwise
I'll
drag
it
over
yeah.
Okay,
all
right,
so
it
pops
up
on
the
other
screen.
Let
me
bring
it
over
here,
so
we
can
all
see
it.
B
B
So
now
we
can
see
I'm
in
the
the
about
page
here
and
if
I
bring
my
mouse
over
an
element,
you
can
see
it's
highlighting
that
element
and
then
it
actually
is
supposed
to
be
opening
the
source
over
here.
But
my
machine
is
just
running
terribly,
so
I
apologize
I'm
not
sure.
What's
going
on
with
this
machine
here,
yeah
there,
it
is
okay,
yeah,
so
yeah
exactly
so.
B
The
idea
is
that
you
know
you
kind
of,
let's
say:
let's
say:
you're
you're
browsing
your
app
here
and
then
you
found
some
sort
of
an
issue
here.
Let's
say
my
asp.net
application
and
then
you
wanted
to
you
wanted
to
change
that.
So
it'll
take
you
right
to
the
to
the
code
here
and
then
we
can
just
go
ahead
and
start
changing
that
directly.
We
can
see
the
the
changes
are
coming
in
the
browser
directly
as
well
yeah.
B
So
that's
that's
kind
of
the
the
high
level
of
it,
but
let
me
show
you
some
some
kind
of
additional
functionality
that
we
have
here.
So
why
don't
I
take
this
browser?
I'm
gonna
make
it
smaller.
Here
I
wanna.
I
wanna
show
you
a
few
things
here.
Some
additional
features
that
we
have
that
we
haven't
really
talked
too
much
about
here.
B
Let's
make
a
new
tab,
a
new
window
I
mean
so.
Okay,
that's
fine!
All
right!
Let
me
get
that
same
url
here
and
paste
it.
So
you
can
imagine,
let's,
let's
say,
you're
developing
an
app
that
that
needs
to
work
on.
You
know
multiple
diff,
multiple
different
device
sizes
here
right.
So
so,
when
I'm
using
my
multiple
monitors,
you
know
I
could
set
up
various
different
browsers
here
with
different
sizes
and
then
and
then
we'll
see
that
the
refresh
gets
pushed
automatically
to
all
the
different
browsers.
B
That's
really
what
I'll
be
showing
you
here
today
or
during
this
during
this
demo,
I
mean
all
right
so
now,
let's
go
and
start
editing
editing
this,
and
we
should
see
both
of
these
pages
kind
of
lighting
up.
Okay,
this
one's,
not
lighting
up
here.
Okay,
for
some
reason!
Well,
you
know
it
is
in
preview,
but
not
sure
why
this
guy's
not
working
good
today.
For
some
reason,
let
me
save
it
again
and
then
I
can
do
see
you
doing
it's
even
telling
me
that
it's
up
to
date
and
then
I
was.
B
Needs
update,
it's
pretty
strange
yeah.
We
got
to
some
funny
behavior
here
you
know
but,
like
I
said
you
know,
I'm
running
a
a
daily
build
here.
Let's
try
it
one
more
time.
Now,
let's
try
to
get
rid
of
all
the
twos
and
notice,
I'm
not
even
saving
the
file
here
right.
You
know
you
can
see
it
might
be
hard
to
see,
but
there's
an
asterisk
here
that
the
the
file.
A
B
Been
saved
one
more
time,
all
right
file
has
now
been
saved,
so
we
can
see
that
okay
great
now,
let
me
show
you
some
some
additional
kind
of
features
that
we
have
here.
We
also
have
a
a
css,
auto
sync
here,
basically-
and
I
think
this
part
is
pretty
cool
too
so,
let's
say
you're
working
on
your
application
and
you
know
you've
got
the
the
different
sizes
loaded
up
in
your
browsers
here,
and
you
just
want
to
kind
of
play
around
with
your
css
here.
B
Let's
get
a
background
color
to
to
red
here
we
can
see
as
I'm
kind
of
typing
here
it's
automatically
getting
updated.
Let's
pick
a
different
color
here,
purple,
so
so
yeah.
This
is.
This
is
what
we
call
css
auto
sync
here.
So
I
think
this
is
really
great
for
for
when
you're
developing
your
css,
especially
when
you've
got
a
bunch
of
media
queries
here,
you
can,
you
can
have
all
the
browsers
with
the
right
sizes
set
up.
You
know
the
the
edge
web
developer,
tools
and
chrome
developer
tools.
B
B
A
B
Yeah
yeah,
absolutely
that's
right,
yeah,
correct
great
question!
So
yeah
here
you
know,
I'm
just
showing
you
know
just
straight
up
css
files,
but
if
you
were
using
less
or
sas
you
know,
we've
got
the
the
source
maps
for
that
information.
So,
as
you
change
those
last
and
sas
files,
those
changes
would
also
be
pushed
to
the
browser
immediately
immediately
as
well
yeah.
So
that's
that's
absolutely
correct.
Yeah,
great
question
there
and
a
couple
other
things
to
kind
of
point
out
here.
B
We
we
also
have
it's
kind
of
like
almost
like
a
tag,
navigator
type
of
thing.
So
let's
say:
if
you
wanted
to
figure
out
where
the
where
the
footer
itself
was
at,
you
know
you
can
select
here
to
go
right
to
that
location
or
if
you
wanted
to
go
back
to
any
particular
element
there.
You
can
use
this
to
to
navigate
to
items
that
you
may
not
be
able
to
see
on
the
screen
itself
and
then
there
there's
also
like
a
little
status.
B
Slash
button
over
here.
So
sometimes
this
will
say,
needs
update
or
up
to
date
and
then
the
cases
where
it
says
needs
update.
You
can
click
on
this
to
to
push
an
update
to
to
all
the
browsers
that
are
currently
connected
all
right.
So
that's
the
idea
there
should.
I
show
some
some
mock-ups
that
I
have
for
ideas
of
things
that
we're
working
on
and
yeah.
A
B
B
B
We're
gonna
work
on
some
of
these
things,
but
you
know
some
of
the
other
things
we
may.
We
may
or
may
not
work
on
these
things.
So
this
is
not
like
any
type
of
commitment
for
what
we
will
be
doing
here,
but
but
instead,
just
just
showing
some
ideas
of
of
what
may
happen.
But
you
know
some
of
these
things
might
never
happen.
B
Let
me
just
give
a
second
for
the
for
the
slideshow
to
start.
Can
you
see
the
the
slides
pretty
good,
got
it:
okay,
gotcha,
okay,
yeah!
So
basically
one
thing
that
one
thing
that
I
don't
like
about
the
current
kind
of
interaction
with
with
web
live
preview
is
that
you
know
users
have
to
explicitly
go
out
and
click
on
a
view
and
say
edit
and
browser
right.
B
So
you
know
what
what
we,
what
we
strive
to
do
is
actually
try
to
meet
the
user
where
they're
at
you
know,
and-
and
you
know,
people
don't
have
to
learn
about
special
gestures
and
and
all
that
sort
of
stuff
right.
So
so
the
edit,
the
right
click
edit
in
browser
is
definitely
not
ideal.
So
what
we
would
like
to
try
and
do
is
basically
come
up
with
a
way
that
we
can
make
this
functionality
visible
as
users
perform
their
normal
every
day-to-day
activities
like
control,
f5
or
f5.
B
B
B
So
you
can
just
enable
inspect
mode,
it'll,
bring
you
right
to
the
code
and
then
you
can
go
ahead
and
make
your
edit
and
see
it
live
in
the
browser
and
then
kind
of
continue
on
your
way
and
then,
in
addition
to
you,
know
entering
the
the
inspect
mode.
We
also
need
some
sort
of
a
way
for
for
people
to
to
to
exit
the
inspect
mode.
So
there'll
be
some
sort
of
a
gesture
there
in
that
menu,
and
you
know,
obviously
with
with
every
feature
that
we
create.
B
So
I
mentioned
a
project
property
and
or
like
a
tools
option
to
disable
that
here's
another
thing
and-
and
I
think
this
is
one
of
the
features
that
we'll
probably
be
working
on
sooner
rather
than
later-
is
just
a
simple
text
edits
in
the
browser,
and
this
kind
of
goes
on
just
with
kind
of
you
know,
enabling
developers
to
be
a
little
bit
more
productive
as
they
develop
their
app.
You
know.
A
Yeah,
that's
that's
nice.
I
mean
it's
definitely
there's
sometimes
where
I'm
in
html
code
mode
and
I'm
thinking
about
html,
but
sometimes
when
you're,
when
you're
editing
content
on
a
page,
nothing
beats
being
able
to
just
interact
directly
with
it
and
a
lot
of
times
in
the
past.
I
would
go
into
my
browser
tools,
edit
in
browser
tools
and
then
bring
all
those
changes
back
over
to
visual
studio.
So
this
is
really
nice.
Productivity-Wise.
B
That's
right,
that's
right!
So
yeah
exactly
and
you
know
some
people,
they
ask
me
they
say
hey
well,
you
know
if
the
user's
got
the
visual
studio
ide
already
opened
and
and
when
they
select
on
the
text
and
if
it
opens
in
the
ide,
what's
the
benefit
of
of
having
the
simple
text
edits
in
the
browser
right
so
so
the
benefit
is
the
the
context.
B
You
know,
you're
you're
you're,
viewing
your
app
and
you
know
you're
not
really
trying
to
you
you're
trying
to
work
on
your
app.
You
notice
a
minor
problem.
You
just
want
to
fix
it
right
away
without
interrupting
whatever
it
is
that
you
are
actually
trying
to
do
there.
So
you
know
yeah,
maybe
maybe
it'll
only
save
five
or
ten
seconds,
but
but
you
can
still
focus
on
what
it
was
that
you're
actually
trying
to
do
as
opposed
to
oh,
let
me
forget
about
what
I
was
trying
to
do.
B
Let
me
fix
this
real,
quick
and
then
come
back
to
it.
So
so
that's
the
that's
the
kind
of
ideas
you
know.
Let's
make
it
so
simple
that
you
can
just
make
a
quick
change,
but
then
kind
of
continue
on
with
whatever
task
it
was
that
you
were
actually
trying
to
perform,
and
then
you
mentioned
you
mentioned,
you
used
the
the
browser
developer
tools
there,
so
that
was
kind
of
a
good
segue
for
my
next
slide
here.
B
B
Here
too,
the
idea
is
that
you'd
be
able
to
edit
your
your
css
source
code,
and
you
mentioned
the
monaco
editor,
so
that
was
what
I
was
initially
kind
of
starting
off.
With
was
that
you
know
we
would
kind
of
embed
the
monaco
editor
within
the
browser
itself
and
then
users
could
edit
their
css
files
directly.
B
But
since
then,
you
know
I've
been
thinking
about
this
a
little
bit
more
and
gotten
some
feedback.
I
think
what
we
can
do
is
actually,
instead
of
using
an
editor,
that's
embedded
in
the
browser.
What
we
can
do
is
actually
just
pop
pop
open.
Another
visual
studio
editor
here
directly,
underneath
the
browser
that's
even
kind
of
attached
to
it.
So
that's
that's,
probably
more
the
direction
that
we'll
be
going
in.
I
think
the
benefits
of
that
is
you
get
the
same
exact
experience.
B
Oh
yeah
sure
sure
sure
yeah
right
exactly
so.
The
difference
is
the
difference.
Is
you
can
you
can
play
around
with
your
css,
get
it
into
a
state
that
you
want
and
then,
when
you
close
it,
those
changes
will
automatically
be
in
visual
studio
for
you.
So
you
don't
have
to
worry
about.
Oh,
what
were
the?
What
were
the
five
or
six
different
styles
that
I
modified
in
the
developer
tools,
and
how
do
I
push
those
back
to
visual
studio?
So
that
would
be
the
the
idea
here.
A
B
Right
right,
right,
yep,
so
that's
the
idea
here
and
then
also
the
the
same
kind
of
comment
about
the
undo
buffer.
So
let's
say,
if
you
made
like
five
or
six
different
changes
here,
you
can
always
go
back
to
visual
studio
to
kind
of
undo
your
way
out
of
some
of
those
changes,
if
you,
if
you
needed
to
okay
yeah,
so
that's
that
is
pretty
much
that
that's
pretty
much
the
most
of
what
I
had.
B
A
B
After
that,
I
think
we're
going
to
start
focusing
on
some
web
forms
functionality
there
to
to
to
replace
the
web
forms
designer
and
then
and
then
also
continue
working
with
the
asp.net
core
team
to
get
support
for
asp.net
core
for
this,
and
so
I
think
what
we'll
do
is
probably
we're
gonna
work
on
a
way
to
to
actually
be
able
to
kind
of
design
your
app
in
the
browser
itself
as
well.
So
you
can
imagine
there'll
be
like
a
toolbox
and
a
properties
pane
in
the
browser
itself.
A
B
That's
right:
that's
right,
yeah!
So
I'm
not
sure
if
the
the
the
viewers
are
familiar,
but
the
the
web
form
designer
is
actually
very
kind
of
old
code
and
it's
it's
almost
impossible
for
us
to
make
that
accessible,
but
but
now
that
we
now
that
we
can
create
this
new
effort,
you
know
we'll
be
able
to
make
that
fully
accessible.
So
that's
the
that's.
The
end
goal
there
for
that.
A
B
B
A
A
B
A
Absolutely,
but
before
we
do
that,
we
had
a
question
in
twitch
and
the
question
was
do
when
you
save
changes,
you
were
showing
the
css
editing
in
the
browser,
and
you
showed
two
different
things
and
one
is
with
the
browser
tools
and
the
other
was
with
the
kind
of
pop-up
and
they
were
asking,
which
does
that
save
changes
back
to
visual
studio.
So
my
understanding
from
what
you
were
saying
was
the
the
kind
of
pop-up
overlay
would
change,
save
those
changes
back
to
visual
studio.
A
B
B
You
know
why
did
you
change
the
the
default
behavior
that
I've
been
using
forever
so
so
that
is
something
that
I'm
interested
in,
but
I
just
haven't
figured
out
what
is
the
right
way
to
actually
surface
that
functionality
in
a
way?
That's
not
going
to
be
frustrating
to
a
lot
of
users
there.
You
know.
I
know.
A
Yeah,
okay,
I'm
kind
of
remembering
with
browser
link,
and
then
there
was
like
browser
sync
or
something
like
that,
and
there
was
a
checkbox
you
could
turn
on
and
it
would
sync
them
back
and
forth.
Personally
now,
I'm
I'm
maybe
an
oddball.
I
really
love
my
browser
tools,
and
so
I
would
I
mean
if
you're
taking
votes
or
whatever.
A
B
Yeah
yeah
so
so
yeah.
I
think
it
would
be
great
to
hear
in
the
comments
from
the
community
on
that
as
well.
You
know
so
yeah
yeah,
definitely
so
so
yeah.
I
think
I
think
we
could
definitely
take
a
look
at
editing,
adding
some
sort
of
a
checkbox
to
to
push
changes
back
to
visual
studio
and
then
maybe
another
idea
that
I
could
come
up
with
was
you
know?
B
B
A
A
B
Right
right,
yeah,
exactly
perfect
man,
I
was
going
to
show
you
some
some
updates
to
some
css
media
queries
that
we
have
made
here.
I
was
gonna.
I
was
gonna
fire
up
a
older,
an
older
version
of
the
visual
studio,
so
we
can
do
like
a
side
by
side.
We
compare
what
we
had
before
versus
what
we,
what
we
will
have
soon
so
yeah
these
these
media
query
updates
that
I'll
be
showing
are
not
are
not
available
quite
yet
for
users,
so
yeah
this.
B
B
B
B
B
B
So
what
we
decided
was
you
know
it's
it's
too
difficult
to
to
try
to
keep
up
with
the
devices
with
specific
devices
here,
not
not
only
from
a
css
snippets
perspective,
but
also,
I
think
you
know,
from
a
web
developer
perspective.
You
know,
I
think
I
think
in
the
past
I
think
you
know.
A
few
years
ago
people
were
were
trying
to
target
specific
devices
with
their
media
queries,
but
not
so
much
sorry,
not
too
much
anymore.
B
I
think
I
think
what
I
think,
what
more
users
are
doing
is
actually
just
defining
certain
break
points
in
their
css
now
and
then
just
using
those,
because
you
know
there's
a
plethora
of
devices,
that's
out
there
and
you
know
every
day
or
every
week
there's
new
devices
that
are
kind
of
getting
getting
rolled
out.
So
so
it's
not
possible
really
to
create
a
website
that
supports
you
know
different
devices,
but
instead
you
know
it's
it's
easier
to
just
try
to
figure
out
what
sizes
that
you're
trying
to
to
support
here.
A
Yeah
yeah,
you
know
this
is
bringing
back
memories
too
of
like,
and
I
know
with
both
mvc
and
web
forms.
You
know
before
even
dot
net
core.
We
had
like
device,
specific
views
and
and
all
that
kind
of
stuff
and
totally
agree.
It
was
back
back
in
the
day
it
was
like
hey,
I
feel
like
we
were
then
kind
of
new
to
supporting
devices
and
and
after
a
while,
it's
like
man,
I'm
too
like
I.
I
got
better
things
to
do
than
chase
down
every
individual
device.
You
know
and
try
and.
B
B
For
example,
right
I
got
iphone
5,
which
is
going
to
give
me
the
the
kind
of
base
media
query
and
then
I
have
a
separate
one
for
landscape,
and
then
you
had
a
separate
one
for
portrait
here
and
then
you
know.
In
addition,
you
know
I
can't
really
see
the
full
list.
I
have
to
scroll
this
list
to
figure
out
if
it's
got
the
device
or
the
size
that
I'm
looking
for
here
right.
So
so
what
we've
decided
to
do
is
really
just
try
to.
B
B
A
B
Sure
sure
sure
no
problem
yep
better
yep,
okay,
great
so
so
yeah
one
one
kind
of
so
not
only
were
the
devices
old,
the
list
was
getting
pretty
long.
We
had
three
entries
per
device,
but
we're
also
using
things
that
are
no
longer
best
practice
from
a
css
perspective
right.
So
you
can
see
here
that
we're
using
men
min
device
with
and
then
also
max
device
width
here.
So
you
know
over
the
past
couple
of
years.
B
A
B
Right,
that's
right!
That's
right!
That's
right
and
then
you
know
also
the
the
mdn
and
w3c
you
know
they're
they're
recommending
to
stay
away
from
device
with
from
now
on.
So
that's
another
reason
why
we're
getting
rid
of
this?
Okay.
So
on
the
on
the
left
side
of
my
screen,
you
can
see
the
the
kind
of
new
experience
you
can
see
it's
much
simpler.
We
just
have
four
media
queries
here.
B
The
media
one
is
just
kind
of
a
very
basic
media
query
here,
not
for
any
kind
of
particular
device
or
anything
it
just
just
creates
you
a
kind
of
a
basic
media
query
and
then,
let's
say
if
I
was
trying
to
target-
let's
say
a
phone
here,
because
that's
the
example
that
we
used
on
the
on
the
right
side.
I
can
go
into
phone
here
and
do
tab
tab,
and
then
we
can
see
that
I
get
all
my
I
get.
I
get
those
three
media
queries
generated
automatically.
A
B
B
We
can
we
can
see
now
it's
got
my
max
width
selected
here.
So
let's
say
if
I
needed
to
change
that,
let's
say
a
thousand
and
if
I
tab
I'll
get
to
back
to.
Oh,
maybe
I
have
a
book
here.
Actually
you
know
what
okay
so
yeah.
I
got
a
bug
here.
So
in
my
when
I
created
the
snippet,
I
had
it
this
one
for
max
with,
but
then
I.
B
A
B
A
B
But
let's
do
it
one
more
time
for
the
viewers
here
so
yeah
we'll
do
dash
media
go
down
to
the
one
that
we
want.
Let's
try,
the
the
tablet,
one,
this
time
tab
tab
to
invoke
the
snippet.
We
can
see
now
I'm
on
max
with,
but
this
has
the
same
bug
as
the
previous
one,
but
we'll
see
we'll
see
these
three
seven
six
eight
change
here
so
we'll
see
1200
px
and
then,
if
I
hit
enter
here,
I
don't
know
actually
I
should
have
hit
hey.
B
I
should
have
hit
tab
to
go
to
the
next
one,
but
that's
fine,
but
yeah.
We
can
see
that
that
it
was
applied
to
to
all
those
areas
where
that
number
was
applied,
yeah
so
yeah,
that's
the
idea
and
then
kind
of
like
what
you
mentioned.
You
know
this
is
not
specific
to
css,
but
but
also
c-sharp
files
have
a
lot
of
snippets
and-
and
it's
also
relatively
easy
to
create
your
own
snippets
and
and
have
those
as
well.
A
B
There's
a
there's
a
good
amount
of
them.
I
wouldn't
say:
there's
like
an
exhaustive
list
of
snippets
here,
but
but
yeah
there's
there's
a
good
amount
of
snippets
that
we
have-
and
this
is
also
an
area
that
I'll
probably
be
going
to
take
a
look
at
all
the
existing
css
snippets
that
we
have
to
make
sure
that
they're
they're
all
up
to
date
with
the
current
recommended
best
practices,
yeah.
B
After
we
get
through
that,
then
I'll
be
looking
to
to
add
some
additional
snippets
as
well
so
yeah
for
any
any
of
the
viewers.
If
they
have
ideas
for
snippets,
definitely
send
them
my
way,
either
in
the
comments
or
on
twitter
or
or
wherever.
Basically
right,
you
can
also
do
help
provide
a
suggestion
in
visual
studio
to
send
those
suggestions
to
us
as
well.
B
B
B
A
B
But
then,
after
that,
we
can
take
a
look
at
features
like
emmett
and
and
and
other
things
here.
Yeah
and
the
idea
behind
this.
This
razer
language
server
here
is,
is
so
let
me
kind
of
explain
how
it
would
work
in
the
past
and
and
what's
different
about
this
right.
So
in
the
past
we
had
two
different
teams
involved.
Here
we
had
the
asp.net
runtime
team,
then
we
had
the
visual
studio,
tooling,
team
right
and
and
the
the
editor
portion
was
really
owned
by
the
visual
studio
web
tooling
team.
B
You
know
this
this
this
this.
This
would
kind
of
slow
us
down
a
little
bit,
because
you
know
the
asp.net
team
would
would
implement
some
sort
of
a
new
feature
and
then
they'd
want
support
in
visual
studio
and
then
they'd
have
to
come
and
talk
to
us
and
then
then
we'd
have
to
schedule
that
and
then
and
then
and
then
implement
that
right.
B
So
now,
with
the
with
this
new
razer
language,
server
we're
using
it's
using
that
same
exact
model
of
the
of
the
lsp
model,
as
they
call
it
right
and
and
then
we'll
be
able
to.
The
asp.net
team
will
be
able
to
embed
this
editor,
not
only
in
the
visual
studio,
but
also
in
the
visual
studio.
Sorry,
not
only
in
the
visual
studio,
but
also
into
visual
studio
code,
and
it
would
also
be
feasible
to
to
plug
these
into
a
visual
studio.
B
B
But
some
things
oops
yeah
see
so
it's
a
little
bit
slower
then,
but
obviously
we'll
be
working
on
the
the
performance
of
this
as
well.
Let
me
take
a
look
at.
I
don't
have
too
much
stuff
in
this.
This
is
just
a
regular
kind
of
dummy
project
that
I
just
created
here.
So
there's
not
really
a
whole
lot
here,
but
yeah.
Let's
take
a
look
at
editing.
Some
some
c-sharp
here
as
well.
B
But
with
that
being
said,
you
know
visual
studio,
2019.
We
we
will
actually
be
building
on
top
of
this
editor.
For
for
some
particular
things,
you
know
like,
let's
say
the
the
css
color
picker,
those
types
of
things
and
then
and
then
completions
for
for
local
resources.
You
know
like
let's
say
if
you
have
an
img
tag
and
you
do
src
it
will.
It
will
provide
you,
those
completions,
so
yeah
so
basically
we'll
take
that
we'll
take
the
the
experience.
B
A
Cool
so
that
moves
all
the
I
mean
summarizing
what
I'm
hearing
here,
but
that
moves
the
ide
specific
coding
out
and
it
really
just
kind
of
says:
hey.
I
support
language
server
protocol
and
then
now
you
can
implement
that
in
in
whatever.
But,
like
you
know,
in.net
core
or
whatever
kind
of
thing
you
can
separate
that
out
and
then
anything
that
speaks
that
language
server
protocol
can
provide
that
those
features
and
the
the
completions
and
stuff.
B
Dude,
nice,
so
yeah,
that's
pretty
much.
The
idea
here
and-
and
these
are
these
are
the
kind
of
things
that
the
the
team
is
really
kind
of
working
on
right
now,
so
we're
taking
the
the
css
editor
and
we're
we're
going
to
do
an
lsp
for
that
and
and
the
the
json
editor
will
do
an
lsp
for
that
one
as
well,
and
and
then
eventually
just
share
these
editors
across
all
the
different
ides
and
editors
that
we
own
yeah.
That's
the
idea
here
and.
B
A
A
You
mentioned
several
ways
for
people
to
keep
up.
I
mean
there's,
there's
the
blog
that
asp.net
blog
there's,
which,
like,
for
instance,
that's
where
the
announcement
was
of
the
preview,
eraser
support
and
then
there's
asp.net
on
twitter.
I
guess
and
then
also
like,
of
course
you
on
twitter.
When
you
know
people
can
reach
out
to
you
anywhere
anywhere
else.
People
should
be
looking
to
keep
up
with
these
changes.
B
I
think
for
for
getting
notified
of
changes.
I
think
you
kind
of
mentioned
all
of
them
there
so
yeah
on
twitter.
You
know,
there's
there's
not
only
you
know,
people
like
yourself
and
me,
there's
also
a
visual
studio
account
and
there's
also
an
asp.net
account.
So
those
are
those
are
good
things
to
follow.
I
believe
for
for
kind
of
being
alerted
about
new
features
with
respect
to
giving
feedback.
B
You
know
we,
we
have
a
lot
of
avenues
for
for
feedback,
and
you
know
twitter
is
obviously
one
of
them.
So
if,
if
people
prefer
to
send
feedback
over
twitter,
you
know
we're
definitely
happy
to
engage
there.
Also.
Another
kind
of
avenue
is
the
built-in
support
that
we
have
in
visual
studio
itself,
so
you
can
go
to
help.
A
Yeah,
I
I
tell
people
that
also
for
visual
studio
for
mac.
You
know
like
hey,
you
can
send
me
something
on
twitter
or
whatever,
but
if
you
do
it
within
the
ide
that
tells
us
like,
especially
if
you
do
report
a
problem,
it'll
tell
us
like
what
version
you're
running
and
it
gives
some
more
debugging
on
text
for
us.
So
we
can
help.