►
From YouTube: ASP.NET Community Standup - August 6th 2019 - ASP.NET Core A to Z eBook with Shahed Chowdhuri
Description
Join members from the ASP.NET teams for our community standup covering great community contributions for ASP.NET, ASP.NET Core, and more.
Community links for this week: https://www.theurlist.com/aspnet-standup-2019-08-06
B
A
B
B
B
B
Cool
all
right,
so,
first
of
all,
last
week,
I
briefly
mentioned
the
HTTP
repple
and
pointed
out
the
docs
thing
here:
there's
an
official
post
about
it,
so
just
kind
of
going
through
the
the
HTTP
repple.
So
this
is
on
the
asp
net
blog
the
docs
go
through
kind
of
in
more
detail.
This
is
neat
when
one
thing
that
that
Angeles
is
doing,
in
addition,
is
showing
setting
it
up
in
Visual
Studio
code
and
in
Visual
Studio,
so
as
a
tool,
so
pretty
cool.
B
A
As
you
point
out
there,
our
goal
is
to
kind
of
get
this
to
be
the
default
experience
for
API
application.
Just
to
make
this
more
first-class,
so
once
the
rapa
Liz
kind
of
bedded
down,
we
would
love
to
get
it
just
in
by
default.
For
visual
studio
is
a
first-class
option,
but
these
API
style
apps,
where
you
don't
have
UI
as
such.
So
but
now
you
can
do
this
work
around.
It
has
a
couple
little
things
that
don't
work
perfectly,
but
it
works
well
enough.
A
You
know
to
set
up
yourself,
but
this
is
just
the
beginning,
so
please
people
try
it
out.
I
think
I
checked.
Yesterday
there
were
only
like
500
downloads
of
the
tool.
You
know
it
doesn't
which
isn't
nothing,
but
we
have
like
50,000
users
in
July
who
tried
out
dotnet
core
3,
which
is
a
phenomenal
number
by
the
way.
So
I
want
to
say
thank
you
to
everyone,
there's
my
little
tangent
here,
but
trying
out
the
preview
of
Nicole
3,
because
we've
never
had
penetration
numbers
like
that.
It
is
absolutely
fantastic.
A
Of
I
think
HTTP
2
will
just
work
like
you,
don't
really
get
any
you,
don't
really
utilize
hiv-2
from
your
HTTP
api's,
all
right,
like
you,
don't
get
access
to
highly
kind
of
it's
all
under
the
in
the
transport
layer,
GOP
C
is
different.
Gop
C
is
built
on
top
of
HTTP
2
primitives,
and
so
you
need
H
to
be
to
to
sort
of
get
the
full
benefit.
Yeah.
We
see
this
tool
does
not
yet
support
G
RPC,
but
we
have
had
extremely
early
discussions
about.
A
But
this
whole
idea
of
having
either
a
command-line
repple
or
something
like
postman
or
you
know
the
chrome,
dev
tools
or
something
like
that
available
to
you
for
G
RPC
is
something
that
we
are
keen
on
and
we're
sort
of
currently
looking
at
the
landscape
to
see
what's
already
out
there
there's
a
couple
of
things:
they're,
not
particularly
great
from
what
I
hear.
So
there
is
an
opportunity
to
do
something
there
and
we'll
see
how
we
go.
Go.
B
A
B
And
then
just
another
call
out
we're
trying
to
be
more
conscious
of
they're
doing
some
great
stuff
with
Visual
Studio
for
Mac
lately,
and
so
that's
also
in
here
showing
how
to
set
that
up
as
a
custom
tool.
Yeah
Gunnar
pikemen
here
he's
writing
up.
This
is
an
interesting
thing.
I
haven't
done
this
for
quite
some
time.
This
is
setting
up
vCard
support
in
asp
net
core,
so
just
kind
of
you
know
custom
action
result.
B
C
B
A
A
B
B
A
B
C
A
C
A
A
Right
was
that
they
mixed
like
tier
JSX
and
TSX,
and
those
other
touch
of
templating
was
they
went
back
to
putting
everything
into
one
file,
but
they
make
it
testable,
etc,
etc
and
yeah
razors
had
that
forever.
But
it
wasn't
particularly
testable
because
of
the
way
the
view
was
compiled.
It
was
compiled
into
a
separate
assembly.
It
depends
on
your
application.
It
was
that
a
run
time,
so
you
couldn't
even
get
it
at
unit
test
time.
So
it
was
never
really.
You
know
very
conducive
to
that,
but
this
is
very
different.
A
So,
whereas
in
razor
pages
we
still
have
a
code
behind
approach
by
default
because
it
still
compiles
using
the
razor
view
style
whether
the
cease
hTML
is
compiled
into
a
separate
view.
You
don't
generally
test
that
you
test
the
page
more
or
the
viewmodel.
The
blazer
model
isn't
really
mvvm
right.
It's
more
the
model
view
update
style
of
UI
paradigm,
and
so
you
can
test
you
know
the
view
in
the
air
quotes
directly
because
it
produces
a
class,
and
you
can
just
reference
that
class.
A
You
can
create
a
class
library
that
has
all
the
compiled
stuff
in
it
and
you
can
reference
it,
and
you
know
you're
off
to
the
party
there's
all
there's
no
HTTP
or
anything
like
that.
You
have
to
mock
out
it's
just
a
class
that
has
events
and
methods,
and
you
call
it
so
I
mean
it's
not
out
of
the
box.
I
won't
claim
that
it's
fully
testable.
There
are
some
discussions
going
on
right
now
about
the
best
approach
just
like
forever.
There
will
be
forever
and
everything
we
do,
but
it's
all
opinions
and
stuff
so.
B
A
I
mean
you
can
do
that.
We
want
to
make
sure
you
can
do
code
behind
or
code
beside
or
whatever
you
want
to
call
it
cuz.
There
are
some
people
who
prefer
it
and
there's
a
couple
different
ways
of
going
about
it
right
now,
I
think
some
people
are
waiting
for
the
partial
class
support.
Unless
we
did,
we
land
that
already
is
partial
class
supported
in
place
of
components
yet
or
did
that
not
land?
Yet,
okay,
I,
don't.
B
A
B
B
A
Careful
about
those
type
of
things
like
he's,
making
a
claim
there
that
you're
effectively
streaming
data
from
the
database
to
the
HIV
response.
It's
never
that
simple
in
G
RPC,
that's
true,
because
G
RPC
supports
duplex
streaming
as
a
protocol
HTTP
the
crest
doesn't
really
in
that
sense,
like
you
kind
of
expect
the
entire
response
to
come
back
before
the
client
starts
actually
processing.
The
response.
A
I
mean
hTML
is
different,
like
the
browser
can
start,
obviously
rendering,
while
the
HTML
still
streaming
and
there's
a
whole
a
science
around
constructing
the
HTML
response
in
order
to
best
allow
the
browser
to
do
that.
But
for
rest,
knowledge,
Jason,
you
don't
even
know
it's
valid
ace
until
you
get
the
last
byte
right,
you
can.
B
A
That's
not
possible,
it's
it's
not
really,
idiomatic,
it's
not
widespread
and
certainly
by
default.
This
is
not
what
this
is
doing
right.
You
know
like
turning
icing.
What
happens
behind
the
scenes
here
is.
We
will
do
the
await
for
you
on
the
enumerable
from
the
layer
before
the
action
result
right
and
so,
instead
of
you
having
to
do
the
to
list
yourself,
we
will
do
it
for
you
and
we
will
release
the
thread
and
return
it.
And
yet
we
will
do
the
right
thing
in
the
sense,
but
we're
not
we
won't
be
buff.
A
We
won't
be
sending
the
responses
back
to
the
client
in
a
way
that
the
client
could
really
utilize
each
record
as
it
comes
down.
I'd
love
for
us
to
get
there,
but
that
requires
the
client
and
the
server
to
really
agree
on.
What's
going
on
and
to
my
knowledge,
that's
not
something
we
can
kind
of
just
do
out
the
box
and
it
works
everywhere.
So
what
will
happen
behind
the
scenes?
We
may
actually
end
up
buffering
as
well.
A
B
A
A
And
so
I'd
to
be
to
be
really
clear,
it
would
be
really
crappy
if
we
had
shipped
dotnet
co3
off.
We
shipped
out
Nico
3,
which
has
c-sharp
8,
which
supports
this
new
idiom.
Isn't
you
primitive
and
then
MVC
either
just
like
throws
an
exception.
If
you
try
and
return
it
or
worse,
it
does
something.
You
don't
expect
like
it's,
how
it
tries
to
serialize
the
entire
I,
a
sync
innumerable
structure
rather
than
going.
Oh,
this
is
an
enumerable
object.
I
need
to
like
iterate
over
it
and
then
those
are
the
objects.
A
I
want
to
return
and
run
through
the
format
of
pipeline
right.
That
would
have
been
bad,
and
so
we
had
to
do
something,
but
there's
only
so
much
we
can
do
given
the
constructs
available
in
MVC
and
over
HTTP
and
what
people
kind
of
expect
by
default
out
of
the
box.
There
is
more
we
could
do,
but
it
would
require
a
lot
more
work
and
design
and
thought
and,
like
I
said,
the
other
side
would
probably
have
to
agree
cool.
B
Yeah,
okay,
all
right
big
post
from
Nick
Craver,
who
is
on
twitch,
which
was
fun
to
see
so
here
he's
talking
about
how
they
do
app.
Caching,
in
Stack,
Overflow,
there's
a
lot
here
so
there's
you
know,
of
course,
of
Redis
caching,
and
he
talked
about.
Currently,
you
know
the
current
state.
This
is
running
with
dotnet
framework.
They
are
working
towards.
You
know
the
big
kind
of
update
to
dotnet
quarter
3.
B
So
just
some
things
I
wanted
to
point
out
and
again.
This
is
a
grab,
grab
a
couple
of
cups
of
coffee
and
spend
some
time
with
it,
but
talking
about
cache
performance
using
mini
profiler,
of
course
you,
the
the
Stack
Exchange
Redis
profiling,
API
and
then
some
fun
stories
in
here
too,
as
well.
So
looking
at
some
some
things
that
worked
and
didn't
work
as
they're
kind
of
going
through
all
this,
so
so
accidentally,
not
using
cash
setting
long
or
setting
incorrect
cash
time
so
time
span.
B
Sixty
is
not
60
seconds
at
sixty
ticks,
so
a
lot
of
kind
of
fun
stuff
there
so
yeah,
definitely
definitely
a
good
post.
All
right,
exciting
one
to
wrap
up
with
here
is
sure
heads
post
at
the
end
of
his
26
series,
so
he
did
last
year.
He
did
in
a
through
Z
series.
This
excuse
me
last
year
he
did
a
Happy
New
Year
thing
where
each
letter
spelled
out
Happy
New
Year,
so
that
was
fun.
This
year,
he's
written
26
posts
a
through
Z
and
we've
been
featuring
quite
a
lot
of
them.
B
B
D
C
D
D
As
soon
as
it
came
out,
1.1
was
right
around
the
corner
tools
that
changed
so
I
thought
why
not
just
work
on
something
that
I
can
update
over
time,
and
so
it's
always
relevant
and
when
I'm
done
with
the
series
updated
again.
So
this
is
a
living
breathing
series
of
blog
posts.
With
every
topic
you
can
imagine
around
asp.net
core
so
from
authentication
down
to
deployment
to
Azure
or
getting
zero
downtime
I
know
John
wanted
me
to
share
some
stats
on
it
as
well.
So,
if
I
share
the
screen,
can
you
guys
see
my
slide?
D
Show
here?
Yeah
all
right
and
though
there's
some
demos
as
well,
so
it
led
up
to
this
being
this
series,
but
I
was
looking
at
what
are
people
interested
in?
What
is
it
like
to
read
so
I
see
that
over
time,
when
I
first
started,
this
series
I
had
like
next
to
no
views
at
all
mm
or
less
views
every
month,
and
then
you
see
right
now
in
the
latest
month,
the
highest
one
is
up
to
65,000
and
there's
also
a
bunch
of
spikes
there.
D
So
look
back
at
what
do
people
like
what
are
people
interested
in
and
all
these
spikes
are
related
to
major
announcements.
So
back
in
December
2018,
we
had
a
spike
with
a
connect
2018
coming
out
a
lot
of
new
announcements,
our
net
core
3.0,
closer
to
April,
where
we
had
the
big
B
as
2019
launch
again.
These
are
few
and
far
between,
because
you
have
all
the
big
events,
but
the
new
ID
release
usually
doesn't
get
a
launch
event.
D
So,
looking
back
at
what
people
like
to
search
for
the
authentication
posts
being
the
first
one
just
happen
to
be
the
most
popular
one
as
as
of
now,
because
people
have
been
seeing
it
for
a
while
for
the
past
six
months,
our
production
tips-
although
this
is
more
recent
post,
a
lot
of
people
love
that,
because
once
you're
done
developing
your
asp.net
core
app,
you
want
to
deploy
it
somewhere.
How
do
you
get
it
out
there?
What
are
some
tips
and
tricks?
D
Logging
again,
something
that's
important
after
your
app
is
out
highlighted
number
four
and
five,
because
these
are
just
the
index
page
and
home
page,
so
that
could
be
looking
at
whatever
its
current
right
now
we're
just
browsing
through
the
series.
The
second
half
also
shows
you
additional
things
around.
What
people
are
reading
around
dotnet,
core
3.0
I
know.
We
heard
some
stats
earlier
massive
number
of
downloads,
more
people
getting
interested,
and
these
are
specific
to
forms
and
feels
like
as
soon
as
you're
building
a
web
app.
You
need
to
know.
D
You
know
how
to
put
everything
together,
obviously
and
then
not
to
be
forgotten
blazer.
So
a
lot
of
people
are
looking
at
blazer
and
I
built
a
word
clutter
around
this.
This
was
interesting.
This
is
a
little
Pacman
shape.
I
used
a
word
cloud
generator
you'll
see
people
are
searching
for
asp.net
and
core,
but
also
down
here
on
the
left.
I
found
blazer
with
his
blazer
cer.
Now
I
haven't
misspelled
it
myself
on
my
site,
but
people
are
searching
for
it,
so
this
is
important,
so
maybe
I
should
have
a
keyword
in
there
somewhere.
D
So
somehow,
they're
ending
up
in
my
son,
maybe
Google,
are
being
corrected,
I'm,
not
sure
so
yeah,
it's
good
to
see
that
they're
searching
for
all
these
different
words,
your
stuff
on
cookies
and
consent,
their
sample
tutorials,
a
handling
errors,
key
vault
again
cookies
down
here,
as
your
storage
Ashur
is
really
big.
You
know
people
want
to
be
able
to
deploy
really
to
any
platform
cuz
that
in
a
course
cross-platform
but
again,
they're
looking
at
Azure
as
well,
so
yeah,
it's
great
to
see
any
feedback
insights
on
any
of
the
search
terms.
D
D
It
was
back.
It
was
a
second
post
right
back
in
January,
so
a
lot
has
changed
since
then.
So
the
demo
that
we'll
see
shortly
is
around
Blazer.
The
way
things
were
done,
as
you
know
well
days,
have
been
changing
a
lot.
So
what
the
comments
were?
Some
of
the
comments
I
got
were
hey.
This
is
great
for
this
version,
but
this
other
version
this
one
isn't
working
for
me.
So
again,
that's
a
really
nice
prompt
from
the
community
saying
they.
This
is
something
you
should
look
back
and
change.
B
Yeah
yeah
that
that's
always
a
problem
right
was
when
you
find
a
blog
post
and
it's
like
four
three
previews
back
and
semantics
change
and
the
code
doesn't
work
so
so.
I
definitely
appreciate
that
that
you
keep
things
up
to
date
and
that's
that's
a
cool
system
by
the
way.
I
hope
you'll
show
that
also
the
the
way
that
you're
regenerating
stuff
so
you're
obtaining.
D
D
And
this
dungeon
up
done
with
so
it's
done
with
the
worker
service.
This
is
really,
as
you
can
super
simple
code.
I
literally
have
a
string
of
URLs,
so
this
could
be
something
that
you'd
extract
out
and
stick
it
into
a
JSON
file
or
just
a
text.
File
and
I
want
to
run.
This
I
would
literally
just
hit
the
play
button
and
how
this
works,
because
yesterday
I
had
to
update
my
no-good
dependencies
who's
on
preview.
D
Seven
right
now
and
all
it
literally
does
it
goes
out-
pulls
out
a
file
with
a
zoom
in
a
little,
so
people
can
see
on
the
screen,
so
it's
just
processing
one
by
one
and
what
it
does.
Is
it
literally
spits
out
all
these
Word
documents-
and
this
is
a
really
interesting
because
I'm
using
a
third-party
package
to
generate
a
Word
document
and
if
any
of
you
have
ever
automatically
generated
Word
documents
from
webpages.
You
know
that
it's
not
always
perfect,
so
the
first
thing
I
noticed
was
I.
D
Have
the
grits
turned
on
over
here
to
make
sure
that
I
see
where
things
are
aligned?
So
let
me
go
ahead
and
open
one
of
the
other
files,
so
the
intro
here
was
actually
written
by
our
very
own
John
Galloway.
So
this
one
over
here
as
you
can
see
it's
generating
pretty
good
formatted
files.
But
what
happens
is
all
the
images
are
a
little
messed
up
so
initially
the
first
way
I
was
able
to
fix
this,
and
this
is
super
painful
at
to
manually
click
that
but
we're
able
to
automate
it
by
adding
a
macro.
D
Now
I
didn't
publish
the
macro
version,
because
I
don't
want
to
put
in
a
published
word
talks
backwards
in
them,
but
the
end
result
is
a
very
nice
PDF
so
to
this
single
page
as
the
intro
by
John,
and
then
all
the
code
samples
are
formatted
and
they're
all
single
color
right
now,
but
yeah.
This
is
all
generated
with
the
worker
service.
Everything
is
if
I
go
back
to
my
worker
service
site.
D
Everything
is
open
source,
as
is
all
the
samples
there
you
go
so
a
very
simple
worker
service
and
all
it
generates
is
a
bunch
of
chapters.
But
if
I
go
back
to
the
Blazer
example
right
here
again,
you've
seen
a
bunch
of
examples
before
this
is
a
very
simple
dice
roller
app
sort
of
like
Yahtzee.
So
what
you
do
is
when
you
click
on
reset
the
dice.
It's
just
making
it
1
2,
3,
4,
5,
6
I
can
go
ahead.
Roll
the
dice
make
it
something
different
again
part
of
the
demo.
D
If
you
look
at
the
sample
code,
that
I
have
it's
automatically
generating
all
these
files
on
the
client
side,
not
unlike
the
demos
we've
seen
before
so
again,
not
not
something.
It's
too
different
from
other
examples
of
st.
but
I
also
pulls
like
a
sickle
are
something
that
was
added
quite
late
to
the
game
in
signal
and
a
Sputnik
or
and
once
it
was
on
the
horizon.
I
started
telling
a
lot
of
people
hey
signal
ours
out.
This
is
something
really
cool.
D
You
can
start
using
it
right
now
and
I
noticed
that
the
community
responded
like
there
is
very
positive
response
around
not
only
the
maturity
of
dotnet
core,
but
around
things
being
added
that
they
were
familiar
with
before.
So
it's
super
cool
to
have
this.
This
is
a
life
pull
right
now,
I'm
gonna
zoom
in
to
this
URL
I,
don't
know!
If
you
can
you
guys
see
that
URL
right
there
yeah
all
right,
so
it's
live
in.
D
Marble
pulled
your
website's
net,
so
I
will
go
ahead
and
leave
that
there
John
Galloway
butter
for
I
am
the
captain
now,
so
I
can
go
ahead
and
order
that
so
you
can
do
anonymous
voting
if
I
put
my
name
shy
than
there.
I
can
vote
for
Captain
America
and
they
can
sort
of
cheat
because
I'm
not
blocking
anything.
But
the
goal
of
this
is
to
show
that
you
know
again.
You
can
use
signal
R
for
a
lot
of
different
cool
things,
including
live
demos,
but
also
capture
that
data.
D
However,
you
wish
to
rate-
and
in
case
you
wonder
how
this
little
tiny
icon
is
generated.
So
it's
not
a
broken
icon,
that's
literally
the
Unicode
character
for
a
black
square.
So
again
just
a
placeholder
that
does
that
and
I
see
Scott
Hanselman
likes
Captain
Marvel,
but
I
am
the
captain.
Now
is
winning
so
there
you
go.
So
those
were
the
three
demos
that
I
wanted
to
show
today.
I
know.
B
D
D
All
right
so
yeah,
so
one
thing,
I
realized
things
were
changing
in
people.
That
would
ask
me
all
the
time.
Well,
why
should
I
learn
all
this
new
stuff?
It's
always
changing
and
I
don't
want
to
watch
all
these
videos
read
all
these
Docs,
so
the
first
thing
I
wanted
to
do
is
sort
of
for
counter
that
by
referring
to
all
the
official
stuff,
so
one
thing
you'll
see
I
have
in
common
all
the
post
is
that
I
refer
to
the
official
documentation
wherever
it's
relevant.
D
D
I'll
put
tweets
on
there
as
well
from
official
tweets
that
are
out
so
that
way,
it's
all
interconnected
right,
there's
new
announcements,
everything
that's
coming
out
and
I'm
able
to
get
all
that
information
so
that
a
reader
wouldn't
have
to
go,
seek
out
everything
on
their
own,
but
at
the
same
time
they're
not
left
to
just
reading
this
isolate
a
set
of
blog
posts
because
everything
is
connected
and
they
can
go
back
to
the
source.
Oh.
B
A
Just
you
know
not
learning
enough
about
something
to
go
yeah.
This
isn't
particularly
useful
or
interesting
to
me
or
applicable
and
I'm
just
gonna.
You
know
let
it
pass
me
by
and
you're
handsome
and
talks
about
drinking
from
the
fire
hose
yeah
guys
to
Twitter
and
a
bunch
of
other
stuff,
and
this
is
no
different
in
my
mind.
A
A
A
Then
you
know
that's
just
a
skill
that
we
all
need
to
develop
and
is
not
a
skill
that
all
yeah
doesn't
just
quit.
You're
calling
it
a
skill
doesn't
mean
that
there's
always
a
right
answer
that
is
applicable
everywhere
and
you
Nick
always
publicly
talked
about
trade-offs
and
I,
always
love
that
and
we
we
live
trade-offs
on
our
team,
because
you
know
we
serve
millions
of
customers
with,
but
you
know,
there's
a
handful
of
people
at
the
end
of
the
day,
like
you
know,
we're
well-funded.
B
A
B
B
C
A
That
would
be
there,
we
go
so
yeah,
it
is
it.
This
is
a
thing
that
we
constantly
live
with
on
the
team
which
any
software
team
should
or
does
I
hope,
which
is
you
know,
it's
always
a
question
of
trade-off.
So
it's
always
a
question
of:
what's
the
cost
now,
what's
the
cost
over
time,
and
then
what
is
the
opportunity
cost
of
either
doing
it
now
or
not
doing
it
now
and
then?
What's
the
benefit,
all
right
and
say,
cost
cost
cost
benefit.
This
is
the
way
I
kind
of
think
about
it.
A
A
I
guess
there's
not
even
a
software
right
yeah,
it's
great,
these
type
of
things
I
think
help
because
I,
let
people
you
know,
invest
a
small
amount
of
time
with
some
structured
material,
which
is
also
really
important,
because
the
Internet
is
a
firehose
and
it's
hard
to
get
a
nice
thread
through
that
to
learn
something
quickly.
So
having
a
series
of
structured
content
is
useful
and
then
they
can
make
that
decision
for
themselves.
D
Wanted
to
comment
on
that
going
going
back
to
something
that
initially,
maybe
you
didn't
think
you
needed
a
new
feature,
a
language
feature
or
whatever.
It
is
because
a
lot
of
the
time
you
don't
know
what
you
don't
know
right.
So
if
you
never
viewed
it
initially,
you'll
never
know
to
go
back
to
it
or
search
for
it,
so
find
it
very
useful
to
when
something
new
comes
out
just
to
browse
it.
I
don't
have
to
understand
the
whole
thing
and
I
don't
know
about
you
guys,
but
I.
Never
remember
anything.
D
So,
if
want
to
write
to
a
text,
file
I,
don't
like
I
have
to
look
it
up
and
sometimes
I
find
my
own
blog
post
I
find
my
own
code,
which
is
fine
but
I'm
able
to
search
for
something
that
I
know
to
search
for
because
I've
seen
it
before
so
again,
when
a
new
language
feature
comes
out,
I
want
to
know
when
it's
out
first,
just
so
that
it's
in
the
back
of
my
head
somewhere
and
that
way,
I
know
to
come
back
to
it
later.
On
yeah.
B
I
like
to
kind
of
keep
that
you
know
I,
think
of
something
like
they
have
the
Gartner
graph
or
whatever,
and
there's
like
with
all
those
things.
It's
like
technology,
it's
like
okay,
this
thing's
out
here.
Let
me
take
two
minutes:
skim,
a
page:
okay,
I've,
a
Glee
know
where
it
fits
in
at
least
and
we're
in
a
you
know
what
I
mean
I
know.
I
can.
B
B
A
Should
I
drop
it
now
that
would
be
great
for
dotnet
someone
who
was
in
you
can
do
an
informed.
You
know
we
shouldn't
do
it
because
we're
just
Michaels
tell
you
about
lay
it'll,
be
nice
to
have
someone
with
a
different
opinion
and
more
informed
approach
in
the
real
world.
Do
something
like
that,
but
the
technology
radar
from
thought
works.
I
find
particularly
useful.
I
tend
to
check
it
every
quarter
to
see
what
they're
saying
about
emerging
technologies
legacy
technologies.
A
C
Joke
about
my
resume
being
multiple
pages
and
then
how
I
have
to
yank
out
the
middle
part
of
the
resume
you
have
to
get
used
to
being
able
to
do
that.
I
had
a
three
page
resume
page
to
just
yank
it
out
right,
like
back
in
the
early
90s
early
2000s.
Rather
you
wanted
to
scale
a
web
farm.
I
was
your
guy.
C
Now
it's
a
checkbox,
fine
rip
that
page
of
the
resume
out,
and
if
you
don't
accept
that,
like
that's
the
put
that's
a
thing
that
you're
gonna
have
to
give
up,
then
you're
gonna
have
problems
yeah.
Absolutely
looking
at
the
Gardner.
Quadrants
is
a
good
way
to
decide
which
part
of
your
resume
to
throw
out
the
door.
Yeah.
A
I
mean
a
list
has
something
you
really
want
to
go
deep
on.
There's
someone
who
works
at
the
cloud
companies
who
implements
that
for
the
millions
who
now
don't
have
to
worry
about
it.
But
that's
now
a
very
specialist
thing
right:
it
is
a
checkbox,
like
you
said,
there's
a
lot
of
code
behind
that
checkbook
and
you
could
you'd
want
to
write
that
guide
right.
C
We
used
to
talk
about
our
friends,
the
IT
department
at
Little,
Debbie,
snack,
cakes,
yeah
yeah
right.
Are
they
really
the
world's
foremost
experts
at
scaling
web
farms?
If
they
are
great,
that's
amazing,
they
should
write
books
and
do
seminars.
If
not,
they
should
focus
on
snack
cakes
and
let
somebody
else
do
the
checkbox
I.
A
Know
that's
funny
because
that's
been
the
argument
that
I've
heard
in
tech
marketing
for
literally
decades.
It's
just
that
the
sort
of
the
watermark
about
where
that
is
has
moved
over
time
because
it
used
to
be
normal
to
run
your
own
email
server.
And
then
people
were
like.
Why
are
you
running
your
own
email
server
like.
A
C
B
D
So
it's
only
not
only
just
lift
and
shift,
but
also
expanding
the
capabilities
of
what
they
can
do
so
work
with
both
retailers
and
vendors.
Everything
from
dotnet
applications
an
app
service
to
as
your
functions,
sequel,
DB
spanning
like
different
countries.
People
are
working
with,
so
all
things
asher
with
all
sorts
of
technologies.
You
can
imagine
and
any.
B
D
There's
actually
so
what
I
can
explain
it
more
when
it's
live,
but
I
can
say,
there's
a
couple
of
major
retailers
I've
been
working
with.
They
started
with
dotnet,
where
they
had
some
SharePoint
developers
who
had
done
experience
and
I'm
wondering
what
else
they
could
do
with
that
experience.
So
I
did
a
workshop
with
them
just
to
learn
about
asp.net
core
from
scratch.
A
lot
of
them
hadn't
touched
MVC.
So
again
a
lot
of
it
was
new
and
they
got
the
fire
hose
of
MVC
blazer
and
everything
the
stuff
that
was
coming
and
stuff.
D
That's
out
now
subsets
that
mist
over
the
years
and
within
a
few
months
they
had
their
first
prototype
up
running
running,
live
in
Azure
with
asp.net
core,
with
sequel,
server,
database
and
they're.
You
know
they're
they're
gonna
go.
There
live
right
now,
they're
staging
servers,
but
they're
going
into
production
by
the
end
of
the
year.
B
A
C
A
I
think
it's
next
Tuesday,
along
with
the
next
update
of
Visual
Studio
visual
tree,
a
preview.
That
is
because,
as
you
probably
know,
three
oh
I've
done.
A
core
is
aligned
with
sixteen
three
of
Visual
Studio
for
Windows
and
so
they're
they're
shipping
in
lockstep,
because
there's
so
much
new,
tooling
and
Emmas
buildi
stuff
and
raise
the
stuff.
So
we
have
to
kind
of
work
chosen
to
don't
tell
those
together
and
so
and
there
are
a
preview
nine
build.
A
Support
if
you
need,
if
you
need
that,
and
if
we
find
you
know
critical
issues
or
security
issues
will
issue
a
update
to
that
very
quickly
as
good
as
we
can.
The
preview
8
as
I
said,
will
be
out
next
week.
There
are
there's
a
body
of
work.
I
know
that's
coming
post
preview,
7
some
people
say
well.
Does
that
mean
it's
not
going
to
change,
and
there
are
some
caveats.
A
C
A
A
Yeah
and
blaze
is
not
frosting.
You
know,
blazer
is
kind
of
a
little
lower,
like
your
app
is
probably
the
sprinkles
on
top
of
the
frosting
with
these
finality,
but
it
means
that
your
we've
we've
locked
down
core
CLR
and
core
effects.
Pretty
much
and
the
hosting
layer
already
they're,
basically
they've
done
and
they're
in
servicing
bar,
which
means
they're
not
gonna,
make
a
change
unless
something
is
bad
enough
that
we
would
push
it
out
as
a
patch
as
a
released
servicing
patch
right.
A
These
are
the
different
bug
bars
that
we
have
a
spinet
core
EF
core
those
framework
level
things
the
bar
is
slightly
lower,
but
not
a
lot
so
they're
in
what's
called
ask
mode
which
we've
talked
about
on
the
stand-up
before
so.
Every
change
to
those
areas
generally
at
the
moment
requires
director
level
approval
or
ship
room
crew
approval,
which
is
basically
a
group
of
people
that
decide
whether
any
code
change
can
go
in
or
not
at
this
point,
because
the
product
is
trying
to
get
shut
down.
A
There
are
some
areas
of
the
product
that
have
a
big
tick
to
say.
No
we've
already
pre
approved
this
body
of
twenty
nine
issues
and
you
can
go
ahead
and
work
on
those
and
then
check
them
in
without
letting
us
know
and
there's
some
area
there's
some
stuff
in
MVC.
That's
having
that
because
a
lot
of
the
team
has
been
focused
on
doing
pleaser
work,
so
they
haven't
been
able
to
do
MVC,
bug
fixing
and
so
there's
a
body
of
MVC
bugs
that
we
wanted
to
fix
in
three
ochres.
A
It's
a
major
version
and
we
couldn't
really
fix
them
in
or
servicing
of
one
because
they
may
change
behavior
subtly,
even
though
they're
more
correct,
and
so
we
can't
do
that
in
a
patch
because
it
may
break
applications,
but
we're
gonna
do
it
in
three,
so
that
will
come
in
preview,
9
and
then
blazer
as
mentioned
in
an
EF
core,
because
it's
separate
from
dotnet
core
in
regards
it's
not
the
shared
framework.
It's
packages
you
opt
into
now.
A
They
did
this
huge
query:
engine
rewrite
which
only
came
out
in
preview
7,
and
so
they
are
very
late
in
regards
to
that
big
breaking
change
and
so
they're
still
reacting
and
churning
quite
a
lot
to
get
that
query
engine
up
to
snuff,
to
ship
on
the
same
timeline
but
they're,
looking
pretty
good
lust.
Sync,
we
have
with
them.
So
that's
pretty
cool,
and
so
some
folks
asked
about
you
know
well
we'll
go
to
RC.
When
is
there
going
to
be
a
release
candidate,
so
preview
7s
go
live
you
can
use
in
production.
A
With
those
caveats
right,
there
will
be
some
changes
to
some
parts
which
yeah
it
won't
be
super
impactful.
But
you
have
to
keep
that
in
mind.
If
you
wanted
something,
that's
closer
to
what
you
would
call
a
traditional,
RC
I
think
it's
more
likely
going
to
be
a
preview
9.
The
preview
9
build
and
that's
because
of
those
bodies
of
pre-approved
work
that
I've
already
talked
about
it's
two
more
releases
after
preview
7,
where
blazer
can
finish
their
lockdown.
A
If
core
can
finish
their
their
query,
stuff
and
NBC
can
get
a
lot
of
those
bugs
fixed.
That
they've
been
wanting
to
fix,
so
I
think
the
preview
9
build
is
going
to
be
the
one
that
looks
closer
to
what
most
people
would
agree
is
a
genuine
release
candidate,
even
though
it
won't
be
labeled
it
release
candidate.
If
there
is
gonna,
be
a
release
after
preview
9
that
isn't
the
the
final
release,
it
would
actually
be
called
RC,
because
we
can't
do
preview
10,
because
that
breaks
the
semver
so
order.
A
Just
not
go
beyond
9
well,
we
could
choose
to
just
not
go
beyond
9,
except
remember
we're
dovetailed
into
visual
studio
and
we
want
for
this
release
and
if
there
is
going
to
be
another
preview
release
of
that
where
we
have
to
take
a
fix
because
of
a
change
in
visual
studio,
we
will
have
to
increment
the
version
number
because
semver
and
preview
9,
because
we
we
put
the
9
in
the
same
segment
of
the
semver
suffix
as
we're
stupid.
In
hindsight,
as
the
alpha
part,
that
part
is
only
sort.
A
It
is
not
semantic
to
get
semantic
sorting
in
the
suffix.
You
have
to
have
a
period
which
we
now
December
2
right
and
we
have
that
for
some.
The
build
numbers
are
in
that
area.
For
example,
preview
9
to
preview
10
doesn't
work,
but,
as
someone
Nick
Turse
said,
preview,
dot
9
to
preview
doc
10
works,
but
we
didn't
do
that
at
the
beginning
of
3.
Oh
because
we
weren't
building
sim
ver
to
stuff
at
the
beginning
of
3.
A
Oh,
we
only
switched
December
2
version
numbers
in
like
preview
5
and
for
all
that
we
haven't
done
it
for
the
whole
stack.
Yet
we
only
did
it
I
think
it
like
the
site
extension,
for
example,
for
a
spinet
core
preview
run
times.
It
works
in
Azure,
app
service
that
still
isn't
simper
to
versioning,
because,
as
your
app
service
site
extension
gallery,
isn't
using
a
new
new
enough
version
of
new
get
to
support
same
virtu
versions
because
everything's
complicated
and
not.
A
It
sounds
like,
and
so
that's
why
anyway,
so
we
won't
do
that
if
an
f5
will
switch
to
full
same
virtu,
we
won't
do
preview,
one
will
do
preview
dot
one
or
something,
and
then
this
problem
will
go
away
and
only
takes
us
to
five
versions
to
figure
that
out.
So
that's
happening.
So
if
you
really
are
waiting
for
an
RC,
I
would
probably
preview.
Now
it's
going
to
be
that
one.
A
But
honestly,
if
you're,
already
updating
your
code,
you
know
week
to
week
with
this
stuff
I
would
adopt
it
now
and
see
what
it
looks
like
and
if
it
works
for
you,
then
I'd
put
a
production
in
and
go
for
it.
The
other
big
thing
I
wanted
to
call
out
was
this
blog
post
that
just
went
live.
Let
me
share
my
screen.
Oh
look,
no
signal,
that's
the
wrong
one!
Let
me
do
that
one.
So
this
blog
post
just
went
live
today.
A
This
is
one
of
the
biggest
changes
that
we
made
with
regards
to
how
core
is
included
and
delivered
with
visual
studio,
and
it's
a
it's
a
it's.
The
first
step
as
part
of
a
bigger
change
with
donek,
with
the.net
sdk
moving
forward.
This
blog
post
went
live
this
morning
or
last
night
and
it
talks
about
this
change.
A
So
now,
with
you
know,
everyone
who's
used,
visual
studio
and
dotnet
core
will
be,
will
be
familiar
with
the
proliferation
of
dotnet
cool
versions
that
they
end
up
with
on
their
machine,
and
you
know
that
they
go
over
to
the
favorite
command
and
they
type
dotnet
info
and
like
it
Scrolls
for
pages
and
pages,
especially
if
they
use
two
different
versions
of
Visual
Studio.
You
can
see
down
here
in
the
taskbar.
I
have
two
side
by
side.
Instances
installed
for
what
it's
worth.
A
I'm
use
this
one
on
the
left
is
the
public
preview
channel
of
Visual
Studio
and
the
one
on
the
right
is
the
internal
preview
channel
of
Visual
Studio.
So
this
is
stuff
you
haven't
seen
yet,
and
this
is
the
one
that
you
all
have
now
for
using
the
preview
channel.
I,
don't
even
have
the
you
know
the
public
released
channel
installed
because
I
haven't
used
for
it.
A
I
always
want
the
preview
channel,
which
is
what
you
need
for
dotnet,
core,
free
and
I
want
the
internal
preview
channel,
because
that
is
the
one
that's
closest
to
the
internal
master
branch,
which
means
that
I
can
use
the
stuff
that
the
developers
checked
in
a
couple
days
ago.
Okay-
and
so
this
is
the
one
that
y'all
will
be
getting
next
week,
and
so
the
point
was
in
the
old
days.
A
If
you
had
both
of
these
things
installed
the
release
channel
in
the
preview
channel,
you
would,
by
default,
get
at
least
two
versions
of.net
core,
which
makes
sense
because
they're
both
of
their
own.
The
problem
was
that
any
change
to
any
part
of
dotnet
core-
a
template,
core
CLR,
the
host
asp
net
core
EF
core
anything-
would
result
in
a
new
SDK.
Also
any
change
to
Emma's
build
and
he
changed
a
new
gate
and
any
change
to
the
compiler
Rozlyn
would
result
in
a
new
SDK.
A
Those
SDK
is
installed
side
by
side,
which
meant
that
any
one
of
those
components
changed
you've
got
a
new,
side-by-side
installation
of
Nick
or
SDK,
which
means
when
you
went
to
this
screen
it
just
added
at
least
one
more
line,
if
not
three
or
four
new
lines,
because
this
is
listening,
both
SDKs
and
runtimes,
or
shared
frameworks
that
are
installed.
The
big
change
is
there
in
vs
now
from
16
3
onwards,
you
will
only
ever
get
one
dotnet
SDK
vs
that
you're
installing
so
I
have
to
here.
You
can
see
them.
A
I've
got
preview
701
to
81,
which
is
the
current
preview
7
build
that
everyone
is
using
and
I
have
preview
801
3
437,
which
is
the
current
build
that
is
inserted
into
the
internal
dogfooding
builder
Visual
Studio,
which
is
very
close
to
what
will
be
released
next
week.
If
not,
is
actually
the
one
that
will
be
released
next
week
and
that's
all
I
will
ever
have.
I
will
only
have
two
versions
and
they
will
just
go
up
based
on.
A
What's
going
on,
the
runtimes
underneath
are
now
treated
separately,
so
you
will
get
a
runtime
with
an
SDK,
because
the
SDK
needs
a
runtime
to
run
itself
on
and
it'll
always
be
the
latest
runtime.
But
then
you
will
opt
in
to
earlier
runtimes.
So
in
16/3
preview
1
we
defaulted
to
just
giving
you
the
300
runtime
preview
7
and
the
300
SDK
by
default,
and
then
you
had
to
choose.
A
If
you
wanted
the
2
one
runtime
or
the
two
two
runtime
based
on
feedback
and
using
that
we've
decided
that
in
preview
2
or
3
or
whatever
it
is
onwards
of
16
3,
we
will
always
give
you
the
LTS
current
LTS
runtime,
which
is
still
2.1
today,
and
the
latest
current
runtime
by
default.
The
vs
installs
all
right.
So
you
would
get
two
runtimes
two
versions,
I
should
say
so.
A
B
A
Latest
version
lets
you
target
any
version.
Of.Net
you
shouldn't
have
to
have
multiple
versions
of
vs
installed,
just
to
build
four
different
versions:
of.net
right.
Obviously,
so
that's
what
we're
doing
for
the
SDK.
That
makes
it
much
much
much
simpler.
Then,
as
the
SDK
does
have
to
change.
It
now
defaults
to
uninstalling
the
previous
version,
so
that
you
don't
get
this
proliferation
of
SDKs.
A
Similarly
for
runtimes,
as
we
update
the
runtimes
with
servicing,
because
we
do
roll
forward
automatically
onto
the
latest
patch
for
a
given
major
minor
pair
of
the
runtime
will
uninstall
the
previous
runtime
for
you
when
you
install
the
new
one
or
when
it
comes
down
through
Visual
Studio,
now,
I'm
talking
about
developer
boxes
here
for
people
who
are
maintaining
their
production
servers
themselves
like
you,
you
do
whatever
you
do
right
you.
You
know
what
you
have
on
your
machine.
A
You
know
what
you
need
to
do
to
run,
that
you
want
on
the
actual
version
of
the
runtime.
You
want.
That's
all
on
you.
Al
installer
has
one
behavior,
but
you
should
always
be
aware
of
what
you're
running
on
your
production
machines
I,
wouldn't
ever
dream
that
we
could
get
the
defaults
right
for
everyone
for
how
we
get
the
production
instances
of
runtimes
and
things
installed,
but
for
developer
machines
we
kind
of
have
you
know
we
kind
of
own
the
message
here.
A
We
want
to
make
sure
that
there's
the
least
amount
to
run
your
stuff
successfully
in
a
developer
machine
and
not
have
you
have
to
maintain
this
stuff.
Now
in
the
past,
I
had
given
some
guidance
on
how
to
clean
up
these
versions,
and
so
I
would
tell
folks
to
kind
of
go
into.
You
know
you're
right,
mouse-click
down
here
you
go
to
apps
and
features
you'd
type
in
net
core,
and
you
would
see
like
four
hundred
entries
right
now
notice.
A
There
are
none
yeah
at
all
and
we're
still
re-evaluating
this
behavior
by
the
way,
and
that's
because
the
dotnet
cores
that
are
installed
on
my
machine
now
are
wholly
managed
by
Visual.
Studio
I
got
them
via
Visual
Studio.
So
if
I
were
to
allow
you
to
uninstall
them
here,
you
could
effectively
break
Visual
Studio
unless
you
went
and
repaired
Visual
Studio
through
the
Installer,
but
you
can
always
do
by
the
way.
Okay
repair
does
work.
A
If
we
do
it
right,
and
so,
if
you
ever
find
yourself,
you
deleted
a
file
on
disk
it
you
weren't
supposed
to
because
you're
in
program
files
and
then
BS
dot
doesn't
work,
go
and
repair
vs
and
it'll
fix
itself.
So
you
don't
see
any
of
them
in
in
here
anymore,
because
we
manager
for
you
as
part
of
the
vs
and
stuff,
but
in
the
old
days
you
would
see
a
whole
bunch
of
stuff
here.
A
I
would
tell
you
to
uninstall
everything
that
had
dotnet
core
in
it
then
I'd
tell
you
to
go
to
Program
Files
delete
the
dotnet
folder,
because
there
was
stuff
in
that
folder
that
wasn't
tracked
by
the
installer
for
uninstall
reasons,
but
was
laid
down
by
the
Installer.
That's
really
bad!
By
the
way!
I'm!
Sorry
we
did
that
and
then
why
we
tell
you
to
just
go
and
install
the
latest
one.
You
don't
have
to
do
that
anymore.
A
You'll
manage
the
dotnet
core
sdk
yourself,
you'll
run
the
installer
if
you're,
really
kind
of
custom,
you'll
download
the
zips
and
the
archive
and
you'll
do
it
yourself
and
then
I
have
no
advice
for
you
do
whatever
you
want,
because
you've
obviously
decided
to
do
that,
but
if
you're
using
the
installers
we're
trying
to
make
this
much
better
for
you
now
so
I'd
love
to
get
feedback
about
this.
The
whole
team
would
love
to
get
feedback
about
this
change
because
it
is
a
very,
very
large
change.
A
So
please
do
read
the
blog
post
that
Lee
published
last
night
hush
this
morning
and
if
you've
had
any
issues,
please
let
us
know
I
noticed
some
folks
in
the
in
the
comments
here
put
their
hands
up
already
in
the
chat
saying
yeah
I
did
that
I
deleted
my
dotnet
folder,
because
you
told
me
to
a
year
ago
and
it
broke
my
ves
this
week.
You
can
just
repair
the
s
and
it
will
fix
itself.
This
is
new
and,
as
I
said,
we
are
rewriting
this
to
see.
A
If
there's
a
way
we
can
sort
of
get
the
best
of
both
worlds.
There
you
go.
There
is
a
question:
what
happens
if
you
don't
use?
Visual,
Studio,
I,
think
I
just
addressed
that
didn't
I.
If
you
don't
use
Visual
Studio,
you
will
install
as
usual
the
dotnet
core
SDK.
You
can
still
download
the
dotnet
core
SDK
separately
and
install
it,
and
it
will
then
appear
in
the
add/remove
programs
or
what
to
called
our
programs
and
features.
A
And
then,
if
you
uninstall,
Visual,
Studio
you'll
still
have
the
SDK,
because
you
installed
it
separately
and
those
two
things
ref
count
correctly.
You
know
it
won't
delete
it
from
your
machine
right.
So
if
you
want
to
main
control
your
own
destiny
with
regards
to
dr.
ko
SDKs,
you
can
still
just
download
any
version
and
install
it.
That's
totally
fine
right!
You
can
still
do
that.
Don't
worry
about
that.
A
The
other
thing
is
we're
working
on
a
new
windows
net
installer,
which
is
in
this
future
enhancements
section,
which
I've
talked,
which
I've
seen
is
looking
really
good.
There's
a
couple
of
things
reasons
for
that.
One
is
the
installer
tech
that
we're
using
today
is
an
old
version
of
weeks.
It
doesn't
support
high
DPI,
which
is
a
little
Barisan,
because
that
nicka
3includes
WinForms
and
WPF
and
our
own
installer
doesn't
render
in
high
DPI
which
kind
of
X
me.
A
But
it
was
a
huge
effort
to
change
that,
and
so
that
wasn't
able
to
happen
for
300,
but
we
have
an
investment
now
to
write
a
custom
installer
that
is
doing
that
and
also
make
it
more
like
kind
of
the
vs
world
where
you
don't
want
to
manage
every
single
installation
of
dotnet
core
separately.
Generally,
you
just
kind
of
want
an
installer.
That
then
says
hey:
these
are
the
runtimes
you
have
installed.
These
are
the
SDKs.
A
You
have
install
there's
an
update
for
this
one,
there's
an
update
for
that
one
and
you
can
just
hit
like
go
right,
so
we
are
working
on
that,
install
the
tech
and
again
that
it
and
and
that's
designed
for
running
on
Windows
Server
as
well.
So
if
you
have
full
is-
and
you
need
to
manage
the
versions
of
the
HTML
core
module,
all
that
type
of
stuff
can
be
managed
from
the
one
installer
and
you
don't
have
to
go
the
download
site
and
go.
Oh
look.
A
It's
a
page
of
links
which
one
do
I
need
for
my
machine
again.
You'll
just
download
the
one
net
core
Windows,
install
it'll
boot
up
and
go
Oh
looks
like
you're
running
on
Windows
server.
You
probably
need
these
things
right.
Oh
it
looks
like
you've
got
a
version
of
Visual
Studio.
You
should
do
this
instead
right,
so
we
want
to
make
it
easy,
obviously,
to
focus
to
get
the
internet
on
the
machine
and
have
that
managed
in
the
most
appropriate
way.
Keep
it
up
to
date,
all
that
type
of
stuff,
all
right.
A
They
were
the
two
things
I
was
going
to
talk
about
and
I
see
a
bunch
of
questions
down
which
I'm
happy
to
dive
into
quickly.
I
saw
someone
ask
about
benchmarks.
The
latest
on
benchmarks
is
we
do
have
a
PR
out
on
the
official
tech
empower
repo
right
now,
which
is
using
preview.
Seven.
All
the
tests
pass
they're,
showing
the
improvements
that
we
expect
to
see
so
that'll
either
get
merged
this
week
or
we'll
just
wait
for
preview.
A
Wait
to
drop
next
week,
then
we'll
update
the
PPR
for
preview
eight
and
then
we'll
submit
that
so
you'll
see
the
asp
net
core
entries
and
tech
empower
continuous
results,
move
on
to
the
three
o
stuff
and
you'll
see
some
improvements
here,
which
is
great,
there's
some
other
stuff
going
on
in
benchmarks,
we're
still
trying
to
get
our
hardware
updated
from
ten
gig
to
40
gig.
We
had
that
breakthrough.
A
Finally,
had
our
breakthrough
on
that
in
this
last
week,
where
we
finally
got
a
Linux
box,
one
of
our
Linux
servers
and
one
of
the
Windows
servers
successfully
talking
to
each
other
over
the
40
gigabit
NICs
over
the
existing
switch
that
we
have
and
we
were
able
to
do.
One
successful
test,
run
of
doing
a
load
test
of
the
plaintext
platform
benchmark
on
Windows
and
we
managed
to
go
from
six
and
a
half
million
to
8.3
million
requests
per
second,
just
to
prove
that
the
network
really
was
our
bottleneck.
A
That
is
seems
to
be
preventing
us
from
going
beyond
that
as
well
and
so
taken
power
saw
that
as
well
when
they
updated
all
their
Linux
service.
With
this
kernel
patch
a
couple
of
weeks
ago,
it
basically
from
my
very
rudimentary
understanding
it
does
increase
the
CPU
usage
for
anything
to
networking,
and
so
what
we
saw
is
that
cluster
of
results
at
the
top
of
the
tech
and
power
benchmarks
for
plain
text
has
started
to
separate
again,
because
those
frameworks
are
were
already
using
a
lot
of
CPU.
A
When
the
patch
was
in
put
in
place,
they
started
to
drop
right
no
longer
were
they
limited
by
the
network,
bandwidth
them
taking
more
CPU
and
they
weren't
able
to
do
the
numbers
they
were
doing
before,
whereas
those
that
were
not
particularly
CPU
sensitive.
There
was
one
written
as
you
live,
but
that's
written
in
C++.
That
is
particularly
very
efficient
from
a
CPU
point
of
view.
It
maintained
its
performance
even
after
the
kernel
patch,
the
wrinkle
in
all.
A
That
is
that
we
observe
the
results
going
down
just
when
we
applied
the
patch
to
the
load
server,
not
even
to
the
app
server
where
all
this
code
is
running,
so
we're
still
not
really
sure
what's
going
on
yet
so
we're
still
yeah
performance
testing
turns
out,
like
everything
is
really
hard
to
get
consistently
right.
So
we're
looking
at
that
what
else
the
EF
core
preview
thee
of
core
engine,
the
new
engine
in
e
of
core
3,
that
went
out
in
preview
7,
but
isn't
as
fast.
A
Yet
as
the
old
engine,
we
confirmed
that
when
we
switch
the
benchmarks
over
for
preview
7,
but
it's
actually
nowhere
near
as
bad
as
folks
were
expecting
because
they
hadn't
actually
got
to
doing
any
perfect.
It's
only
a
fairly
small
drop,
and
you
know
in
some
arguments
the
trade-off
in
correctness
of
the
new
engine
will
be
well
worth
the
drop
that
we've
seen
already
and
they
haven't
even
started
doing
perfect
yeah.
So
that
was
really
encouraging
to
see
as
well.
A
We
got
a
whole
bunch
of
stuff
fixed
on
the
adapt
o
was
broken
for
a
long
time.
The
test
we
got
that
stuff,
fixed
and
dapper
still
looking
really
good
on
aircon
core
3
I
should
say
we
have
some
work
scheduled
for
the
next
3
to
6
months
to
really
go
after
the
Fortunes
benchmark,
which
is
the
database
and
HTML
rendering
benchmark.
The
big
bottleneck
for
us
there
right
now
is
that
the
top
frameworks
have
implemented
database
driver
pipelining,
which
is
the
day
at
the
database
driver
level.
A
They
actually
pipeline
requests
seamlessly
under
the
covers
for
you,
you
don't
have
to
do
anything
about
it,
a
little
bit
like
HTTP
pipelining,
and
so
then
they
send
them
serially
and
then
the
other
side.
The
database
will
support
sending
those
back
serially
as
well.
We
don't
have
that
in
a
deonette
yet,
but
we
have
now
scheduled
work
to
implement
that,
and
so
we
hope
that's
going
to
push
our
Fortunes
tests
up
into
that
top
echelon
of
tests
again,
which
would
be
great
because
we
were
there.
A
We
hit
the
like
numbers
and
I
think
in
around
16
or
17
or
something,
and
then
this
new
technique
of
pipelining
in
databases.
Database
drivers
got
greenlit
for
the
benchmarks
and
then
we
haven't
implemented
that
yet
so
we're
gonna
do
that
work.
So
that's
probably
the
latest
on
the
frameworks
stuff
and
the
I
mean.
Obviously
we
continue
to
try
and
push
other
stuff
down.
A
A
spinet
coil
with
DI
and
middleware,
and
everything
plain
text
was
using,
was
getting
a
working
set
of
a
hundred
megabytes,
which
is
you
know
crazy,
because
in
2.2
it
was
like
1.2
gig
and
in
300
it's
a
hundred
megabytes,
because
we've
done
so
much
work
on
the
GC
and
the
allocations
and
a
split
call
that
went
down
to
like
seventy
four
megabytes
this
week.
So
we
got
like
a
25%
reduction.
You.
A
B
A
C
A
I
mean
so,
and
anyone
who's
ever
done,
like
in
def
performance
testing,
knows
that
this
is
really
in
relationship
between
latency
and
queuing
and
CPU
use
and
memory
use
and-
and
it
all
depends
on
stuff-
and
it's
never
as
easy
as
one
goes
up.
The
other
goes
down
like
it
all
depends
on
an
interplay.
But
in
this
case
we
didn't
really
do
anything,
but
the
memory
went
down
which
is
great,
which
is
really
good
and
also
what
contention
went
down
massively
on
our
thinking.
A
What
was
it
the
Jason
test,
one
of
them
and
so
that
the
Linux
performance
is
now
started
to
converge
with
their
windows
performance,
which
is
something
that
we've
also
been
working
on
because
the
windows
implementation
of
the.net
networking
stack,
is
you
know,
20
years
old
and
has
been
improved
over
that
time,
whereas
the
linux
one
is
like
four
years
old
and
got
rewritten
in
2.1,
and
so
there's
still
a
whole
bunch
of
work.
We're
doing
there.
Also
the
thread
pool
implementation
is
different,
and
so
we
continue
to
do
that.
A
C
A
C
A
C
A
A
A
C
C
A
C
C
A
C
C
C
A
C
C
A
A
In
dotnet
v,
nothing
yeah,
I,
don't
know
if
I've
planning
has
just
started
other
than
what
you
know
Hunter
already
announced
earlier
this
year,
is
the
general
direction
of
dr.
5-1,
net
unification,
etc,
etc.
So
yeah
there's
a
few
working
group
set
up
and
we're
just
doing
really
really
early
stuff,
we'll
have
more
to
share
about
that
after
our
summer.
There's
no
one
here,
like
it's
August
like
the
car.
B
A
No,
no
plans
for
karate
karate
is
still
experimental.
If
the
repo
says
the
repo
says
it
quite
clearly,
it's
experimental
unfunded,
there's
some
good
learnings
in
karate
karate
has
a
different
implementations
for
some
of
the
core
pieces,
like
the
thread
pool
and
we
still
look
to
because
it
was
an
opportunity
to
write
a
lot
that
stuff
from
scratch
and
there
are
still
pieces
of
the
karate
runtime
that
we
pull
over
to
core
seola
when
we
have
an
opportunity
to,
and
it
makes
sense
and
I
know
if
I
don't
know.
A
Five
some
folks
are
thinking
about
taking
the
karate
thread,
pool
implementation
and
moving
that
into
core
CLR,
the
biggest
cost.
There
is
actually
just
testing
and
making
sure
that
we
haven't
regress
to
any
specific
scenarios
with
that
new
implementation.
But
we
know
it
has
benefits
for
some
scenarios
we
care
about.
So
that
would
be
super
interesting.