►
From YouTube: ASP.NET Community Standup - August 21, 2018 - ASP.NET Core 2.2.0 preview 1 release party!
Description
ASP.NET Community Standup - Aug 21, 2018
Community links for this week: https://www.one-tab.com/page/Lbn9-De1RbOCEvxKyt4tSw
C
D
E
B
B
E
E
B
E
B
C
Who
are
you
hi
everyone?
My
name
is
Mikael
Mengistu
I'm,
an
engineer
on
the
asp
net
core
team
I
work
specifically
on
signal,
R
and
I'll
be
showing
the
signal
Java
client.
Today,
I've
been
on
the
team
almost
two
years
now
and
yeah
things
are
going
great
cool
and
also
from
Portland.
So
we
got
to
Portland
people
representing
here.
B
F
A
A
G
B
A
A
B
G
E
E
A
E
So
Steve
goes
through
and
he
writes
up.
You
know
what
is
endpoint
routing
I
think
previously
it
was
talked
about
his
dispatcher
he's
been
updating
it
based
on
conversations
with
with
James
and
other
people.
So
the
name
now
in
point
routing
and
my
understanding
high-level-
is
that
this
allows
you
the
goodness
of
like
MVC
routing,
but
it
allows
it
earlier
in
the
pipeline,
so
your
middle,
where
your
other
middleware
can
take
advantage
and
understand
the
routes
as
well.
That's
true,
so
yeah
cool,
so.
E
E
It
and
it's
it's,
this
great
feedback,
loop
I've
got
some
other.
Some
others
will
be
showing
too
from
people
that
regularly,
post
and
and
that
we
feature
and
it's
cool,
seen
the
interaction
between
them
and
so
I'll
kind
of
say:
hey.
Did
you
check
this
out
or
that
kind
of
stuff?
So
here's
a
neat
one
from
Philip,
so
he
wrote
about
an
AI
file
provider
for
Azure,
blob
storage.
So
the
idea
here
is
asp.net
has
had
this
I
file
provider
thing
forever
and
the
ideas
you
can
abstract
away.
E
You
can
talk
to
something
as
if
it
was
a
file,
but
it's
not
a
file.
So
the
idea
is
I.
People
have
used
this
for
things
like
reading
assets
out
of
like
a
new
get
package,
or
something
like
that.
So
what
he's
doing
here
is
he's
actually
set
up
a
sure,
blob
storage
as
an
AI
file
provider.
So,
what's
neat
with
that
is
in
one
place
you
register
your
Azure
blob,
storage
and
then
anywhere
else
in
the
site.
You
can
just
interact
with
it
as
if
it's
a
file
under
slash
files,
so
meaning
you
can.
E
You
can
refer
to
the
code
as
if
it's
inside
your
app
and
boom
magic,
so
I
think
this
is
yeah.
This
is
really
really
cool,
so
I'd
like
to
I'm
gonna,
keep
an
eye
on
that
one,
this
one's
interesting,
John
Bristow
just
so
this
is
a
this
is
from
a
survey.
This
is
survey
data.
This
is
definitely
weighted
towards
the
like
they
if
you
scroll
down
to
the
bottom
here
it
talks
about
this
is
from
an
online
pop-up
at
TELRIC
calm.
E
So
this
is
weighted
towards
people
who
are
buying
you
know
or
on
the
telluric
site,
but
it
is
interesting
seeing
over
time
the
demographic
shift,
so
here's
here's
the
numbers
and
I'm
just
going
to
go
to
the
actual.
You
know
the
the
data
stuff
that
they
saw.
They
are
seeing
more
people
aware
of
SP
net
core,
which
is
good
and
they're.
Seeing
you
know,
people
continuing
to
look
at
an
adopt
asp
net
core
I
did
think
it
was
a
little
interesting
that
you
know
this
is.
E
This
is
folks
who
are
just
kind
of
getting
on
board
with
asp
net
core
and
he's
worried
about
their
awareness
of
blazer,
which
is
completely
new
and
experimental.
So
I
am
not
so
worried
about
that
personally,
but
but
I
thought
this
was
really
cool,
seeing
the
kind
of
change
over
time
as
people
are
getting
more
involved
with
asp
net
core
all.
E
So
andrew
lock
is
writing
about
segments
and
segments
is
something
I
was
not
aware
of
before.
It
is
basically
a
an
a
layer
on
top
of
other
analytics
engines.
It's
they
have
an
analytics
jeaious
library
and
the
idea
is
you
can
feed
in
from
one
place
to
multiple
things
so
say
you
want
to
be
tracking.
You
want
to
use
Google,
Analytics
and
Mixpanel,
and
you
know
so
whatever
else
they
they
have
tons
of
other
integrations.
So
what
he's
gone
through
and
done
here
is
kind
of
showed.
E
E
So
he's
he's
shown
that
and
then,
of
course,
wrapping
up
with
you've
got
to
write
this
analytic
Scot
out
in
so
he's
showing
writing
that
out
and
razor
pretty
cool
alright,
so
here's
one
from
Mohammed,
Rohan,
Sahid
and
he's
showing
about
optimally
configuring
asp,
net,
core
HTTP
client
factory,
so
these
are
kind
of
his
opinionated-
looks
at
here's.
How
I
would
like
to
see
HTTP
client
factory
set
up
some
some
interesting
things
he
pulls
out
in
here.
He
talks
about
setting
up
poly
for
retries.
He
talks
about
gzip,
compression
and
and
setting
up
compression.
E
He
talks
about
as
well
and
I
think
this
is
a
really
interesting
one.
The
XCore
X
correlation
ID
HTTP
header.
So
the
idea
is
having
this
correlation
ID
to
track
all
the
way
through
the
logs.
You
know
where,
where
things
are
going
so
so
you
know,
there's
several
different
things
in
here:
setting
up
the
policies,
etc,
etc.
E
G
Like
a
bunch
of
stuff
that
could
be
in
like
a
like
a
nudey
package,
like
you
know
his
apply
these
conventions
or
policies
to
my
HP
client
Factory
is
like
a
just
a
broad
convention
across
the
board.
I,
don't
know
if
it's!
If,
if
he
feels
like
those
are
good
practices
just
for
any
app,
maybe
that
should
be
something
that
could
be
pre-built
and
just
added
to
an
existing
application.
You're.
E
Right
yeah
that
sounds
good
I'll.
Ask
him
about
that:
okay,
here's
David
pine,
doing
a
walkthrough
of
blazer,
so
here
he's
just
kind
of
over
viewed.
He
previously
did
an
interview
with
Steve
Sanderson
about
blazer.
Here
he's
just
kind
of
pointing
people
to
the
getting
started
stuff
and
then
he
went
through
and
wrote
an
internet,
Chuck
Norris
database
client,
so
he's
pulling
data
from
the
the
Chuck
Norris
FAQs,
and
so
here's
showing
how
to
do
that
going
through
and
setting
it
all
up.
E
D
E
E
E
Excuse
me
bing.com
very
large
service.
They
also
have
a
lot
of
internal
services
calling
each
other
so
ton
of
stuff
going
on.
So
this
is,
this
is
cool
to
see
a
you
know,
large
real-world
production
application
moving
to
dotnet
core
and
talking
about
why
they
did
it
and
what
they
got
out
of
it,
what
they
learned
so
as
they
talk
about
in
here.
This
is
things
like
their
their
view.
Logic
is
written
in
Razer
so
that
you
know
I
mean
this
is
kind
of
all
the
way
up.
The
stack.
E
It's
not
just
some
dotnet
core
stuff.
In
the
background,
so
some
neat
things,
that's
ready
to
run
images
thing
is
exciting.
So
the
idea
there
is,
you
know
when
you
deploy
your
code
out
to
a
server,
there's
still
some
JIT
that
goes
on
and
with
ready
to
run
that
kind
of
engine
step
happens
at
Build
time
and
then
you're
pushing
that
out.
It's
already
pop
it
on
a
server
and
it's
ready
to
go
so
that
so
that's
exciting!
You
see
here
the
performance,
so
this
has
been.
This
is
showing
their
their
server
latency
dropping
34%.
B
E
Just
huge,
so
this
next
part
here
is,
is
really
interesting
and
I
recommend
kind
of
digging
through
a
clicking
through
on
these
links
here.
What
they're,
showing
is
here's
why
they
got
that
34%
job,
so
they
dug
in
specifically
to
their.
You
know
their
performance
data
and
showed
what
was
going
faster.
So
these
are
the
kinds
of
things
like
as
I've
been
doing
dotnet
for
talks
lately
and
I'll.
Tell
people
like
this
is
why
being
on
dotnet
course,
so
great
every
release
gets
you
all
these.
E
B
Master
is
a,
and
one
thing
if
I
may
that's
worth
pointing
out-
and
we
talked
to
the
Bing
team
is
even
though
Bing
is
Microsoft
and
we
are
dev,
dev
and
Microsoft.
You
would
think
that
we
like
to
talk
to
each
other
all
the
time,
but
it's
really
different
companies
right
Microsoft
is
a
hundred
thousand
people.
It's
basically,
you
know
a
thousand
little
hundred
person
companies
if
being
wanted.
Some
modification
to
like
the
CL
are
fundamentally
or
they
wanted
to
change
c-sharp.
B
Fundamentally,
it's
not
quite
as
easy
as
just
ringing
us
up
demanding
a
feature
and
fitting
it
into
the
thing.
The
fact
that
dotnet
core
is
open
source
literally
allowed
them
to
modify
it
change
it
without
talking
to
us
and
then
then
their
negotiations
change.
They
can
show
us
well
here's
the
thing
that
we
want.
Here's
a
feature:
we
want,
here's
a
drop
that
we
did
and.
B
E
B
E
And
some
of
the
things
on
this
list
actually
I
think
it
was
this.
This
call
I
this
an
internal
call
of
optimization
and
that
that
was
something
where
they,
the
Bing
team,
said
hey.
We
could
use
this
or
you
know
people.
There
was
an
open
issue
and
the
dotnet
core
team
was
like
yeah,
not
sure.
If
this
is
going
to
be
useful
and
then
the
Bing
team,
like
prototyped
it
and
said,
look
here
are
the
performance
improvements
we
get
and
because
of
that,
that's
that's
why
that
feature
shipped
there,
so
so
this
is.
E
This
is
some
really
cool
stuff
like
call
I
I
wasn't
aware
of
that?
That's
there's
something
that's
been
around
for
a
while,
but
wasn't
inlinable,
and
this
is
call
like
a
or
or
whatever
is,
is
a
it's
like
P
invoke,
but
a
lot
faster.
So
in
certain
cases
things
can
go,
you
can
make
internal
calls
much
faster.
So
one
other
really
cool
thing
here.
Is
this
runtime
agility,
so
the
the
ability
to
have
X
copy?
You
know
side
by
side,
CI,
all
that
kind
of
stuff
being
able
to
roll
things
out
so
much
quicker.
E
E
B
And
it's
really
cool
the
way
that
they've
plugged
it
into
asp.net
core,
like
you
can
see
right
there,
how
the
giraffe
add
giraffe
extension
method,
our
registers,
dependency,
they're,
basically
using
parts
of
asp.net
core
that
they
like
and
the
parts
that
they
don't
want.
They
just
plug
into
the
pipeline
and
they
take
over.
So
it's
really
the
best
of
both
worlds
and
it
makes
a
really
comfortable
environment
for
our
people,
cool.
E
So
it's
neat
to
see
the
continued
like
they're
they're
continuing
to
build
out
on
this
big
feature
here
is:
this
is
up
updates
for
authorization,
policy
and
and
policy
based
authorization,
so
yeah
a
lot
of
good
stuff
last
link
that
I
always
end
up
with,
as
we
get
closer
to
Netcom,
just
reminding
people.
So
one
thing
that
a
favor
I
would
ask
of
you,
even
if
you're
totally
aware
of
dotnet
comp
go
ahead
and
and
save
the
date,
so
we
can
kind
of
track
and
get
an
idea
of.
E
E
E
E
E
E
Then
local
events-
this
is
neat,
so
we
have
over
a
hundred
local
events.
So
this
includes
live
viewing
parties
during
the
event
that
twelve
through
the
fourteenth,
but
then
we
also
have
live,
or
we
have
follow-on
events
that
you
can
go
register
for.
So
these
are
all
around
the
world.
These
are
places
you
know
near
you,
so
number
one
find
one!
That's
near
you!
If
there
is
not
one
near
you,
you
can
register
a
new
one,
so
you
can
go
and
create
a
new
event
and
tell
us
about
it
even
know.
E
What's
that
they
can
do
that
even
now,
even
now,
yeah
they
can
go.
So
we
have.
We
have
some
swag.
We
have
sent
out
to
events
that
have
already
registered,
can't
promise
we'll
get
you
swag
if
you,
if
you
register
one
late,
but
still
if
you
want
to
have
an
in-person
event
and
tell
us
about
it
and
get
it
get
on
the
map.
We're
happy
to
add
you
awesome,
yeah,
all
right,
I'm
done,
shiny
I
will
share
out
the
links
in
the
chat
and
put
it
on
the
description,
cool.
G
G
So
we
thought
we
would
spend
some
time
talking
about
what's
coming
into
to
specifically
in
preview,
one
we've
been
harder
work
on
to
to
I'm.
We've
already
saw
someone
to
the
community,
apparently
as
he's
on
the
ball
and
already
looking
at
the
vets
and
trying
things
out
and
writing
content,
which
is
fabulous
but
preview
on
is
pretty
much
done.
G
It's
not
public
yet,
but
maybe
this
week
like,
we
hope
to
have
it
out
this
week
the
the
bits
that
you
can
install
and
start
using
and
start
playing
around
the
features
it
is
early
in
the
Tootoo
milestones,
so
things
are
still
being
being
worked
on.
Things
are
being
polished,
so
there
there
certainly
be
bugs.
G
That's
what
we're
hoping
we'll
see
how
the
the
releases
go,
but
this
is
all
the
new
stuff.
That's
going
to
be
available
to
start
playing
around
with
in
in
preview,
1
and
I
thought
it
might
be
fun
just
to
take
an
early
look
literally
a
preview
preview
of
the
the
new
features
that
are
coming
in
this
release.
So
new
stuff,
the
new
templates
are
being
updated
with
getting
a
facelift.
G
We
were
moving
from
bootstrap
3
to
boot,
strap
for
and
I
think
we're
on
four
one
three
now
so
we're
trying
to
keep
up
with
the
latest
releases
and
our
third-party
dependencies,
and
so
as
part
of
doing
the
bootstrap
4
update.
We
also
did
a
bit
of
a
design
clean-up
on
the
templates,
simplify,
make
them
a
little
cleaner.
Looking,
we
also
updated
the
the
spa
templates
to
update
their
dependencies
and
we
move
to
angular
6,
specifically
for
the
for
the
angular
template
and
I.
G
Think
angular
7
actually
is
slated
to
come
out
somewhere
later
in
the
fall,
so
we
may
have
to
do
another
update
I,
don't
want
to
have
to
look
to
see
how
their
their
release
goes.
Http
2
is
coming
in
this
release.
We've
been
actually
working
on
the
HB
2
for
yeah.
It's
been
it's.
It's
I
mean
HB.
2
is
a
pretty
involved
spec.
Actually,
when
I
talk
to
the
the
devs
that
are
working
on
the
that
protocol
implementation,
they
they
make
it
clear
that
this
is.
This
is
not
as
simple
I
mean
actually
be.
G
Hp1
itself
was
not
not
a
simple
effort
that
took
honestly
like
I
would
say
even
a
couple
releases
in
the
a
core
before
the
kestrel
implementation
of
HB.
One
really
became
came
of
age
like
for
a
while.
We
were
doing
that
thing
where
we're
saying
we
really
need
to
run
kestrel
behind
some
sort
of
proxying
server
like
IAS
or
nginx,
and
which
took
a
little
while
before
we
be
more
comfortable
with
putting
it
as
an
edge
server.
G
So
HB
2
is
a
even
more
complicated
protocol
and
we've
been
working
on
it,
and
we
now
have
bits
that
you
can
try
out
with
with
with
freebie
one
and
we'll
see
a
little
bit
of
that
is
in
process
hosting.
This
is
the
ace
net
core
module
like
historically
that's
been
an
out
of
process
model
where
you
all
your
requests,
get
forward
forwarded
to
a
dotnet
that
eggsy
process
effectively
and
that
has
performance
implications.
G
We've
been
looking
at
for
again
for
a
little
while
trying
to
improve
the
performance
of
that
setup
by
moving
the
a
spec
or
logic
into
the
EIS
process
itself.
So
you
don't
have
to
have
that
orbit
of
having
an
IPC
channel
communication
from
the
is
process
to
the
dotnet
exit
process
and
we
have
the
the
Bitzer
we're
planning
to
ship
them
with
2.2,
which
I
think
we
tried
to
get
them
out
with
with
2.1.
G
G
Big
theme
for
this
release
has
been
services
and
building
web
api's,
and
so
we're
really
trying
to
improve
the
experience
of
building
api's
that
are
descriptive
and
some
sense
self-documenting.
So
if
you
have
an
API-
and
you
want
to
generate
an
open
API
specification
from
your
API
we'd,
like
the
to
have
a
really
good
experience
in
doing
that,
if
you
build
an
API
with
previous
releases
of
a
spec
or
there
was
a
lot
of
sort
of
flexibility,
I
would
say
and
how
those
your
action
methods
could
be
called
like.
You
could
have
a
parameter.
G
That
could
be
it's
just
as
equally
been
a
query
string,
value
or
a
form
data
value
or
a
header
value
like
it
was
a
fairly
flexible
model,
binding
system
and
that's
great
for
in
terms
of
functionality.
But
it
means
that,
in
terms
of
providing
a
description
of
what
your
API
supports,
it
meant
the
matrix
was
pretty
large.
So
we're
I've
been
trying
to
add
conventions
that
make
things
a
little
bit
more
opinionated
they
give.
G
Your
API
is
a
better
description
that
you
can
then
use
for
things
like
code
generation,
documentation,
testing
tools
and
the
like,
so
another
round
of
Web
API
conventions
in
this
release,
endpoint
routing
we
saw
the
blog
post
earlier
about
what
what
we've
been
doing
their
thumbs
in
the
past.
You
may,
for
the
the
term
dispatcher.
This
is
an
effort
to
improve
our
routing
systems
so
that
it
is
available
throughout
the
stack,
as
opposed
to
being
kind
of
an
NBC.
G
We
are
now
shipping
the
health
checks
API
with
a
spinet
core
into
two
and
then
Sigma,
R
Java
client,
a
new
new
Java
client.
So
you
can
write
all
your
Android
apps
and
talk
to
your
signal,
our
hubs
and
get
real
time
real
time
data.
That's
that's
the
the
list
of
stuff.
That's
coming
in
preview!
One
and
some
things
are
more.
Are
you
know
more
feature?
Complete
than
others
in
this
release,
but
you
know
how
many
views
will
be.
We
expect
I
think
what
we
published
in
there
was
a
roadmap
announcement.
B
G
C
G
The
plan
so
August
preview
is
what
we're
doing
right
now.
We
plan
to
do
another
preview
in
September
and
October
and
then
try
and
ship
it
before
the
the
end
of
the
year.
That's
the
the
plans
schedule
and
you
can
get
a
feel
for
all
the
features
that
we're
trying
to
do
in
this
release
through
the
roadmap.
So
definitely.
G
G
G
Been
pushed
out
to
so
we
so
you
know
the
roadmaps.
We
do
our
best
to
try
and
predict
the
future.
Looking
our
crystal
ball
about
how
much
we
can
actually
get
done
in
and
release
and
something's
making
it
something
stoat.
So
that's
a
an
example
of
a
feature
that
actually
got
pushed
out,
but
a
lot
of
this
stuff
is
is
certainly
in
alright
cool.
So
shall
we
shall
we
take
a
look?
Shall
we
play
around
with
the
bits?
So
what
I
did
is
I?
G
Basically,
the
latest
CI
build
and
I
think
it's
actually
still
the
candidate
build
for
what
we're
planning
to
ship
and
I
started
playing
around
with
the
features
to
see
you
know
what
the
state
of
things
are
and
I
thought
I
would
do
a
few
few
demos,
let's
try
and
take
a
look,
a
few
things.
So
let's
go
to
visual
studio
and
if
you
do
file
new
project
new
web
application,
my
23rd
web
application-
apparently,
let's
make
it
20-7
for
good
measure.
G
Since
that's
my
favorite
number
and
what
we
should
see,
I've
installed
the
latest
SDK
and
you
can
see
I
have
the
a
Smith
core
to
showing
up
as
an
option
in
the
dialog.
The
SDK
version
that
I
currently
have.
If
we
take
a
look,
it's
a
dotnet
version
I'm
on
202,
103,
B,
193
49.
Is
this
the
current
build
that
that
I'm
on?
Can
you
see
that
so
there
that's
the
current
build
of
this
of
this
SDK,
and
so
you
can
create
an
ASIC
or
a
two
application
yeah.
G
No
interesting,
that's
interesting!
Dial!
I
can
see
that
one
before
that
bad.
So
this
interesting
question
about
what
version
of
Visual
Studio
you
should
be
using
with
with
two
bits:
the
the
plan
is
that
then
we're
going
to
be
recommending.
15
959
is
the
version
of
Visual
Studio
that
you're
going
to
want
to
use
right
now.
Yes,
we're
currently
on
a
the
59,
is
in
the
preview
Channel.
G
E
G
Will
be
been
updated,
but
fifty-nine
is
the
plans
targeted,
updated
for
for
a
snack
or
two
two
and
dotnet
cor
2:2,
but
it
still
works
with
the
older
versions
of
Visual
Studio.
There
are
just
newer
features
that
you
may
run
to
issues
with
so,
for
example,
the
new
asp
net
core
module
that
supports
in
process
hosting.
That's
something
that
to
wire
that
up
with
ice
express.
We
need
extra
Visual,
Studio
changes,
so
that's
gonna
be
one
of
the
features
that's
going
to
require
fifty
nine.
It's
just
a
new
template.
This.
B
G
New
template
so
I
think
we
showed
this
a
little
bit
before
in
the
the
last
community
stand
up,
but
this
is
bootstrap
for
base.
We
can
see
that
if
we
go
into
our
the
blip
root
folder
and
look
at
the
actual,
let's
look
at
the
the
index-
the
layout.
Let's
look
at
a
couple
things
here
and
there's
a
big
enough.
Yeah.
B
B
G
The
bootstrap
link
is
a
bootstrap
for
one
three
links,
so
we
have
bootstrap
for
one
three
in
the
templates.
You'll
also
notice
that
we're
not
pulling
it
off
of
cDNAs,
so
instead
of
using
our
own
CDN
we're
now
just
using
the
the
public
existing
ones
that
are
popular
in
the
community.
This
aligns
us
with
Lib
Man,
which
is
the
new
vs
tooling,
for
managing
client-side
dependencies.
They
also
by
default,
will
pull
from
CDN
j/s
we'd
love
to
hear
what
people
think
about
this.
Like.
Is
this
just
a
good
idea?
G
E
G
B
F
E
E
G
B
G
B
G
G
G
G
B
B
A
new
template
for
these
scenarios,
a
couple
of
people
that
desperately
ask
them
for
a
left
side,
nav
bar
I,
think
nav
bars
are
up
to
bootstrap,
so
we're
probably
not
going
to
do
that,
but
I
think
the
point
is
there
are
two
kinds
of
people
there
are
people
who
understand
that
empty
is
all
they
want.
Mmm-Hmm.
F
G
Started
product
in
with
that,
you
do
the
first
time
you
use
a
spin
accord
on
a
core
I
think
needs
to
have
a
little
bit
of
stuff
in
it
needs
to
have
some
pages
needs
to
have.
Some
links
needs
to
show
you
how
to
do
a
few
things
for
the
people
that
are
doing
like
day-to-day
development,
that
I've
already
done
the
getting
started
experience
and
what
a
starting
point
for
building
their
next
app
for
their
for
a
new
project,
I'm.
Guessing
that
that's
what
the
people
that
are
asking
for
empty
that!
That's!
That's!
What
writer.
B
G
Okay
and
I
would
love
to
hear
from
people
what
they
think
about
the
existing
empty
template
like
is
it?
Is
it
what
you
want?
A
car
I
think
empty
right
now
has
just
like
a
single
middleware
that
returns
HelloWorld
right.
Is
it
too
empty
yeah?
Is
it
to
him
like
something
some
people
have
asked?
Can
you
take
the
empty
template
and
just
add
a
single
page
or
add
a
single.
G
Like
like
at
least
have
MVC
concepts
in
the
empty
template,
so
that
you
know
how
to
use
that,
but
that
makes
it
less
empty.
Is
that
too
much
like?
We
would
love
to
hear
what
people
have
thoughts
on
that?
Obviously
we're
not
gonna
be
able
to.
Maybe
we
won't
be
able
to
make
everyone
happy,
but
we'd
love
to
how
make
the
majority
as
happy
as
possibly
our
empty.
C
B
G
G
Is
the
new
spot
template,
so
the
spot
template
still
does
have
some
some
content
in
it
curious
to
hear
what
people
think
about
that
for
people
who
want
to
know.
G
Bit
more
content,
we
did
shift
the
spot
templates
to
like
we
decided
that
the
template
should
be
consistent
in
terms
of
their
nav
bars
like
before.
The
spot
templates
had
a
left
nav.
So
now
it
has
a
top
nav.
It
still
has
the
same
functionalities
before
you
know
a
counter
and
a
fetch
data,
page
yeah
for
consistency
here
instead
of
a
left
nav.
But
you
know,
let
us
know
what
you
see:
I.
B
G
Marketing,
so
just
to
show
the
interest
of
time
what
else
we
got
in
the
angular
template
just
to
show
that
this.
This
also
now
has
angular
6.
So
if
we,
if
we
look
in
the
package,
so
JSON
file
for
this
guy,
you
can
see
it's
using
angular
6
across
the
board.
I
think
angular
6
is
now
just
6.1.
So
we
will
update
that
as
the
angler.
E
G
E
G
Size
update
so
we're
thinking
that
maybe
all
these
templates
actually
just
need
to
be
just
new,
get
path.
Template
pack
set
on
new
get.
That's
that's
the
current
thing.
We're
not
gonna
do
that
in
2
2,
but
the
future
thinking.
That's
what
we're
looking
at.
Ok,
what
else
should
we
look
at?
Let's
look
at
the
wire
a
little
bit
for
this
project
and
notice
that
something
that's
happening
on
the
network.
G
So
if
I
refresh
you
notice,
there's
a
protocol
column
down
here
and
it's
showing
h2,
which
is
a
preheated
version
of
HTTP
2,
so
this
application
out
of
the
box
has
HTTP
to
turned
on
talking
to
kestrel
yeah.
This
is
talking
directly
to
to
to
well
actually,
in
this
case
this,
this
app
is
going
to
your.
B
G
B
E
B
G
B
G
B
B
It
should
okay
I'd
like
to
know
that
that
would
be
interesting.
G
Hp
2
is
working
with
Castro
things.
We
do
support
the
multiplexing
of
the
streams.
You
know
the
compressed
headers
all
that
stuff
things
that
we
do
not
support.
We
don't
support
server,
push,
that's
not
something
we
currently
plan
to
add
I,
believe
we
don't
currently
have
prioritization
of
the
streams
in
this
release
either.
So
those
are
two
things
that
are
not
enabled
that.
B
G
G
C
Not
something
we
really
talked
about,
yeah
we're
still
sort
of
in
the
middle
of
like
working
on
to
to
stuff
that
we've
got
slated
and
figuring
out
like
3
Oh
planning.
We've
got
a
bunch
of
features
that
hasn't
really
come
into
conversation,
yet
I
hope
you
bring
it
up.
I'm,
probably
asking
a
question.
G
G
G
G
So
we
can,
you
know,
flush
out
those
bugs
like
there's,
there's
known
issues
right
now
with
the
performance
of
the
hb2
implementation
in
kestrel,
that
we
still
need
to
optimize
and
work
on
like
one
of
the
whole
points
of
hb2
is
supposed
to
be
perfect
and
we're
not
quite
there
yet.
So
it
may
be
that
the
signal
our
folks
are
just
sort
of
like
well,
let's,
let's
wait
to.
F
G
But
it's
there
so
please
try
it
and
let
us
know
how
it
goes
if
you
hit
by
this,
please
file
them
performance
issues.
Please
let
us
know
so:
that's
HB
2,
a
next
one
I
want
to
talk
about
is
the
a
spec
core
module
yeah
go
ahead,
so
I,
don't
think
I'm
gonna,
actually
there's
not
much
to
demo
on
this
one,
but
this
is
a
moving
moving.
G
G
E
G
And,
or
or
like
one
common
problem
that
we
hear
about
a
lot
is:
if
the
don''t
exit
process
fails
to
start
okay,
and
then
you
just
get
an
ACM
can
try
to
restart
it,
but
it
doesn't
it's.
It
keeps
failing
to
start,
and
then
you
get
like
a
502
touch
style
error
where,
like
your
application,
failed
to
start
and
that
that's
kind
of
tricky
to
diagnose,
because
you
need
to
go
figure
out.
Why
did
that?
G
Why
did
it
on
an
exit
process
have
an
issue
with
startup
like
you
get
through
a
second
exception
at
some
point,
something
you
go
digging
through
logs
to
figure
that
out
one
of
the
nice
things
about
the
in
process
model.
Is
that
diagnosing
any
issue
with
your
startup
logic
becomes
a
lot
easier
because
you're
debugging
it
right
within
the
iOS
worker
process
itself?
Okay
and
performance
is
like
almost
four
times
faster
like
this.
Is
that
our
latest
numbers
from
our
internal
benchmarks?
G
This
is
the
returning
a
chunk
of
Jason
benchmark
from
my
blue
from
Tekken
power.
The
green
line
at
the
bottom
is
the
performance
of
is
hosting
with
the
2-1
bits
and
the
sort
of
pinkish
line
at
the
top.
That's
with
the
new
in
process
model
and
in
a
snake
or
two
too
so
quite
a
bit
better
in
terms
of
performance.
Now,
with
the
preview
one
bits
getting
actually
using
the
the
new
imprecise
ma
in
proc
model
does
require
a
little
work.
You
do
have
to
set
an
MS
build
property
in
your
CS
proj
file.
G
You
have
to
then
publish
your
app
and
then
and
then
you
should
be
good
to
go
on
yes,
but
it's
not
something
that
you'll
get
out
of
the
box
with
the
f5
experience
in
visual
studio
until
a
I
think
like
59
preview,
to
is,
when
we
plan
to
actually
have
that
integration
done.
So
the
dev
experience
will
take
a
little
longer,
but
in
four
deployments
you
can
at
least
try
it
in
with
PB
1
bits,
and
we
are
getting
a
little
long
on
time
and
I
want
to
make
sure.
B
C
E
G
B
C
Idea
are
you
in
right
here?
This
is
IntelliJ
IDEA,
so,
basically
without
here
what
we
have
to
do
for
now,
because
it's
not
a
public
build.
Yet
you
have
to
define
our
staging
repository
and
then
from
there
we
can
add
the
signal,
our
dependency
mm-hmm.
So
we
just
add
another
sort
of
node
within
our
dependent.
These
tags,
and
this.
B
B
C
R
and
then
the
version
number
and
then,
if
we
go
over
to
chat
I,
just
wrote
a
simple
chat.
Application
mm-hmm,
which
news
up
a
hub
connection,
takes
input
from
the
scanner
for
defining,
which
signal
our
server.
You
want
to
connect
to.
We
define
our
on
handlers,
so
when
we
receive
an
indication
from
the
server
with
the
target
of
send,
we
basically
just
take
the
arguments
from
that
invocation
from
the
server
and
we
can
do
whatever
logic
we
want
here.
We
just
print
it.
It.
C
E
C
B
E
C
G
C
Me
that's
confuse
people,
and
this
is
the
application
here
running
live
so
if
I
have
a
different
client
here,
this
is
using
the
JavaScript
client.
If
I
hit
broadcast
with
the
message
browser
we
go
back,
we
can
see
that
we
have
this
printed.
We
receive
that
invitation,
so
we
can
say
from
here
hello
console
and
if
we
hit
son
we
should
be
able
to
go
back
and
see
that
a
little
family
goes.
Oh
yeah.
C
Virtual
desktops
yeah,
we
can
see
very
similar,
so
this
uses
Android
studio
in
general
uses
great
or
rather
than
maven.
So
we
can
see
how
we
would
bring
in
the
signal
our
Java
client
here
instead
of
or
we
still
basically
have
to
define
this
repo,
the
staging
where
you
go.
So
it's
very
similar.
So
this
is
in
our
project
level
built
that
Gradle
and
then
for
the
app
level
build
build
our
cradle.
C
We
have
to
in
our
dependencies
similar
to
maven,
add
another
node
and
we
just
define
it
the
same
way
just
isn't
a
different
shape
to
online
instead
of
like
seven.
So
we
have
calm,
Microsoft
ASP,
not
bah,
blah
blah,
and
there
will
be
information
in
the
2.2
preview,
one
blog
post,
with
the
updated
like
build
members
for,
like
the
actual,
like
release
preview,
one
build
mm-hmm.
B
B
C
B
C
Of
ACK
yeah
yeah
like
just
connect
and
like
get
a
positive
response
and
then
from
there
like
making
it
look
more
and
more
like
the
client.
So.
C
C
C
No,
it's
it's
really
working
well
in
the
house
snappier.
So
if
we
say
hello.
C
Sweets
got
Android
running
yeah,
and
this
is
just
a
simple
app
that
I
have.
It
will
be
posted
in
this
signal,
our
samples
repo
until
then
I
just
have
it
like
on
my
personal
github,
but
you'll
be
able
to
see
it
there
in
the
signal,
our
samples,
repo,
but
yeah.
This
is
signal
are
the
Android
or
the
Java
client
right
on
Android
any.
C
C
G
C
B
G
B
D
G
Talk
a
little
bit
about
routing,
so
this
are.
These
are
the
numbers
that
we're
seeing
now
with
the
MBC
route,
the
new
endpoint
routing
system
in
a
snit
cor
2:2
we're
seeing
about
a
10
percent
performance
bump
with
the
new
routing
annotation.
So
when
you
think
about
endpoint
routing,
you
should
think
about
is
basically
a
rewrite
of
routing
that
I
think.
That's
honestly,
the
the
right
way
to
think
about
it.
There's
there's
the
existing
routing
system.
G
That's
in
a
state
court
today
that
you're
using
if
you're,
using
MVC
your
razor
pages
or
building
web
api's
we're
doing
another
turn
of
the
crank
and
though
there's
a
couple
reasons
for
that,
one
is
to
get
you
know.
Performance
benefits
like
this.
Another
is
because
we
really
would
like
the
routing
concepts
to
apply
broadly
across
a
snit
core.
You
should
be
able
to
use
link
generation
from
middleware
to
route,
to
a
hub
or
to
an
API
action
or
to
a
to
a
controller
action
on
in
your
in
your
application.
E
Changed
already,
we
kind
of
did
some
stuff
with
that
with
like
way
back
in
the
day,
routing
came
out
with
MVC
and
then
we're
like.
Oh,
this
should
be
plumbed
in
through
everything
like
vacuuming
with
web
worms
right,
we
kind
of
rolled
it
back
into
routing
being
kind
of
a
more
global
concept,
I
hadn't.
So
it's.
G
True,
it's
true
that
the
like
routing
the
other,
where
is,
is
a
decoupled
piece,
but
each
route
is
basically
it's.
Each
route
is
kind
of
like
its
own
world
of
implementation,
like
you
have
to
execute
the
route
code
in
order
to
figure
out
what
does
it
do
and
all
of
that
logic
really
ends
up
being
MBC
logic
like
there's.
No,
there's
no
notion
of
that
being
something
that's
sort
of
independent
that
you
can.
G
You
could
use
from
like
a
middleware
like
it's,
so
it's
there's
a
lot
of
stuff
that
happens
in
routing
that
actually
happens
at
the
MVC
layer.
That's
built
upon
on
top
of
the
core
routing
abstractions,
but
it
ends
up
being
really
only
useful
the
MVC.
As
a
result,
we're
gonna
really
like
to
make
that
functionality
more
broadly
applicable.
It's
really
what
this
is
all
about.
So.
E
G
If
you
wanted
to
generate
documentation,
sir,
for
your
API
honestly,
you
could
do
this
at
this
layer
now
by
scan,
you
can
inspect
and
generate
links
for
anything
in
your
API
from
from
a
middleware
layer
as
and
have
it
be
a
reusable
component.
So
that's
something
you
could
do
as
opposed
to
having
that
having
to
have
that
live
in
the
MVC
layers.
Okay,.
E
G
It's
not
something
that
I
far
as
I
know
that
we've
been
taught
it
may
be,
but
it's
I
don't
know
honestly
the
answer
to
that
one.
If
this
is
a
really
as
a
dynamic
support,
it's
more
than
more
about
making
like
the
the
route
table,
inspectable,
making
it
making
the
notion
of
what
the
endpoints
are
known
up
front,
making
them
things
that
you
can
route
to
up
front
without
having
to
get
to
some
point
in
the
pipeline,
where
you
didn't
have
to
execute
a
bunch
of
code
to
figure
out.
G
G
The
the
programming
model
for
HP
browning
works
the
same
way
the
this
one,
the
so
like,
you
still
add
the
same
attributes
to
your
controllers
and
actions.
The
underlying
infrastructure,
that's
actually
resolving
the
routes
and
doing
the
linking
has
been,
is
being
replaced
and
so
you're
getting
the
new
implementation
of
the
of
the
routing
system
under
the
covers.
G
Let's
just
to
show
an
example
of
how
what
you
can
do
today,
it's
worth
calling
out
that
also
with
the
endpoint
routing
it's
a
bit
of
a
journey
like
we,
we
have
the
the
vision
of
it
being
this.
You
know
generic
dispatcher,
that
you
can
route
to
any
endpoint
in
your
application
and
then
there's
what's
actually
implemented
in
preview,
one.
G
The
things
that
you'll
be
able
to
do
in
preview,
one
is
you'll,
be
able
to
get
a
new
service,
which
is
this
link
generator
service
which
is
available
through
di,
and
you
can
then
use
that
from
pretty
much
anywhere
in
the
application
to
generate
links
to
MVC
endpoints.
Ok,
so
you
can
generate
links
to
your
MVC
actions,
your
your
razor
pages,
that's.
G
G
In
the
future,
of
course,
you'd
like
to
be
able
to
link
to
other
things
as
well,
and
that's
one
of
the
items
that
we
still
need
to
go
and
implement.
But
with
what
we've
got,
we
go
slash
Browdy,
you
know,
I
can
see.
I
get
a
correct
route
to
my
to
my
privacy,
privacy
page
based
on
the
the
path
to
the
page
on
disk.
So
that's
that's
kind
of
cool
is
to
start
playing
around
with
that.
G
If
we're
interested
in
particular
to
see
how
this
affects
existing
applications,
because
there
are
some
some
you
know
anytime,
you
draw
sort
of
reimplemented
something
there
are
some
subtle,
behavior
changes
that
if
that
occur
like
what
happens
when
you
link
to
something
that
doesn't
exist,
the
behavior
right
now
is
a
little
bit
different
like
it.
It
will
generate
a
link
with
an
empty
string
as
opposed
to
a
link
with
values
that
just
goes
to
a
for
or,
for
you
know,
we'd
love
to
hear
people
what
people
think
about
that.
G
So
try
upgrading
your
applications
with
this
new
routing
system
and
and
see.
If
how
much
it
we
actually
curious
to
see
how
much
is
a
break
like?
How
do
is
there
anything?
That's
a
overly
disruptive
that
we
actually
need
to
align
closer
with
the
old
routing
system.
The
way
it's
controlled
like
how
you
get
the
new
routing
system
is
purely
by
saying
that
your
compatibility
version
is
to
two
so
that
by
having
that
that
in
there
you
will
get
the
new
routing
system.
G
If
you
need
to
roll
it
back,
you
can
go
into
the
embassy
options
and
flip
a
switch
and
say
use
the
old
routing
system
instead
of
the
new
one.
If
you
hit
too
many
breaking
changes
and
you
need
to
to
get
something
working,
so
that's
that's
how
you
do
that?
That's
the
new
routing
system-
and
the
last
thing
I
just
wanted
to
show
is
health
checks,
real
quick,
so
health
checks,
health
checks
is
a
way
to
stand
up.
A
simple
endpoint
that
infrastructure
can
hit
to
tell
that
your
services
and
your
application
are
actually
alive.
G
It's
a
library
we've
actually
been
playing
around
with
for
for
a
while.
We
just
have
haven't,
had
a
chance
to
completely
bake
it
and
get
it
shipping,
but
it's
now
shipping
with
two
two:
it's
in
the
box
in
this
application,
I've
added
health
checks
to
the
application,
and
you
can
see
I've
added
a
single
check.
It
has
a
just.
A
name
is
what
this
config
name
is,
and
then
this
check
is
saying
my
app
is
healthy.
G
If
this
particular
config,
this
--tz--
in
the
application
you
can
think
of
this
is
sort
of
like
being
a
knowledge.
Astute
ekang,
like
is
my
database
connection.
Life
is
what
this
is
trying
to
show.
You
could
do
something
very
similar,
in
fact
in
it,
we
hope
to
in
the
future
have
like
sugar
methods
where
it's
like,
you
know,
like
add,
DB
context,
check
or
or
something
like
that.
Where,
with
that,
you
would
actually
would
check
to
make
sure
that
your
DB
context
is
there
and
it's
live
and
running.
G
C
G
D
G
And
if
we
go
to
the
slash
health,
let's
see
if
it's
okay,
so
currently
I'm
healthy.
So
that's
good
I
go
back
to
my
application
and
mess
around
with
the
config.
Let's
say
like:
let's
get
rid
of
this
required
config
value
that
I
need
and
run
to
be
healthy,
just
save
that,
and
if
I
refresh
you
can
see
now
the
be
the
endpoint
is
saying
that
you're
on
healthy.
So
you
can
then
integrate
these
endpoints
with
things
like
like
kubernetes,
which
Cooper
News
has
infrastructure
for
checking
like
house
health
endpoints
of
your
application.
G
You
can
wire
it
up
with
like
the
asthma
Traffic
Manager.
It
has
capabilities
of
pointing
it
at
the
the
health
endpoints
for
your
app
and
it
will
then
be
able
to
detect,
is
the
app
online
or
not,
and
if
it's
not
online,
like
the
traffic
manager,
could
then
roll
traffic
over
to
two
other
nodes
in
your
application
to
make
sure
that
your
customers
are
still
happy.
You.
G
Yeah
they
could
do
that
or
even
like,
if
you're
like
in
the
middle
of
a
deployments
like
you
deployed
something
and
the
deployment
you
know
broke
something
you
didn't
play
something
correctly,
you
could
stop
the
deployment
and
then
roll
back
and
correct
things
in
that
way.
So
that's
what
that
does
so,
just
in
summary,
here's
all
the
stuff
that
you'll
see
in
preview,
one
we
show
most
of
these
things
I
think
we
showed
the
web
api
conventions
that
the
last
community
stand
up.
G
G
Yeah
we
will
publish
blog
blog
posts
on
the
ACE
minute
blog
the
web,
dev
blog.
As
soon
as
the
release
goes,
live,
you'll,
see
the
the
releases
go,
live
and
the
repos
and
yeah
they'll
be
also
be
I
believe
on
the.net
site,
the
the
courts
I
done
it
so
you'll
see
a
banner
advertising.
The
preview
there
as
well
great
okay,.
E
This
is
exciting,
so
I'm,
actually
relatively
new
on
the
dzo,
also
known
as
dramatic
zoom
out
technology
that
we
can
support
in
that
room
exist.
Well,
it's
not
that
I
know
of
I
know.
Damien
did
some
weird
thing
with
OBS,
so
may
I
I,
don't
know
what
we
do.
Do
we
just
dramatically
just
stop
and
also
the
recordings
running
from
your
side.
Yeah.