►
Description
Join members from the .NET teams for our community standup covering great community contributions for Framework, .NET Core, Languages, CLI, MSBuild, and more.
B
A
B
A
D
A
A
B
She
knows
nothing
about
what
we're
doing.
I
just
asked
her
to
come,
so
she
just
parachuted
in
and
we're
where
she
has
no
absolutely
no
idea
what
we're
gonna
do
here
with
her,
but
she's
got
something
I
want
to
show
I
want
her
to
show
later
so
all
right.
So
where
do
you
want
to
start
today?
Email,
yeah,.
A
Very
worried
for
him.
Well,
yes,
so
am
I
that's
that's
a
good
point
so
anyway.
So
if
you
are
in
the
chat,
please
ask
questions
as
usual:
we
try
to
answer
them.
If
we
can
make
sure
you
ask
a
bunch
of
questions
about
rich
because
nobody
can
answer
them
and
there
will
be
fun
exercise
yeah.
So
today
what
we
can
talk
about
a
bunch
of
stuff.
Let
me
actually
move
my
keyboard
around,
because
I
I
cannot
see
what
I'm
doing
it's
all
messed
up.
I.
A
A
We
were
talking
about
it,
so
you
probably
your
arm,
maybe
have
heard
about
this,
so
in
the.net,
compton
frame.
We
posted
this
thing
called
the
project
maturity
model
we
blocked
about
on
the
dotnet
block,
but
the
real
announcement
was
under
the
net
foundation
block
because
it's
really
an
initiative
from
the
donut
foundation.
A
They
said
the
goal
we
pursued
with
this
was
we
wanted
to
make,
so
we
wanted
to
make
it
easier
for
people
to
take
dependencies
on
open-source
projects
in
a
way
where
they
can
trust
the
project,
and
they
know
where
the
project
is
coming
from
right
and
what
we
have
seen
over
the
last.
What
15
years
of,
like
you
know
open
source
in
the
community.
It
was
basically
like
I
would
say
this
like
to
kind
of
Tia
model
right.
A
That
was
like
a
microscope
provided
open
source
project
and
the
rest
right
and
like
the
problem
of
that,
is
that
many
enterprises
said
we
only
trust
things
that
come
from
Microsoft
and,
of
course
we
don't
want
this
to
be
the
default
moving
forward
right.
Our
intention
is
to
to
make
it
so
that
there's
many
high
quality,
open
source
project
projects
and
libraries,
in
fact,
some
of
them
were
way
better
than
what
Microsoft
put
together.
A
I
mean
you
pulled
him,
a
member
of
the
early
days,
so
system,
dot
Jason,
where
we
try
to
provide
JSON,
API
and
couldn't
quite
get
them
right
and
Jason.
What
Ned
was
the
library
that
actually
everybody
was
using
and
it
wasn't
done
by
Microsoft
right,
so
we
really
wanted
to
create
a
model
where
people
can
reason
about
the
open
source
projects
in
the
sense
that
you
know
as
a
fortune,
500
company
and
you
think
about
10
plus
years
Hulk.
How
can
you
make
sure
the
dependencies
you
are
taking
are
safe?
They
don't
disappear
overnight.
A
There
was
this
idea
that
this
was
a
Microsoft
driven
idea
and
Microsoft
is
forcing
their
view
on
the
rest
of
the
world.
But
really
what
happened
is
we
worked
with
the
dotnet
Foundation
board?
And
you
know
it
was
basically
BRR
ation
between
people
from
our
team,
which
learner
in
particular
and
the
dotnet
Foundation
board,
and
we
also
worked
with
several
projects
that
already
on
the
in
the
foundation
to
validate
that
this
model
you
know,
has
legs.
A
Unfortunately,
we
didn't
share
it
publicly
before
we
announced
it
at
the
donut
convent,
and
some
people
were
surprised
by
this,
and
so
there
was
some
sort
of
you
know,
expression
of
disappointment
and
how
we
communicated
this
and
I.
Think
that's
that's
a
very
fair
statement
at
this
point.
There's
there's
a
you
know.
Also.
We
got
some
feedback
on
the
model
itself.
The
way
we
measure
quality
or
you
know,
plan
on
measuring
quality
and
so
right
now
what
ends
up
happening
is
Ben
Adams,
who
is
a
dotnet
Foundation
board?
Member
and.
B
Not
a
Microsoft,
some
of
the
people
on
the
couple
people
in
the
video
are
Microsoft
people
Ben
is
not
he's.
He's
a
community
member,
a
longtime
community
member
I've
done
a
lot
of
really
good
stuff
in
the
community
and
is
also
on
the
board
and
was
part
of
building.
This
I
think
he's
also
made
a
statement
about
this
house
new.
Yes,.
A
It's
a
Vernon
was
just
standing
on,
but
because
you
just
mentioned
that,
like
you
know,
if
you
look
at
the
dotnet
Foundation
board,
this
is
these.
Are
the
board
members
Beth
messy
is
the
only
Michaels
would
employee
here.
Everybody
else
is
not
working
for
Microsoft,
but
they're.
All
community
members
Phil
heck,
used
to
work
on
Microsoft
a
long
time
ago.
He
joined
guitar
when
you
already
left
get
up
again.
So
now
he's
I.
A
Think
self-employed
right
now
has
his
own
gig,
so
they're
all
people
that
are
independent
of
Microsoft
and
have,
of
course,
their
own
views
on
how
things
should
be,
and
we
believe
that's
that's
actually
a
good
thing.
I
mean
that
was
the
whole
idea
of
the
donor
foundation
being
a
separate
entity
that
we
wanted
to
have.
A
You
know
stewardship
of
net
that
is
not
dictated
just
by
Microsoft,
right
and
so
Ben
Adams
is
not
the
person
who
is
basically
taking
this
whole
idea
of
the
maturity
model
and
he
what
a
very
lengthy
blog
post
about
all
the
issues
that
you
know.
We
have
received
over
the
model
that
was
proposed
and
he's
the
one
who's
driving
this
moving
forward.
A
So
I
am
I'm
very
happy
to
see
this
and
I'm
also
very
happy
to
see
that
there's
a
lot
of
community
engagement
here
and
it's
not
just
driven
by
Microsoft,
but
it
will
probably
take
us
a
long
time
to
get
this
into
some
some
shape
and
but
a
long
time
I
mean
probably
I,
don't
know
at
least
six
months,
but
we
will
people
be
my
guess.
The
other
thing
I
would
like
to
point
out
here.
There
was
like
there
was
some
people
who
were
saying
that
this
is
an
example
of
Microsoft.
A
Doing
it
badly
and
I
would
agree
with
that.
Like
I
think
the
way
we
communicated
it
was
not
ideal
and
I.
Think
we've
learned
our
lesson
here
once
again
that
we
should
be
very
careful
with
the
way
we
we
know
we
communicate
things
and
make
sure
we
and
we
engage
the
community
as
early
as
possible.
So
that
surprises
like
this,
don't
happen
again.
A
B
Were
just
so
excited
about
this
that
we
got
carried
away
and
it
wasn't
clear
enough
that
it
was
really
intended
as
a
proposal
that
was
worked
out
with
people
outside
Microsoft,
but
we
were
Microsoft.
We're
really
excited
about
the
idea
of
making
Microsoft
a
more
even
player
in
certain
aspects
of
the
open-source
community.
We
would
like
you
to
be
able
to
use
open
source
projects
with
confidence,
and
we
have
talked
to
people
over
the
years
to
understand
some
of
the
reasons.
People
are
hesitant
and
that's
that's
the
goal,
and
it
was.
B
It
was
kind
of
a
side
select
to
us
because
we
were
so
excited
about
making
it
more
open
and
we
made
mistakes.
It's
not
perfect.
We
need
to
adjust
it,
but
in
our
excitement
we
were
like
did
I
and
people
would
go,
you
didn't
get
it
right
and
we're
like
great.
Let's
fix
it
and
that's
the
mode.
We're
in
right
now
is
just
that
that
fix-it
mode,
but
we're
still
excited
about
it.
We
still
think
it's
a
good
idea.
We
just
think
it
needs
tweaks
to
be
right
for
the
community.
You.
B
Community
people
that
work
hard
authoring
and
maintaining
open
source
software,
we
obviously
want
to
be
supporting
them
and
then
also
making
sure
that
it
is
giving
confidence
to
the
people
that
are
out
there,
that
that
will
make
it
easier
for
them
to
adopt
easier
for
the
people
in
the
trenches
writing
software,
because
their
organizational
rules
can
be
looser
around
the
open-source
they
use.
So
that's
that's
where
we
came
from.
We
never
meant
it
to
be
Microsoft
trying
to
do
a
you
know
a
control
grab
or
anything
like
that.
That
was
never
the
intention.
A
A
A
Like
the
idea,
the
intention
was
that
the
Bobby
announced
was
an
expression
of
intent
that
we
were
built
this
plant
with
the
community,
but
I
think
part
of
the
reason
was
we
announced
it
as
part
of
the.net
corner.
He
basically
announced
the
GA
version
of
donek,
or
so
there
was
an
expectation
that
everything
we
announced
that
day
is
GA,
which
is
not
the
case
right.
C
A
B
B
C
B
Developer
box
was
an
x64
box,
so
they
were
in
64-bit
and
they
did
a
publish
and
they
got
an
executable
and
they
were
extremely
confused
about
why
that
executable
wouldn't
run
on
x86,
which
is
in
fact
a
different,
read
and
would
need
a
different
publish
output.
The
only
piece
of
it
that
is
specific
for
a
framework
dependent
application
is
the
executable.
So
if
you
want
to
type
dotnet
space
blot
DLL,
you
can
run
it
and
in
fact,
Sarah
sent
me
an
executable
this
morning.
That
was
a
Windows
executable.
B
I
said
well
that
won't
work,
but
I
can
still
run
what
she
sent
me
on
my
Mac
by
saying
net
space
blah
dll.
So
the
two
key
takeaways
here
first
of
all,
self-contained
is
not
portable
across
hardware
platforms
and
exe
s
are
not
portable
across
hardware
platforms.
You'll
need
one
for
x86
and
x64
and
Mac
OS
and
Linux
distributions,
and
so
the
rids
are
the
driver
there
as
to
what
we
can
group
and
what
has
to
be
specific
to
the
platform.
So.
A
B
C
A
B
A
A
A
That
gets
folded
amando
the
way
you
would
invoke
stuff
now.
The
thing
is,
though,
this
one
here
that
is
basically
portable,
because
the
idea
is,
you
have
a
dotnet.
You
have
a
dotnet
on
your
box,
that's
specific
to
your
hardware.
This
guy
basically
takes
care
of.
You
know
what
architecture
the
about
operating
system.
Do
you
have
that's
kind
of
the
interaction,
and
this
guy
just
is
pathetically
your
app.
So
assuming
your
app
itself
doesn't
do
anything
where
specific.
The
idea
is
that
the
output
here
is
generally
portable,
except
for
this
launcher
here
right
right.
B
And
and
you're
so
correct
that
what
the
exe
is
is
actually
the
app
host
that
we
use
inside
of
dotnet
exe.
That
has
been
hard
branded
or
hard-coded
into
your
DLL.
So
we
we
initially
did
this
for
our
global
tools
and
then
we
were
able
to
push
it
out
everywhere,
so
it's
ajust
a
special
quick
copy
of
the
app
post
by
the
way.
If
that
feels
a
little
bit
big,
we
think
so
too.
We're
planning
on
making
that
smaller
in
the
5o
timeframe.
B
Yoko
does
so
we
have
to
find
the
right
code
to
run
on
your
machine.
That's
the
big
thing
that
happens.
It
goes
and
it
finds
the
right
code.
It's
also
going
to
use
I'm
like
I.
Don't
think
we're
gonna
talk
deeply
about
it,
but
there's
a
runtime
config.
They
can
do
some
roll
forward
stuff.
It
can
give
some
more
information.
All
of
that
selection
of
what
framework
is
actually
going
to
do
is
actually
going
to
be
used.
There
might
be
multiple
ones
installed
on
the
machine.
B
That's
all
done
by
this
app
host,
which
is
in
Kathleen
exe,
and
then
it
does
all
that
work
sets.
It
up
knows
exactly
what
skin
around
it's
ready
to
go
and
then
it
kicks
off
the
DLL
in
the
same
way
that
dotnet
exe
it's
a
little
lighter
than
net
dot
exe,
but
that's
just
because
there's
other
work
done
it
exe
has
to
do
that.
You
don't
have
to
do
here,
and
this
executable
and
I
think
we
haven't
done
a
really
good
job
and
I
know.
B
You
know
I'm
I'm
behind
on
my
blogging
and
my
Docs,
and
so
I
wanted
to
just
bring
that
up.
Today
and
make
sure
it's
clear
and
I
think
we
should
probably
make
sure
that
nobody
has
questions
on
that,
because
some
folks
have
been
confused
about
it.
It's
tired
of
squinting
to
see
text.
Does
that
mean
that
we're
not
big
enough
because
we
can
make
it
bigger
few.
A
C
A
B
B
B
You
can't
supply
red,
so
I'm,
afraid
I
can't
immediately
talk
on
the
nuance
between
supplying
it
here
or
publish
I'm
gonna
assume
you
would
do
it
both
places,
but
I
assume
that
that
is
I'm,
not
gonna.
Actually,
I'm,
not
gonna.
Guess
let
me
just
not
guess
right
there,
okay,
I,
think
I
know
what's
going
on
there,
but
I'm.
Unless
it's
Rd.
Do
you
have
an
answer
to
that?
No
yeah
ask
the
person's
been
here
for
just
a
while.
Well
put
you
on
the
spot,
yeah
all
right.
B
And
Phillip
is
like
really
excited
about
this
demo,
because
I've
seen
his
machine
and
I've
seen
Emma's
machine
and
it
really
shows
the
difference
between
how
different
people
look
at
the
way
that
they
treat
their
machine
so
emos
machine
and
if
you
know,
email
you're,
not
surprised.
Okay,
it's
very
neat,
okay,
his
car's,
not
as
neat
as
his
machinist,
but
his
machine
is
very
neat.
My
car's
been
Steven,
hi
I
haven't
been
in
it
for
a
while
and
and
his
his
nose
yet
gets
don't
get.
B
This
kids
are
older,
so
young
as
they
were,
while
back
so
at
any
rate
that
we
have
been
putting
a
lot
of
SDKs
and
in
runtimes
on
people's
machines,
we're
sorry.
We
are
doing
a
lot
of
work
to
make
this
not
true
going
forward,
but
we're
in
this
transitional
period
we're
in
I'm
going
to
talk
about
Visual
Studio.
B
But
the
same
thing
is
true:
if
you
put
it
on
yourself
so
Visual
Studio
is
just
the
case
where
we
feel
like
it's
extra
bad,
because
if
you
were
doing
dotnet
core
development-
and
you
took
every
update
that
for
Visual
Studio,
you
have
a
lot
of
copies
on
your
machine
and
we
going
forward
are
not
doing
that
anymore
so
going
forward.
Each
version
of
Visual
Studio
is
much
smarter
about
cleaning
up
after
it.
B
So
if
I
won't
go
into
the
details
of
that,
but
it
will
not
always
be
a
hundred
percent,
but
at
least
it's
going
to
be
small
enough
that
anything,
it
leaves,
and
you
don't
want
anymore.
You
can
just
go
to
add/remove
programs
in
Windows
and
take
it
off
because
Visual
Studio
here
we're
talking
Windows
and.
A
B
B
You
know
the
infos
a
good
way
to
do
that.
You
also
have
list
SDKs
and
Lister
runtimes,
and
so
you
can
see
that
that
he's
got
basically
one
SDK
and
now
there's
several
runtimes
that
come
along
with
that.
So
he's
actually
got
some
old
runtimes
that
he's
still.
That
would
be
there
either
because
they're
installed
by
default
with
Visual
Studio,
because
that's
a
long
term
support
release
or
because
you
implicitly
put
them
on
the
same
kind
of
thing
can
happen
if
you
use
our
installer
going
to
our
website.
B
B
I'm
gonna
have
to
look
that
up.
I
feel
really
bad.
That
I
don't
have
that
on
top
of
my
head.
Okay
was
an
intern
with
this,
is
summer,
wrote
the
tool
and
on
the
day
he
left,
we
had
it
reviewed
by
somebody
for
UX,
and
it
didn't
really
do
well
in
that,
which
is
entirely
my
fault,
and
one
of
the
reasons
I
want
to
talk
just
thing
out
things
I
want
to
talk
a
little
bit
about
is
that
this
is
a
community
stand
up.
B
It's
on
me
that
it
happened,
and
then
it
kind
of
kind
of
got
quiet
for
a
while
until
we
got
Sarah
and
had
the
resources
to
put
somebody
back
on
it
and
respond
to
the
the
UI
feedback
that
we
got,
and
so
the
interesting
thing
is
that
I
gave
sarah
feedback
a
couple
days
ago,
and
she
did
exactly
what
I
told
her
to
do.
I
looked
this
morning
and
go:
oh
I've
got
more
feedback,
so
we
had
this
back
and
forth
between
engineers,
who
also
have
a
huge
amount
of
input
on
the
product.
B
I
love
working
with
all
the
engineers
on
all
the
teams,
I
work
with,
because
they
have
really
really
good
opinions
on
things.
At
the
end
of
the
day,
I
have
to
do
the
hard
stuff
I
have
to
you
know,
make
the
decisions
on
whether
we're
going
to
hold
because
of
the
feedback,
but
anyway,
it's
absolutely
fantastic
to
work
with
the
teams.
I
do
so.
Let
me
let
Sarah
show
you
this
tool.
So
if
you
can
join
the
meeting,
oh.
A
B
B
Going
to
be
available
on
the
downloads
page
it'll
first
be
available,
I
believe
in
a
preview
and
then
fully
available.
Its
job
is
to
clean
up
your
machine
right
now
it's
focused
on
three
below
300,
which
was
one
of
my
requests
yesterday
and
then
I
looked
at
my
Mac
and
realized
that
for
Macs
we
are
not
yet
doing
the
extra
levels
of
cleanup
that
we're
doing
on
the
on
the
windows
boxes.
So
we
might
want
to
go
ahead
and
also
have
this
available
higher
than
three
at
least
on
Macs.
B
So
that's
one
of
the
pieces
of
feedback
that
Sarah
had
not
heard
until
this
moment,
so
you
can
see
that
that
it's
got
three
commands
dry
run.
What
if
and
removed,
and
one
of
the
pieces
of
feedback
we've
got,
was
that
just
saying
the
name
of
the
command
net,
core
uninstall
and
then
hitting
return
and
having
it
be
destructive
on
your
machine
was
like
not
a
good
idea,
so
we
added
the
remove
command
so
that
by
default
it
gives
you
nothing.
It
doesn't
do
any
any
work.
So
why.
C
Don't
I
give
it
to
you
and
let
you
show
that
show
it
off
yeah,
and
so
one
of
the
commands
that
you
didn't
mention
was
the
list
command
as
well,
so
I'll
run
that
it's
being
a
little
laggy,
but
it
just
displays
all
of
the
SDKs
and
rent
times
that
I
have
installed.
My
machine
is
relatively
clean.
Considering
I
got
it
five
weeks
ago
you
can
see
the
SDKs
that
I
have
installed
and
the
ones
that
don't
have
the
little
brackets
next
to
them
are
things
that
we're
fine
with
you
uninstalling.
C
So
if
I
wanted
to
do
a
dry
run
of
that
dry
run
and
what,
if
are
the
same
thing,
then
I
can
say
that
I
want
to
uninstall
all
the
SDKs
that
we
think
are
definitely
safe
for
you
to
uninstall
and
on
my
computer.
I.
Don't
have
any
right
now,
but
if
I
wanted
to
tell
you
I
definitely
want
to
uninstall
to
point
one
point
701.
Then
it
will
allow
me
to
explicitly
uninstall
that
with
a
warnings
that
it
could
break
things
and
the
reason.
B
What
it
could
break
is
visual
studios,
so
where,
where
we
don't
want
one
of
the
other
pieces
of
feedback,
we
got
on
the
on
the
review,
which
I
give
a
shout
out.
It
was
Scott
Hanselman
who
gave
us
really
good
feedback
on
this.
Unfortunately,
because
my
schedule
was
Scott,
it
was
very
late.
New
tongue
was
was
leaving
us.
We
one
of
the
pieces
of
feedback,
was
not
to
break
Visual
Studio
easily
at
least
make
it
hard
to
do,
and
so
we've
put
in
some
pieces
that
we
think
will
do
that.
B
It's
one
of
the
reasons
we'll
go
out
and
preview
is
to
make
sure
we're
doing
that.
If
we
happen
to
break
your
visual
studio,
you
can
just
do
a
repair
to
fix
it,
but
this
is
so
in
process
that,
if
you
want
to
go
to
the
github
site,
you
can
absolutely
give
feedback
on
this
as
well
as,
of
course,
we'll
try
to.
If
you
put
something
in
the
window,
we'll
work
from
that
to
yeah
alright.
So
we.
A
C
A
It's
the
idea,
if
I
have
let's
say
to
one
a
hundred
and
two
one,
two
hundred,
that
we
would
only
uninstall
the
two
one,
one
hundred
or
whatever.
It's
basically
that
we
only
remove
the
older
patches
but
belief,
major
versions
and
minor
version
like
at
least
one
of
them,
like
the
latest
one
on
each
of
them
on
the
box.
Yeah.
B
And
it's
it's
a
little
bit
more
complicated
than
that
because
of
the
way
that
the
whole
SDK
historic
numbering
has
been
it's
better
than
nightmare,
so
we're
basically
blocking
removal
of
things
that
we
think
a
copy
of
Visual
Studio
could
be
on
your
machine.
We
actually
don't
check
that,
and
so
then
you
can
look
at
you
go
you
know,
20:19
update,
3,
I,
know
I,
don't
really
need
anything
lower.
B
Let
me
just
get
rid
of
a
lot
of
stuff
and
then
of
course
again
the
how
their
approach
you
can
take
is
clean
up
my
machine
and
then
I'm
going
to
repair
my
Visual
Studio.
We
don't
think
that's
a
bad
plan.
We
just
think
it's
embarrassing
to
say
that's
our
major
plan,
so
we
put
in
these.
These
back
stops
yeah
and
we
can
you
know
we
have
this
round.
If
you
show
it
again,
we
can
also
show
that
we
have
this
I
think
it
was
an
opportunity.
B
Can
you
do
the
the
list
again
mm-hmm
to
show
how
pm's
can
say
something
that
they
don't
actually
mean?
Okay,
so
this
is
exactly
what
I
asked
Sarah
to
do,
and
the
PR
which,
by
the
way
is
not
checked
in
will
say
what
the
github
site
is,
but
we
are
this
is
this
is
not
quite
checked
in
once
it
is.
You
could,
of
course
build
it
yourself
and
run.
This
immediately.
Is
that
right
now
you
could
uninstall
the
run
times
that
are
needed
by
some
of
the
SDKs.
B
B
This
is
a
place
to
go,
look
for
tab
completion
and
then
once
you
do
that
all
system
command
line
stuff
should
respond
to
that
and
so
I
don't
know
whether
Sarah
has
done
that
so
I
don't
know
if
town
completion
would
work
at
all
and
then
to
do
the
what
you're
asking
for
there,
we
would
need
a
little
bit
of
extra
completion
and
we
might
look
at
how
easy
that
is
to
do,
but
that's
a
great
feedback.
Anything
else.
Yeah.
A
B
Is
not
about
an
envious
to
do
that
we
are
going
to
definitely
want
to
prove
it
out
via
the
download
make
sure
that
we're
extremely
comfortable
with
it
and
then
we'll
chat
with
the
folks
in
Visual
Studio.
My
hope
is
that
we
will
find
a
place
for
it.
If
we
do,
it
would
most
likely
be
in
the
willow
installer,
because
that's
the
place
that
you're
already
elevated
this
does
obviously
require
elevation.
B
Maybe
it's
not
obvious,
but
we
are
messing
with
your
program
files,
so
it
does
require
elevation,
and
so
willow
would
probably
be
the
most
likely
place
that
we
would
look
at
putting
that,
but
it's
not
obvious
how
it
fits,
and
we
want
to
be
extremely
confident
in
it
before
we
do
that.
We're
kind
of
trying
to
stick
our
realize
that
we
did
a
bad
thing,
we're
trying
to
fix
it
as
best
we
can
in
the
short
term
and.
D
D
Oh
there's
like
a
very
strong
expectation
that
it
will
always
work
100%
of
the
time
you're
not
gonna,
get
into
this
weird
spot
and
like
we've,
we've
we've
gotten
into
trouble
before
like
putting
stuff
in
there
with
like
a
button
that
you
can
click
and
then
it
doesn't
always
work
and
then
it
like.
Some
people
are
like.
Oh,
it
wasn't
clear
why
it
didn't
work
right
and
and
then
yeah
it's
it's
Joan.
So.
B
We
have
a
couple
things:
real,
quick
in
the
chat
that
I
want
to
respond
to.
One
is
I'm,
not
sure
whether
it's
related
to
this,
but
the
Linux
or
Windows
comment.
This
doesn't
work
on
Linux,
because
Linux
has
its
own
way
to
do
things,
so
we
don't
want
to
get
in
the
way.
So
it's
not
available
there.
It
is
available
on
Mac,
Sarah
and
I.
Probably
two
fine
tuning
a
couple
things
on
Mac
do
to
the
rest
of
our
acquisitions
story
and
on
the
logging.
B
We
do
give
some
feedback
about
what
we're
actually
doing,
I
think
the
broader
problems
that
this
could
cause.
You
will
not
happen
running
the
tool,
but
will
happen
later,
and
we
are
working
on
things
for
the
5o
timeframe
to
overall
improve
our
acquisitions
story,
meaning
that
we
don't
make
common
scenarios
easy.
An
example
is,
if
you
have
a
global
Dutch
JSON
that
says
you
should
be
using
this
version,
and
that
version
is
not
on
the
machine.
Our
error
is
not
as
great
as
it
could
be.
Doesn't
tell
you
enough
about
how
to
solve
it.
B
So
those
are
the
kinds
of
things
that
we
are
looking
for.
We
would
love
any
feedback
from
you
about
where
it
is
painful
to
get
the
right
versions
of
the
SDK
and
runtimes
and
I
guess
as
part
of
that,
I
also
want
to
bring
up
that.
We
think
you
should
always
run
the
latest
SDK
and
that
will
build
everything
previous.
B
We
know
there
are
people
that
want
to
take
more
conservative
stance
on
that,
but,
as
we
go
into
the
three
hour
time
frame,
we
do
plan
on
only
servicing
the
two
and
that's
because
we
have
become
overwhelmed
to
a
point
that
we
would
have
been
unable
to
move
forward
by
the
number
of
things
that
we're
producing
it
just
it.
You
know
it
was
going
towards
25
versions
across
nine
deployments
into
a
whole
bunch
of
different
scenarios
and
the
whole
matrix,
which
just
went
completely
crazy.
B
So
we
do
plan
to
service
the
tip
and
the
SDKs
wills
will
build
all
previous
runtimes,
so
I'll
add
that
it's
kind
of
out
of
the
blue.
It
was
kind
of
a
segue
away
from
making
sure
does
everybody
have
their
questions
for
Sara
answered
because
she's
gonna
leave
us
in
about
15
or
20
minutes.
She
has
another
meeting.
She
needs
to
get
to
so
actually
important
people.
These
are
customers.
B
A
B
A
Let
me
taste
is
obviously
relevant
like
like
well,
let's
say
right,
but
I
think
the
difference
is
we
want
to
make
sure
that
the
IDE
looks
consistent
with
the
rest
of
the
operating
system.
Right
and
like
you
know,
Mac
has
a
very
different
UX
from
Windows,
so
it
makes
sense
to
me
that
vs,
the
format
looks
different
than
ps4
Windows
does,
because
you.
C
A
Look
great
on
how
the
operating
system
looks
like
and
personally
I,
actually
like
the
very
clean
look
and
feel
of
yes,
for
my,
like
vs,
looks
a
little
bit
more
like
you
know:
Boeing
747!
You
know
if,
like
a
500
switches
everywhere
and
that's
cool
that
has
his
own
charm
but
I
actually
like
to
clean
our
local
ps4,
Mecca
yeah.
B
Then
you
will
have
downloaded
things
from
from
the
download
page
and
if
you
are
using
our
installer
than
this
tool
that
you
Chong
and
Sarah
have
been
working
are
going
to
be
great
and
if
you
use
zips
and
tar
balls,
it
won't
touch
them
because
we
feel,
like
you,
have
made
a
statement
of
control
and
we
don't
want
to
mess
with
it.
So,
for
the
same
reasons,
we
don't
mess
with
Linux.
We
don't
mess
with
things
installed
with
zips
and
tar
balls,
there's
actually
a
technical
reason
to
be
really
hard.
B
B
A
B
A
A
Basically,
the
idea
is,
we
asked
for
a
bunch
of
blog
posts
right
and
so
like
keep
the
ideas
coming.
I
mean
you
know,
as
you
said,
like
we're
all
somewhat
behind
of
what
we
can
talk
about
and
like
all
the
things
you
could
be
documenting
and
right
now
we
are
busy
doing
two
things
where
you
know:
preparing
dotnet
core
3.1,
which
is
basically
the
rock-solid
version
of
three
oh,
and
we
also
already
starting
or
planning
on
donate
five.
B
It's
landing
also
right
in
the
middle
of
the
fall
conference
season,
so
we're
we
have
all
sorts
of
other
things
that
you
know.
We've
got
people
traveling
all
around
for
conferences,
September
through
November
used
to
be
September
in
October,
and
now
it's
stretched
into
all
the
way
to
Thanksgiving
Deb
intersections
the
week
before.
Thanksgiving
ignite
is
the
first
week
in
November,
and
so
we're
excited
about
those
things.
It's
great
fun,
but
it's
also
makes
it
even
more
stuff
to
get
done
if.
A
D
D
And
yeah
it's
got
some
pretty
neat
little
features
in
it.
I
think
I've
talked
about
them
before,
but
yeah.
It's
it's
shipped.
It's
out
there
like.
If
you
get
the
latest
on
it
chorus
TK.
If
you
get
the
latest
visual
studio,
then
you're
just
gonna
get
it
that's
sharp
or
something
by
defaults
and
what's
cool?
Is
it
also
ships
with
to
preview
features?
D
So
if
you
can
set,
you
can
set
the
language
and
property
in
your
project
file
to
be
preview,
and
then
you
can
get
access
to
the
name
of
feature
and
opening
of
static
classes
which
we're
probably
going
to
tweak
the
designs
of
a
little
bit.
So
like
we
reserve
the
right
to
break
your
code.
If
you
use
those
features
because
it
is
preview,
but
they
are
stable
enough
to
use
but
more
for
the
purposes
of
giving
us
feedback
than
anything
else.
D
When
the
first
previews
of
dotnet
5
come
out,
which
is
I,
don't
even
know
when
that's
gonna
be
but
I'm
going
to
assume
it's
probably
gonna,
be
sometime
early
next
year,
because
we're
not
going
to
come
out
with
a
preview
over
Christmas.
That
would
be
weird.
So
present
at
least
historically,
we
always
kind
of
do
it
like
in
the
fall
or
in
you
know
the
new
year,
and
so
whenever
that
time
is
F,
sharp
five
is
going
to
be
also
in
its
first
preview.
D
So
we're
gonna,
align
F,
sharp
five
previews
of
sorry
ya,
previous
of
F,
sharp
five
with
previews
of
dotnet,
five
sort
of
whenever
we
have
that
monthly
rolling
preview
cycle,
we're
intending
to
get
some
F
sharp
goodies
in
basically
every
single
month,
and
we
can
control
that
with
the
preview
flag.
So
that's
going
to
be
set
by
default
to
be
preview
if
you're
using
the
previous.
D
While
the
compiler
is
going
to
understand
those
additional
preview
features
because,
like
we
don't
produce
two
compilers,
you
know
one
for
don''t,
five
and
one
for
everything
else.
It's
the
same
compiler,
and
so
you
don't
actually
have
to
be
entirely
like
on
the
preview
train,
to
try
out
some
of
this
stuff
and
give
us
feedback
on
it.
So
we're
hoping
that
we
can
get
a
lot
more
feedback
on
what
we're
doing
throughout
the
year.
Another
interesting
thing
which,
although
it
info.
B
C
B
C
B
Then
sometimes
the
language
is
that
we're
actually
previewing
does
not
ship
in
that
round,
which
will
happen
with
six
with
Visual
Studio
2019
update
four
will
not
have
the
the
newest
first
things
in
F
sharp
that's
going
to
come
in
five,
which
is
another
year,
so
you
need
to
just
set
the
preview
flat,
yeah
and
then
you're
good.
Yes,.
D
So
that's
all
kind
of
stuff:
that's
coming
for
F
sharp!
We
we
don't
really.
We
don't
have
like
a
concrete
deliverable
at
this
time,
because
you
know
we're
sort
of
looking
for
Donna
at
five
is
for
F
sharp
five,
so
we're
sort
of
saying
okay.
So
when
the
first
preview
rolls
around
there's
gonna
be
some
goodies
and
then
kind
of
as
they
come
in
and
they're
stable
and
we
just
kind
of
want
to
you
know:
vet
the
design
with
people,
they're
gonna
be
available
and
sort
of
whatever
the
next
rolling
preview
comes
around.
D
Now
there
is
going
to
be
some
a
a
release
like
a
public
preview
of
a
release
of
dotnet
and
Jupiter
notebooks
in
November
at
the
ignite
conference.
Getting
back
to
this
discussion
about
conference
driven
development,
it's
quite
timely,
actually
that
we
are
going
to
be
doing
a
public
preview
of
something
at
a
conference
because
it
goes,
but
so
basically
there
there
have
been.
D
There's
been
sort
of.
You
know
like
some
relatively
small
community
projects
around
c-sharp
with
jupiter
notebooks
and
there's
been
an
f-sharp
community
project
with
f-sharp
and
jupiter
notebooks
called
I
f-sharp.
That,
historically,
has
basically
just
had
a
single
part-time,
maintainer
microsoft,
research
kind
of
trying
to
keep
it
up
to
date,
but
you
know
there's
all
sorts
of
little
problems
with
it
and
like
if
you
wanted
to
use
it
for
your
actual
work.
You
wanted
to
do
like
proper
data
science
for
your
work
with
with
it.
Then
you
know
it's
it's
a
little
bit.
D
It's
it's
a
little
unsatisfying
if
you're
like
oh
this
infrastructure,
that
I'm
using
is
only
just
kind
of
partly
maintained
by
someone,
and
you
know,
there's
no
product
team
behind
it.
None
of
that-
and
you
know
you're
kind
of
on
your
own,
this
sort
of
make
it
a
good
experience.
And,
frankly,
a
lot
of
people
do
that.
So
we
got
a
lot
of
feedback
from
people.
Basically
saying:
hey,
Jupiter,
notebooks,
really
matters.
Data
science
is
not
going
away.
Jupiter
is
sort
of
like
the
ecosystem.
D
For
that
and
in
fact,
a
lot
of
data
scientists
really
like
F,
sharp
and
functional
languages
in
general
because
they
like
having
you
know
stronger
types
to
model
things
and
they
like
just
dealing
with
inputs
and
outputs.
Like
you
know,
they're,
not
real
fans
of
object
oriented
you
know,
design
patterns,
things
like
that.
So
why.
B
A
A
E
D
D
D
That's
all
handled
by
this
sort
of
shared
kernel
that
we're
calling
the
dotnet
kernel
we're
going
to
come
out
with,
and
so
it's
it's,
it's
gonna
be
pretty
cool.
The
the
main,
important
thing,
I
think
to
keep
in
mind
is
we
are
scoping
out
language
service
integration
right
now,
because
it's
extremely
tricky
to
get
right
and,
frankly,
there's
just
more
infrastructural
stuff
that
we
want
to
land
and
get
stable
and
get
to
the
point
where
you
know
you
could
integrate
with
you
know:
Apache
spark.
B
B
D
B
D
There's
a
lot
of
try
dotnet
frankly,
like
you
know,
it
was
just
all
about.
Oh
I
want
to
host
some
code
and
I
execute
it
interactively
well.
That
is
like
fundamentally
what's
going
on
in
Jupiter
now
there
were
a
huge
number
of
changes
that
had
to
go
in,
but
you
know
at
it's
very
core.
It's
still
sort
of
roughly
doing
the
same
thing,
but.
B
D
B
D
D
On
where
you're
using
it
and
what
you're
paying
for
like,
if
you're
using
it
on
the
website
right
here,
like
you
know,
yes
there's,
you
know
some
language
service
integration
there
I
might
write
on
that
site.
If
you're
using
it.
You
know
within
vs
code,
then
probably
go
because
the
the
you
know,
all
that
stuff
is
going
to
be
supplied
by
your
your
plugin
for
BS
code.
If
you
have
some
other
environment
that
using
it
in
then,
probably
not
all.
A
A
B
D
So
at
least
sort
of
wrapping
up
the
Jupiter
stuff
look
for
the
public
preview.
It
ignites!
If
you
have
any
data,
scientist,
friends
or
if
you
are
a
data
scientist
of
yourself.
Oh
sorry,
not
a
data
scientist
of
yourself.
If
you
are
a
data
scientist
yourself
or
if
you're,
just
kind
of
interested
in
learning
machine
learning
and
integrating
with
various
things
trying
to
get
into
that
space,
Jupiter
is
the
way
to
do
it,
and
so
we're
really
looking
forward
to
you
actually
using
that
in
a
public.
So.
A
D
C
D
They
like
really
simple
types
to
model
stuff
if
they
can
like
do
some
basic
data
modelling
and
get
some
guarantees
with
the
tool
that
they're
working
with
and
they
like
functions,
and
they
like
coding.
That
is,
you
know,
really
easy
to
map
back
and
forth
between
the
actual
mathematics
behind
stuff.
If
they
have
to
really
go
out
of
their
way
to
sort
of
represent
that
in
a
language
they
they
tend
to
not
have
a
good
time.
And
so
that's
one
of
the
core
reasons.
D
Why
f,
sharp
is
very
strongly
involved
in
the
Jupiter
space,
because
F
sharp
is
much
easier
to
sort
of
take.
You
know
like
hey
here's.
Here's
like
the
actual
mathematics
behind
the
the
data
science
work
that
we're
doing
right
now
that
in
the
F,
sharp
typically
looks
a
lot
closer
to
that
than
if
you
were
to
do
it
in
c-sharp
and
so
right.
D
That
being
said,
though,
there
are
still
a
lot
of
c-sharp
developers
who
love
interactive
programming,
and
this
is
you
know
a
case
where
interactive
programming
in
a
tool
that
is
designed
around
an
or
interactive
programming,
is
being
released
or
for
the
first
time,
like
you
know,
aside
I,
guess
there
was
the
c-sharp
interactive
process
and
BS,
but
we
don't
really
talk
about
that
very
much.
So
this
is
like
a
very
big,
concerted
effort
that
we're
trying
to
do
here
so,
and
so
there
were
some
questions.
A
C
A
A
You
know,
look
at
the
program
holistically
and
then
we
move
on
you
stuff,
like
you
know,
shaking
them
out
so
to
speak
and
the
the
idea
of
most
of
these
things
is
they
work
really
well,
when
you
have
a
whole
program
analysis,
meaning
you
see
the
entire
program
end
to
end
and
then
you
can
basically
walk
from
the
thing
that
the
program
is
using
to
the
things
and
then
mark
the
things
that
are
being
used
and
remove.
The
things
are
not
being
used
kind
of
like
a
GC
works.
A
If
you
will
the
problem
very
often
is
that
for
things
like
their
virtual
or
delegates,
it's
very
hard
to
see
all
the
entry
points,
and
so
you
have
to
be
sometimes
conservative,
which
means
to
leave
a
lot
of
stuff
left
in.
But
there
are
a
bunch
of
techniques
like
D
virtualization,
or
you
know,
basically
trying
to
do
a
Skype
analysis
and
figuring
out
where
stuff
goes
and
practice,
and
so
I
think
we
are
still
doing
more
and
more
analysis
there.
Unfortunately,
there's
a
trade-off
there.
A
If
you,
if
you're
too
aggressive
and
your
program
uses,
for
example,
reflection
or
other
things,
we
can't
actually
reason
about.
Then
it
would
remove
stuff
that
your
application
depends
on
and
then
stuff
doesn't
work
anymore,
which
is
why
most
IOT
pipelines
that
have
dynamic
systems
like
you
know
the
mono
linker.
Does
it
and
I
think
got
inhibited
as
well?
There
is
a
way
for
you
to
mark
things
as,
like.
A
You
know,
whatever
you
think,
keep
this
into
the
remaining
program
because
ever
use
it
at
runtime,
so
I
think
that's
something
we
will
probably
push
them
a
little
bit
more.
There
was
one
question
on:
will
donate
five
get
a
native
or
will
be
be
switching
to
the
mono
äôt
pipeline?
So
we
will
discontinue
dotnet
native
Dada
native
was
the
to
chain.
We
use
free
WP,
which
is
using
a
very
specific
version
of
the.net
runtime
of
a
particular
tool
chain
which
we
will
no
longer
evolve.
A
So
the
idea
is
that
moving
forward
for
WP,
we
will
in
more
invest
in
Coursera,
meaning
a
JIT
past
one
time
and
we
were
also
equally
invest
in
the
mono
iot
pipeline
for
things
like
iOS
or
as
an
option
for
you
WP
as
well.
So
there
is
that
then
there's
one
question:
will
you
WP
get
dotnet
native
sorry,
we
get
donneson
a
2.1
and
when
the
plan
is,
it
will
get
understand
a
2.1
by
basically
moving
uwp
over
to
donít
core
session
at
5:00.
D
B
B
Sometimes
next
next
year,
safe
when
next
year
will,
because
that's
part
of
Visual
Studio
that'll,
be
on
a
Visual
Studio
timeline,
not
the
dotnet
core
5
timeline.
So
we're
optimistic
about
getting
you
that
kind
of
sooner
rather
than
kind
of
later,
but
we
also
won't
give
it
to
you
until
we
think
it's
ready
right.
A
Someone
who
says
I
never
seen
jitter
succeed
with
D
virtualization
I'm,
still
dreaming
of
spotting
that
event
in
life
code.
I,
don't
understand
the
rules
when
jitter
can
be
virtualize.
So
the
poem
of
the
JIT
in
general
is
that
the
JIT
basically
runs
as
part
of
your
application
at
runtime
right,
so
the
longer
that
it
takes
to
compile
something.
The
long
I
will
take
your
application
to
actually
do
something
meaningful.
So
there's
this
trade-off.
A
How
much
time
do
you
spend
compilation
versus
compiling
versus
how
much
time
you
will
spend
running
that,
and
so
Java
has
done
this
for
years,
what
they
call
hot
spot,
where
the
ideas
they
start
with
a
very
simple
code
generation
and
then,
as
you're
executing
the
function
more
and
more,
you
know
in
parallel,
there
will
spend
more
time
compiling
that
function
and
do
more
optimizations.
That
will
take
longer
to
give
you
better
performance
and
we
have
done
started
doing
the
same
thing.
I
think,
since
on
a
core
to
1
to
2.
A
We
call
this
approach
tier
2
jetting,
where
the
same
approach
applies.
We
basically
start
with
a
simple
version
of
your
application
and
then,
as
the
application
runs
and
stuff
gets
more,
we
improve
the
cogeneration
by
doing
more
aggressive,
optimizations
that
might
take
longer
to
compute,
for
example,
the
virtualization
I'm
not
sure
how
much
we
have
done
with
the
virtualization,
but
that's
the
general
technique.
A
Another
question
was
without
and
five
support,
WCF,
yes,
and
no.
The
support
we
have
for
dotnet
in.net
core
for
WCF
is
pretty
much
unchanged
since
v2
I
believe
so
there's
some
basically
the
the
summary
is
we
have
decline,
pieces
of
wucf
or
most
of
them
I
should
say
we
do
not
have
any
of
the
server
pieces
and
for
the
client
pieces
I
think
we
are
still
lacking
some
of
the
soap
bindings
and
but.
A
We
announced
I
want
to
say
six
months
ago
as
part
of
the
direct
300
plans
that
we
are
done
porting.
So
whatever
we
have
a
WCF
right
now
is
considered
complete,
there's
a
community
project
that
is
going
on
a
core
WCF,
which
we
blocked
about
as
well
that
they
will
try
to
back
in
Dec,
fill
in
more
of
the
stuff,
but
basically
taking
the
the
open
source.
Sorry
the.net
framework
reference
sources
and,
and
and
start
this
as
an
implementation.
A
B
Right,
it
was
already
it
was
already
had
a
proxy
that
was
a
challenge
with
that
we
scrolled
off
one
about
IOT
and
I
I
think
we
should
put
into
our
roadmap
that
to
do
next
month.
This
a
lot
of
this
community
stand
up
around
IOT
we're
gonna
do
a
little
this
morning,
but
which
isn't
with
us,
yeah
and
he's
really
the
guy
on
that
and
he's
the
one
with
the
toys,
and
we
should
bring
toys
and
play
if
I.
B
A
B
A
B
Want
to
I
want
to
actually
see
some
more
programming
on
that
and
I'd
like
to
see
actually
some
live
programming
and
how
that
actually
works
and
hi
yeah
I
like
I,
enjoy
technirama.
That's
great.
That
was
a
fun
conference.
It's
a
fun
conference
for
me
also
because
I'm
able
to
make
a
pretty
big
donation
from
that
the
money
I
would
have
made
on
my
workshop
went
to
augment
to
cancer
research,
so
3,000
euros
to
cancer.
I
felt
really
good
about
that.
That.
B
A
Yeah,
there
was
one
more
will:
we
support.
Sequel
are
not
a
core
the
answer's.
No,
we
not
only
invest
in
sequel.
Solari
in
I
would
generally
say,
like
secrecy
are
something
I
would
recommend
against
anyway,
because
I
think
the
idea
that
you
run
net
is
sort
of
your
database
seems
always
seem
strange
to
me,
and
I
think
there
are
usually
better
languages.
It
just
means
you
have
to
learn,
sequel
or
t,
sequel
or
PL
sequel.
Depending
will
database
ends
up
being
about
it
and.
C
B
Like
a
but
the
people
that
are
doing
it
for
a
reason,
so
I'll
give
them
give
them
the
assumption
that
that
is
a
good
reason.
It
does
let
you
do
some
things
with
types
that
are
are
interesting
and
I.
Wouldn't
really
suggest
people
look
for
a
way
to
use
it,
but
if
you're
using
it
today,
you
believe
it's
the
right
answer
for
you.
I
think
that
I
don't
know.
I
haven't
heard
anything
about
sink
while
pulling
support
for
that.
No.
A
I,
don't
think
they
do
what's
the
story
about
see
charade
of
uwp,
if
you
have
time
to
answer,
can
I
use
it
rendering
the
project
file
or
do
we
need
to
wait?
I
would
recommend
waiting
because
you
will
get
see
charade
models
for
free
on
the
new
version
of
the.net
core
based
version
of
vwp.
So
you
know
you
can't
hack
your
project
file
today,
if
you
really
wanted
to,
but
that
doesn't
give
you
more
functionality
right.
So
all
the
language
features
that
require
API.
A
It
will
still
not
work
and
you
still
don't
have
that
ability
notations,
you
still
don't
have
range
and
index
still
don't
have
icing
in
your
mobile,
so
that
you
would
have
to
do
a
lot
of
work
to
get
some
other
stuff
up
and
running.
But
even
then
it
will
be
a
flaky
experience
or
an
incomplete
experience.
So
I
would
not
push
the
envelope
on
that.
One
yeah
do.
A
Mean
it
might
because
it's
clearly
nullable
the
poem
is
malleable,
though,
is
it
so
it's
a
long
tail
right.
We
have
just
started
annotating
the
framework
for
five
for
oral
planners
to
get
the
rest
of
the
core
framework
annotated
and
then
I
think
the
experience
will
be
pretty
good.
I
started
using
it
to
my
own
projects
and
I'm
I'm,
actually
really
surprised
how
well
it
works.
I
thought
adopt.
A
B
D
A
B
Yeah
and
so
making
a
static
like
seem
like
a
small
thing,
but
it
did
a
lot
internally
to
make
them
more
efficient
and
so
for
us
Kiko's
that
you
know
think
about
this
stuff.
Then
we
looked
at
the
first
local
functions
and
it
when
you
started
doing
certain
things,
it
was
not
bad
super
efficient
and
static
local
functions
pretty
much
solves
that
problem.
The
direct
passing
of
parameters,
instead
of
just
reaching
out
to
the
outer
scope
and
grabbing
them
that
allows
for
a
much
cleaner
thing.
B
So
you
started
to
steal
mine
I'm,
going
to
go
with
these
extremes
because
async
streams,
let
you
do
something
that
was
kind
of
difficult
to
do
right
before
and
now
it's
so
easy,
it's
scary!
So
if
you
have
a
situation
where
you're
getting
input
in
and
that
input
is
timed
and
then
you're
doing
something
with
it,
for
example,
putting
it
in
a
database.
So
even
something
that
simple
to
have
those
two
steps
individually
awaited
is
actually
a
super
super
big
step
and
that's
what
we
get
that's.
B
What
async
streams
are
all
about,
and
so
I'm
super
pleased
with
how
simple
it
is,
and
while
it
is
similar
to
the
reactive
framework,
it
just
works.
It's
just
so
simple
to
add
it.
If
you
have
that
scenario,
I
know
everybody
doesn't
have
it
so
some
people
will
never
use
async
streams.
But
if
you
have
that
scenario,
I
think
that
is
the
killer
feature
in
802,
be.
A
A
Somebody's
asking
what
does
function
pointers
give
you
compared
to
funk
of
T.
Well,
it's
basically
a
funk
of
T
or
any
delegate.
Type
in
dotnet
is
multicast,
meaning
it
has
a
list
of
potential
receivers
function.
Pointers
is
basically
as
as
lean
as
it
gets.
You
little
just
have
a
pointer
to
the
function,
plus
the
the
instance
I
believe
right
and
then
that's
pretty
much
it.
So
it's
seeing
a
cost
so.
A
B
Helping
thank
you
for
catching
that,
so
it
helps
us
make
the
the
runtimes
faster
and
better
so
sometimes,
there's
features
that
will
come
in
and
you
go
wow.
How
can
I
use
that
and
much
more
than
five
or
ten
years
ago?
The
answer
may
be
no
you're
not
going
to
use
it.
I
yeah
I
think
that
you
want
to
pay
attention
to
the
scenarios
they're
built
for
understanding
that
some
things
are
really
built
sort
of
firm
for
emo.
B
C
B
So
you
will
see
I
think
function.
Pointers
are
probably
in
that
group
for
most
people.
Forty
is
perfectly
adequate.
The
the
slight
hit
that
you
take
on
that
the
thing
that
I
we
talked
about
performance
being
important
on
local
statics.
That's
because
you
can
do
that
a
lot
if
you
start
using
those
you're
using
them
a
ton
and
that's
why
that
can
hit
into
a
little
bit
more
performance
stuff,
because
I
now
don't
want
more
than
like
I
didn't
know.
B
Five
six
lines
in
any
logical
group
and
I
just
used
static,
local
functions
inside
a
function
which
has
the
the
face
within
the
method
inside
that
I'll
use
a
static
local
function
so
that
the
the
code
size
that
I'm
tolerating
is
getting
a
lot
smaller
because
of
that
I
just
give
it
a
name
make
it
small
and
I
feel
whole
lot
better
about
my
card.
So.
A
Depending
for
the
with
me
study
local
function,
this
is
really
not
about
perf,
like
as
in
I
like
local
functions.
The
problem
with
non-static
local
functions
is
that
you
implicitly
blind
to
any
variable
that
is
outside
of
your
of
your
local
function,
which,
just
from
a
reasoning,
standpoint
I,
don't
like
I
like
the
fact
that
I
can
say
no
anything
that
goes
into
this
function.
You
pause
in
there's
no
implicit
capture
of
anything
local
that
is
outside
that
right.
A
So,
if
you
move
code
from
the
outer
method
into
the
local
method,
you
know
it
would
get
compile
errors
if
you
would
start
reference
out
of
variables
which,
for
the
most
part,
is
probably
not
what
you
wanted
anyway,
it's
because
well,
depending
on
where
you
put
it
in
appending.
When
you
invoke
the
function,
you
might
get,
funky
results
right
and
so
to
me,
setting
is
really
more
about.
You
know,
declare
your
inputs
and
outputs,
whether
they
just
magically
bind
to
everything.
I.
Think.
B
That's
a
good
point
and
in
the
in
the
comment
that
I
made
about
the
you
know,
then
I
want
really
small
blocks.
No
I
know
exactly
what
that
block
is
going
to
touch
with
a
static
with
a
static
local
function.
It
never
reaches
beyond
what
I'm
communicating
to
it
and
that's
super
important
and
then
generally
it's
just
going
to
return
a
value
and
I'm
gonna
do
something
with
that
value,
but
it
really
I
used
to
make
small
private
functions
sometimes
and
now
I
mean
if
that's
gonna
get
used
all
over
the
method.
B
Of
course,
it's
still
going
to
be
in
the
same
location,
I'm,
sorry
I
said
all
over
the
method.
If
it's
used
all
over
the
class,
then
obviously
it's
still
going
to
be
a
private
at
the
class
level,
even
if
it's
one
line,
but
even
if
it's
one
line
and
it's
kind
of
goofy
to
understand,
I'll
still
give
it
a
name
with
a
local
static.
Oh
yeah
function,
so
we've.
D
D
We
had
some
interns
over
the
summer,
implement
code
fixes
and
yeah
in
Visual
Studio
that
relate
to
static
local
functions
like
if
you
have
estat
isn't
marked
static
but
you're
treating
it
as
if
it
was
a
code
fix
will
basically
like
analyze.
Like
oh,
is
this
at.
Can
this
actually
be
into
a
static
local
function?
It'll
add
it
and
if
and
then
I
think
it'll
also
do
the
inverse,
if
like,
if
you're,
trying
to
capture
something
that
was
declared
upwards
it'll
say:
oh,
don't
make
this
thing
static
anymore.
So
it's
pretty
mean.
There's.
A
B
A
So
one
question:
that's
actually
really
interesting
that
it's
kind
of
we
ever
need
to
talk
about.
We
wanted
to
win
donate
five,
which
table
is
a
good
thing,
because
you
don't
want
to
confuse
people
too
much.
But
one
question
that
came
up
here
is
Visual.
Studio
suggest
adding
standard
analyzers
to
project
should
those
be
backed
into
the
default
project
templates.
A
So
what
we
actually
talking
about
right
now
is
bit
larger
than
that,
so
we
basically
want
to
get
to
a
point
where
we
have
a
set
of
default
analyzers
that
are
always
referenced
and
there
may
not
be
always
on
meaning.
There
might
be
some
other
project
settings
you
have
to
fuss
with
to
actually
enable
the
rules
so
similar.
How,
when
you
use
FX
cop,
you
may
not
use
all
the
106,
you
may
only
use
ten
of
them,
but
we
don't
break
them
into.
You
know
12
different
NuGet
packages,
but
you
reference
them
all.
A
Then
you
can,
you
know,
turn
them
on
and
off
individually,
and
the
reason
for
that
is
that
we
very
often
made
design
decisions
for
AP
is,
for
example,
to
say.
Well,
if
we
had
an
analyzer
that
we
know
everybody
is
running
all
the
time,
it
would
feel
warm
and
fuzzy
about
doing
certain
things,
but
because
it's
optional-
and
maybe
people
may
not
have
turn
it
on
most
people
will
probably
not
know
that
they
miss
using
the
API.
If
we
don't
design
it
differently
and
so
there's
certain
api's.
A
We
just
haven't
done
because
we
feel
like
they
were
way
too
easy
to
abuse
or
use
incorrectly.
I
should
say
without
you
knowing
it
and
that's
it
so
in
that
sense,
for
500
I
would
expect
us
to
have
a
set
of
default
analyzers
that
are
always
there.
One
thing
that
I
want
to
do
for
500
is
make
Absolution
better,
and
the
other
thing
I
would
like
to
do
is
make
our
platform
of
supported
exception
experience
better.
So
we
can
actually
warn
you
at
compile
time
when
you're,
depending
on
API,
stable
mode
work
at
all.