►
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-09-10
A
It's
a
throwback
to
maybe
our
first
four
years
there
it
is,
we
are
live,
I
know
for
sure.
We
live
because
I
just
showed
up
so
much
for
the
automatic
introduction.
Now
it
should
be.
A
dramatic
zoom
in
I
need
to
figure
out
how
to
change
it
manually.
So
I
can
see
you
they
see
now
you're
on
the
screen,
but
I
need
to
do
the
picture-in-picture
thing.
Oh,
oh,
what's
this
one
is
the
name
no
no
picture
make.
B
B
A
C
C
A
C
B
A
C
A
A
Five
years
ago
we
were
doing
DNX,
so
we
had
announced
it
was
fairly
obvious.
We
were
rebooting,
we
were
rebooting,
like.net
well,
I
mean
honestly.
At
that
time
it
was
the
asp
net
team.
We
were
in
different
organizations,
so
ESP
net
was
in
the
azure
org
and.net
was
in
debited,
and
the
a
spinet
team
had
wanted
to
modernize
their
stack
in
order
to
compete
with
the
young
web
upstarts
like
nodejs
and
the
more
dynamic
things,
and
also.
A
To
decouple
ourselves
from
the
windows
train
we
wanted,
we
knew
we
had
to
kind
of
go
across
plateau
at
least
support
that
technically.
In
order
to
be
competitive,
and
so
we
started
this
effort.
We
were
using
mono
originally
to
prove
that
we
could
do
non
is
hosted
a
new
web
model
and
we
had
that
project
Jason
thing
which
I'm
sure
folks
have
been
with
us,
the
whole
time
or
remember,
and
then,
as
is
inevitable,
when
you
start
something
radical
and
we
did
it
on
github
like
run
right,
it
was
super
early
and
super
public.
A
There
was
quite
a
lot
of
fun.
There
was
a
lot
of
people
who
thought
they
knew
or
they
had
heard
things
and
they
would
go
on
podcast
and
talk
about
things
that
were
planned
to
happen
and
what's
gonna
be,
what's
what's
gonna
mean,
and
you
know,
I
was
the
program
manager
for
it
at
the
time
and
I
was
it
was
concerned.
B
A
Was
like
well,
this
is
misinformation.
This
is
we
kind
of
need
to.
We
need
to
own
this
message
a
bit
better
while
we're
developing,
so
we
can
explain,
have
a
channel
to
directly
with
the
community
to
talk
about.
What's
going
on
and
so
I
pitched
this
idea
of
hey,
why
don't
we
do
a
weekly
community
stand
up
an
idea
between
code-behind
calling
a
stand
up
was
that
we
wanted
to
keep
it
quick?
A
Like
in
the
beginning,
we
would
always
have
a
whiteboard
in
the
background
and
we
would
be
diagramming
the
things
as
we
were
working
on
them
and
we
would
explain
all
the
new
concepts
that
we
were
doing
using
white
boards
and
lines
and
boxes.
You
might
remember,
their
early
shows
Lou
and
Fowler,
and
myself
and
we'd
be
talking
about.
You
know
diagramming
things,
and
then
we
people
would
ask
questions.
We'd
have
a
lot
of
you
know.
A
People
asking
questions
and
I
would
answer
them,
often
interactively
and
just
try
and
make
sure
that
everyone
understood
where
we
were
and
because
we
were
doing
things
so
rapidly
at
that
point,
because
it
was
literally
all
it
was
brand
new
every
week
it
was
like
this
is
what
we've
done
in
the
last
week.
These
are
the
decisions
we've
made.
This
is
what's
gonna
change.
This
is
what
we
want.
Feedback
on.
You
know
we're
up
to
preview,
14
or
whatever
it
might
be,
and
then
of
course,
the
whole
project.
A
B
B
A
B
You
know
I
I,
do
love
that
about
this.
It's
been,
you
know
like
not
just
not
just
showing
off
what's
going
on,
but
also
taking
live
questions,
and
then
people
would
say,
hey
I'm,
having
trouble
with
this
and
that's
kind
of
shaped.
You
know
that
it's
been
a
community
project
from
the
like
as
part
of
its
not
just
throwing
it
up
on
github,
but
it's
also
like
interacting
with
the
community
as
it's
being
built.
A
A
C
A
A
Two
more
dead
teams,
even
after
the
first,
what
I'm,
gonna
say
two
years
of
the
show
of
us
doing
the
show
we
had
other
teams
in
Microsoft
coming
to
us
saying
we
see
what
you're
doing
with
the
show
and
we
want
to
emulate
that
or
you
know,
product
X
product
Y
and
those
shows
are
still
going
like
I
know
that
there
are
shows
and
different
boards
I.
Don't
I,
don't
know
if
they
run
out
of
the
studio,
because
this
studio
didn't
exist
right.
A
B
C
B
A
A
A
C
A
I
do
hope
people
appreciate
this
I
ran
out
at
lunchtime
to
the
party
store
and
I
just
grabbed
every
purple
thing
with
the
letter
number
five
on
it
that
I
could
and
then
we
very
hardly
put
it
together
before
we
started
today
because
I
said
ñ,
including
snacks,
because
it's
very
important
at
a
party
when
you're
celebrating
a
snack
we've
lost,
Scott
I,
don't
know
where
he's
gone.
Maybe.
A
B
B
B
Excellent
okay,
well,
a
common
theme
over
these
shows,
especially
over
the
past
few
years,
is
ban
and
Andrew
Locke,
and
so
I've
actually
got
two
from
him
today.
So
one
is
looking
at
the
new
project
file
program,
CSS
and
generic
host,
and
so
this
is
part
of
a
series-
and
here
he's
looking
at
you
know,
what's
new
in
dotnet
core
3
and
some
of
this
I,
like
you
know,
some
of
this
has
been
touched
on.
B
You
know,
and
sometimes
multiple
times
over
the
community
stand
ups
and
the
demos
and
stuff
you've
shown
off
here,
he's
kind
of
rolling
it
up.
You
know
in
a
nice
way,
kind
of
I
don't
know
putting
it
all
together.
So
talking
about
the
project
file
and
changes
a
shared
framework
and
I,
you
know
honestly
I
held
up
on
on
showing
this
one
off
before
this
one
he
actually
published
in
August
and
I,
didn't
know
if
you
had
any
thoughts
or
anything
you
would
want
to
highlight
as
part
of
this,
but
so
he's.
B
You
know
he's
talked
about
this
he's
talked
later
on
in
here
talking
about
changes
to
program
CS
and
especially
looking
at
the
move
to
run
on
generic
host.
So
looking
at
what's
in
generic
host
and
generic
host
builder,
so
what's
in
what's
involved
there?
Oh
so
then
yeah
and
then
I
always
like
Andrew
always
does
these
nice
kind
of
wrap
ups
at
the
end,
like
I
showed
you
a
bunch
of
stuff
here's
you
know,
here's
the
summary
I
thought.
B
A
A
A
A
B
Just
usually
go
with
Devo
for
parties,
but
I
mean
whatever
works
for
you,
so
ok,
another
from
Andrea
in
here.
This
is
part
2
and
he's
looking
comparing
startup
CS
in
the
asp
net
choreo
templates.
So
this
is
not
comparing
2
or
2
1
or
were
to
2
to
3
o.
Instead,
this
is
looking
at
3
o
and
looking
at
the
different
templates
that
are
available.
So,
first
of
all
the
empty
template
got.
You
know
completely
empty.
A
B
Razor
pages,
that
kind
of
stuff
right
so
yeah
and
then
summary
I
always
like
this.
You
know
it's
very
easy
to
just
go
file
new
project
and
say:
oh
there's,
some
magic
stuff
here.
I
do
like
this
kind
of
digging
into
here's.
What's
different,
here's
you
know,
and
you
could
always
go
through
and
build
up
like
if
you
start
it
with
an
empty
and
you
wanted
to
add
in
stuff
to
host
an
API.
You
could
do
that
absolutely.
A
A
B
A
A
That's
not,
we
don't
have
the
button.
The
stream
decks,
not
working
so
I'm,
literally
in
OBS
and
I'm,
looking
at
all
the
screen
names
and
there's
one
called
P
IP,
but
that
is
a
black
screen
with
me
in
the
bottom
corner,
which
everyone
is
looking
at
right
now
and
P
IP
with
guest,
which
is
both
of
us
in
the
bottom
right
hand,
corner
with
a
big
black
screen,
and
then
there
is
nothing
that
I
can
see
that
looks
like
it
would
be.
I.
A
Do
that
yeah
yeah,
so
so
in
1x,
you
had
to
kind
of
like
call
all
these
micro
methods
to
get
everything
set
up,
and
the
templates
in
1x
were
quite
large
because
to
get
what
we
would
term
an
idiomatic,
a
spinet
core,
app
with
configuration
setup,
the
way
we
would
recommend-
or
we
would
expect
and
logging
setup
the
way
you
would
recommend
and
expect
and
the
the
standard
middleware
that
you
would
need
for
most
reasonable
apps.
You
needed
quite
a
lot
of
code
and
a
lot
of
those
things
were
in
different
packages
too.
A
Most
folks
just
want
to
be
able
to
have
just
give
me
what
you'll
normally
want
like
iam,
what
you
think
most
apps
will
have
as
a
default
set
of
like
a
one-one
line
method
essentially,
and
then,
if
I
need
to
deconstruct
that
and
pull
things
out,
you
can
write,
you
can
always
go
back
to
doing
it
manually.
So
that
was
a
quite
a
big
change
between
1
&
2,
but
the
empty.
A
A
So
I
mean
you,
go
get
the
source
code
to
do
that
or
which
is
pretty
easy
to
do
for
that
later.
Web
host
default
create
default
builder
or
host
crate
builder,
as
it
is
now,
but
the
thing
I
was
going
to
point
out
was
that
the
reason
there
is
a
cost,
in
fact
we're
doing
a
whole
bunch
of
startup
time.
Analysis
right
now
is
part
of
very
early
dotnet
5
work
for
a
certain
age,
Minette
core
scenarios,
and
it
is
evident
that,
like
setting
up
the
default
logging
providers,
the
default
configuration
sources.
A
The
console
provider
is
a
logging
output.
It's
set
to
yo
HTTP
is
on
by
default
in
our
default
host,
with
all
the
change
we
made
into
one
all
those
things
have
a
cost
in
terms
of
startup
time,
and
we
think
it's
you
know
when
I
say
it's
significant
the
whole
startup
time
for
the
app
that
we're
testing
is
under
400
milliseconds
from
the
time
you
start
the
process
say
please
go
to
when
the
first
request
has
finished.
A
Ok,
we
would
like
to
get
that
down
to
at
least
half
that,
and
we
think
at
the
moment
our
best
lead
from
the
early
looking
is
that
quite
a
lot
of
that
time
is
actually
not
in
MVC
or
di.
It's
actually
setting
up
all
those
default
providers
for
things
like
config
and
login,
etc,
etc,
and
so
we're
gonna
go
off
and
do
a
bunch
of
investigation
to
figure
out
if
it
is
those
things
and
if
it
is,
what
can
we
do
to
optimize
them,
etc,
etc.
So
it
is
just
worth
highlighting.
A
Yes,
there
is
a
cost
of
doing
those
things.
We
were
big
about
pay-as-you-go
5
years
ago,
and
that's
why
things
look
that
way.
We
met
people
in
the
middle,
so
here's
a
default.
It
does
these
things,
you
get
them
by
default
in
every
single
app
and
you
may
have
to
pay
a
couple
hundred
second,
a
couple
of
hundred
milliseconds
of
startup
time
in
order
to
get
those
things,
but
it
doesn't
mean
we're
not
going
to
continue
trying
to
make
the
process
go.
B
B
I
was
working
on
the.net
Comet
a
bit
lately
and,
and
it
has
some
back-end
services-
and
it's
just
so
helpful-
to
dig
through
and
be
like
wait
a
minute.
What's
still
calling
that
service,
we
actually
had
a
staged
version
of
the
site
that
was
calling
an
API
too
much
and
I
was
troubleshooting
it
and
it
was
the
way
I
found.
It
was
with
application.
Insights,
it's
great
and
then
here
talking
about
you
know,
costs
of
logging.
You
know
it
does
have
some
overhead
and
so
then
wrapping
up
with
some
possible
solutions.
B
You
know
only
log
certain
environments
or
only
log
certain
percentages
and
then
what
he
wraps
up
with
here
is
also
there's
a
possibility
of
only
log
for
certain
flows.
So
when
something
happens
then
you
start
logging,
so
yeah.
What
a
good
idea
and
we've
had
some
some
things
to
be
featured
on
here
too
lately
like
there,
there
are
browser
shortcuts.
All
right,
I
mean
excuse
me,
browsers,
are
standards
and
things
where
you
can
flow
logging
through
the
entire
system,
which
is
nice
too
right.
B
So
you
can
have
correlation
that
flows
through,
which
is
nice,
yep,
yep,
all
right,
the
next,
so
Phillip
logging
or
blogging
about
dynamic
controller
routing
in
asp
net
core
three.
Oh,
this
is
something
like
for
many
years
with
with
routing
it's
always
like
I
wish.
I
could
do
that.
So
here
he
talks
about.
You
know
traditional
where
you
have
manually
declared
routes,
and
you
know
the
the
the
options
you've
had
in
the
past
and
then
he's
talking
here
about
endpoint
routing
and
the
ability
to
do
something
in
this
case.
B
B
Yep
all
right
Jeremy
talking
about
healthcheck
endpoints
in
MVC
project,
so
this
is
kind
of
a
survey,
the
different
things
in
in
health
checks.
Looking
at
you
know,
starting
with
basics
of
setting
up
health
checks,
then
he
does
point
out
the.
What
is
his
Abril?
The
here
he's
talking
about.
You
know
what
you
can
figure
for
your
health
checks.
He
talks
about
the
dashboard,
and
this
is
kind
of
neat.
The
ability
also
that
you
can
put
in
custom,
CM,
CSS
and
customize.
It.
C
A
C
C
B
Then
he
also
talks
about
hooking
in
with
a
pin
sites
which
is
kinda
neat,
and
you
know
that
you
can
have
you,
can
you
see
it
a
pin
sites
publisher
and
you
can
integrate
more
deeply
than
within
a
pin
sites?
You
can
also
drill
down,
and
you
can
say,
I
would
like
to
you
know,
see
cific
things
from
health
checks.
So
here
he's
looking
at
the
is
peanut
core
health
check
status
metric
and
then
it
stops
here
in
this
post.
B
A
B
C
B
So
here
he
talks
about
this
is
the
kind
of
bullet
points
of
what
he
does.
You
know
floats
a
zip
unzips
it
into
an
upgrade
folder.
Then
he
actually
restarts
the
app.
So
he
does
an
API
call
to
shut
down
the
site
and
then
once
it
does
set
every
time
the
app
starts
up.
It
looks
in
this
folder
for
specific
file.
If
it
sees
that,
then
it
loads
that
new
code-
and
he
goes
into
more
depth
about
how
the
actual
loading
and
stuff
happens-
it's
pretty
cool.
So
anyhow,
it's
it's
neat.
B
I,
don't
know
like
you
said:
you'd
want
to
make
sure
all
your
security
and
all
that
stuff
is
sad,
I
mean.
Obviously
it
could
work
better.
You
know
also
and
like
a
I,
don't
know,
enterprise
snare
intranet
or
whatever
yeah
stuff.
Oh
all,
right.
This
is
a
walkthrough
from
Canon
on
building
a
credit
application,
pretty
straightforward
here
he
goes
through.
He
does
what
I
do
like
about.
This
is
it's.
You
know.
It
includes
all
the
stuff:
here's
how
you're
gonna,
run
your
sequel
scripts
and
and
create
your
database.
B
He
has
you
created
an
inventory
database,
go
through
and
scaffold
out
an
application,
and
then
you
know
I'll
just
kind
of
skip
you
through,
but
basically
it's
an
inventory
management.
So
this
is
a
great
kind
of
getting
started.
Walkthrough
straightforward
I
have
to
keep
flagging
Eckhoff
coming
up
very
soon.
We've
got
all
the
we
now
have
the
agenda
published.
So
you
know
day
one
with
all
the
keynotes
and
all
this
showing
off
the
new
stuff
day,
2
as
well
kind
of
some
deeper
dives
and
then
day
3
is
24
hours
around
the
world.
B
C
Gonna
be
a
lot
of
stuff
going
on
we're.
Gonna
have
multiple
days
of
content
and
we're
also
going
to
have
many
many
many
many
hours
of
additional
content
that
is
separate
from
this
that'll
be
more
like
training
content.
That'll,
get
you
up
to
speed
on
dotnet
core
3.0
cuz.
The
launch
happens
at
this
time
and
having
having
enough
like
how
do
where
do
I
even
start
content
will
have
you
covered
as
well.
B
I,
don't
want
to
use
up
all
our
time,
it's
okay,
so
the
visual
studio
terminal
dropped
today.
Obviously,
as
a
web,
dev
I
use
the
terminal
quite
a
bit.
So
this
is.
This
is
really
cool.
This
is
developer
PowerShell
built
into
you,
Visual
Studio,
you
go
into
you
enable
it
in
the
in
the
latest
previews
you
go
experimental,
yes
terminal
and
it
just
turned.
On
so
that's
hand.
Let.
C
Me
actually
go
even
farther
if
I
may,
there's
there's
two
things
there
that
were
conflated
so
first,
the
terminal
is
actually
sharing
code
with
the
windows
open
source
terminal,
which
is
really
cool.
There
was
a
terminal
back
there
in
the
back
in
the
day
called
Wack
Wack
terminal.
We
search
for
the
word
wack
that
would
use
node
and
X
term
Jas.
This
one
is
actually
using
and
that's
it
that
will
give
you
the
terminal
inside
of
Visual
Studio
2017.
C
This
terminal
here
is
actually
sharing
code,
with
the
visual
studio
with
the
windows
open
source
terminal,
and
then
you
also
said
the
developer
command
prompt,
if
you
wouldn't
mind
down
scrolling
down
just
a
smidge
so
right
there
there's
the
developer
command
prompt
right
now.
If
everyone
who's
watching
the
show
just
hits
the
Start
menu
intention
developer,
you
should
see
developer
command,
prompt
if
you
have
Visual
Studio,
2019,
updated,
you'll,
see,
developer
command,
prompt
and
developer
PowerShell,
and
that
one
has
the
vs
dev
CMD
path
setup.
C
So
if
you
ever
wanted
to
have
multiple
side
by
side,
visual
studios,
what
you
do
now
now,
you
can
have
multiple
side
by
side.
Developer
command
prompts
your
choice
of
both
PowerShell
and
Doss,
and
then
you
can
go
and
type
msbuild
and
it'll.
Just
work
and
you've
got
all
of
your
paths
exactly
right.
That's
something
that
we
should
have
done
a
long
long
time
ago,
and
then
you
can
tweak
them
to
write.
If
you
want
I
mean
because
this
uses.
C
C
C
B
A
A
A
A
C
C
C
B
A
I
put
myself
back
on
with
you
to
wonderful
people.
Oh
you've
swap
positions.
Scott
was
on
the
left
before
and
John
was
on
the
right
and
now
John's
on
the
left
and
Scott's
on
the
right
when
you
weren't
looking,
which
hat
is
trippy?
Okay,
that's
cool!
So
so
yes,
preview,
9
was
out.
Was
it
last
week?
Yes,
okay,
so
I.
A
A
C
A
A
That
remember
a
few
weeks
ago,
I
said
we
weren't
able
to
do
another
preview
up
to
preview.
Now,
because
of
the
way
we
had
implemented
our
cember
to
versioning,
we
messed
up,
and
so
there
will
be
an
RC
one
release
next
week
as
I
as
I
understand
it.
That
was
the
case
two
days
ago
in
yesterday,
I
haven't
checked
today,
so
maybe
I'm
saying
things
that
are
phony,
but
my
understanding
is,
there
will
be
one
next
week.
A
B
A
My
god,
I
just
got
my
updated
to
preview
nine
you're,
not
gonna
break.
You
should
just
be
able
to
install
the
new
runtime
and,
yes,
you
can
you'll
be
fine.
It's
just
a
bunch
of
fixes.
Okay,
it's
just
a
whole
set
of
API
behavior
fixes
and
documentation,
attributes
and
all
the
time
all
the
other
photos
come
through
the
very
lovely
purple
on
someone's
lamp.
This
is
wonderful.
I
like
this.
This
is
super
interactive,
so
yes,
that's
gonna
happen
and
then
obviously
dotnet
will
have
the
big
big
big
release.
A
The
folks
asking
about
3.1,
which
is
our
next
LTS
release.
I
am
we
had
said
in
November.
It
will
still
be
November,
it
might
be
November,
36
or
37,
but
okay,
okay
and
so
it'll
be
it'll
be
around
at
that
time,
and
three
one
is
still
is:
is
the
the
bar
for
three
one
is
servicing
fixes
very
targeted,
API
changes
where
we
want
to?
A
Other
oh
I'm
happy
to
answer
people's
questions
because
it's
been
a
while,
since
we've
just
had
a
good
20
minutes
to
question,
people
are
asking
make
2
LTS
or
one
person
is
asking
make
tutorial.
Yes,
now
we
have
no
plans
to
me
to
12
TS.
It
was
announced.
You
know
all
along
that
one
would
be.
The
LTS
was
a
current
release
and
then
the
300
would
be
the
next
current.
We
announced
a
build
I
think
this
year
that
three
one
would
be
LTS
in
the
roadmap.
A
Will
go
out
of
support
sometime
about
three
months
after
three
Oh,
so
we
encourage
folks
to
move
to
three.
Oh
now,
it's
already
supported
or
already
adds
on
preview.
Seven
I
think
it
was.
We
marked
it
as
go,
live
supportable,
so
I
would
encourage
folks
to
move
to
Rio
now
if
they
can
and
then
yes,
they
also
saying
was
the
last
release
that
can
run
on
full
framework
runtime.
It
was
the
latest
release,
yes,
but
one
will
be
supported
on
full
frame
work
indefinitely,
which
we
announced
also
earlier
this
year.
A
A
We
will
support
a
spirit
core
one
packages
on
that,
basically
forever
indefinitely,
very
similarly
to
how
we
support
MVC
5,
whatever
it
is
5
and
the
Web
API
to
dot
whatever
it
is,
Sigma
2,
dot
or
yield
they
still
supported,
and
they
will
be
supported
practically
forever
as
long
as
done.
That
framework
is
supported
as
part
of
window.
A
So
the
support
policy
for
that
is
actually
being
updated
right
now,
because
we
need
to
give
it
in
line
with
the
windows
support
policy
because,
ultimately
done
that
framework
ships
in
Windows,
and
so
the
windows,
support
policy
for
client,
skews,
I
think
has
moved
to
a
model
of
like
at
certain
Windows
10
versions:
cuz
like
Windows
7,
when
out
of
support
like
this
year.
Right.
That
looks
like
a
big
thing.
It
was
like
not
that
long
ago,
yeah.
A
And
Windows
Server,
2008
r2
as
well
I
think
is
part
of
that,
and
so
the
dotnet
framework
related
support
is
tied
to
the
window,
support
policy,
and
so
those
packages
will
be
tied
to
that
support
board.
So
as
long
as
you
want
to
support
a
version
of
Windows
running
a
supported
version,
of.net
framework
you'll
be
supported
using
the
last
version
of
signal,
our
Web
API
MVC
and
a
spoon,
a
core
2.1
family
packages
and
things
as
well
running
on
done
all
goodness.
A
There
ivan
asks
any
word
on
dom
binding,
so
we
can
use
things
like
canvas
with
Jas
control.
No
I!
Don't
have
any
word
on
that
best
to
ask
the
Blazer
theme,
although
I
think
they
are
pretty
much
we'll
just
be
giving
you
information
relayed
from
the
mono
hasn't,
but
that's
a
fair
question
to
ask.
Over
there
someone's
asking
can
be
a
motivational
background,
music.
C
A
B
B
B
A
B
A
C
C
B
C
C
A
C
A
C
A
Someone
Michael
asks
us
to
clarify
re
LTS
support
for
Windows
7,
going
away
at
such
a.
We
can
still
run
self-contained.
Of
course
you
can
support.
There's
no
kill
bit
in
any
of
this
stuff
right,
like
nothing
explodes
into
flames,
the
second
after
it
goes
end
of
life.
One
point:
X
dot,
Nicole
went
end
of
life
earlier
this
year,
I
think
it
was
about
June
and
that
we
still
have
some
thousands
of
customers
who
we
know
are
working
on.
A
One
point:
X
apps,
we're
just
you
know
it's
the
same
without
new
framework
apps
the
running
versions,
without
a
framework
that
no
one,
so
they
don't
stop
working.
It's
just
that.
You
won't
get
security,
bug,
fixes
for
them
or
stability
bug
fixes
or
if
you
call
Microsoft
support
to
try
and
get
paid
support.
They
and
you
say
yeah
I'm
running
on
doctor
X.
A
You
won't
get
paid
support
for
it
and
if
you
like,
a
github
issue,
because
you
think
you'll
find
an
issue
we'll
go
yeah
if
it
repros
and
the
latest
version
will
fix
it
in
the
latest
version
if
it
meets
the
servicing
bar,
but
it
won't
be
back
ported.
So,
that's
all
you
know,
that's
what
support
means
in
the
context
of
these
last
line.
If
it
works
on
the
platform
it
works,
you
can
physically
work
or
get
it
to
work
or
like
it's
like
any
software.
A
That's
all
three,
eight
nine
one
asks.
Are
you
looking
forward
to
anything
specific
and
done?
Tear
five,
oh,
my
goodness,
so
much
so.
Full
transparency
as
much
as
I
can
give
because
the
team
you
know,
honestly,
the
team
is
focused
on
landing
the
three
over
lease
and
the
three
one
release,
because
it's
obviously
the
most
important
thing
right
now.
We
only
have
very
few
people
who
are
actually
thinking
about
or
looking
they've
got
their
five
stuff
right
now,
the.
But
there
was
an
email
sent
out
yesterday
by
Scott
hunter
internally.
A
A
We
start
looking
for
ways
to
annoy
our
customers
instead,
looking
for
ways
to
make
them
happy.
No,
but
I
think
it's
fair
to
say
that
in
three
and
in
oh
and
one
that
we
had
a
few
large
efforts
that
took
a
lot
of
developer
effort
on
our
side,
a
lot
of
investment
which
meant
that
there
were
other
areas
of
the
product
that
were
pre-existing,
but
that
probably
could
have
just
done
with
some
continuous
improvement.
You
know,
tweaked
an
API
added
support
for
an
extended
scenario
here.
Make
this
easy
to
use.
A
Make
these
two
subsystems
better
together,
and
none
of
that
stuff
was
really
prioritized,
because
we
were
working
had
most
folks
work
on
big
things
like,
let's
add
signal
to
core
into
one.
Let's
make
the
SDK
five
times
faster
to
build
into
one
between
also
give
in
to.
We
really
focused
on
api's
in
MVC
and
really
not
much
else,
and
then
in
three
four
asp
net.
It
was
blazer
right.
That
was
a
really
big
of
G
IPC
and
blaze
it.
A
It
was
like
the
two
big
things
that
we
did
it's
probably
more
on
the
beginning,
but
that
was
kind
of
it
right
and
that
took
up
a
lot
of
the
team,
and
then
there
was
kind
of
peanut
butter
for
the
rest
of
HTTP
got
turned
on
by
default
and
Kestrel.
You
know
that's
like
aphid
eV
and
you
know
a
smattering
of
other
things,
but
we
would
like
to
in
five
actually
budget
a
portion
of
the
time
and
effort.
A
Let's
find
those
things
that
will
have
high
customer
impact
like
a
lot
of
people
are
asking
for
them
or
they
cause.
You
know,
they're
paper
cuts
type
things
and
see
if
we
can
improve
a
whole
bunch
of
those
all
the
way
through
the
stack
right
from
the
very
bottom,
all
the
way
up
to
the
top
to
a
snake
or
yeah
that
cub
stuff.
A
So
that's
all
that's
a
theme
so
I'm
looking
for
us
I'm
looking
forward
to
that
area
because
there's
a
whole
bunch
of
little
things
that
that
we've
had
issues
logged
for
a
while
all
evenness
tissues
that
were
logged
during
three
as
a
result
of
features.
We
added
into
one
that
we
didn't
act
on
because
we
were
too
busy
doing
the
stuff
we'd
already
play
so
I'm
excited
about
that.
A
What
else?
In?
Obviously
the
expansion
or
the
unification
of
of
the.net
core
developer
story
to
the
wider
to
more
dotnet
app
models,
so
in.net
core
3?
We
added
the
Windows
desktop
as
an
app
model,
so
you
can
do
winforms
WPF,
which
was
a
huge
effort
which
is
I'm
going
to
get
the
designer
support
there
for
wind
farms
and
vs,
for
example,
but
in
5
we
announced
you
know
we
want
to
bring
the
xamarin
project
server,
so
you
can
build
a
xamarin
project
using
the
new
SDK
style
project.
A
B
A
So
you
can,
you
know,
build
your
xamarin
apps
from
the
command
line
and
create
them
from
the
command
line,
using
the
don't
SEO
live,
oversee
and
vs
a
mac
and
vs,
and
then
vias
code
as
part
of
that
story
as
well,
because
the
CLI
and
the
vs
cocoa
hand-in-hand,
the
customers
who
use
that
so
I'm
excited
about
that.
Another
big
area
that
I
know
that
we
want
to
focus
on
is
the
ecosystem.
A
I've
talked
about
on
the
show
before,
like
I
have
I
think
we
use
this
Marvel
Cinematic,
Universe
style
analogy,
which
is
you
know,
I'd
kinda
see,
is
just
ending
phase,
one
now
of
the.net
open
source
journey,
and
then
the
next
phase
is
how
do
we
more
democratize
or
what
I
guess
the
the.net
open
source
community
so
that
more
people
get
the
benefit
of
dotnet
and
not
as
a
product
but
as
dotnet
as
an
open
source
project
and
ego
surrounding
community?
How
many?
How
do
we
get
more
people
to
get
the
benefit
of
that?
Now?
A
A
That's
the
stuff
yeah
and
then
the
next
set
of
work
is
we
need
to
the
dotnet
product
as
in
you
know,
the
SDK.
The
way
templates
work,
scaffolding
all
the
features
in
the
asp
net
core
and
dock
that
itself,
even
things
in
Visual,
Studio
and
vs
for
Mac.
How
do
we
make
those
things
feel
more
open
and
actually
be
more
open
so
that
you
know
if
you
go
wow,
you
know.
Mvc
is
great
but
I'd
like
to
build
this
other
framework.
That's
more
targeted
as
specific
things.
B
A
hard
it's
a
hard
challenge
to
you,
because
we
want.
We
want
everything
right.
We
want
to
keep
all
the
quality
level,
the
servicing,
the
the
enterprise
like
being
able
to
trust
long
term
support
all
that
kind
of
stuff
right,
and
we
want
to
grow
that
and
make
it
so
that,
and
you
know
we
can
make
out
a
more
open.
You
know:
vibrant
open-source
community,
yeah
and.
A
A
run
thing
when
we
look
around
at
other
open-source
communities
that
started
differently
to
us.
You
know
dotnet
and
Microsoft's
history
and
things
whether
it
be
Java
or
node
or
Python
or
whatever
it
might
be.
They
look
quite
different
that
they
don't
know
open
source
community
and
it's
just
because
they're
different,
they
have
different
histories
and
different.
You
know
the
investments
coming
from
different
places
and
different
parties
with
a
different
I
guess,
spread.
A
You
know
different
allocation,
and
so
things
are
different
because
they're
different,
but
we
would
like
to
when
we
look
at
some
of
those
other
communities
that
are
traits
that
we
admire
we'd
like
well.
How
would
we
foster
that
trait
in
our
ecosystem?
So
that's
something
that
we
really
want
to
focus
on
and
dot
that
fire,
and
specifically
from
my
point
of
view,
is
you
know
on
the
product
team?
A
It's
probably
still
not
as
approachable
as
it
could
be.
It
could
be
better
if,
if
I
have
a
custom
template
that
is
probably
better
served
as
being
owned
by
the
community,
because
it's
really
not
strategically
important
to
Microsoft
from
a
dotnet
product
point
of
view,
which
means
that
we'll
probably
never
own
it
or
we'll.
Never,
you
know,
invest
in
it
such
that
it'll
be
in
the
SDK
and
supported
or
in
Visual
Studio
supported
for
a
long
time,
but
there
would
be
value
in
the
community
owning
that.
A
How
do
I
start
that
project
and
then
get
it
to
show
up
in,
like
I
said
it's
like
side-by-side
almost
in
the
same
experiences
in
dotnet
new
and
in
Visual
Studio.
So,
if
I
install
at
the
command
line,
it
shows
up
in
Visual
Studio
with
all
the
new
search
experience.
So
that's
a
technical
problem
that
we
have
to
solve,
not
just
a
community
versus
Microsoft
problem
in
similar
for
other
parts
of
the
product
and
so
I'm
really
really
looking
forward
to
the
work
that
we
have
to
do.
There.
A
B
A
A
A
And
but
it's
a
dotnet
language,
like
we've
seen
in
the
Java
community
right
where
you
got
all
these
amazing
languages
that
have
didn't
come
from
Oracle
or
Sun
before
them
or
whatever,
but
they
run
on
the
Java
VM
and
they
can
build
sort
of
sub
communities
that
really
aren't
in
a
lot
of
ways,
aren't
even
associated
with
the
Java
community
they're
their
own
thing,
whether
they're
Kotler
nor
mm-hmm,
the
other
one
I
can't
head
right
now.
That
could
be
something
that
happens
to
dotnet
in
the
future.
A
Who
knows
right
and
so
I'm
super
super
interested
in
super
area.
So
I
didn't
see
where
that
way,
what
else?
What
else
is
worth
talking
about
this
early
without
sending
false
expectations?
It's
because
you
know
we
started
working
on
again.
Obviously,
we
added
the
single
file
stuff
in
three
Oh,
which
we've
talked
about
a
little
bits
of
publishing,
go
file,
publish
trimmed,
which
is
the
make
a
smaller
single
file
for
me,
which
is
still
experimental.
A
It's
not
quite
going
to
be
there
in
three,
oh,
but
it's
available
for
people
to
try
out
and
then
the
other
one
is
published
crushed
in
which
not
only
makes
it
it's
basically
pre
gets
it
right.
It's
part
a
suck
engine,
but
it's
for
cross-platform
for
your
whole.
App
we're
gonna
really
go
hard
on
that
in
five
to
make
it
even
smaller,
even
faster
startup
time
and
avoid
some
of
the
tricks
that
we
had
to
play
in
three
Oh
to
get
a
single
files
like
today
in
three
Oh.
A
When
you
compile
a
single
file
application,
it
creates
a
zip
archive
and
then
the
first
time
you
run
it.
It
extracts
that
zip
archive
to
a
temporary
location
actually
runs
it
from
there.
Then
subsequent
invocations
of
the
original
archive
will
detect
that
it's
already
been
archived
and
then
yo
sorry
extracted
and
then
run
it
from
this.
You
don't
pay
that
cost,
but
it's
not
really
a
single
executable
right.
It's
just
kind
of
a
shell
wrapper
and
then
we
we
shove
the
bits
over
somewhere
else
and
just
run
them
like
they
normally
say.
A
If
you
looked
at
that
folder
this
still
100
deal,
so
we
really
we
want
to
go
further.
We
want
to
make
it
so
it's
actually
a
true
single
executable,
while
preserving
all
of
the
identity
characteristics.
Diagnose
ability,
characteristics
that
you
expect
in
a
day
so
that
you
know
a
type
that
lives
in
a
certain
assembly.
Name
still
has
to
be
that
type
and
it's
tied
to
the
assembly
name,
which
is
a
deployment
unit,
but
now
we're
going
to
try
and
put
it
all
in
one
executable.
A
A
Oh,
so
Michael
brings
up
an
interesting
one.
So
can
you
address
the
which
is
on
topic
for
this?
Can
you
address
the
outlook
for
net
core
versus
net
standard
than
the
near
medium
and
long
term?
Yes,
this
Wis
was
brought
up
a
little
bit
after
the
announcement
at
build
and
it's
still
early
days,
so
nothing
I'm,
gonna,
say
now
will
be
authoritative.
So
just
take
it
all
whether
this
is
the
top
of
my
head
thoughts.
Okay,
so
don't
say,
Demian
said
on
the
show.
That
officially
is.
A
This
is
just
you
know,
as
someone
who's
been
involved
over
the
last
few
versions.
This
is
my
thoughts
about
where
I
think
it's
going,
dotnet
standard
will
always
I
think
need
to
continue
to
exist
or
targeting
or
building
net
code
that
can
run
basically
on
all
the
dockets.
Okay,
even
dot
there,
five
and
beyond,
because
Donnie
framework
is
going
to
be
in
Windows
forever,
for
all
intents
and
purposes,
its
forever
like
this,
it's
been
there
for
20
years,
there's
no
word
of
it
ever
going
away.
A
So
it's
going
to
be
different,
and
so,
if
you
want
to
write
dotnet
code
that
runs
on
doc
their
framework,
but
also
runs
on
the
noon
f5
or
because
that
their
five
is
that
unification
point
where
everything
kind
of
adopts
that
done
their
core
model,
then
you
need
something
that
bridges
that
jump
right.
Just
like
don't
know
standard
today,
bridges
start
their
framework
and
xamarin
and
mono
and
unity
and
Tizen
and
dotnet
core
and
you
know,
etc,
DWP,
etc,
etc.
A
Moving
forward,
we,
you
know,
we
announced
we
want
to
move
more
of
those
models
onto
the
dotnet
5
as
the
surface
area.
Okay,
modulo.
The
things
that
our
platform
Pacific
specific,
like
your
windows
forms,
is
not
coming
to
Linux
Mac,
so
those
API
side,
windows,
own
and
so
dhaniya
standard
will
exist
for
that
purpose.
But
the
other
app
models
will
will
re
platform
themselves
essentially
on
2.85
will
be
on
okay,
that's
the
way,
I
think
about
it.
I,
don't
know
how
fast
that
will
happen.
A
I'm
not
saying
it's
all
going
to
happen
in
dotnet
5,
but
I
think
that
is
the
future
direction.
So
in
terms
of
like,
was
it
past
a
near
medium
and
long
term,
near-term
I
think
if
you're
building
libraries
today
that
you
intend
to
be
consumed
by
the
wider
dotnet
ecosystem,
my
recommendation
would
be
to
start
with
dotnet
standard
Oh,
try
and
avoid
doing
anything
that's
less
than
because
it
brings
in
a
whole
world
of
new
get
pain.
A
If
you
need
to
rehab
that
run
on
dotnet
framework
target
dotnet
framework,
T,
FM's,
specifically
and
I
would
suggest
you
target
supported
versions.
So
net
461
is
usually
the
one
I
tell
people
the
focus
on
you
can
get
away
with
targeting
that
standard
and
running
on
dotnet
framework.
But
as
many
folks
who
do
this
know,
there
are
certain
areas
of
dotnet
standard
that
are
problematic
on
dotnet
framework
until
dotnet
framework
or
seven
one
or
four
seven.
But
there
are
lower
versions.
A
A
Has
its
own
T
FM's
today
and
if
you
need
Samer,
an
api
you'll
need
to
target
those
two
units,
because
that's
what
RTFM
is
right,
it's
a
bunch
of
it.
It
unlocks
those
api's
for
dotnet
standard
is
the
smaller
set
of
api's.
It
runs
everywhere
and
the
other
teams
give
you
other
other
guys.
So
that's
how
I
would
start
today
in
the
medium
term,
I,
don't
think
that
will
change.
A
That
would
still
be
my
guidance,
at
least
at
the
moment
and
I
think
that
will
be
the
the
the
wider
guy
in
your
future
and
then
longer-term.
It's
really
going
to
come
down
to
what
the
ecosystem
looks
like
with
regards
to
that
that
framework
usage
in
terms
of
adopting
more
modern
libraries.
So
you
know
five
years
from
now
when
you
have
an
idea
for
a
new
library
depending
on.
A
So
you
might
just
target
those
2t
events,
don't
they
five
and
above
all,
done
it
correctly
and
above
and
but
their
net
force
it's
one,
but
if
it's
a
library,
phrase
phonetic
or
in
a
few
years
from
now,
the
only
versions
that
will
be
supported
will
be
the
ones
that
run
on
dotnet
core
except
Ray's,
been
in
court.
Two
point
one,
but
it
depends
on
what
feature
in
a
spinnaker
you
want,
if
you're,
targeting
a
new
feature,
you'll
need
to
target
the
duty
FM's
to
get
that
feature.
A
If
a
targets,
a
feature
that's
been
around
since
Eastern
Air
Corps
two,
then
you
could
target
then
standard
two
and
have
it
run
in
both
worlds.
So
you're,
not
in
short,
the
answer
is,
it
depends,
but
generally
you
start
adding
standard.
Then
work.
Your
way
out
as
you
need
to
right,
so
we
are
an
hour
in
now
it
is
450.
So
if
there's
one
more
question
that
I
can
see
here
or
appears
quickly,
I'm
happy
to
answer
it.
Otherwise
we
can
call
it
I.
A
B
A
What
there
was
there
was
an
effect
that
somehow
accident
someone
accidentally
invoked
on
one
of
the
other
shows
by
hitting
a
button
and
I
think
it
was
what
it
was
is
they
were.
They
had
teams
on
their
laptop
via
HDMI
right
and
then
they
shared
their
HDMI
to
the
stream
and
then
so.
You've
got
that
like
doctor,
who
were
they
right,
yeah
I'm
having
to
try
it
like
nothing's
worked
today,
but
I'm
happy
to
try
it.
So,
in
theory,
if
I
go
to
the
team's
call
on
my
laptop
well
just
try,
this
live
right.