►
Description
Join members from the .NET teams for our community standup covering great community contributions for Framework, .NET Core, Languages, CLI, MSBuild, and more.
A
B
C
C
A
B
B
C
C
A
I
think
that
yeah,
oh
yeah
I,
think
I
just
prints
the
bun.
So
the
thing
is
so
I.
Don't
know
whether
you
saw
this,
but
they
did
this
picture
of
the
black
hole
right,
which
is,
if
you
think
about
it,
doesn't
sound
super
amazing.
On
the
first
side,
it
comes
like
you
just
point
something
at
this
guy,
you
press
the
button.
The
picture
comes
out,
but
that's
not
quite
foot
half
done
right.
C
C
B
Yeah,
well,
it
was
yeah
they
talk
about,
so
you
can
find
it
I
think
not
on
this
onebut
and
there's
like
a
CNN
article.
They
actually
linked
the
papers
that
they
submitted,
they
submitted
I
mean,
was
six
individual
papers.
They're
intense
I
tried
to
read
them
and
they're
kind
of
like
I.
Don't
understand
like
three
paragraphs
and
I
understand
a
little
bit
like
they
got.
They
assembled
everything
the
point
where
they
actually
effectively
had
this
image
back
in
2017,
but
it
took
them
or
sorry,
20
I,
don't
know.
B
Basically
it
took
them
like
almost
three
years
to
actually
have
a
with
a
degree
of
mathematical
certainty
that
that's
what
it
actually
looks
like
because
they
had
to
spend
that
long.
Developing,
like
you,
know,
okay,
this
is
this
is
what
our
tolerance
is.
This
is
okay.
How
do
we
define
a
mathematical
function
that
defines
what
our
bias
is
for
the
things
that
we're
trying
to
generate
out
of
this
thing?
How
do
we
make
sure
that
we're
not
biasing,
yeah
yeah,
it
was
extremely
rigorous,
is
pretty
yeah.
C
A
C
C
Any
ID
I
couldn't
quite
get
my
act
together
to
get
this
push
this
morning,
but
it's
going
to
show
up
on
dotnet
designs,
hopefully
today
or
or
tomorrow,
we
might
skip
to
announcements
on
this
one
because
we're
not
really
gonna
I,
don't
think
we're
going
to
take
input
unless
somebody
really
screams
it.
It's
a
problem
so
dotnet
build,
which
is
at
the
command
line.
Cli.
You
type
do
T
any
T
space
build
and
it's
a
very
common
way
for
people
to
build
their
applications.
Everything's
cool.
C
You
need
to
run
a
target
name,
build
well,
there's
a
couple
of
scenarios
where
that's
not
really
what
you
wanted
to
do,
one
of
them
and
the
most
important
is
if
you
had
a
default
target
in
your
project
file,
it
actually
didn't
run,
and
so
you
weren't
running
the
target
that
you
wanted,
and
in
this
unusual
case
you
know
it
was
somewhat
unusual
case
and
then
the
other
case.
The
other
situation
wasn't
quite
doing
what
you
wanted
was
if
you
had
your
own
target
that
you
added
to
don
t
build.
C
But
we
don't
expect
it
to
affect
anything.
So,
at
any
rate,
the
case
that
will
affect
is,
if
you
were
counting
on
running
billed,
you
were
saying:
dotnet
build
T,
Colin,
something
and
you
were
counting
on
build,
also
running,
which
would
be
sort
of
unusual,
because,
if
you're
that
much
into
the
switches,
you're,
probably
using
a
missile,
so
we're
taking
t
:
build
off
of
the.net
build,
and
that's
just
this
little
thing
we're
doing
that.
I,
don't
actually
have
anything.
I
can
put
up
on
screen
right
now.
C
A
C
Can
you
bring
up
that
a
copy
of
the
document
we're
working
on
getting
it
we're
working
on
getting
this
into
Docs,
because
it
is
quite
confusing
and
I'll
try
to
stay
light
on
it,
which
is
specifically
what
we're
going
to
put
what
we've
proposed
to
put
into
Microsoft
Docs
explains
why
this
happens,
but
right
now,
I
want
to
focus
on
what
happens
and
how
this
will
affect
some
of
you,
I
with
confidence.
I
can
say
it
will
affect
some
of
you.
So
msbuild
ties
a
SDK
version
to
a
visual
studio
version.
C
Exactly
why
it's
it
going
to
be
explained
like
somebody
can
reach
out
on
Twitter
I
can
explain
it.
It's
real
we're
working
on
changing
that
in
the
long
term,
but
in
the
short
term.
What
this
means
is
that
2.2.1
hundred
that
2.2.1
nn
so
105
is
what
I
think
we've
got
up
right
now,
but
one
something
2.2.1
and
n
is
required
for
Visual
Studio
2017
to
do
2.2
development.
C
You
can't
use
2.2
dot
200,
which
is
the
thing
that
you're
likely
to
get
if
you
just
reach
out
to
our
current
downloads
page
because
it
doesn't
really
say
yeah.
This
wasn't
this
isn't
going
to
work
with
2017,
so
you
get
a
rather
bizarre
situation
where
your
templates
will
work,
but
then
you
won't
be
able
to
work
with
a
project
that
you
create,
and
so
it's
that,
if,
if
you
can
scroll
up
to
the
top
quickly
there,
the
message
that
you
get
is
is
in
this
I
think
it's
right
at
the
near
the
top.
C
If
you
can
look
for
where
we're
listening
messages,
we
have
to
point
me
right.
There
I
think
you
just
went
past
it.
So
this
is
the
kind
of
message
that
you're
going
to
get
if
you
run
into
this
problem,
so
you
just
need
to
download
2.2
that
one
and
and
whatever
the
most
recent
patch
is
for
2017
development,
and
you
need
2
to
2
and
n
for
2019
development,
and
so
you
want
both
of
the
machines.
If
you're
working
in
both
and
doing
2.2
development
we're
working
on
it.
So.
A
C
We'll
have
a
link
to
it.
If
you
go
to,
how
is
the
SDK
version
how's
the
dotnet
core,
SDK
version?
There
is
a
a
page
right
now
on
that
in
help
we
will
link
from
there,
but
we're
not
quite
sure
a
lot
of
things
about
where
it
goes,
because
I'm
used
to
contributing
to
the
dotnet
core
help,
and
this
is
likely
to
be
in
the
visual
studio
help
because
it
is
in
fact
a
visual
studio
where
you
encounter
the
problem.
C
So
I
know
less
about
how
that's
organized
so
I
really
can't
comment
on
exactly
where
it's
going
to
be
and
there's
one
other
small
way
you
can
run
into
this,
which
is
just
a
surprise.
We
have
sort
of
left
SDKs
on
your
machine
and
you
may
sometimes
like
to
clean
them
up
and
if
you
remove
dotnet
core
2.1
dot
510,
you
remove
that.
Then
your
Visual
Studio
2017
well
no
longer
work
for
2.1
apps,
it
needs
to
dot
1.5
and
n,
and
2019
needs
to
don't
1.6,
n
n
and
yes,
I'm.
C
Sorry
we
are
working
on
this.
I
could
I
can
explain
how
we
got
here
and
it
was
logical,
small
steps
and
I'm
actually
going
to
be
have
an
upcoming
talk,
which
is
what
do
you
do
with
30
years
of
mistakes
and
I've
actually
decided
for
a
big
part
of
that
talk
is
the
last
year
and
a
half
and
the
just
how
hard
it
is
to
get
this
SDK
versing.
So
it
works
in
all
cases.
But
in
this
case
we
think
we
have
some
plans.
C
I
think
we're
good,
but
I
just
don't
know
if
we
can
land
them
in
the
next
period
of
time
during
the
2.1
2.2
timeframe.
It's
just
stuff,
I
don't
know
if
we
can
land
in
patches.
So
that's
that's
the
messed.
We
have
any
comments
on
that
anybody
saying.
Are
you
kidding
me
because
I've
been
getting
that
on
Twitter
a
lot?
Yes
yeah,
it's
been
loud,
it's
been
loud
on
Twitter
yeah,
okay.
So
how
do
you
update
your
knowledge
of
framework
versions?
C
So
one
of
the
places
you
can
go
on
that
is
help
and
if
you
have
trouble
with
this
article,
let
me
know-
because
we
worked
on
this
six
six
months
ago.
Maybe
a
little
longer
to
get
the
how
our
Nick
I
think
it's
called
how
or
dotnet
core
st
how
is
dotnet
core
version
or
close
to
that
it
in
help.
If
you
have
trouble
finding
it
we'll
get
it
in
the
page
here,
but
I
think
it's
pretty
straightforward,
you're
getting
the
same
error
with
that
neck
core
three
and
Visual
Studio
2019.
C
C
Can
you
make
sure
you
have
dotnet
core
three
preview
installed
because
we
do
not
install
dotnet
core
3
o
preview
with
Visual
Studio
2019
release
we're
not
in
the
habit
of
putting
previews
on
to
full
release.
So
you
could
check
that
out.
My
guess
is
that's
your
problem.
If
not,
can
you
put
something
on?
You
can
go
ahead
and
use
the
dotnet
core
SDK,
so
its
github
slash
net,
slash
SDK
and
you
can
put
an
issue
there.
C
What
factors
about
2019
well
2019
is
not
causing
any
of
the
issues
that
I
just
talked
about.
So
if
you
just
do
an
install
of
2019,
you
should
be
good
and
it
is
a
sweet
version.
It's
faster.
It's
got
some
really
good
stuff
going
on
in
tests.
You
can
check
out
the
release,
notes
to
see
what's
there
and
you
can
run
it
side
by
side.
So
it
should
be
a
very
safe
install
for
you
to
put
that
on
and
then
jump
back
to
to
the
Visual
Studio
2017,
where
you
need
to
yeah.
C
Oh
yeah,
can
you
can
you
go
back
to
the
version
matches?
We
we
scrolled
off
of
that,
to
show
the
message
and
I
forgot
to
ask
you
to
scroll
back
sorry,
we've
got
this.
We
have
a
table
and
we're
looking
in
the
location
that
this
table
will
reside,
but
it
will
be
linked
from
as
many
places
as
we
can
find
it,
because
this
is
the
the
key
information
to
get
what
you
need.
I
vote
about,
yelled
about
Hut,
I,
don't
know
what
your
what's
going
on
there
and
I.
C
Don't
have
enough
information
from
these
comments
to
get
that
so
I'm
gonna.
Ask
that
you
reach
out,
if
possible,
our
preferred
place
would
be
github
and
then
some
of
the
super
smart
people
I
work
with
a
most
amazing
engineers,
and
one
of
them
will
take
a
look
at
it.
So
if
we
can
figure
out
what's
going
on.
A
Yeah
I
think
that
people
often
ask
that
can
install
30:19
safely,
like
there
I
think
the
entire
team
on
our
site
is
not
putting
at
least
multiple
versions
of
es.
Most
people,
new
team
even
have
multiple
versions
of
the
same
branch,
meaning
like
you
have
2019
in
multiple
versions
like
the
master
branch
is
the
preview
branch
at
their
preview
branches
and
it
works
pretty
well
like
vs.
C
I
want
to
get
this.
This
next
comment,
which
is
about
the
Mac
Mac
OS
2
to
2
or
3
SDK,
we're
working
on
that
I
talked
to
Lee
yesterday
about
that,
and
we
will
I
expect
it
will
be
up
soon,
because
I
think
we
can
work
with
the
concern
that
we
had,
if
not
there'll,
be
an
announcement
on
that,
but
I
believe
it
should
be
up
quite
soon.
C
A
C
A
I
mean
the
one
thing
I
would
say
is:
if
you
go
from
for
all,
don't
go
to
four
or
five
no
go
to
for
six
or
four
seven,
at
least
because
we
made
a
bunch
of
fixes
post,
four
or
five
they'd
make
that
one
more
compatible
for
all,
because
between
four
and
four
five
there
were
a
bunch
of
breaking
changes.
They
were
unintentional
that
we
they'd
be
addressed
later
on.
A
What
we
do
have
is
like
this,
like
in
MSDN,
when
you
social
framework
versions,
we
actually
do
list
a
break
and
changes.
So
there's
actually
document
that
tells
you
what
changes
we
have
done
and
you
can
actually
want
api
port
over
your
code
as
well,
and
it
will
actually
point
you
to
api
said
you
were
using.
That
might
cause
problems
on
the
later
version
of
the
framework
and
they
actually
link
the
the
knowledgebase
articles
directly
from
that,
I
can.
C
C
A
C
A
If
there
was
a
document
somewhere,
I
cannot
find
it
right
now,
because
you
moved
it
a
few
times,
but
I
can
link
to
it
as
well.
Like
digitally,
there's
a
there's,
a
page
for
Arizona
for
a
favorite
version
that
there
we
ship
they
list
the
breaking
changes
that
you
have
done
or
impactful
changes.
We
have
done
on
all
our
Breaking
Away
yeah
yeah.
That
would
be
my
recommendation
to
go
about
that.
So.
A
Event
stalled
for
a
tow
for
certainly
will
not
break
the
current
production.
That's
the
intention!
So
what's
it
what's
important,
it's
like
any
4x
releases
in
place
right.
So
that
means,
if
you
install
for
8
on
the
box
that
has
400
on
it
afterwards,
you
only
have
four
8
on
the
box
right
so
for
aid
replaces
and/or
any
firmware
version
8
for
X
replaces
any
other
framework
version
4x
right,
so
that
there's
no
side
by
side.
A
So
if
you
want
to
run
a
photo
app,
you
probably
want
to
be
on
a
photo
machine,
otherwise
you're
basically
say
yeah
when
I
might
get
my
approved
for
Oh
2
4
8,
and
then
you
should
test
that
and
then
check
that
it
that
it
still
continues
to
work.
The
intention
is,
there
continues
to
work
because
we
take
compared
really
seriously.
So
we
do
a
lot
of
testing
on
that.
But
you
know,
if
you
in
place
update,
you
know
a
framework
and
an
even
application.
You
know
things
might
can
go
wrong
right.
A
C
And
just
to
just
to
clarify
that,
because
it's
a
production,
server
right
so
I
want
to
be
like
make
sure
we
haven't
forgotten
this,
which
is
that
if
you
put
a
new
version
into
the
GAC
on
your
production
server,
that's
the
one.
That's
can
run
so.
Do
your
testing
prior
to
going
to
your
production
server.
So
you
make
sure
that
you're
you're
doing
that.
You
know
you.
You
may
not
have
changed
anything
in
your
app
yet,
but
your
you
just
want
to
make
sure
that
that
goes
smooth
for
you.
C
Okay,
so
I
have
one
more
thing
on
version,
so
you
want
to
just
Trevor
that
really
quick!
Can
you
go
to
github
net
announcements?
Please
and
look
at
one
or
two,
because
this
happen
I,
don't
think
we've
act
we
missed
last
month
because
there
we
were
like
right
on
top
of
the
the
launch
and
all
and
said
we
just
said
well,
you
know
well
skip
this
month,
so
we
didn't
do
March
and
going
back
to
February.
This
came
out.
This
was
announced
after
February,
one.
C
Or
two,
not
that
one
that
one
all
right
so
I
mentioned
earlier
that
we've
been
leaving
SDKs
on
your
machine.
We
are
going
to
improve
that
we're
not
going
to
maybe
take
that
as
far
as
some
people
want,
but
we
need
to.
We
need
to
stay
in
the
right
level
of
conservative
decision
here.
So
what's
gonna
happen
is
patches,
will
now
overwrite
each
other
by
default.
So
if
you
use
the
installer-
and
this
right
now
is
on
Windows
assuming
it
goes
well,
there
we'll
move
it
to
Mac.
C
So
the
SDK
installment
on
Windows
will
now
say
will
now
install
over
patches.
So
if
you
have
to
dot
one
dot
500
on
your
machine
right
now,
and
you
install
two
dot
one
at
5:05,
which
is
the
latest
that
you
can
download,
then
you
will
that
will
500
will
go
away
so
it'll
it'll
overwrite,
that
we've
also
done
some
working
Visual
Studio,
so
it
leaves
less
behind
and
we
are
definitely
moving
towards
having
at
doing
a
better
job
keeping
your
machine
clean.
C
In
the
meantime,
there
is
actually
a
help
for
removing
old
net
core
runtimes
and
SDKs
from
your
machine,
and
it
will
walk
you
through
finding
out
what
you've
got
and
how
you
can
install
it.
And,
yes,
it
can
be
tedious
and
we
are
trying
to
make
that
better
going
forward,
but
it
is
only
within
the
future
band,
which
is
the
100th
series
that
we're
going
to
be
overriding,
and
the
reason
for
that
is
that
there's
various
reasons
you
may
need
different
feature
bands,
one
of
which
I
just
talked
about
which
is
Visual
Studio.
C
A
C
I,
try
not
to
use
major
minor
kind
of
numbers
here,
I
try
to
say
first
position,
second
position,
third
position
and
then
third
position,
there's
the
hundreds
and
then
the
patch.
So
that's
why
you'll
hear
me
say:
3n
n,
which
might
be,
or
let's
say,
five
and
n,
which
might
be
501
502,
503
504.
Those
are
just
patches
and
one
of
the
things
is
that
the
way
the
SDK
is
designed,
those
actually
are
not
changes
to
the
SDK.
A
C
There's
pass
so
500
would
be
the
2.1
versions
that
work
with
Visual
Studio
2017.
You
can,
of
course,
also
use
them
from
the
command
line,
but
if
you
do
command
line
and
Visual
Studio
code
development,
you
might
want
to
be
on
the
latest
latest,
which
is
2.2
200,
because
all
versions
of
the
SDK
on
the
command
line
work
with
previous
everything.
Previous
so
there's
backwards.
Compatibility.
The
problem
with
Visual
Studio.
Is
that
they're
the
way
that
it
works?
C
We
would
have
to
have
forward
compatibility
which
we
don't
have
in
order
to
not
have
this
problem
and
we
are
looking
at
it
ways
to
make
that
better
as
I
said,
but
if
you're
just
command
line,
the
latest
should
be
good,
but
if
you're
on
something
where
you
feel
like
you
need
to
know
what
feature
band
you're
on
and
then
as
much
as
possible
patch,
because
we
do
include
things
we
think
are
important
in
patches.
That
should
be
things
that
could
crash
and
things
that
are
security
issues
and
occasionally
something
else.
C
C
B
E
C
B
B
B
E
B
B
B
B
B
4.6
released
with
Visual
Studio
2019,
so
if
you're
an
app
developer,
you
get
a
new
language
which
is
great,
but
no
C.
Sharp
E
is
not
released
with
Visual
Studio
2019.
There
is
a
preview
that
is
in
the
box
that
you
can
use
and
the
way
that
you
access,
that
is
through
dotnet,
cord
3.0
preview,
and
the
reason
for
that
is
because
that
you
know
there's
basically
like
half.
B
And
then
you
go
to
the
dotnet
core
section
under
projects
and
solutions,
so
this
is
kind
of
I
wish.
I
could
blow
my
screen
a
little
bit,
but
you
go
under
donna
core
and
there's
a
checkbox
called
news,
previews
of
the.net
core
sdk,
and
when
you
do
that,
then,
if
you
have
dotnet
core
3
o
installed
on
your
machine,
everything
will
just
line
up
perfectly.
If
you
don't
have
this
checked,
then
it's
gonna
be
kind
of
confusing
stuff
is
not
really
going
to
compile.
B
It's
not
gonna
recognize
the
donna
core
3.0
stuff,
some
c-sharp
8
stuff
is
not
gonna
get
recognized,
and
things
like
that.
So
you
have
to
make
sure
that
you
have
this
checked
if
you're
using
Visual,
Studio,
2019,
16.1
preview,
1,
basically
the
studio
2019
preview,
this
checkbox
is
always
checked,
so
the
simplest
way
actually
is.
If
you
install
the
Visual
Studio
2019
preview,
then
this
is
always
tracked.
You
can
then
download
donek
core
3
preview,
and
then
you
get
C
sharp
8
is
in
its
entirety.
All
on
all
working
kind
of
no
questions
asked
so.
B
Want
to
access
a
small
bit
of
that
preview
functionality.
You
have
to
do
a
bit
of
additional
work,
which
is
why
you
have
to
check
this
checkbox.
So
that's
kind
of
I
just
wanted
to
offer
a
little
bit
of
clarity
on
the
C
sharp
8
set
of
things,
because
I've
seen
sort
of
a
lot
of
people
confused
online
about
if
it
was
shipping,
if
it
was
released
when
it
was
shipping,
which
is
it,
ships
with
donek
or
3.0.
So
that's
gonna,
be
later
this
year,
yeah.
C
B
C
C
D
B
To
be
pretty
soon
so,
if
you
want
to
use
c-sharp
date
with
Donna
corrido
today
you
go
under
projects
and
solutions,
Donna
core
there's
a
checkbox,
starting
with
the
16.1
updates.
You
go
under
preview
features
here,
it'll
be
there
and
you
can
also
just
search
for
it
right.
If
you
search
for
preview,
you
get
you
get
stuff
right,
you'll
see
there
you'll
be
able
to
use
it
so
boom,
that's
sort
of
a
whole.
That's
the
story
for
c-sharp
bait.
That's
now.
B
Hold
my
beer
yeah,
so
some
other
stuff
before
sure.
So
as
I
said,
I
also
worked
on
integration,
tooling,
and
so
a
few
things
that
are
new
here
in
es
2019
is
we're
making
project
files
first
class
because
product
files
are
files.
We
don't
really
hide
the
fact
that
they're
files
and
that
you
should
be
able
to
edit.
B
B
E
B
B
B
Open
itself
right,
but
there's
more
than
just
opening
the
file,
so
I
can
search
right
there.
It
shows
up
in
control,
T
results
and
I
can
also
control
shift.
F,
I'm
gonna
go
look
for
the
SDK
attribute
somewhere
there
and
that's
gonna
show
up
in
the
find
window
results,
so
I
find
results
window.
So
it's
worked.
So
this
was
something
that
you
used
to
be
able
to
never
do
like,
basically,
especially
for
people
who
modify
their
builds
all
the
time
right.
C
B
Of
stuff
it
was
kind
of
on
them
to
have
a
completely
untold
experience.
They
would
have
to
unload
the
project
files
they
would
have
to
edit
them
and
like
there
was
it
was.
It
was
basically
like
we
were
trying
to
hide
the
fact
that
project
files
are
files.
One
of
the
big
efforts
with
dotnet
court
was
to
reduce
the
size
of
these
things,
because
it's
like
ok,
well,
pretty
much.
Every
other
ecosystem
has
you
modify
files
for
configuration,
whereas
we
were
still
still
kind
of
stuck
in
this
world
of?
B
Oh,
we
don't
want
you
to
think
about
the
files.
We
want
you
to
use
these
GUI
tools
that,
like
hide
the
stuff
from
you
and
for
most
people
or
I
shouldn't,
say
most,
but
for
a
whole
lot
of
people.
It
was
actually
just
easier
to
modify
the
file
size.
So
in
this
case,
is
actually
a
fairly
complicated,
F
sharp
project,
but
it
there's
there's
not
a
whole
lot
there
really
and
that's
because
there
doesn't
need
to
be
a
whole.
So
does
that
work.
C
C
B
B
So
that's
also
one
of
the
one
of
the
reasons
why
I
like
you
know
that
it's
basically
it's
an
entirely
new
system
using
the.net
SDK
and
it's
much
easier
to
modify
and
we
don't
like
have
this
insane
risk
of
breaking
people
all
the
time,
whereas
the
older
system,
whenever
we
want
to
make
an
improvement,
there's
a
huge
risk
of
breaking
and
we've
done
that
before
in
the
past,
and
it's
like
we
get
kind
of-
let's
not
don't
they
don't
want
to
be
broken.
They
just
went
there.
B
C
We
catch
up
for
comments
on
comments
really
quick
because
I
well,
there's
one
comment
down
there:
I
want
to
make
sure
we
get,
which
is.
This
is
the
the
dynacord
community
stand
up,
which
is
all
things
random
things
that's
going
on
in
dotnet,
core
languages
and
runtime
and
SDK,
and
then
I
don't
know.
If
we
have
anything
above
this
that
has
scrolled
off
so
do
you
have
a
way
to
check
that
emo.
D
C
D
B
B
B
B
B
But
yeah
we
yeah,
we
have
a
new
version
of
the
language.
The
number
of
features
isn't
really
big,
but
the
number
of
changes
in
the
compiler
is
a
lot.
We
did
a
tremendous
amount
of
performance
work
in
the
compiler,
especially
when
you
have
a
long-lived
process,
and
so
especially
if
you
have
larger
solutions
or
the
big
things
is
one
of
big
problems
is
people
with
really
large
solutions
over
time
stay
over
the
course
of
an
entire
day.
They
remember.
C
B
To
get
really
really
high
and
they
might
have
to
restart
do
a
lot.
That
is
something
that
should
happen
significantly
less
as
a
result
of
some
of
its
work.
So
a
sharp
4.6
is
it's
less
about
a
whole
bunch
of
features
so
much
it
is.
It
is
a
whole
bunch
of
infrastructure
under
the
covers
to
just
make
the
stuff
that
you
do
from
a
day-to-day
basis
and
I'm.
C
Hearing
I
haven't
run
any
tests
myself,
but
I'm.
Seeing
comments
on
Twitter.
That
2019
overall
is
got
some
really
nice
performance
gains
for
folks,
and
so
it
gains
as
an
improvement.
So
not
gains
is
in
larger
numbers,
but
so,
if
you
haven't
tried
out
2019
Visual
Studio
2019,
you
might
want
to
put
it
on
your
machine
and
see
how
it
runs
for
you.
B
B
Its
yeah,
it's
basically
once
once
it's
better
than
people
say.
Oh,
this
is
the
now
the
new
thing.
Now
it's
not
good
enough,
because
this
other
thing
needs
to
be
better
and
like.
We
feel
that
internally
as
well
and
so
but
I
don't
know,
I
like
working
on
performance
in
general,
so
it's
kind
of
fun
to
talk
about
so.
B
Is
a
more
washed
out
example
of
anonymous
record
types,
anyways
they're,
just
sort
of
like
ad-hoc
collections
of
data
so
similar
the
tuples
except
they're,
they're
more
like
named
tuples,
but
they
also
are
default
comparable
default
equatable
that
sort
of
stuff,
because
we
generate
all
of
that
under
the
covers
with
record
types.
So
they
are
the
equivalent
of
f-sharp
records,
except
you
don't
have
to
declare
them
upfront
what
their
types
are.
B
C
B
B
E
B
Gonna
be
thinking
about
Donna,
core
3.0
and
we're
thinking
that
the
version
of
F
sharp
that's
gonna
go
with.
That
is
going
to
be
F
sharp
5.0,
it's
it's
gonna,
be
more
of
a
quality
call.
I.
Actually
I
talked
about
it
in
this
blog
post,
whether
or
not
we
go
with
another
minor
update,
whether
or
not
we
go
at
that
chart
five.
You
know
which
features
go
in
which
features
don't
go
in.
It's
all.
A
quality
call
we're
not
interested
in
rushing
certain
features
in
just
to
meet
a
deadline,
because
languages
have
to
be
stable.
B
So
if
something's
not
good
enough,
we're
gonna
cut
it.
But
that
being
said,
we
do
have
about
eight
features
that
are
on
deck
so
far,
most
of
which
are
not
related
to
other
dotnet
stuff,
but
one
of
the
big
ones
is
knowable
reference
types,
and
so
we
have
a
version
of
that
running.
We
ran
it
against
our
own
compiled.
We
found
15
places
where
we
weren't
doing
an
appropriate
Knoll
handle.
So
that
was
that
was
interesting.
C
B
C
So
you
didn't
get
a
lot
of
spurious
or
warnings.
The
way
you
had
written
your
code
was
such
that
there
wasn't
a
lot
of
stuff,
but
you
were
gonna,
ignore
it,
and
so
the
no
reference
work
were
the
c-sharp
yeah
work
went
really
well,
you
ran
f-sharp
nullable
references
or
c-sharp
I
think
it
said
so.
The
F
sharp
stuff
ran
on
itself.
I
know
you
didn't:
okay,
cool
great.
B
I
mean
it's,
we
don't
know
for
sure
if
those
paths
had
ever
been
hit,
but
they're
sort
of
like
ladybugs,
like
you
know,
who
knows
some
little
thingy
that
somebody
does
triggers
one
of
those
things
causes
an
exception
and
the
compiler
paints
their
editor
red.
They
have
to
close
and
open
the
file.
They
don't
know
what
caused
that
they
get
freaked
out
or
something
like
that,
and
we
made
them.
We
may
have
never
even
heard
from
those
people,
but
just
the
fact
that
we
know
that
we
can
squash
those
things
that
feel
pretty
good.
C
C
A
A
A
A
Another
end
they
have
to
bind
to
particular
types
and
so
index
type
is
basically
the
type
that
can
denote
indexing
from
the
beginning
or
indexing
from
the
end
and
range
is
basically
two
indices
combined,
and
so
we
had
to
effectively
in
order
to
support
those
types
in
them
and
in
the
framework
we
will
not
tasks,
we're
basically
adding
a
bunch
of
indexers
that
take
index
a
bunch
of
indexes
the
tank
range,
and
that
is
actually
a
lot
of
work
for
us
to
do.
Also,
there
are
some
things
that
we
just
can't
add
them.
A
So,
for
example,
if
you
take
all
the
collection
interfaces
that
we
have,
we
don't
really
have
a
way
to
add
a
method
to
an
interface
I
mean
we
now
have
the
implementations
of
interfaces
but
they're
not
fully
baked
yet
they're
not
supported
by
languages.
Yet,
so
we
don't
see
this
as
a
good
way
to
do
that.
So
basically,
what
what
this
proposal
here
is:
it's
in
the
C
shell,
an
orc.
A
It
was
accepted
and
basically
the
ideas
how
about
the
compiler
takes
care
of
that,
because
if
you,
if
you
have
an
expression
like
this
here,
where
you
say
had
one,
the
compiler
can
do
the
lifting
and
just
rewrite
this
to
this
right
and
in
the
same
way
that
the
the
compiler
can
do
this
with
range
support
as
well.
If
you
say
where's
the
example
here
yeah,
if
you
say
you
know,
you
call
the
get
method
and
then
it
would
turn
to
your
collection.
A
Maybe
not,
but
basically
the
idea
is
that
the
compiler
will
take
care
of
a
good
chunk
of
those
things
and
we
write
them
so
that
we
don't
have
to
add
a
bunch
of
stuff
to
the
VCL
and
there's
actually
issue
that
I've
filed,
which
basically
highlights
what
we
will
do.
We
basically
move
a
bunch
of
function,
I
didn't
mean
editing,
I,
don't
know
preview
three,
maybe
and
make
it
easier
for
the
compiler
to
actually
use
the
compiler
to
make
it
a
lot
easier
to
to
do
this,
which
also
makes
it
somewhat
more.
A
You
know
viable
to
use
these
interfaces
and
we
think
that's
all
a
good,
a
good
thing.
So,
if
you
do
the
languages,
learn
if
you
interested
in
library
design
and
how
they
interact,
I
highly
recommend
reading
this
fantastic
document
written
by
by
Jared.
So
it
tells
a
little
bit
about
how
the
compiler
actually
works
on
the
covers
and
how
the
framework
types
in
the
compiler
interact
in
some
meaningful
fashion.
A
cool
feature
can.
C
It
turns
out
that
the
way
that
the
VCL
put
together
the
index
and
range
they
have
factory
methods
which
are
very
readable,
like
in,
like
the
the
indexed
from
end
like
index,
stop
from
end
and
so
they're,
very,
very
readable.
And
so
the
current
plan
is
that
Visual
Basic
will
use
those
factory
methods,
at
least
to
the
point.
Where
we're
we
cover
some
other
issues
that
we
think
are
bigger
and
because
we
think
it's
it's
actually
a
very
VB
like
that
those
names.
C
D
C
Also,
just
be
it'll
just
flow
through
the
other
languages
with
no
problem,
so
it's
a
kind
of
a
cool
place
where
the
BCL
and
all
the
languages
just
kind
of
worked
without
a
lot
of
friction.
Sometimes
it's
a
little
harder
there's
a
few
features
that
we've
all
worked
harder
to
make.
No
reference
types
come
to
mind
that
were
we've
all
had
to
work
harder,
maybe
defaults,
interface
method,
so
we
just
had
to
work
harder,
but
this
was
one
where
it
just
naturally,
all
came
together,
which
was
very
cool
yeah.
A
I
actually
really
happy
with
the
feature
all
in
all,
so
the
other
thing
I
want
to
talk
about
is
observation.
So
if
you
have
paid
attention
to
net,
then
you
probably
notice
that
you
have
not
just
amazing
things.
We
also
have
some
things
that
are
somewhat
questionable
right
and
that's
just
normal
for
any
framework
that
you
know
exists
for
a
while
alright
soom
into
this,
and
actually
make
that
someone
be
the
ball.
A
A
So
basically
the
idea
is
this
right.
So
today,
if
you
so,
the
problem
that
we
have
effective
in
the
framework
is
every
time
you
obsolete
something.
Somebody
gets
a
warning
right.
That's
kind
of
the
idea
of
the
feature
fundamentally
right.
The
problem
is:
if
we
obsolete
technologies,
then
it's
not
just
a
single
API.
You
have
to
obsolete
right.
If
you
think,
for
example,
non-generic
collections
is
like
twelve
types
or
something
like
this
right,
so
that
means
you
will
have
two
obsolete
twelve
times.
A
If
you
use
twelve
tribes
to
all
your
code
base
that
can
easily
result
in
hundreds
of
warnings
in
your
code
base
right
now.
You
combine
this
with
all
the
other
things
you
would
like
to
obsolete
some
networking
API
some
reflection.
Api
is
you
know
whatever?
It
is
right,
then,
upgrading
from
one
firm
reversion
to
the
other,
no
results
and
I'd
say
five
hundred
warnings
right,
yeah.
C
D
C
A
C
A
C
A
C
Isn't
it
even
worse
because,
in
order
to
get
it
right,
if
I
want
to
say
no
more
non
generic
collections,
that
I'm
ready
to
get
rid
of
I
have
to
know
what
all
of
those
are
and
I
have
to
look
at
everything.
Go.
Is
that
in
that
category
or
is
in
some
other
category,
and
so
it's
actually
pretty
nasty
to
work
with
the
current
situation,
which
is
why
you're
looking
at
a
variation
of
it
going.
A
Forward
so
the
fundamental
idea
is
like:
if
you
look
at
the
obsolete
attribute
today
today,
it's
pretty
simple:
it
has
a
message
and
you
can
say
whether
he
wants
to
be
an
arrow
or
not
and
that's
it,
and
so
what
I
plan
on
doing
is
I
try
to
push
them
to
say.
Well,
imagine
you
get
a
diagnostic
ID,
so
you
can
basically
say
if
this
OP
solution
occurs.
Give
this
diagnostic
ID.
So
if
you
look
at
how
we
would
use
this
in
the
frame
wrap,
you
would
say
well
ArrayList
and
hash
table.
A
We
would
both
attribute
with
you
know.
This
is
the
collector,
the
ID
for
non
generic
collections
and
then
secure
string,
which
is
another
one,
would
get
a
different
ID.
And
then
you
can
say:
I
really
don't
care
about
monitoring
our
collections,
you
suppress
them
and
then
you
know
251
disappear
and
then
ten
remain
and
it's
like
secure
string.
You're
like
okay,
great,
let
me
let
me
fix
this
one.
So
this
way
you
can,
you
can
tailor
it
to
your
existing
code
bases
more
easily.
A
You
may
have
to
add,
like
you
know,
10
12,
different
warning
ideas
to
your
project
file,
but
that's
still
better
than
to
you
know,
get
like
hundreds
of
warnings
and
suppress
them
all
individually,
and
so
the
idea
is
every
of
this.
We
have
a
much
easier
time
of
actually
telling
you
when
things
are
obsoleted.
The
other
thing
I
would
like
to
do
is
add
a
URL,
because
today
the
other
problem
is
you
get
this
one
liner
and
the
one
liner
is
usually
not
enough
right.
A
So,
for
example,
non-generic
collections,
it's
really
more
of
a
well
this
collection
kind
of
maps
to
this
collection.
But
here
are
some
caveats
you
have
to
keep
in
mind.
So,
for
example,
hash
table
will
give
you
now
when
the
key
doesn't
exist.
Dictionary
goes
to
work,
he
not
found
exception,
so
you
kind
of
have
to
change
your
code
a
little
bit
and
that
you
can't
really
express
this
meaningfully
in
a
one-liner.
A
So
really
what
we
want
to
be
able
to
say
well,
there's
repeat
URL
behind
that
obsolete
category
and
then
the
idea
is
usually
that
takes
you
to
one
page
where
it's
nicely
written
up
and
in
Visual
Studio.
When
you
actually
look
at
the
error
list,
and
you
see
the
ID,
it
should
become
a
link.
So
when
you
click
on
that,
it
directly
takes
you
to
the
documentation
page
that
that
explains
to
you.
A
C
A
This
is
I
mean
the
public
I
mean
the
downside
with
the
attribute
is,
of
course,
because
it's
for
the
platform.
In
order
for
you
to
use
it,
you
have
to
upgrade
to
the
new
version.
So
if
you're
building
it
on
SNHU,
why?
Every
today,
you
can't
use
it
even
after
we
ship
this,
unless
you
put
it
into
more,
my
get
to
whatever
new
version
of
Don
and
standard
has.
Is
that
you
do
chain,
so
that's
the
downside,
but
it.
A
A
There's
this
tool
that
we
division
called
platform
content
and
basically
the
idea
is,
if
you
use
an
API
that
is
talk
from
specific,
then
it
would
be
nice
if
we
would
tell
you
up
front
that
is
platform
specifics.
You
don't
have
to
actually
run
the
code
on
the
platforms
where
it
will
blow
up
and
hit
us
and
hit
us
cut
pass
and
all
that
yeah.
The
downside
with
this
tool
is
that
this
is
a
tool
that
you
can
install
today.
A
It
works
pretty
well,
but
the
tool
today
is
basically
a
tool
that
carries
a
database
with
all
the
ephemeral
API
step
in
now.
Don't
work
everywhere,
so
it
doesn't
really
scale
for
third
parties
right.
So
the
first
thing
I
want
to
do
is
I.
Want
to
make
sure
that
we
basically
have
a
mechanism
for
anybody
to
annotate
their
own
API,
so
saying
this
one
is
platform
specific
and
then
the
second
problem
is
well.
The
tool
doesn't
really
help
you
a
lot
with
writing
platform.
A
You
know
cross-platform
code
because
it
just
tells
you
where
the
errors
occur,
but
then
suppressions
become
kind
of
hard
to
deal
with,
because
usually
what
you
want
to
do
is
you
want
to
say:
yes,
I
want
to
wrap
a
platform
specific
API,
it's
a
good
example.
Here
is
this
case
here
of
an
existing
code
path
where
you
say
or
extract
some
thing
from
the
registry,
but
if
the
registry
can't
be
used
because
I'm
going
on
Windows,
then
well,
all
I
have
to
do.
A
Is
I
just
wrap
this
code
in
this
platform
guard
and
then
say:
yep
I
only
run
this
code
when
I'm
on
Windows
and
if
I'm,
not
on
Windows
or
if
the
registry
key
doesn't
exist,
I
just
fall
back
to
some
default
value
right.
So
this
is.
This
is
historically
known
as
light
up
code.
We
just
provide
additional
functionality
on
a
particular
operating
system,
and
this
in
this
example.
Here
you
really
don't
want
to
get
a
warning,
because
your
rewrote
your
code
in
a
correct
way
and
the
other
analyzer
wasn't
smart
enough
to
realize
this.
A
C
A
Is
all
like
still
like
I
said
that
the
OPR
has
some
draft
mode.
I
will
probably
finish
the
PR
over
the
next
days.
I
will
tweet
about
it
and
I'm
looking
forward
to
get
feedback,
but
the
the
general
concept
of
platform-specific
warnings
or
an
analyzer
for
that
we
basically
have
done
like
a
year
and
a
half
ago.
We
have
shifted,
many
people
are
using
it
and
we
have
received
a
lot
of
feedback
from
that.
So
I
think
the
idea
is
pretty
much
validated
that
it's
useful,
but
you
know
as
it
is.
C
A
B
A
So
the
thing
is
basically
what
we
do
is
we
said
we
will
remove
patch
versions
by
default
in
visual
studio.net
core
right,
and
I
think
the
question
was
well
just
because
they'll
show
up
so
many
things.
This
is
really
the
right
fix
and
I
think.
The
idea
was
that,
while
Visual
Studio
will
remove
the
patches
by
default,
because
you
really
don't
want
to
be
only
this
but
I
think
you
can
still
install
the
patches
side
by
side.
If
you
really
have
to
all
right
yeah.
C
So
here's
a
couple
of
things
on
that
so
first
of
all,
Visual
Studio
itself,
is
takes
care
of
what
Visual
Studio
needs.
So
Visual
Studio
is
actually
even
a
little
more
aggressive
as
you
update
within
a
particular
channel,
so
within
either
preview
or
release
and
2017
and
2019.
So
that
would
be
four
channels.
Preview
released,
2017
2019
within
the
channel
Visual
Studio
is
doing
a
better
job
of
taking
care
of
itself.
C
If
you're
installing
on
Windows
through
the
SDK
installer,
you
get
the
behavior
that
I
talked
about
if
you're,
installing,
via
the
Zips
and
tarballs,
and
all
that
stuff
you're
taking
care
of
this
yourself,
we're
not
expecting
to
be
cleaning
up
after
you.
We're
expecting
that
you
you
want
that
control.
So
it's
absolutely
intended
that
you
can
do
that.
C
It's
just
that,
we're
being
we're
being
a
little
bit
more
helpful
for
the
many
cases
where
people
are
just
winding
up
with
boatloads
on
their
machine,
some
of
whom
work
for
Microsoft
and
take
a
lot
of
previews,
but
even
if
you're,
not
working
for
Microsoft.
If
you
take
every
patch
you're
gonna,
have
a
lot
of
I've
got
Nick
or
SDKs
on
your
machine?
Is
that
was
there
another
question?
Yes,.
A
However,
if
you
have
a
random
button,
ephemeral
project
that
may
use
features
and
tooling
that
the
desiccator
projects
do
not
support,
so
a
good
example
would
be
click
once,
let's
say,
or
ad
service
reference
or
some
of
the
other
things
laboring.
That's
it
yeah
flavoring
is
more
like
almost
immediately
good
for
us,
but
yeah
like
there's
a
bunch
of
stuff
that
we
can't
replicate.
A
B
C
And
so
just
to
clarify
that
there's
there's
the
original
project
system
and
those
the
SDK
trust
project
system
and
this
work
that
you
showed
about
2919
is
SDK
only
so
we
talked
about
is
for
framework
and
we
were
not
very
precise
when
we
did
that
because
in
fact
it's
the
SDK
style
versus
the
original
format,
as
opposed
to
actually
it
being
full
framework.
So
whoever
said
that,
thank
you
very
much.
That
comment
was
helped
us
to
be
more
precise.
So
thanks
a
lot
on
that
yeah.
C
A
The
other
question
was
how
the
Jason
stuff
coming
yeah.
We
talked
about
the
Jason
stuff.
A
lot
in
the
past
I
will
alert
up
Jason.
No
one
apart
is
that
Jason,
the
JSON
API
is
I'm,
pretty
sure
it's
the
question
here,
so
a
custom
type
of
solution,
the
polymorphism.
It's
your
last
types,
all
that
yeah.
We
will
talk
a
little
bit
more
about
this
right
now.
We
are
heavily
working
on
this,
so
this
thing
is
changing
faster
than
I
can
speak
and
again.
A
So
that's
not
necessarily
helpful,
so
I
will
cover
that
in
a
later
episode.
The
other
question
was
the
observation
or
for
our
suggestions
for
replacements.
No,
because
in
the
general
case
of
solutions
are
not
done
when
there's
literally
a
drop-in
replacement,
because
if
there
would
be
a
drop-in
replacement,
but
what
would
the
observation
be
about?
The
shape
of
the
AP
are
the
name.
Neither
of
them
are
really
good
reasons
to
obsolete
something
usually
obsolete,
something
when
the
fundamental
design
is
bogus
or
has
shifted
right.
A
Think
non-generic
collections,
engineering
collections
right,
like
they're,
there
is
really
a
one
to
one
with
Iseman
I
there's
a
suggestion
to
replace.
Let's
say
hash
table
dictionary,
but
we
can't
really
code
fix
this
because
well
you
have
to
change
the
code
that
you
use
to
get
made
use
out,
for
example,
right
so
I
fundamentally
believe
that
there
has
to
be
a
dog
page
that
you
have
to
read
and
understand,
like
I.
Don't
think
we
can
do
that
and
then
you
know
it
takes
secure
string.
Did
they
really
the
replacement
here
is
don't
use
it.
A
So
how
would
you
even
do
that,
like
the
the
replace
from
there's,
don't
have
passwords
use
other
means
of
authentication
I,
don't
require
you
to
pass
your
own
password.
So
again,
like
your
your
code
fixes
reengineering
your
application
right.
It's
not
it's
not
like!
Oh
yeah,
you
know
change
this.
One
line
with
this
one
line,
I
think
that's
all
we
had
are.
C
A
C
C
The
second
time,
if
you
are
producing
one
of
those,
you
need
to
be
aware
that
you
won't
need
to
continue
to
target
2.2.
We've
tried
to
make
this
2
at
2
or
below.
We've
tried
to
make
this
as
smoother
transition
as
possible,
but
we
are
transitioning
to
to
the
new
net-net
sdk
tunneling
system,
the.net,
CLI,
tooling,
system
with
local
and
global
tools
and
local
tools
are
now
introduced,
and
we
really
want
to
hear
where
there
are
not
a
full
replacement
for
dotnet
CLI
tool
reference.
C
But
the
reason
that
we
did
a
new
design
is
that
dotnet
CLI
tol
reference,
really
it
has
a
really
serious
flaw
in
its
design
and
because
of
that,
we
just
we
created
the
new
system
from
scratch
and
now
we
need
to
start
turning
the
old
system
off
and
it
will
continue
to
have
all
the
problems
it
has
today
which
I
can
discuss
in
way
more
detail.
But
you
put
up
with
versions
so
I'm
not
doing
that
to
you.
C
We
we're
going
to
hold
that
at
2.2,
so
we
will
not
make
the
situation
worse
by
going
across
the
major
version,
boundary
and
various
other
things
that
contribute
to
making
it
worse.
So
if
you
go
to
done
a
core
3.0
and
you
use
a
package
that
is
a
dotnet
CLI
to
a
reference
for
at
least
the
three
Oh
time
frame,
you
should
work
fine.
C
The
only
thing
is
that
you're,
the
producer
that
package
does
need
to
target
2.2
or
below,
or
it
just
won't
work
and
I,
don't
know
how
much
help
we
will
be
able
to
give
authors,
because
they
don't
all
use
donut
pack
to
create
those
tools.
So
since
we
don't
know
how
it's
created,
we're
not
sure
we're
even
going
to
spend
the
cycles
to
give
warnings
to
the
authors,
but
the
authors
need
to
know
this,
and
as
soon
as
they
try
to
run
it,
then
it
will
fail
if
it
targets
done
it
three
dot
o.
C
So
all
your
tools
should
still
keep
working
if
you're
an
author
and
are
not
making
any
changes
to
your
tool.
Everything
should
be
fine,
but
if
you
are
planning
for
a
future
for
your
tool,
please
be
aware
that
that
future
for
a
dotnet,
CLI
tool,
reference
should
not
include
dotnet
core
3.
That's
a
problem
for
you
should
definitely
reach
out
to
me.
We
had
a
few
internally
that
were
actually
kind
of
gnarly
and
we
were
able
to
work
with
people
to
to
get
a
good
solution
for
them.
C
C
So
if
you've
been
wanting
to
specify
preview
and
your
global
dot,
JSON
we're
working
on
that
we're
working
on
some
other
possible
changes
as
well,
and
if
you
watch
dotnet
designs,
I
expect
we'll
have
a
draft
design
which
all
of
the
designs
on
dinah
designs,
you
should
expect,
may
change,
but
I
hope
that's
gonna
be
up
today
or
tomorrow.
So
you
can
watch
for
that.
It.
A
A
B
C
C
You
brought
you
brought
a
bow
while
you
were
talking
about
observables
I.
Think
if
folks
have
things
that
observable
does
that
you
do
not
think
that
the
I
sink
and
numerable
is
going
to
do.
You
should
make
sure
it's
in
our
radar
and
let
us
know
you
can
reach
out
to
to
me
and
I'll
pass
it
on
it's.
It's
not
an
area
of
my
high
expertise,
but
I
can
certainly
have
pass
it
on
or
you
can
I
reach
out
on
C
sharp
line.
C
sharp
Lang
is
always
a
good
place
for
all
things.