►
Description
The ASP.NET team is actively working on .NET 6 planning and would like your help! Come chat with the team as they review the backlog for possible focus areas for the next release.
Community Links: https://www.theurlist.com/aspnet-standup-2020-10-13
Featuring: Daniel Roth (@danroth27), Damian Edwards (@DamianEdwards), Artak Mkrtchyan (@mkArtak)
#aspnet #aspnetcore
A
A
A
A
B
B
D
C
A
C
A
A
B
A
A
It
could
be
could
be.
I
don't
know
I
would
have
got
away
with
it
if
it
wasn't
for
this
so
yeah.
So
this
this
looks
neat.
I'm
I'm
interested
to
see
this.
I've
heard
podcasts
and
stuff
about
this
12
factor
thing,
but
I'm
eager
to
see
them
dig
into
that.
So
that
looks
cool
franz
boma
just
announced
this
yesterday.
So
this
is
hmd
3.0.
A
So
what's
interesting
here
is
he's
been
producing
llblgen
for
forever
and
it's
a
you
know:
it's
a
it's
a
data
code,
generator
thing
it
does
all
kinds
of
advanced
stuff
for
you
know,
making
it
easier
to
access
and
deal
with
your
database.
I
probably
said
that
very
terribly
wrong,
but
it's
it's
a
very
advanced
product.
A
What's
cool
is
he
uses
hnd
and
and
his
team
uses
hnd
for
their
support
forums
internally,
and
so
he
has
released
this
and
he's
showing
here
it's
it's.
He
talks
about
the
history
of
it
and
he
also
talks
about
like
here's.
It's
released
as
as
open
source,
and
he
talks
about
you
know:
here's
how
it's
built,
how
it's
architected
digs
through
all
the
security
stuff.
A
So
what's
what's
neat
here
is
two
things
I
think
one
is
as
a
product,
it's
interesting
and
good
to
know
about,
and
then
two
just
as
a
real
world
like
this
is
a
net
production
application.
Where
you
can
see
the
source
code
see
how
it's
built
and
see
you
know,
and
he
cares
deeply
about
data
data
architecture
and
stuff,
and
so
it's
really
cool
to
see
as
he
digs
through
and
explains.
A
D
A
Say
something
wrong,
but
here
he
talks
about
pushing
ui
changes
from
blazer
server
to
the
browser,
and
one
really
cool
thing
about
blazer
server
is
that
you
have
the
signalr
connection,
so
you're
actually
running
code
on
the
server,
and
you
have
a
signal
or
connection.
That's
just
for
free
set
up
for
you,
so
he
talks
about
how
that
works.
But
he
does
say
you
know.
Blazer
server
is
not
going
to
automatically
re-render
the
components.
A
A
C
Okay,
blazer
in
general,
will
will
have
some
heuristics,
where
it
will
assume
that
your
state
is
probably
changed
and
will
re-render
components
for
you,
but
in
general
the
model
is
very
much
like
react
where,
if
you
have
a
state
change
inside
your
component,
the
the
framework
doesn't
generally
know
that.
So
you
have
to
tell
the
framework
and
then,
if
you
have
events
that
are
happening
like
on
a
separate
thread,
blazer
has
a
synchronization
context.
C
A
B
I
will
say
that
I
would
love
to
see
us
lean
into
this
pattern,
a
little
bit
more
in
blazer
server
and
actually
improve
the
developer
experience
for
building
these
types
of
apps.
I
think,
there's
the
the
signal
connection
isn't
exposed
to
you
in
any
way.
So
you
you,
don't
you
can't
add
methods
to
a
hub,
for
example,
that's
behind
it.
You
have
to
layer
your
own
signal
hub
into
your
blazer
server,
app.
B
If
you
want
to
and
then
unfortunately,
you
actually
got
two
connections
effectively
except
one
is
between
the
browser
and
the
server,
and
then
one
is
between
the
server
and
the
server,
which
is
a
little
unfortunate
and
that
can
cause.
You
know,
scale
issues
if
you're
not
careful
with
it,
and
so
I
would
love
to
see
us
somehow
expose
the
fact
that
there
is
a
real-time
connection
between
the
browser
or
the
wherever
the
rendering
is
happening
and
and
and
the
blazer
server
components
running
on
the
server.
And
it's
an
interesting
it.
B
I
think
it
raises
some
interesting
opportunities
for
for
app
model
sort
of
changes
that
we
could
do
so.
Obviously,
if
you're
just
doing
it
with
components
which
is
what's
happening
here,
you
raise
an
event:
you
push
it.
You
know
you
make
a
component
change
and
then
you
rely
on
the
framework
to
push
it.
That's
obviously
a
start,
but
there's
a
whole
bunch
of
semantics.
That
signaler
gives
you
that
just
aren't
replicated
here
like
groups,
for
example,
or
addressing
an
individual
client
and
get
any
of
that.
B
You
would
have
to
recreate
all
that
again
from
scratch,
which
is
a
little
unfortunate
and
I'd
it'd,
be
really
cool.
I
think
for
us
to
to
dive
into
this
a
little
more
and
try
and
tease
these
patterns
out
and
then
have
make
them
available
as
first-class
principles
and
plays
as
ever.
There's
no
plan
to
do
that
currently,
as
I'm
aware
of,
but
I
would,
if
you,
if
you
care
about
that
segway
into
our
yeah,
discuss
redundancy.
A
Yep,
okay,
benjamin
talking
about
printing
pdfs
and
blazers,
so
he
does
a
roundup
of
several
different
options
for
printing
pdfs.
He
looks
at
you
know
some
of
the
different
alternatives
that
are
out
there.
He
ended
up
using
print
js.
I
do
see
that
pattern.
Quite
a
bit.
People
are
finding.
You
know
existing,
really
nice
web
framework.
You
know
javascript
libraries
and
then
wrapping
them
up,
and
so
he
is,
he
is
based
it
on
that
and
then
built
built
forward.
A
He
said
you
know
there
are
some
caveats
to
it,
but
you
know
generally
it's
able
to
print
and
it's
building
on
the
print
js
support.
So
that's
pretty
cool
john
hilton
talking
about
pre-rendering,
your
blazerwasm
application
with
applicationwith.net5,
and
so
he's
he's
got
a
you
know
relatively
deep
dive.
Some
nice
diagrams
here
I
will
be
completely
honest.
I
still
get
lost
with
with
laser
pre-rendering,
I'm
on
a
chat
with
that
you're
on
dan
and
I'm
like
always
struggling
to
keep
up
a
bit.
So
I
think
the
series
is
nice.
C
Yeah,
not
that
not
bad
I
mean
there
are.
There
are
some
some
some
gotchas
with
with
blazer
perspective,
the
new
webassembly
pre-rendering
that
you
need
to
be
aware
of,
but
I
mean
the
conceptual
model
is
right:
we
have
client-side
rendering
in
the
browser
and
we
have
the
ability
to
also
render
stuff
on
the
server
which
we've
had
forever
like
with
mvc
and
razer
pages,
and
all
pre-rendering
is
is
like
hey.
Let's,
let's
go
ahead
and
run
the
components
on
the
server
we've
got
them.
C
We
can
run.net
code
on
the
server,
let's
generate
the
html
up
front
so
that
the
client
gets
pixels
as
soon
as
possible
possible
while
we're
wiring
up
the
you
know
the
interactivity
in
the
background,
whether
it's
the
web
assembly
runtime
or
the
signalr
connection.
So
I
think
that
part
conceptually
shouldn't
be
hopefully
not
too
overloading
things
where
it
gets.
C
A
little
tricky
is,
like
you
know,
getting
that
experience
to
be
really
smooth,
not
having
like
like
ui
flashes,
is
often
something
that
people
find
they
hit
when
they
try
to
to
wire
up
pre-rendering
like
if
you're
doing
something
asynchronous
during
your
component
logic,
then
you
might
pre-render
on
the
server
and
that'll
look
great
and
then
the
components
will
do
their
async
stuff.
When
blazer
sees
that
any
sync
work
has
happened,
it
will
immediately
kick
off
a
render.
C
So
you
have
an
opportunity
to
put
like
loading,
spinners
and
stuff,
but
that
render
won't
have
the
data
yet
and
so
you'll,
usually
like
blast
away
the
dom
that
was
just
nicely
pre-rendered
and
you'll
see
this
flash
that
goes
away,
and
then
it
comes
back
again.
So
there's
some
trickery.
You
sometimes
need
to
do
to
to
have
the
data
already
available,
so
you
avoid
those
those
those
types
of
problems
and
one
that's
another,
one,
those
areas
for
dot
net,
six,
that
we
want
to
make
more
seamless,
more
and
more
easier.
C
A
A
They
announced
this
apps.peachpie.io
and
the
idea
here
is
to
make
it
easy
to
consume
php
projects
from
c-sharp,
so
they've
got
some
listed
here
and
so
like,
for
instance,
if
you
want
to
use
ascii
math
text
to
dot
net
like
so.
This
is
a
port
of
the
php
and
you
know
using
peach
pie
and
then
they've
got
these
examples
here.
So
nice,
just
kind
of
way
to
expose
and
kind
of
a
bridge
for
all
these
php
libraries
in.net.
A
So,
okay,
here's
gerald
and
he's
he's
writing
he's
continuing
a
series
about
testing-
and
here
he's
talking
about
automated
unit
tests
with
playwright
and
xunit.
So
just
the
whole
kind
of
I
was
looking
into
this
recently,
like
all
the
different
ways:
the
the
automation
opera.
You
know
options
you
have
and-
and
there
are
several
so
this
is.
This
is
interesting:
the
integration
with
playwright
so
using
playwright,
sharp
and
using
xunit,
and
then
actually
automating
and
doing
a
full,
automated
unit
test,
and
they
they
serve.
A
You
know
really
kind
of
different
things.
You
can
do
a
unit
test
of
your
code,
but
but
when
you're
doing
things
that
are
interacting
with
the
with
the
browser-
and
you
know,
testing
loading
timing
and
all
that
kind
of
stuff
it
can
get
complex.
So
so
this
is
good.
I'm
looking
forward
to
see
more
in
in
series
here
and
with
that,
I'm
ready
to
turn
over
to
you
folks.
So
I
saw
this
go
out
last
week
and
I
was
like
hey:
why
don't.
D
C
C
C
Net
six
planning
right
now,
so
if
anyone
on
the
call
is
expecting
to
like
to
have
the
full
roadmap
for
dot
net
six
like
what's
all
the
new
stuff,
that's
coming
we're
not
there.
Yet
we're
still
trying
to
figure
that
out,
and
so
actually
the
point
of
of
this
community
stand
up
was
more.
How
can
you
get
involved
like?
How
can
you
see
what
we're
doing
as
part
of
our.net
6
planning,
and
how
can
you
participate
in
that?
C
We
very
much
care
about
the
community
being
involved
in
our
planning
efforts,
and
we
want
you
to
know
what
channels
we're
currently
looking
at,
and
maybe
you
have
some
ideas
about
how
we
can
we
can
better
listen
to
to
those
things.
So
there's
there's
no
like
big,
reveal
here.
Sorry,
if
you're
hoping
to
know
like
all
the
features
we're
doing
for
dot
net
six
in
terms
of
road
map
for
the
plan.
I
know
the
road
map
for
the
road
map.
C
We're
shooting
for,
like
imagine
like
early
next
year,
is
where
we're
hoping
to
publish
a
asp.net
core
in
dot
net
six
road
map.
For
what
are
we
going
to
be
doing?
That's
about
the
time
frame,
we're
looking
at
so
we're
in
the
middle
of
planning.
Not
not
don't
have
a
done
plan.
That
said,
let's
we
want
to
give
you
guys
a
little
bit
of
content.
C
You
folks
a
little
bit
of
context
about
what
dot
net
six
is
about,
at
least
as
far
as
we
know,
it
is
still
still
early,
so
things
are
evolving
and
changing
and
everything
I
say
now
is
subject
to
change,
so
don't
don't
write
it
in
stone,
but
we
have
already
said
that,
of
course,
the
net
releases
are
yearly
releases.
Don
f5
is
coming
up.
The
the
rc2
release
should
be
shipping
momentarily,
so
that
should
be
out.
You
may
have
seen
the
nougat
packages
start
to
fly
up
to
nuget.org.
C
The
on
f5
is
basically
wrapping
up
and
we'll
ship
in
november
of
this
year
make
sure
you
join
us
for
the
dot
net
conf
event
don
at
six
is
then,
a
year
later,
like
we're
on
a
year
cadence
for
all
of
our
releases,
so
we're
basically
planning
a
a
year-long
release
and
we
do
have
some
like
general
themes
that
we're
thinking
about
for
for
net
six,
and
these
things,
even
the
made
broad
themes,
are
still
being
heavily
discussed.
You
know
some
areas
that
we
really
care
about,
that
we
want
to
invest
in.
C
We
know
with.netcore
that
we
of
course
appeal
to
our
existing.net
audience
and
that's
great
and
we're
trying
to
add
more
value
to
those
developers,
but
we
want
to
make
sure
also
that
dot
net
is
appealing
to
as
broad
a
set
of
folks
as
possible
coming
from
diverse
backgrounds
and
that
they
have
a
really
good
getting
started
experience,
and
you
know
not
too
many
concepts
thrown
at
them
that
they
haven't
seen
before.
Try-
and
you
know,
smoothly
get
them
on
to
the
to
the
stack
as
much
as
possible.
C
C
You
may
have
seen
efforts
like
thai
that
make
working
with
net
and
systems
like
kubernetes
and
containers,
making
that
easier
during
your
local
development
and
also
easier
to
get
your
apps
into
those
those
types
of
environments.
We're
trying
to
do
a
bunch
of
work
in
that
space,
ongoing
investments,
of
course,
in
reducing
app
size
and
improving
performance.
C
A
big
area
that
we
want
to
look
at
for
dotnet
6
is
improving
the
developer
inner
loop
by
inner
loop.
We
mean
that
that
iterative
experience
where
you're
editing
your
code
and
you
want
to
see
the
changes
as
fast
as
possible-
damien's
actually
very
heavily
involved
in
that
space
and
is
driving
the
effort.
So
if
you
have
lots
of
questions
about
what
are
we
thinking
about
doing
there
like?
What
do
we
think
about
hot
reload,
I'm
sure
damian
will
have
great
thoughts
to
share
about
that
and
then.
C
Lastly,
the
last
thing
I
just
wanted
to
share
is
about
the
ecosystem.
There's
a
lot
of
discussion
going
on
about
how
can
we
better
support
the
open
source
ecosystem?
How
can
we
better
enable
customers
and
developers
to
take
advantage
of
great
third-party,
open
source
components
we're
shipping
more
more
of
those
like
we
just
in
dot
net
5?
We
updated
our
web
api
template,
for
example,
to
take
advantage
of
swashbuckle
for
the
open
api
support.
C
We
want
to
enable
more
of
that
and
have
that
trust
that
you
can
feel
as
good
about
taking
dependencies
on
third-party
components
as
you
would
from
something
that
came
from
from
microsoft.
So
those
are
just
some
broad
themes
and
I
know
that's
fairly
amorphous.
It's
not
super
specific
yeah
and
that's
just
kind
of
where
we're
at,
but
hopefully
it
gives
you
some
framing
of
things
that
are
top
of
mind
for
us
and
then
what
we
wanted
to
do
today
is
go
into
more
detail
about
for
a
smith
core.
C
C
C
I'm
gonna
actually
turn
it
over
to
our
talk,
I'm
actually,
I
could
say
I'm
gonna
have
to
drop
off
in
just
about
10
minutes
here,
because
I
would
have
a
conflict,
but
our
talk
is
here
to.
As
our
you
know,
the
the
engineering
lead
for
a
good
chunk
of
ace
mccor
is
going
to
show
a
little
bit
about
how
we've
been
thinking
about
our
backlog.
D
So
recently,
we've
introduced
a
tool
to
help
us
with
planning
and
it
helps
us
looking
to
get
a
better
view
into
the
github
really
github
issues
and
to
try
to
better
understand
what
we
need
to
do
and
we
we
use
that
tool
as
simply
one
input
for
our
decisions,
not
actually
a
definite
guide
like
hey.
This
is
this
is
the
things
we
need
to
work
on.
So
let
me
share
the
view
I
have
in
that
tool
and
we
can
go
there.
One.
D
D
D
Okay,
you
can
see
the
only
information
which
is
missing
in
github
is
a
score,
and
this
score
we
calculate
is
based
on
multiple
factors
for
each
issue,
so
for
for
certain
issues
for
each
issue,
we
try
to
go
and
make
certain
calls
regarding
what
is
the
audience
specific
issue
impacts
like
how
big
that
audience
is.
That's
the
first
one
and
the
second
call
we
make
is
given
the
audience,
how
bad
that
issue
prevents
them
from
adopting
certain
feature
or
how
how
what
like?
D
How
much
does
it
block
them,
and
you
can
see
the
most
and
major
labels
in
here.
These
mapped
to
some
relevant
slightly
differently
named
labels
in
github,
but
these
are
the
labels
which
contribute
to
the
final
score
and
then
based
on
this
score,
you
can
see
how
like
most
important
issues
based
on
community
upvoting
and
comments,
have
been
brought
up
on
this
list.
So
we'll
later
use
this
again
as
just
an
input.
D
This
is
not
a
different
call
and
we
start
going
through
that
through
from
top
to
bottom,
to
understand
what
are
the
things
we
will
be
working
on
during
each
next
milestone.
So
there
is
also
a
small
change,
we're
trying
to
do
in
the
2006
time
frame.
Like
you,
if
people
who
have
been
following
us
and
are
our
like
issues
in
github
during
2005,
you
have
seen
the
next
print
planning
milestone,
which
we
used
heavily
and
relied
on
heavily.
D
We
are
trying
to
get
away
from
having
two
backlog
milestones
and
we
will
have
a
single
just
simple
backlog
milestone
and
you
utilize
more
of
this
tool
to
help
us
differentiate
between
things.
We
will
do
in
0.6
time
frame
and
things
we
want
and
just
to
clarify,
like
dan
earlier
mentioned,
that
we
will
be
do
do
publishing
roadmap
4.06.
D
That
doesn't
mean
we're
going
to
do
a
water,
waterfall
type
of
approach
for
the
whole
year.
We
are
just
going
to
pick
up
the
biggest
investments
for
dot
net
six
and
we
still
are
going
to
have
monthly,
like
monthly
planning
meetings
which,
where
we
will
come
back
to
this
list
and
pick
up
another
set
of
issues
based
on
recent
changes
in
community
needs
and
prioritize
things
like
especially
smaller
enhancements,
has
been
included
in
our
in
in
our
deliverables.
D
Exactly
the
same
way,
the
in
5.0
you
may
have,
you
may
recall
the
place,
a
roadmap,
for
example,
issue
there
we
have
had
listed.
I
don't
know,
20
maximum
issues
we
would
work
on,
but
we
have
delivered
at
least
50
enhancements
throughout
four
five.
All
and
these
smaller
ones
come
each
month
each
milestone
and
if
it
makes
sense,
if
it
helps
community
a
lot,
we
will
just
do
it.
D
A
A
D
So
we
use
gita
projects,
but
not
for
this.
Github
project
has
certain
limitations
and
yeah.
There
is
stack
ranking,
but
it's
very
hard
to
keep
them
up
because
it
is
manual,
whereas
the
order
by
score
here
is
calculated
automatically
based
on,
for
example,
the
number
of
upvotes
of
an
issue.
The
number
of
comments,
the
number
of
participants
and
factors
like
this.
C
So
I
find
one
thing
I
found
really
interesting
is
you
know
like
with
the
acemic
core
repo,
as
we
look
at
like
upvotes
and
reactions
like
for
a
while?
We've
noticed
that
the
the
actual
the
number
of
reactions
that
we've
gotten
is
is
hasn't
been
like
a
huge
amount
like
when
we
look
at
some
other
repos,
like
even
the
net
runtime
repo
ef,
core
repo
or
third-party
repos.
We've
noticed
that
the
communities
there
tend
to
get
very
involved
with
upvotes
and
you'll,
see
like
hundreds
of
upvotes
on
that
particular
issue.
C
So
one
thing
we're
trying
to
to
work
on
to
try
and
address
is
to
at
least
you
know,
communicate
to
our
community
folks,
like
folks
like
you
that
we
are
actually
looking
at
that
upvote.
So
if
you,
if
you
care
about
an
issue,
it
does
matter
if
you
click
the
upvote
button.
That
is
something
that
that
we
are
considering.
We
are
looking
at
the
issues
where
there
seems
to
be
a
lot
of
community
interest
based
on
the
number
of
comments.
C
These
aren't
the
only
things
we
look
at
and
it's
certainly
not
a
contract
that
if
you
upload
something
to
the
top
that
it's
going
to
definitely
get
done
and
we
understand
these
systems
can
be
gained
and
we
hope
people
will
will
be
be
respectful
of
the
the
measurement
we're
trying
to
get
here.
But
it
is
something
that
we
use
and
it
is
helpful
to
us.
So
if
there
is
an
issue
that
you're
like
yeah,
I
hit
that
too
great.
A
B
B
C
We're
just
we're
currently
just
looking
at
plus
ones.
I
believe
I
think
we're
only
looking
at
thumbs
up
look
at
the
thumbs
up.
Okay,
I
believe
so
I
mean
we
can
double
check
that
I'm
not
100
sure
on
that,
but
I
believe
that
and
we're
not
doing
anything
fancy
with
like
and
subtracting
the
down
votes
or
something
like
that,
but
go
ahead
and
click
on
the
little
if
you
click
on
the
little
smiley
face
in
the
upper
right,
yeah
yeah.
C
So
that's
that's,
that's
the
type
of
stuff
that
we're
asking
people
to
use
as
a
way
to
give
us
some
signal
and
feel
free.
Also
to
comment
like
we
are
also
looking
at
just
comments
on
the
issue.
That's
again,
it's
a
noisy
signal.
We
know
sometimes
issues
just
get.
You
know
lots
of
discussion
on
them.
It's
not
necessarily
indicative
that
people
care
about
it,
but
if
you
have
some
information
to
share
with
us
about
why
this
issue
is
important
and
you
post
a
comment
that
does
help
us
know.
B
The
lack
of
this
thing
in
blazer
is
really
a
a
problem
for
us
right
now
that
that's
useful
sort
of
customer
information
for
us
like
otherwise
you
know
we
can
assume
that
that
is
true
of
of
some
folks,
but
actually
having
the
concrete
comment
that
that
is
true,
for
you
really
really
does
help
us
or
if
there's
anything
else,
that
you
know
this
is
preventing
you
going
live
because
we
have
this
type
of
requirement.
Or
you
know,
the
performance
of
this
area
is
so
bad
right.
B
Now
that
I
lose
x
hours,
you
know
a
week
in
productivity
or
whatever
it
might
be
like,
and
you
know
be
genuine,
obviously,
but
those
type
of
things
really
do
help
us
prioritize
when
it
comes
to
trying
to
balance
these
like
I
I
I'm
quite.
I
would
hope
that
most
people
understand
and
appreciate.
This
is
a
very
difficult
process
for
a
team
like
the
asp.net
team
to
to
try
and
prioritize
the
work
for
a
release.
Like
this,
you
know
we
do
one
release
a
year.
B
That's
a
fairly
standard
thing,
top-down
planning
of
things
where
the
directors
or
the
the
vps
will
set
direction,
and
they
want
us
to
focus
on
a
particular
opportunity
or
a
particular
problem
that
they
have
identified
and
that
gets
pushed
down
through
and
then
they
want
us
to
say
hey.
This
is
how
we're
going
to
help
address
that
or
you
know,
develop
towards
that
goal.
B
Bottom
up,
which
is
more
what
we're
talking
about
here,
which
is
people
log
issues
directly
on
github,
and
we
want
to
be
able
to
fit
those
into
the
work
that
we
do
or
the
team
would
like
to
take
the
product
in
this
direction
as
the
as
the
product
owners
for
asp.net.
But
remember,
aspienet
is
part
of
a
larger
product.
It's
part:
of.net
and
asp.net
sits
up
on
top
of
the.net
runtime
and
the
net
bcl,
and
so
they
are
they.
They
have
their
own
agendas
and
they
have
their
own.
B
As
an
example
dan
mentioned
in
a
loop
performance,
we
want
to
make
the
development
experience,
obviously
as
productive
as
it
can
be,
and
a
lot
of
the
time
that
just
means
make
stuff
faster
just
make
it
faster.
Like
I
made
a
code
change
and
I
saved
it.
How
quick
until
I
can
see
that
code
change
in
my
app
while
I'm
sitting
here
doing
development,
there's
a
lot
of
things
that
go
into
making
that
occur.
It's
definitely
not
something
that
just
the
the
so
many
person
blazer
team
can
make
work
by
themselves.
B
They,
you
know,
there's,
there's
tooling,
underneath
that,
whether
it's
command
line,
there's
ms
build
there's
compilers,
there's
a
separate
razer
compiler
to
the
c
compiler.
There's
a
visual
studio
thing
element.
There's
the
editor,
which
know,
which
is
the
thing
that
knows
where
the
edits
occurred,
like
there's
a
whole
bunch
of
elements
that
go
into
figuring,
that
out
and
yeah
there's
some
simple
things
that
we
can
do
like
just
make
the
build
faster.
We
will
obviously
look
at
those
type
of
things,
but
then
there
are
more
complicated
things
that
will
hopefully
yield
far
better
results.
B
B
Maybe
a
new
user
experience
and
hot
reload
is
one
that
gets
thrown
around
a
lot
right,
because
we
see
that
in
other
frameworks-
and
so
it's
very
desirable
that
you
can
within
certain
constraints,
I
could
make
an
edit
and
then
get
that
component.
Reloaded
live,
but
those
constraints
are
a
trade-off,
and
so
we
need
to
kind
of
balance
that,
with
the
existing
experience
and
so
yeah,
so
that
we
have
these
sort
of
two
elements.
B
I
think
dan
enumerated
some
of
the
top-down
themes
for
net
six,
which
we're
in
the
middle
of
kind
of
planning
and
reviewing
right
now,
appealing
to
new
developers
who
are
making
the
interloop
faster,
making
a
good,
solid,
lts
release,
which
means
trying
to
smooth
out
anything
that
from
five
and
I'm
focusing
on
folks
moving
from
dot
net
core
three
one
to
net
six.
That
we
need
to
make
sure
that
that's
as
smooth
as
experience
as
possible.
B
C
So
another
column,
I
think,
is
really
interesting.
Here
is
this
type
effects
and
severity
column
on
the
on
this
tool?
I
don't
know
if
you
want
to
show
a
little
bit
or
talk
a
little
bit
about
that
our
talk
and
what
those
things
mean,
because
in
some
sense
this
information
is
even
more
important
like
like
how
we
think
how
impactful
is
it
for
us
to
address
this
issue?
How
many
people
are
actually
being
impacted
by?
C
It
is
what
these
two
things
are,
and
these
are
things
that
we
we
tag
the
issues
with
based
on
our
own
intuitions
and
what
we've
heard
from
from
users
like
like
you,
and
I
think
it's
interesting
to
discuss
like
you
know.
How
can
how
can
we
get
better
insights
from
the
community
about
whether
these
assessments
are
actually
correct
like
like,
if
the
thumbs
up
helps
us
a
little
bit?
C
If,
if
it's
affecting
a
lot
of
people,
but
really
understanding
the
like
blocking
nature
of
the
feature
like
how
many
people
are
really
need
to
do
this?
And
if
we
don't,
you
know
chip
this
functionality,
then
you're
completely
blocked.
That
type
of
discussion
really
comes
from
people
publishing
those
really
good
comments,
or
when
you
open
up
an
issue
like
really
doing
a
good
job
of
describing.
What
are
you
trying
to
do?
What's
not
working,
and
how
does
that
impact
you
in
your
your
life?
C
D
D
A
D
So
right
now
we
we
just
adopted
this
steve
sanderson
built
this
tool
to
help
us
out
with
this,
and
it
is
just
maybe
a
week
old.
Only
I
assume
at
some
point
I
don't
accept.
The
possibility
of
this
becoming
an
open
source
tool,
definitely
will
share
the
feedback
with
steve,
we'll
see
I
I
can't
comment
further.
A
B
Yeah
so,
like
I
think,
obviously
right
now,
the
focus
publicly
is
much
much
more
largely
on
the
upcoming
release
of
dot
net
five,
and
so
you
won't
see
a
blog
post
about
net
six
themes
or
anything
until
well.
After
dot,
net
five
is
released,
but
you
know
this
is
a
community
stand
up,
so
we
often
talk
about
what's
going
on
week
to
week
day
to
day
in.
B
Do
but
some
of
those
top-down
things,
as
I
mentioned,
which
a
couple
are
for
all
of
net.
This
is
not
just
for
asp.net
they're,
not
asp.net
themes.
We
don't
have
asp.net
themes
as
it
is
with
our
planning.
We
have
net
themes,
and
so
you
know
one
of
those
there's
a
theme
that
covers
client
development
right.
What
are
we
doing
with
regards
to
mobile
development
and
desktop
development
and
there'll
be
more
to
talk
about
that?
To
say
about
that
in
the
coming
months?
B
There's
a
theme
that
talks
about
a
building,
a
stable
lts
release
and
what
we
need
to
do
to
ensure
a
you
know:
a
good
transition,
a
confident
transition
for
folks
running
on
core
31
to
6
and
the
type
of
things
that
they
expect
out
of
that
there's
also
one
that's
focused
on
sort
of
our
larger
scale,
enterprise
customers
and
their
unique
needs,
and
also
our
first
party
customers.
So
our
first
party
customers
are
those
at
microsoft
who
build
services
on
and
what
we've
seen
in
the
last
year
is
with
the
release
of.net
core
31.
B
You
know
there
was
a
blog
post
about
bing
for
example,
months
ago,
and
their
efforts
to
move
to.net
core
and
some
of
the
gains
that
they've
seen.
Well,
that's
that's
happening
more
throughout
the
company,
and
so
we've
got
actually
a
dedicated
team
that
focuses
on
helping
first-party
customers
move
to
net
core
and
now.net5
and.net
six
and
we
talked
we
get.
B
You
know
obviously
lots
of
valuable
information
from
them,
because
we
can
work
probably
more
closely
with
them
than
we
can
with
any
other
company
and
then
everything
we
learn
from
them
and
everything
we
build
or
help
them
with
just
feeds
into
making.net
better
for
everyone.
You
know,
I
know
we
often
get
the
feedback
that,
especially
with
a
lot
of
our
frameworks.
It's
like
what
stuff
it
might.
B
You
know
highly
used
highly
distributed
example
from
microsoft
of
using
that,
and
that's
that
can
be
an
issue.
I
can
totally
understand
why
folks
would
want
to
see
that
type
of
thing,
and
so
we
are,
we
hope,
to
share
more
details
about
how
we've
been
able
to
help
some
of
these
large
first
party
customers
move
their
things
to
dotnet
and
what
you
know
to.net
core
and
five,
and
then
what
how
those
things
will
help
other
folks.
So
that's
been
a
really
good
resource
that
we
have
now
as
well.
B
The
inner
loop
theme
is
a
big
theme.
This
year,
like
we
do
want
to
make
a
large
improvements
in
the
develo
in
the
developer,
experience
with
regards
to
performance-
and
that
includes
everything
you
know
like.
I
mentioned
everything
from
let's
just
make
like
the
command
line
faster
like
today
on
my
machine
here.
B
If
I
use
the
net
cli
to
build
a
console
app
after
it's
warm
like
after
I've
run
it
a
few
times
the
fastest,
it
can
build
a
hello
world
console
app
incrementally,
like
I've
already
built
it
once,
and
I'm
just
going
to
build
it
again
and
making
no
changes
is
over
a
second.
It
takes
over
a
second
to
do
that.
You
know
which
isn't
slow,
but
it's
not
particularly
fast.
Given
I
didn't
make
any
changes,
you've
already
built
it.
B
Why
can't
you
be
faster
than
that
and
if
it
was
cold,
if
I
hadn't
run
it
on
my
machine
or
already
or
if
I
wasn't
on
a
desktop,
if
I
was
on
a
laptop
or
I
was
on,
maybe
an
older
machine,
we
we
we're
getting
reports
and
we've
observed
and
we
see
outliers
where
it
doesn't
take.
You
know
one
second,
it
can
take
six
seconds
or
seven
seconds
and
if
you're
a
new
user
to
net
that
can
be
really
impactful
like
it's
like
okay.
Well,
you
know,
I
downloaded
the
sdk.
B
That
was
fairly
painless.
I'm
going
through
this
50
minute
tutorial
and
I
do
my
first,
you
know.netnew.net
run
and
it
seems
to
be
taking
a
really
long
time
before
I
see
the
hello
world
printout
and
if
I
was
to
do
the
same
thing
with
some
other
programming
stacks
and
sdks,
you
might
get
something
a
lot
faster.
Now,
there's
lots
of
mechanical
differences
as
to
why
that
is
you
know.
Python
and
javascript
are
interpreted,
there's
no
build
phase,
and
so
they
they
get
to
excel
in
other
areas.
A
B
You're
laughing
like
that
sounds
funny
right,
but
that's
not
too
far
away
from
some
of
the
ideas
that
have
been
discussed
because
we
need
to
find
how
can
we
smooth
out
that
arc,
and
sometimes
that
means
there's
only
so
far.
We
can
turn
the
crank
on
making
something
as
generic
and
flexible
as
the
ms
build
and.net
cli
build
system
and
the
runtime
and
all
the
rest
of
it.
It's
a
generalist.
B
B
B
B
You
know
we
wrote
it
in
c
hello,
maybe
not
that,
but
maybe
the
cli
could
have
a
stripped
down
mode.
That
automatically
is
engaged
for
certain
operations,
but
then
shims
through
passes
through
to
like
the
the
full
beans
one
when
you
do
need
to
do
something
that
utilizes
all
that
flexibility
we're
talking
about
that
type
of
stuff,
because
we
want
that
to
be
a
smooth
progression
and
the
other
advantage
of
that
type
of
design.
Is
you
can
start
building
out
over
time
what
you
build
into
the
optimize
thing
to
expand?
B
It's
it's.
It's
sort
of
footprint,
the
type
of
scenarios
it
covers,
based
on
feedback
based
on
what
people
are
doing,
because
it
doesn't
need
to
do
everything.
It
only
needs
to
do
the
things
that
people
do
a
lot,
and
it
turns
out
that,
if
you
were
to,
if
you
were
like
to
chart
out
all
the
different
operations
like
the
number
of
operations
that
people
do
and
then
how
many
people
do
those
things,
it
generally
doesn't
look
like
a
bell
curve.
B
B
And
we
made
that
very
clear.
I
think
we
over
the
last
couple
years
talking
about
what
the
new
release
cadence,
that
we
introduced
with
the
release
after
dot
net
core
31
when
we
started
talking
about
what's
going
to
happen
after
that
in
the
one.net
strategy,
and
it
was
slowed
down
a
bit
by
the
pandemic
and
we
we
kind
of
talked
about
that
at
build
this
year.
We
had
originally
planned
for
net
5
to
include
the
xamarin
workloads
by
default
and
that
didn't
eventuate
we
had
to.
We
had
to
postpone
some
of
that
work.
B
That
work
will
be
in
six
now,
so
the
net
cli
will
support.
You
know:
building
xamarin
applications.
We
we
did
get
some
stuff
done
for
xamarin,
though
in
five
for
the
core,
the
mono
run
time
using
the
core
framework,
so
the
bcl
from.net
core
on
the
mono
runtime,
as
opposed
to
mono's
framework.
That
did
happen
all
right.
So
now
they
share
the
bcl
between
the
the
workloads
that
use
mono,
which
are
the
xamarin
workloads
and
blazer
webassembly,
and
the
net
core
based
workloads.
B
They
all
share
the
same
bcl
now
so
that
would
happen,
but
in
six
we'll
we'll
continue
that
work
to
pull
them
into
the
tool
chain
as
well,
so
that
you
know
in
visual
studio,
you'll
use
the
same
project
system,
you'll
get
the
new
clean
cs,
proj
files
for
your
xamarin
apps
and
those
type
of
stuff
and
the
cli
will
support,
creating
and
building
those
as
well.
So
that,
as
I
said,
that
work
continues
so.
A
Well,
you
mentioned
projects,
one
of
the
cool
things
with
net5
is
the
dynamic
project
templates
and
those
kind
of
being
pulled
into
like
visual
studio?
Is
there?
Is
there
you
know
anything
being
tracked
like
from
the
high
level
theme
or
or
whatever,
as
taking
that
further,
like
more
look
at
how
the
project
system
works
for
pulling
in
you
know,
new
different
project
types.
B
B
We
still
had
the
you
know
the
one
asp.net
dialogue
where
you
would
do
file
new
asp.net
application,
and
then
you
get
your
a
different
screen,
which
we
built
using
the
visual
studio,
template
technology,
and
then
you
would
choose
a
bunch
of
stuff
and
then
that
would
then
go
and
run
the
templates
from
the
cli,
but
they
were
kind
of
was
like
a
hidden,
bookmarked
vs
or
what
we
call
a
breadcrumb.
It
called
a
breadcrumb
template,
that's
in
visual
studio,
so
that
it
shows
up
in
vs.
B
But
then
we
use
a
template
wizard
to
basically
invoke
the
one
in
the
cli,
so
that's
all
being
overhauled,
so
that
moving
forward
all
the
templates,
whether
they're
running
from
the
command
line
or
in
visual
studio,
are
effectively
based
on
the
cli
template
engine,
and
so
you
can
enable
this
now
in
the
latest
preview,
it's
behind
a
flag.
So
one
of
the
preview
flags
and
tools
options
you
can
have
all
the
cli
templates
show
up
in
the
visual
studio,
new
project,
dialog
or
npd,
as
we
call
it
internally.
B
Basically,
there's
a
template
manifest
json
file,
and
so
we
basically
sold
out
that
ui
in
real
time
rather
than
having
to
like
go
and
customize
and
build
forms
and
ship
them
every
time
we
want
to
build
a
feature
into
the
templates,
so
that's
been
a
very
long
goal
of
ours.
It's
taken
literally
years,
we've
talked
about
being
able
to
do
that
and
it's
finally
finally
finally
happening
which
I'm
very
happy
to
see
and
then
over
time.
B
Obviously
we'll
we'll
promote
that
and
enrich
that,
and
hopefully
there'll
be
a
rich
ecosystem
of
templates
and
we'll
obviously
need
to
look
at
adding
the
what
we
call
discovery
and
acquisition
the
discovery
and
acquisition
phases
of
that
into
vs.
Today
we
only
have
it
the
cli.
So
if
you
go
like
dot
net
new
foo
and
you
have
nothing
called
foo
well,
what
happens?
B
Is
there
an
experience
at
that
point
that
helps
you
find
discover
and
to
quite
install
acquire
a
template
that
could
satisfy
you
know
foo
today,
in
the
cli
there's
a
bit
of
there's
kind
of
a
rudimentary
kind
of
a
there
is
a
there
is
an
ac.
There
is
kind
of
an
experience,
but
it's
not
great,
and
so
we
have
an
index
file
that
gets
calculated
and
downloaded
by
the
cli
that
has
manually
sort
of
scoured
every
package
on
nuget
to
find
ones
that
contain
templates.
B
And
then,
when
you
run.net
new
foo
and
you
don't
find
anything
with
foo,
it
says:
oh,
is
it
in
my
index?
Oh
look
there.
It
does
seem
to
be
a
package
that
has
a
template
called
foo
in
it.
Let
me
print
an
error
message
that
says:
well,
you
don't.
I
didn't
find
one
locally,
but
maybe
this
nuget
package
is
one
that
you
would
want
and
then
it
can
help
discover
it
can
help.
You
know,
instruct
the
user
to
go
and
type
the
next
command.net
new
dash
I
for
install
to
get
that
package.
B
B
Yeah
we've
kind
of
limited
it,
we've
limited
it
limited
it's
utilization.
It's
experience
to
focus
on
the
templates
that
we
wanted
to
ship
for
our
primary
experience,
where
we
needed
to
do
things
like
have
a
template
for
aspirin
at
that
in
the
in
the
sdk
that
supports
the
latest
runtime,
but
also
you
can
you
can
create
an
app
that
is
targeting
the
previous
framework.
That's
lts,
because
generally
the
idea
with
vs
and
with
the
sdk
in
general,
is
you
have
one
version
installed.
You
have
the
latest
version
installed.
B
Vs
just
keeps
giving
you
the
latest
version
of
the
sdk
and
the
cli.
But
if
you
want
to
create
so
say,
that's
five
right.
You
want
to
create
a.net
core
31
template.
We
need
a
template
for
three
one:
it's
not
it's,
not
in
the
five
sdk
by
default,
it's
separate,
and
so
we
have
a
way
to
kind
of
discover
those
index
them
and
then,
if
you
run
the
dot
net
new
web
app
dash,
I
think
it's
r
for
runtime
and
then
you
pass
in
the
version.
3.1
it'll
go!
Oh
well.
B
I
have
a
template
called
web
app,
but
I
don't
have
one.
I
don't
have
a
variant
of
that.
That
takes
the
parameter
value,
3
1,
but
it's
in
this
package
so
go
and
install
that
right.
So
that's
how
that
mechanism
works
behind
the
scenes.
But
again
we
don't
have
that
in
vs
for
like
on-the-fly
discovery,
but
we
do
plan
on
doing
that
and
so
eventually,
hopefully,
for
the
wider
ecosystem.
What
you'll
be
able
to
do
is
create
a
template
package.
B
That's
based
on
the
cli,
publish
it
to
nuget
and
then
naturally,
everyone's
machines,
whether
they're
running
the
cli
vs
vs
for
mac,
will
you
know
people
will
be
able
to
discover
that
either
by
you
know,
having
some
type
of
I
searched
in
a
search
term
in
visual
studio,
I
didn't
find
it
locally,
but
then
there's
a
one
click
to
go
and
find
that
on
on
nougat
or
perhaps
it
was
pre-indexed
and
when
you
typed
it
didn't
find
it
locally.
It
suggested
it
to.
B
B
I
think
right
like
if
I
do
that,
I
can't
do
anything
with
it,
but
in
vs
item
templates
are
a
separate
concept
and
the
the
project
system
can
limit
when
an
item
template
shows
up
in
a
particular
project,
or
particularly
even
a
particular
folder.
In
a
project
like
we
can
customize
all
that
type
of
stuff.
We
don't
have
any
of
that
in
the
cli.
B
Currently,
I
don't
think
it's
in
the
preview
that
we
have
right
now,
it's
just
the
project
templates
and
the
new
project
dialogue
that
are
in
there
right
now,
but
eventually
that
is
the
goal
that
you
just
be
able
to
for
net,
at
least
or
for
templates
using
one
system
and
have
them
show
up
everywhere
that
they
make
sense
whether
it's
the
cli
visual
studio,
visual
studio
for
mac.
You
know
some
code
spaces
thing
whatever
it
is
like
you
would.
A
B
B
I
you
know
package
name
and
then
you
can
pass
another
parameter,
which
is
the
feed
with
regards
to
a
like
one
of
this
more
smooth
discovery
and
acquisition
experience
where
you
try
and
you
know,
use
a
template
that
doesn't
exist
and
then
it
suggests
one
to
you,
because
it's
indexed
while
we're
wearing
an
index
and
you
get
the
all
by
default.
Obviously,
so
that's
perfectly
reasonable
to
ask.
B
Well
how
would
I
add
a
private
feed
to
that
experience
and
I
imagine
in
visual
studio
that
would
be
fairly
straightforward
process
to
do
so
and
at
the
command
line.
Maybe
it's
a
similar
thing.
You
can
run
a
command,
it
adds
it
to
the
to
the
template
feed
by
default
and
then
from
that
point
forward
you
could
it
could
you
know
index
it
and
install
from
there,
but
we.
B
A
B
A
B
A
B
Development
we
could
run
without
compiling
like
an
interpreted
language
yeah.
So
it's
actually
interesting.
You
say
that
obviously
there's
a
lot
of
the
way.net
works
right
is
that
the
il
is
what
the
runtime
understands,
the
intermediate
language
and
you
generally
author,
in
a
different
language.
You
know
most
people
use
c
sharp,
and
so
you
need
to
build
the
c
sharp
run
it
through
the
c
compiler
to
get
il,
and
then
that
gives
you
an
assembly
and
then
the
runtime
loads
that
il
and
then
it
can't
execute
it
by
default.
B
It
has
to
compile
it
down
to
to
assembly,
and
it
does
that
using
the
just
in
time
compiler,
which
is
inside
the
runtime.
It's
a
jit
runtime
right
now,
mono
has
an
interpreter.
The
blazer
webassembly
actually
uses
an
il
interpreter
in
the
browser
to
execute
your
code
and
in
fact,
corcialia
or
ryujit
has
one
now
as
well,
but
it's
still
very
much
in
the
early
days,
and
so
we
introduced
tiered
compilation
in
the
jet.
B
B
It's
not
necessarily
the
jitting
of
the
il
in
the
app
that
is
taking
the
most
time
considering
the
delta.
It's
just
that.
There's
no
intermediate
today,
like
there's
no
difference
between
you
running
the
app
for
the
first
time
for
all
the
code,
and
I
changed
one
line
of
c
sharp
or
a
single
html
attribute
in
a
razor
file.
There's
no
difference
between
those
two
like
you'd
run
through
the
full
build
pipeline,
so
we
can
get
massive
gains
just
by
looking
at
or
introducing
some
more
complexity.
B
With
regards
to
how
much
of
that
pipeline
do
we
run
given
a
particular
type
of
edit
that
occurred
between
the
last
time
that
we
kind
of
refreshed
the
application?
And
you
know
people
will
be
familiar
with
this
in
dotnet
previously
we
have
this
edit
and
continue
feature,
which
was
kind
of
you
know.
Much
better
supported
in
the
existing.net
framework,
with
visual
studio
and
we'd
have
a
little
more
limited
support
for
it.
In
the
newer
frameworks,
like
you
know,
xamarin
has
no
support
for
it,
but
they're.
B
Currently
we
demoed
it
at
build
this
year
under
the
name
of
c-sharp
hot
reload,
and
we
continue
and
we
we
plan
to
continue
that
investment
and
hopefully
get
that
out
to
customers
in
the
near
future.
Razer
cs
html
and
razer
files
for
blazer
don't
have
any
support
for
edit
and
continues.
So
if
you
are
using
vs
and
you
launch
under
the
debugger
and
make
a
code
change
in
those
files,
you
have
to
shut
down
the
debugger
recompile
and
launch
again
to
see
those
changes.
B
Your
cs
files
that
does
work
for
within
the
limitations
of
what
edit
continue
supports,
and
so
we
are
looking
at
potentially
you
know,
adding
support
for
those
things
and
refreshing
the
whole
edit
and
continue
loop,
like
don't
even
think
of
the
feature
called
edit
continue.
Just
think
of
the
loop
of
like
I've
got
I'm
running
got
my
application
running,
the
debugger
may
be
attached.
Maybe
it's
not,
and
then
I
made
it.
I
made
a
c-sharp
change
and
I
want
to
get
that
change
or
razor
change.
B
I
want
to
get
that
change
into
my
app.
What
can
I
do
to
make
that
happen
fast
like
today?
Would
then
continue?
You
have
to
have
gone
through
very
specific
steps
to
have
that
be
successfully
deployed,
we're
looking
at
ways.
We
can
just
make
that
smoother
right,
and
so
we
could
just
say
hey.
Maybe
we
can
just
attach
on
demand.
B
Maybe
we
know
what
processes
your
application,
so,
even
if
you
didn't
launch
with
the
debugger
attach,
because
that's
slower,
maybe
there's
a
single
button
and
we
just
attach
to
it
and
we
deploy
any
changes
that
you've
made
since
you
launched
the
application,
assuming
those
changes
are
compatible
with
the
limitations
of
sort
of
the
c-sharp
reload
experience
or
the
edit
continue
experience,
and
that
would
make
it.
You
know
a
lot
faster.
The
ux
is
better,
so
we're
looking
at
all
those
types
of
ideas
to
kind
of
improve
that
experience.
A
B
They'll
shall
not
use
this
crypto
code.
You
can
only
use
this
crypto
code,
for
example,
and
one
of
the
fallouts
from
that
was
some
changes
with
the
crypto
code
when
running
in
blazer
webassembly.
Now
my
understanding
is,
we
were
able
to
fix,
get
a
bit
of
that
back,
our
tuck.
You
might
you
probably
know
the
answer
to
this
better.
I
think
we
made
a
change
in
one
of
the
previews
for
dot
net
five,
and
then
we
were
able
to
get
a
couple
of
the
methods
back
and
working
again.
It
was.
D
B
Question
might
specifically
maybe
be
about
the
the
browser
there
is
actually
web
crypto
apis
now
in
modern
browsers,
but
we
don't
expose
those
in
blazer
web
assembly
and
we
don't
map
those
to
the
built-in
crypto
feed
types
in
the
net
bcl
and
that's
where
my
knowledge
ends
and
I
wouldn't
even
attempt
to
try
and
make
any
smart
comment
or
reasonable
comment
about
that.
So
it's
a
security
is
an
area
where
it's
just
like
yeah
I'll.
Let
the
experts
stop.
A
Cool,
let
me
see
nothing
else
really
coming
up
in
the
chat.
I
don't
know
if
there's
any
specifics,
you
want
to
talk
about
more
like
so.
Our
talk
earlier
was
sharing
the
the
kind
of
tool
on
the
roadmap
in
general.
I
don't
know
if
there's
anything
specific
because
part
of
the
goal
dan
talked
about
is
we
want
people
to
engage
more
and
help
us.
You
know
like
go
through
and
upload
and-
and
you
know
talk
about
stuff-
is
there
anything
else
we
want
to
share
out
on
that?
That's
fine,
if
not.
D
I
will
just
reiterate
the
same:
ask
like
please:
go
ahead,
engage
and
upload
the
issues
you
will
you
like
and
download
issues
you
don't
like
and
put
the
right
reasons
for
each
one
of
these,
because
we
read
these
comments.
We
not
always
reply
because
we
just
trying
to
save
time
really,
but
we
read
all
the
comments,
so
please
do
so
and
that
will
help
us.
We
stop
and
six
planning
a
lot.
A
D
Very
good
question,
john,
so
I
I
ended
up
slightly
modifying
it
tweaking
the
the
content,
the
description
of
this
issue
with
the
warning
sign,
because
I
realized
many
people
have
been
just
posting
comments
about
what
they
like.
So
the
ask
here
is
just
file
issues.
If
you
can't
find
an
existing
issue
for
what
you
need
file
a
new
new
issue,
so
we
can
easily
track
it
and
it
won't
get
lost.
A
D
A
C
D
A
This
is
we've
talked
about
this
page
in
the
past
damian
there's
some
really
good
information
here,
and
this
like
gives
you
all
the
you
can
get
the
installers
the
binaries.
It
gives
a
lot
of
information
about.
You
know
what
level,
if
it's
an
rc,
if
it's
preview,
all
that
kind
of
stuff,
yep,
of
course,
for
the
5.0.
That's
what
you're
going
to
see.
The
thing
I
want
to
point
out
that
is
awesome.
A
Is
this
right
here
at
the
bottom,
so
we've
been
dog
fooding
on
dot
net
5
like
since
early
on,
we
always
jump
into
the
early,
so
the
the
site.
My
understanding
from
talking
to
myra
is
there
were
some
things
that
were
3-1,
some
that
were
five
and
basically
now
it's
all
five,
which
is
pretty
cool
so,
like
this
site
gets
millions
of
hits
like
you
know
in
a
month,
and
so
it's
getting
pretty
good
usage
there.
So
I
think
I
think,
that's
really
cool.
B
Yeah,
it's
great
that
we're
running
it
on
the
the
big
public
site.
I
run
it
on
a
couple
of
internal
sites
and
I
update
it
with
every
preview.
I
know
handsome
and
he's
running
lts
on
his
site.
He's
running
he's
just
moved
his
blog
handsome
minutes
and
his
main
site
over
to
dot
net
core.
Finally,
it's
been
a
long
process
for
him,
but
he's
running
lts
and
he'll
need
to
keep
that
up
to
date,
obviously
with
the
latest
lts
patch,
because
we
we
release
every
month.
Someone
did
ask
about.
B
Someone
asked
about:
will
there
be
releases
between
net
five
and
net
six,
and
now
the
sdk
generally
releases
every
month,
the
cli,
so
the
net
five
or
the.net
cli
sdk
will
continue
to
release
every
month
and
then
the
we
generally
every
month
have
a
servicing
round
right.
So
there
are
generally
patches
every
patch,
tuesday,
the
standard,
microsoft
patch
tuesday.
There
will
be
security,
fixes
and
other
critical
fixes
for
reliability,
sometimes
performance,
behavior
correction.
B
That
will
happen
every
month
and
then
the
sdk
has
what
they
call
feature:
bands
where
we
have
to
update
parts
of
the
sdk
that
align
with
things
that
also
ship
in
visual
studio.
Typically,
like
new
get
ms
build
the
c
sharp
compiler,
those
type
of
things
they
continue
to
rev,
like
they
add
features
as
part
of
the
visual
studio
release
train,
which
is
pretty
much.
You
know
three
to
four
feature
releases
a
year,
and
so
we
have
to
do
updates
there
as
well.
B
Six,
we're
not
currently
planning
any
we're,
not
planning
any
one
release
this
time
around
we're
very
much
focused
on
trying
to
get
down
to
this
nice
predictable
cadence
of
every
year.
We
have
a
feature
release.
We
alternate
between
a
current
release,
which
has
a
whole
bunch
of
new
features
and
an
lts
release
which
will
have
some
new
features,
but
is
more
focused
on
establishing
a
great
baseline
for
our
three-year
support,
and
then
there's
enough
overlap
to
give
folks
time
to
plan
and
migrate
off.
B
If
you
just
want
to
stay,
if
you,
if
you
can,
if
you're
working
on
the
type
of
things
that
can
stay
current
and
you're,
you
are
set
up
to
be
able
to
deploy,
updates
to
the
framework
regularly,
not
just
servicing
changes,
but
you
know
feature
changes
with
potentially
a
little
bit
of
work.
You
have
to
do
then
just
stay
on
current,
like
you
get
a
full
year,
a
bit
more
actually
for
the
current
release,
because
it's
a
three
month
overlap.
B
So
if
you
go
from
dot
net
core
31
to
net
five,
when
it
comes
out
in
november,
you'll
get
that
will
be
supported
fully
all
the
way
through
the
three
months
after
dot
net
six
comes
out
which
will
be
november
next
year.
So
that
means
february
2022
and
then
as.net
six
is
developing
we're
doing
the
monthly
previews
there'll
be
a
release
candidate.
You
know
mid
to
late
next
year.
B
D
B
You're
set
up
to
be
able
to
react
and
deploy
that
quickly.
Then
I
strongly
encourage
folks
to
go
at
the
leading
edge,
basically
on
the
current
release.
If,
if
you
need
more
time-
and
you
want
to
make
sure
that
you
can
have
apps
and
frameworks
be
supported
without
you
having
to
deploy
a
new
version
every
year
and
when
I
say
a
new
version,
a
new
version
that
may
include
some
something
beyond
a
fully
compatible
upgrade
then
stay
on
lts.
B
A
A
You
know
you
still
need
if
you,
if
support's
important,
you
got
to
install
those
monthly
patches,
and
so
then,
at
that
point
you
know,
because
I've
seen
some
discussions
on
twitter
and
people
saying
hey,
I'm
not
going
to
sell
until
there's
an
lts,
because
you
know
it's
it's
and-
and
my
understanding
too
is
the
goal
that
it's
supposed
to
be
very
quick
and
easy
upgrade
between
five
and
six,
like
the
goal
is
to
minimize
those
breaking
changes
as
much
as
possible.
So
I
understand
that
the.
B
B
This
is
the
fourth
release,
and
the
goal
moving
forward
is
to
make
it
as
easy
as
possible
for
people
to
stay
current,
so
yeah
move
from
yeah,
and
this
starts
with
three
point
one
to
five,
like
the
list
of
breaking
changes
for
aspirin
net
call
between
three
one
to
five
may
look
long
but
go,
and
I
encourage
you
to
actually
read
the
list
and
look
at
the
details.
I
think
you'll
find
that
you'd
be
very
hard-pressed
to
be
hit
by
you
know
more
than
one.
B
If
any
of
those
changes
most
of
the
breaking
changes
in
there
are
very,
very
narrow
cases.
Most
applications
will
find
it's
very
easy
to
move
from
net
core
3.1
to.net
5,
whether
they're
your
winforms
app
a
wpf
app
or
an
asp.net
core
app.
That
move
is
pretty
straightforward.
Laser,
obviously,
is
the
newest
thing.
So
if
you
started
on
blazer
webassembly
or
blazer
server
in
3.1,
3.2
and
you're
moving
to
five,
there
might
be
a
couple
of
especially
because
it's
changed
its
space
underneath
it.
B
A
Cool
I
just
wanted
to
share
this.
I
believe
this
page
just
got
a
major
update,
and
so
this
is
the
support
policy,
because
people
ask-
and
it's
important-
you
know
they
want
to
see
the
exact
dates
they
want
to
have
it
clearly
explained,
and
so
so
they
just
shipped
this,
and
the
way
that
I
got
to
this
page
was
off
of
the
what
is
asp.net
core
and
then
there's
a
link
over
here
to
this
support
policy.
A
I'm
sure,
if
you
just
search
for
net
core
support
policy
that
would
come
up,
but
so
also
good,
all
right.
Well,
we
have
been
we're
kind
of
at
time.
We've
we've
covered
a
lot
of
great
information
thanks
our
tech.
It
was
great
to
have
you
on
and
and
explain
you
know
how
you're
doing
the
planning
and
and
then,
if
you're
watching
you
know
like
please
get
involved
sure
you
know
file
those
issues.
A
Vote
things
up,
it's
it's
cool
to
see
how
that
goes
directly
into
the
team's
planning
and
now
is
that
time
too
right.
This
is
the
gate.
This
is
five
is
kind
of
locked
down.
Six
is
the
hey.
You
can
really
kind
of
dream
big
or
you
can
really
prioritize,
and
so
now
is
the
the
the
sweet
spot
of
when
you
can
get
that
information.
You
know,
get
get
your
votes
in.
B
And
we
know
it's
asking
a
lot
like
there's
a
there's,
a
new
release
coming
and
so
a
lot
of
people
will
be
thinking
about
that
and
spending
time
on
that
and
trying
out
those
new
features
or
thinking
about
that.
But
you
know
obviously
we're
starting,
like
you
said
we're
planning
the
release
after
that,
and
so
yeah
put
really
really
does
help,
and
we
do
appreciate
it
when
people
do
that.