►
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!
Community Links: https://www.theurlist.com/dotnet-community-standup-tooling-7-16-2020
A
A
A
A
A
A
Yes,
awesome:
okay,
hello.
Everyone
welcome
to
the
net
community
stand
up.
This
is
the
tooling
week
where
we
can
talk
about
all
of
the
cool
tools
and
good
stuff
coming
out
in
visual
studio
or
vs
code
or
vs
mac
and
how
you
do
it.net.
A
I'm
just
going
to
continue
and
ignore
cody,
so
we're
all
we're
all
program
managers
on
visualstudio.net,
I'm
kendra
havens.
I
work
mostly
on
the
testing
tools
and
testing
experience.
I
work
a
little
bit
on
productivity
and
I'm
just
like
around
and
doing
some
code
spaces
stuff.
If
you've
heard
of
that
cody
you're
a
regular,
why
don't
you
introduce
yourself
next.
C
Yes,
I
am
regular,
I
don't
know
how
this
works.
Apparently,
twitch
moved
my
cheese
as
they
say,
so
I
don't
know
where
anything
is.
But
yes,
I
am
cody
buyer
program
manager
in
dev
div
here
at
microsoft,
so
I'm
responsible
for
a
lot
of
different
things
under
the
visual
studio
and
developer
tools
umbrella.
So
you'll
see
me
in
different
places
and
doing
different
things.
A
B
B
Oh
yeah,
visual
studio
for
mac
is
the
thing
I'm
on
right
now,
so
I've
been
working
on
that
for
about
three
years
or
so
so
the
iede
is
a
whole
yeah
pick
a
feature.
Yeah
editor,
debugging
kind
of
jump
around
to
the
thing
we
need
at
the
moment.
The
shell
is
the
main
area,
so
the
overall
ide
and
features
that
span
across
the
different
supported
workloads
of
unity,
xamarin
and.net,
core
development,
so
kind
of
all
over
the
place,
a
bit
at
the
in
the
visual
studio
for
mac,
ide,
yeah.
A
Any
interesting
like
work,
history,
anecdotes
that
characterize
your.
I
don't
know
that
you
want
to
share
yeah
well,.
B
I
don't
know
when
it
this
started
happening
because
even
10
years
ago
I
started
to
feel
older
in
this
industry,
but
I
got
into
being
a
software
developer
back
in
1998,
so
I've
got
22
years
surprisingly,
under
my
belt
now,
so
I
was
dev
up
until
eight
years
ago,
a
developer
working
on
various
products
out
outside
of
microsoft,
external
to
the
company
in
consulting
product
development,
development
management
and
then
last
eight
years
at
microsoft,
I've
been
focused
on
those
javascript
tools,
primarily
for
the
first
five
years
or
so
so
worked
on
windows
tooling
for
javascript
developers,
the
javascript,
editor
and
visual
studio
itself,
our
cordova
tools
for
mobile
development
and
then
visual
studio
for
mac.
A
Yeah
cool.
B
Years,
right
before
I
was
on
visual
studio
for
mac,
you
and
I
were
still
crossing
paths
on
various
cordova
stuff
with
cordova.
You
know
there's
and
we're
gonna
talk
a
little
bit
today
on
some
of
the
stuff
behind
the
scenes
of.
You
know
that
we
that
we
do
that's
more
than
the
public
facing
items,
but
we
have
typical
internal
business
reporting
and
different
things.
Cody
and
I
cross
paths,
is
a
good
bit
around
some
of
the
reporting
we
do
in
the
across
mobile
development
back
then.
A
Yeah
all
right,
so
I'm
probably
not
messaging
from
the
correct
account
no
looks
like
restream
is
posting
instead
of
me,
I
guess
I'll
post
as
the.net
foundation.
I
don't
know
okay,
sorry,
so
I
wanted
to
share
our
url
list
in
the
net
community
and
I
actually
want
to
check
if
that
appeared
correctly.
So
those
are
all
the
links
that
we're
going
to
be
talking
about
today.
A
The
main
one
that
I
want
to
talk
about
is
a
really
exciting
blog
post
that
came
out
by
steven
tube
and
honestly
calling
it
a
blog
post,
probably
isn't
doing
it
justice.
It's
a
short
novel
of
all
of
these
incredible
performance
gains
in
net
five,
and
let's
see
if
I
can
actually
open
that
we're
using
a
slightly
different
setup
and
it's
obviously
throwing
off
cody
and
I
a
bit
okay,
let's
see
if
I
can
share
my
screen
with
the
skype
call.
A
I'm
sorry,
it's
that
we
got
a
comment
that
it
sounds
like
the
audio
is
out
of
sync:
we've
been
trying
to
configure
it
a
little
bit
better,
sorry
about
that,
I'm
not
brave
enough
to
do
any
tweaking
live.
So
definitely
just
sorry
about
that.
A
So
what
I
wanted
to
call
out
is
the
performance
improvement
post
in
net5,
and
it
is
super
long
look
at
this
scroll
bar,
but
even
if
you
don't
read
the
whole
thing,
the
I'm
a
very
visual
learner,
so
I
really
like
all
of
the
tables
in
it
just
the
tables
alone,
looking
at
reduced
memory
allocation
and
what
like
runtime
numbers
that
we're
seeing
where
are
some
of
my
exciting
ones
and
go
back
down
to
see
super
super
long
ratio.
C
You
know
kind
of
the
ways
that
we
that
we
do
that
and
the
kind
of
improvements
that
we
see
you
know
this
is
a
course
within.net
and
and
we're
normally
talking
about
the
ides,
but
still
this
kind.
This
level
of
of
of
transparency
into
the
performance
is,
I
think,
a
a
huge
benefit
to
everybody.
A
Yeah,
very
cool
and
all
of
the
code
that
he
uses
he
posts
within
the
blog
post,
and
so
you
can
actually
like
run
this
and
see
and
reproduce
these
results,
which
is
really
exciting
and.
A
C
A
So,
and
now,
of
course,
as
soon
as
I
open
it,
I
forget:
oh
there,
we
go
okay.
Some
of
these.
This
is
what
I
wanted
to
talk
about
a
little
bit,
just
the
allocation
massively
reduced
in
dot
net.
Five
is
just
super
super
exciting
to
see
yeah,
so
super
fun
post
to
dig
into
and
beyond
that.
The
next
step
I
wanted
to
talk
about
is
actually,
I
think
the
title
of
this
live
stream.
If
we
entered
it,
right
was
going
to
be.
Where
do
my
bugs
go?
A
All
right
in
passing,
as
how
do
you
file
bugs
first
off
it's
on
developercommunity.visualstudio.com,
so
this
will
take
you
to
report
a
problem
or
suggesting
a
feature
so
reporting
a
problem
will
always
capture
like
a
certain
amount
of
logs,
that
we
really
appreciate
when
you're
trying
to
reproduce
issues
and
we'll
probably
ask
if
sometimes
we
need
even
more
sometimes
we'll
ask
you
to
collect
a
etl
trace
or
collect
a
dump
with
like
perfume
on
a
process
that
went
went
wrong.
A
So
that's
the
bug
kind
of
section
of
it
and
that's
what
our
developer
teams
interact
with
directly
a
lot
as
all
of
the
bugs,
but
the
other
ability
is
to
suggest
a
feature.
So
if
you
want
to
add
something
new
to
the
ide
or
a
language
or
anything
like
that,
this
is
where
you
do
it
or
I
guess
our
frameworks
or
even
azure,
devops
and
stuff
is
how
you
can
is
are
things
you
can
do
on
this
site.
C
It
almost
has
one
of
those
like
arrival,
departure
fields
around
airports
where,
like
I
want
tfs,
but
I
want
it
in
this
ide,
where
I
put
it
always
put
it
in
the
application
or
the
or
the
product
that
you
want
to
see
the
feature
in,
even
if
it's
like
related
to
tfs
put
it
in
visual
studio
type
thing.
I
don't
know
if
that's
to
be
sometimes
a
little
a
little
confusing
for
folks,
but.
A
Yeah,
so
this
website
kind
of
replaced
user
voice
that
we
used
long
long
time
ago
to
keep
track
of
suggestions
and
something
that's
really
helpful
about
these,
is
you
can
upvote
the
things
that
are
impacting
you
and
we
massively
use
upvotes
to
kind
of
help
us
prioritize
and
figure
out
what
we
yeah
most
need
to
add
and
figure
out
our
road
map?
So
this
will
also
link
to
the
visual
studio
roadmap.
So
you
can
see
what's
coming
up,
that
doesn't
link
directly
to
the
roadmap,
but
it
is
on
our
documentation
page.
A
A
Yeah,
I
mean
definitely
so
you
can
also
kind
of
explore.
What's
coming
up
in
our
next
major
major
releases,
we
kind
of
try
to
keep
these
as
really
big
items.
This
definitely
isn't
like
the
exhaustive
list
of
all
of
the
features
that
we're
going
to
get
in
in
the
next
like
year
or
two,
but
these
are
the
big,
exciting
things
like
fakesupport4.net
core,
which
we
got
in.
A
I
develop
a
team,
yay
them
yeah.
So
that's
kind
of
the
general
flow
that
you
would
expect
something
that
might
kind
of
confuse
a
lot
of
people
is
that
they
might
open
a
suggestion
on
developer
community
and
then
we
might
close
it
as
duplicate
and
send
it
off
to
github.
So
that's
when
we
need
that
when
any
the
place
that
this
change
would
actually
occur
is
open
source
so
and
we
can
actually
talk
about
all
of
the
design
on
sorry
julie.
A
I
can
just
go
to
roslyn
there
we
go
and
it
redirects.
So
this
is
the
repository
that
a
lot
of
our
productivity
features
actually
happen,
and
you
can
watch
all
of
the
progress
online
in
open
source
and
sometimes
your
issues
that
you
open
up
will
end
up
here
in
our
issues.
So
we
move
them
here
so
that
we
can
more
actively
discuss
them
with
the
community,
because
this
is
where
people
tend
to
like
watch
our
repo
and
start
and
even
make
pull
requests.
C
A
Yeah,
actually
do
you
want
to
talk
about
where
that
the
visual
studio
for
back
repos
of
where
we
might
ping
or
how
it
works
on
developer
community,
oh
yeah,
yeah,
yeah,.
B
A
similar
flow
to
actually
the
same
flow
there.
When
you
go
to
the
developer
community
website
of
the
same
site,
you
can
use
for
reporting
issues
on
vs
for
mac.
We
don't
have
things
that
we're
sharing
over
to
like
a
github
repo
unless
we
get
something
that
comes
in
and
is
say
a
roslin
issue
that
you
know,
we
may
route
things
as
well
to
the
different
different
repos
out
there.
So
that's
one
of
the
like
behind
the
scenes.
B
Really
when
you
go
in
from
visual
studio
or
visual
studio
for
mac,
we've
got
tools
built
in
for
reporting
a
problem
or
suggesting
a
feature,
and
then
that
next
step
behind
the
scenes,
when
we
take
that
the
trigger
cash
process
has
that
kind
of
a
flow.
Does
this
item
actually
belong
in
this
product?
Did
I
end
up
in
the
wrong
queue
which
team
does
this
go
to,
and
then
how
do
you
go
about
routing
it
to
the
right
place?
It's
kind
of
the
very
similar
thing
behind
the
scenes.
B
So
if
you
use
the
tool
like
in
visual
studio
for
mac,
pick
our
help,
menu
and
choose
report,
a
problem
it'll
give
us
enough
details.
Log
files,
you
choose
to
include
them,
screen
shots
if
you
choose
to
include
them
and
then
even
the
version
you're
on,
so
that
we
can
in
that
first
response
back
to
you
ask
fewer
questions.
Hopefully
is
the
goal
I
see
chat
just
lit
up
over
on.
C
One
of
the
things
that's
important
about
you
know
what
jordan
said
too.
Is
that
these
don't
really
just
go
into?
You
know
a
box
that
nobody
ever
looks
at.
We
actually
oftentimes
the
way
we
sort.
This
is
by
votes
and
by
impact.
So
when
we
review
these
with
our
team
and
up
the
chain,
we're
normally
reviewing
it
with
the
context
of
votes
as
kind
of
the
main
motivator.
C
So
if
you
see
an
issue
that
you
think
is
important
on
devcom
or
anywhere
vote,
it
up
add
your
your
two
cents
to
it
and
that
definitely
helps
raise
the
the
video
fit.
It
does
raise
the
the
the
what's
the
word
I'm
looking
for.
C
The
visibility
of
it
up,
so
you
know
it
might
seem
like
there's
not
a
lot
going
on
when
you
put
a
def
com
issue
in
and
vote
it
up,
but
it
does
get
discussed
and
we
do
prioritize
it
and
we
do
compare
it
against
other
priorities.
Other
people
voted
up
to.
So
it's
not.
You
know
it's
not
always
the
most
transparent
in
that
context
of
what
we're
doing
internally
to
talk
about
it,
but
it
is
talked
about
at
least.
A
Oh
for
sure,
that's
definitely
something
we
wanted
to
talk
about
that
sometimes
tickets,
especially
that
seem
really
high
priority.
Aren't
always
it
doesn't
always
look
like
we're
making
as
much
progress
as
we're
trying
to
make,
and
I
guess
our
ask
is
for
a
little
empathy
on
some
of
those
tickets.
One
that
occurs
to
me
was
this
giant
ticket
that
I
actually
will.
A
I
think
I
can
yeah
talk
about
this
now,
so
we
added
so
a
lot
of
people
wanted
to
know
when
code
analysis
has
had
stopped
in
the
background
of
visual
studio,
so
we
added
so
they
basically
just
wanted
to
know.
Is
my
error
list
up
to
date,
really
simple
thing
like?
How
do
we
kind
of
do
that,
so
we
added
a
little
notification
in
task
manager.
A
The
problem
is
every
time
you
type.
Basically
code
analysis
is
happening.
It's
almost
always
happening.
Some
people
with
very
large
solutions
will
like
pause
and
like
want
to
make
sure
that
their
list
is
up
to
date.
A
lot
of
people
don't
actually
like
need
to
encounter
that
kind
of
wait
time.
So
we
added
this
notification.
That
then,
would
stop
so
it'd
say.
Like
code
analysis
is
running
in
the
background,
or
it
would
say,
like
all
background
processes
are
completed
or
something
like
that,
and
those
are
basically
the
only
two
states.
A
The
problem
was
if
any
lag
occurred
in
visual
studio.
If
there
are
any
slowdowns,
people
would
see
that
message
and
immediately
think
it
was
code
analysis,
even
if
it
had
nothing
to
do
with
the
rosslyn
theme
and
their
compiler,
or
anything
like
that,
even
if
it
was
an
extension
or
anything
like
that,
so
the
ticket
that
was
opened
with
that
title
gained
a
ton
of
up
votes
and
we
ended
up
finding
like
17,
completely
unrelated
issues
that
we
needed
to
send
to
other
teams.
A
But
just
because
of
the
way
the
ui
happened
and
how
it
could
analysis
all
is
is
always
a
natural
background
process.
It
kind
of
misdirected
a
lot
of
frustration
on
lag
times
with
the
ide,
which
was
so
unfortunate
so
and
sometimes-
and
I
guess
we-
we
tried
to
explain
a
lot,
but
sometimes
it's
really
easy
to
yeah.
I
think
that
you
know
this
issue
has
a
hundred
up
votes,
even
though
it
is
actually
17
different,
underlying
problems
that
we
then
had
to
go
investigate
that
we're
on
completely
different
teams.
B
That
was
that
was
one
part
I
always
took
for
granted
before
coming
to
microsoft.
Was
the
number
of
teams
involved
in
like
visual
studio
and
and
something
like
that,
and,
as
you
start
to
tease
it
apart
and
realize
the
different
impact
acro
like
it's,
that
was
that
was
one
of
those
really
interesting
career
challenges
for
me
was
like.
Oh,
oh,
I've
got
this
many
other
people
that
are
involved
in
this
okay.
C
C
It
also
comes
in
like
we
were
talking
about
like
xamarin,
stuff
and
different
feature
teams
and
how
those
interact
with
the
ides-
and
you
know,
I
think
it's
a
very
collaborative
approach.
There's
no,
you
know
like
it's,
not
not
my
issue
type
attitude
at
all.
It's
very
collaborative,
it's
a
very
much
a
a
culture
of
trying
to
come
to
the
best
solution,
but
a
lot
of
times
it's
hard
to
tell
these
different.
C
You
know
what
is
at
the
root
of
this
delay
or
this
bug
or
this
this
issue
we
had
one
a
few
months
ago,
with
the
iphone
sdk
checking
for
the
sdk,
was
causing
the
ide
to
freeze
every
like
10
seconds.
You
know
it
was
pretty
pretty
wild,
but
trying
to
figure
out
where
that
actually
was
in
the
stack
can
be
something
that
there's
a
lot
of
collaboration
on
that
as
well.
A
Yeah,
there's
always
at
least
two
rounds
of
triage,
I
think
maybe
more.
I
guess
actually
for
anything
that
we
move
over
to
different
repositories,
there's
probably
extra
rounds
of
triage.
So
we
have
people
who,
like
generally
look
at
everything
coming
in
for
like.net
areas
and
then
within
those
areas
they're
assigned
to
pms
who
need
to
go
and
like
look
at
those
suggestions
within
like
seven
days
or
something
like
that
is
what
we
try
to
do
at
the
maximum.
C
Actually,
you
know
we
do
have.
We
do
have
at
least
on
the
editor
team,
there's
a
developer
and
responsible
every
week
for
triaging
these
and
they're.
You
know
they're
supposed
to
go
in
every
day
and
look
at
these
and
kind
of
find
the
importance
and
and
get
the
the
priorities
assigned,
and
that's
always
with
pm
assistance
as
well.
C
So
I
think
each
team
kind
of
has
their
own
structure
as
to
how
they
handle
this
sort
of
this
sort
of
work,
but
the
the
other
team,
at
least
it
was
an
everyday
thing
and
at
the
end
of
the
week
we
always
wanted
to
get
untriaged
down
to
zero.
Of
course,
depending
on
how
how
busy
your
your
product
is,
it
can
be
difficult
to
ever
get
down
to
zero,
but
that's
you
know,
that's.
A
Yeah,
I
bet
I
thought
it
was
often
yeah
and
sometimes
yeah.
The
first
triager
doesn't
even
assign
it
to
like
a
general
area
path.
That
is
what
you
do,
so
we
need
to
ping
it
back.
So
if
there's
like
a
few
days
delayed
on
tickets,
it's
because
it's
a
massive
product
and
a
lot
of
different
teams,
and
it
takes
really
specific
information
to
know
who
can
actually
fix
it.
A
A
So
it
could
end
up
in
a
lot
of
different
places,
with
a
lot
of
different
teams
with
their
own
triaging
cultures.
So
you
know
that's
what
it
is.
It's
it's
it's
much
different
than
I
guess
a
sort
of
more
contained
product
where,
like
one
developer
team
and
all
of
that
owns
it
so
process
is
a
bit
longer
a
bit
different,
just
kind
of
keeping
an
eye
on
chat.
Seeing
if
we're
getting
any
yeah
questions.
A
So
speaking,
we
were
talking
a
little
bit
about
priority.
You
can
upvote
suggestions
and
anything
you
find
on
developer
community,
especially
bugs
that
are
impacting
you,
but
I
also
wanted
to
share
some
things
that
we
as
triagers
actually
want
to
be
uploaded
and
sorry.
I
have
too
many
different
computers,
I'm
getting
totally
lost
on
how
I
actually
share
links.
So
typically,
I'm
not
really
supposed
to
tweet
a
ton
about
issues
that
I
really
want
to
solve,
because
it's
kind
of
stacking
the
table.
A
There
is
an
issue
on
developer
community
to
like
even
improve
developer
community
itself,
so
we're
also
trying
to
constantly
improve
that
platform.
One
of
my
pain
points
is
that
it's
pretty
difficult
to
discover
all
of
the
existing
suggestions
in
order
to
upvote,
even
though,
like
upvotes,
we've
already
said,
are
like
so
important
how
we
prioritize.
A
A
Community
team
is
also
on
board,
so
things
like
tagging
and
a
little
bit
better
search
results
and
being
able
to
kind
of
filter
things
based
on
like
data,
and
that
kind
of
thing
stuff
you
would
normally
be
able
to
do
on
github
would
be
so
nice,
oh
sorry,
that'd
be
so
nice,
the
developer
community.
So
I
put
that
in
chat,
I'm
just
saying
I
I'm
only
allowed
to
share
this
one,
because
if
I
don't
share
it,
then
you
couldn't
find
it
because
that's
what
the
ticket's
about
making
it
easier
to
find
tickets.
A
A
Yeah,
so
any
questions
that
people
have
my
bug-
reports
go
to
github
issues;
cool
that
means
they
could
be
fixed
in
the
open
source.
Is
the
platform
open
source
I,
if
you're,
referring
to
the
developer
community
platform?
No,
it's
closed.
Unfortunately,
it'd
be
super
cool.
If
it
was
open
source,
it
has
an
amazing
azure,
devops
backend.
That
is
how
I
actually
look
up:
tickets,
to
write,
massive
queries
to
filter
to
my
area
and
by
date,
and
look
at
incoming
and
last
updated
and
all
of
that
kind
of
stuff.
C
I
think
one
of
the
other
things
that's
important
with
with
developer
community
is
that
we're
also?
We
have
that's
one
source
of
feedback.
We
also,
you
know,
talk
to
customers.
We
have,
you
know,
support
teams
who
interact
with
customers.
We
have
crash
reports
if
there's
something
that
is
commonly
happening
so
every
time
we
go
through
kind
of
a
planning
cycle,
we
have
to
compare
all
these
different
avenues
of
information
coming
to
us
and
we
always
strive
to.
C
So
if
there's
ever
an
issue
that
you
feel
like
should
have
gotten
attention
and
it
didn't,
you
always
feel
free
to
reach
out
to
one
of
us
and
we
can
hopefully
at
least
point
you
in
the
right
direction
or
explain
the
context
around
it,
because
I
think
that
a
lot
of
times
that
the
the
context
there
is
a
little
bit
missing
with
the
community
about
like
what
what
other
things
are
happening.
Kind
of
in
the
in
the
team
space.
A
Yeah
there's
a
comment
that
it
feels
like
sometimes
the
vs
feedback
is
the
place
that
bugs
and
suggestions
go
to
die
of
loneliness.
I
actually
do
want
to
talk
about
that,
because
we
may
get
like
thousands
of
suggestions
and
only
be
able
to
implement
like
50
or
just
a
handful.
I
think
the
current
open
issues
on
roslyn
is
it's
over
five
thousand.
A
I
feel
like
it
was
far
far
over
that
I
think
we
we
tried
to
go
in
and
kind
of
close
things
that
we
knew
we
would
never
get
to
or
things
that
we
knew
would
most
likely
be
actively
harmful
if
we
did
get
them
in
or
confusing
so
a
lot
of
times.
A
You
might
be
filing
a
suggestion,
but
when
you
look
at
it
from
our
angle
of
how
this
will
affect
like
the
millions
of
users
that
we
have,
it
ends
up
being
more
hurtful
for
a
major
for
a
larger
segment
of
the
population
than
it
would
help
some
really
good
things
as
well.
That
would
make
a
lot
of
sense.
We
also
can't
always
put
in
because
it
would
like
fundamentally
break
an
interaction
model
that
we've
trained
people
to
understand.
A
So
it's
there's
a
lot
of
different
decisions
that
we
have
to
weigh
in
quick
friend,
make
it
work
harder.
No,
no.
B
A
Open
issues
is
fine,
depending
on
different
repo
philoso
philosophies.
I
think
for
a
product,
that's
as
over
4
million
lines
of
code
with
millions
of
users.
We
have
15
000
closed,
which
is,
you
know,
goes
to
show
we're
not
just
not
looking
at
these
or
anything
there's
a
lot
of
stuff
to
take
into
account.
B
So
when
you
take
that
into
our
teams
too,
it's
I
think
one
interesting
thing
you
mentioned
earlier
was
how
it's
on
different
teams
in
their
own
triaging
style,
so
some
teams
actually
apply
different
philosophies
on
how
they
want
to
handle
bugs
and
then
we'll
have
some
from
our
overall.
You
know
product
level
like
visual
studio.
That
has
some
things
we
aim
for,
but
there's
actually
different
teams.
Behaviors
can
affect
it.
So
it
makes
an
interesting.
A
Yeah
yeah,
that
perfectly
aligns
with
what
I
was
gonna
say
I
I
was
gonna
say
I
missed
the
c:
sharp
had
a
milestone
that
was
like
when
hell
freezes
over
for
things
that
they
were
absolutely
never
going
to
introduce
into
the
language,
and
especially
for
something
like
a
language
when
everyone
has
an
opinion
on
all
of
the
improvements
that
you
can
make
and
stuff
there's
even
opinions
about
how
we
need
to
stop
like
adding
more
syntactic
sugar,
even
though
it
doesn't
actually
affect
anything
that
has
existed
in
the
past.
A
C
And
well,
that's
you
know.
I
think
one
of
the
big
things
that
I'm
very
proud
of
that
we
do
at
microsoft
is
that
we
ensure
there's
this
backwards.
Compatibility,
like
you
mentioned
like
if
there's
an
interaction
model
that
people
have
been
using
for
20
years.
We
don't
really
want
to
change
that,
but
that
also
you
know,
as
you
say,
can
limit
some
of
the
the
scope
of
updates.
C
But
I
think
if
you
look
at
newer,
ides
like
vs
code
and
or
you
know,
editors
like
vs
code
and
vs
for
mac,
there's
a
lot
more
of
that
ability
to
kind
of
innovate
in
some
of
the
interaction
models
and
some
of
the
you
know,
features
and
and
aspects
the
ide
that
that
will
would
that
we
wouldn't
be
able
to
do
in
vs
because
of
its
older
interaction
model.
So
that's,
I
think,
an
interesting
way
to
look
at
it
too.
C
Is
that
comparing
kind
of
the
rate
of
change
and
the
ability
to
really
innovate
in
in
some
things
versus
others,
you
know
we
can
innovate
in
the
back
end.
All
we
want,
but
there's
there's
limitations
in
the
front
end
and
that's
you
know
both
of
a
positive
and
negative
depending
on
your
perspective,
but
I
think
it's
a
huge
great
thing
to
keep
that
compatibility
there,
because
you
know
I
I
personally
know
how
frustrating
it
is
to
have
like
your
interaction
model
change.
It's
like
why.
C
A
Mean
me
too,
I
was
a
little
bit
panicked
before
we
started
this
trying
to
figure
out
obs.
I
got
a
question
on
what
headphones
I'm
using.
We
can
start
answering
more
questions.
Oh
it's
a
g430,
sorry,
yeah,
okay,
what
else
questions
did
we
have
a
bunch
of
fixes
that
were
reported
branches
after
branches
unrelated
tooling?
I've
heard
that
support
and
docs
blogs
for
using
when
ui3
and
uwp
is
coming.
Is
there
an
eta?
Not
that
I
know
of.
A
I
would
definitely
ask
that
during
the
desktop
live
stream,
though
with
olya,
because
she
would
probably
have
a
lot
more
wait.
A
Is
the
desktop
stream
might
have
more?
I
forget
who
is
actually
working
on
it?
Sorry
take
back
the
name
drop,
the
desktop
would
probably
have
more
info
on
it,
I'm
trying
to
think
of
who
you
can
tweet.
I
was
talking
about
that
with
someone
recently,
not
sure.
Oh,
I.
C
A
When
ui
streams
awesome,
oh
wpf
is
under
the
win:
ui
team,
thanks
dot,
morton
cool
yeah.
If
we
don't
have
a
ton
of
more
questions,
we
could
probably
wrap
up
be
sure
to
file
feedback.
A
We
have
an
intense
triage
process
that
may
take
longer
than
you
expect,
but
it's
a
big
scope
so
we're
doing
the
best
that
we
can.
You
can
go
to
developercommunity.visualstudio.com
to
do
that
and,
if
you
don't
know
which
repo
in
the
open
source
to
open
a
ticket
on
always
just
use
developer
community
and
we'll
figure
out
what
team
to
send
it
to
and
be
sure
to
vote
on
issues
that
you
care
about,
because
we
look
at
those
and
struggle
over
them.
A
C
And
one
final
note
on
that,
too,
is
we?
We
try
our
best
to
accurately
combine,
duplicates
or
slip
duplicates.
So
you
know
if
we
mark
a
ticket
as
a
duplicate,
and
you
disagree-
that's
totally
fine.
Let
us
know
we
might
have
misread
it
or
misunderstood
it,
but
there's
a
lot
of
instances
where
you
know
we
might
accidentally
marks
them
as
a
duplicate
when
that's
not
really
a
duplicated
issue.
So
it's
never
out
of
malice.
C
It's
normally
out
of
just
you
know,
either
misunderstanding
or
or
even
an
understanding
of
how
things
work
on
our
back
end
versus
how
things
are
presented
in
the
in
the
user.
Space
so
definitely
feel
free
to
interact
with
us
on
that
and
we'll,
hopefully,
you
know,
describe
the
thought
process
there
as
best
as
possible.
A
Even
after
tickets
are
closed,
we'll
get
pinging
notifications,
but
there's
still
activity
on
them.
So
definitely
still
keep
looking
at
those
yeah
so
yeah
that
performance
article
is
super
cool
steven
tube
is
awesome.
So
take
a
look
at
that
and
I
guess
we
can
wrap
up
for
the
morning.