►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
D
A
C
B
C
B
A
C
Right-
let's
do
this
so
starting
here,
dotnet
Kampf,
two
exciting
things
to
know
about
Netcom
one
is
stuff
is
all
up
on
channel
9.
We
have
links
to
it
right
here,
tons
of
good
stuff.
We
also
have
going
on
around
the
world.
We
have
live
events,
so
we're
at
156.
People
are
still
adding
them
on.
They
go
through
the
end
of
October.
So
there's,
there's
tons
of
you
know
local
events.
You
can
get
it
on
all
over
all
around
the
world.
A
C
Question
so
what's
happening,
is
people
are
like
during
during
dotnet
calm
people
had
viewing
parties
for
it
and
they
were
like
watching
stuff
live.
What's
happening
now
is
people
are
actually
grabbing?
We
made
the
content
available
so
out
on
the
dotnet
presentations
events
in
a
box
content
we
have
women
like
the
decks,
are
available,
and
so.
C
Okay,
and
it
goes
from
a
like
one
or
two
hour
thing
like
you
know,
just
a
slightly
bigger
meetup
through
some
people
are
putting
on
full
like
one
and
two
day,
conferences
around
it,
so
yeah,
very
cool
stuff,
and
so
that
that's
the
other
kind
of
link
off
for
this
is
that
the
decks
are
available,
which
is
which
is
kind
of
neat.
We
work
as
high
as
I
promised.
Last
time.
I
was
on.
We
were
clubbing
people
over
the
head
as
they
left
their
presentations
and
grabbing
their
decks
from
them.
So
cool.
F
A
You
sound
perfect
John,
you
sound
like
you're
a
little
far
away,
apparently
maybe
put
your
mic
closer.
That's
just
this
is
what
this
random
called
Sebastian.
Who
works
for
us
is
suggesting.
James
sounds
like
he
doesn't
have
a
mic
at
all
and
that
we're
hearing
it
from
another
one
I
mean
I
can
hear
you.
So
if
you
just
check
again
yeah
no
I
can't
hear
you
through
there.
Actually,
so
you
keep
talking
John
I'm,
gonna
check,
James's
level.
Alright,
maybe
just
trying
to
cool
have
a
bit
higher
all.
C
Right
so
also
at
Nikon,
we
announce
a
new
foundation
website
and
some
things,
some
links
that
Scott
and
I
called
out
were
built
with
net.
So
this
is
a
really
cool
site.
Where
people
you
can
submit
a
project
and
let
people
know
about
it.
So
this
is
all
kinds
of
all
kinds
of
stuff.
You
know
websites,
open-source
projects
just
great
stuff
to
know
about,
and
they
have
they
have
featured
projects
and
stuff.
So
this
is
very
cool.
C
This
is
new
and
then
another
one
that's
been
out
for
a
little
bit,
but
I
just
want
to
call
it
out
again,
it's
discovered
net.
So
this
is
really
neat.
There's
there's
daily
news.
There's
projects
that
need
help.
They've
also
got
things
in
there
like
recent
issues
and
upcoming
events,
so
really
cool
stuff.
All
right,
so
we've
got
a
few
cool
series
going
on.
One
is
from
Jeremy
and
he's
got
this
getting
started
with
angular
on
dotnet
Core
2
1.
So
this
is
an
in-depth
look
talking
about
the
different
templates
and
stuff.
So
he's
he's.
C
You
know
this
is
number
one
and
there's
also
links
to
it
or
two
and
three
as
well.
So
you
know
really
good
to
see.
I
talked
to
Shane
boy
about
this
when
we
were
both
in
in
in
DC
Sydney,
and
he
was
telling
me
that
that
they're
getting
tons
of
you
know
huge
huge
billions
and
billions
of
hits
on
these.
These
posts
already
so
nock
is
server
over.
So
that
is
neat.
Another
cool
thing
that
I
just
saw
pop
up
was:
were
these
from
asp
net
hacker?
C
Honestly
I
forget
your
name:
asp
net
hacker,
it's
your
again!
So
Jurgen
has
a
series
on
customizing
asp
net
core.
This
is
interesting
to
me.
I
just
did
this
talk
at
NDC
Sydney,
where
I
was
saying
like
what
would
you
do
for
the
first
hour
after
file
new
project
and
of
course
he
posted
this
like
the
day
after,
but
but
I
thought
this
was
really
neat,
so
this
is
digging
into
logging
in
this
one
customizing
blogging
and
then
another
on
configuration
and
so
I'm
excited
to
see
this
he's
got
10
part
planned
out
for
this.
C
That
is
cool,
ok,
asp,
net
boilerplate.
So
this
is
something
we've
been
looking
at
for
a
while.
It's
been
it's
been
evolving
onto
over
time.
This
is
a
neat
kind
of
a
there's,
it's
kind
of
like
omakase,
safer
for
soccer
first
for
sushi
or
something
it's
like
a
you
know:
dotnet
template
asp
net
with
a
bunch
of
stuff,
already
kind
of
pre
set
up
for
you
what's
interesting
here
is
they're
actually
doing
a
full
rewrite
for
this.
So
it's
it's
going
from
ASP
dotnet,
boilerplate
they're
ringing,
renaming
it
to
a
BP
and
they're.
A
C
So
this
is
really
neat.
This
is
you
know
and
support
for
some
newer
things.
You
know
micro-services
theming,
modularization
and
all
kinds
of
stuff.
So
the
idea
here
is
a
kind
of
an
opinionated
look
at
file
new
project
and
it's
gonna
kind
of
yeah
and
then
and
they're
kind
of
checkable.
So
you
can
say
I
like
this
and
this
one,
but
I
don't
want
to
include
this.
A
C
C
B
B
C
One
one
exciting
thing
that
I
saw
in
here
was
support
for
template,
based
components
and
in
looking
through
there's
a
huge
threat
in
here
about
how
exactly
they
should
be
implemented
it
and
how
HTML
verse
WPF
vs
am
over.
You
know
which
kind
of
feel
to
go
for
in
there.
I
saw
then
digging
into
this
a
bit
that
Ryan
you'd
made
some
some
like
actual
commits
on
it.
B
C
B
So
there's
a
couple
things
here
for
templating
components,
so
we
added
support
for
razor
templates
to
the
Blazer
dialect
of
Razer,
which
previously,
if
you
had
done
this
it
just
wouldn't
compile
so
you've
added
support.
You
can
think
of
a
razor
template
if
you've
never
used
it
before
is
like
a
lambda
that
writes
HTML.
So
we
added
support
for
razor
templates,
so
you
can
create
sort
of
an
inline
template
and
you
can
pass
it
to
a
component
and
that
doesn't
do
a
whole
lot
of
its
own.
B
But
we
also
added
support
for
templates
to
have
multiple
child's
content
items
and
if
you,
if
you
haven't,
if
you
haven't
done
blazer,
think
about
like
a
grid
component
right,
you
have
a
template
for
the
headers.
You'd
have
a
template
for
the
rows,
maybe
a
template
for
the
the
footer
or
some
other
things,
and
we've
also
added
type
inference
for
generic
components.
So
you
can
write
a
grid
of
tea.
You
can
pass
it
a
list
of
person
and
then,
when
you
typing
inside
that
template,
you
should
get
completion.
Intellisense
fir
for
person.
B
B
B
A
And
so
blazer
is
kind
of
kind
of
all
that
today,
but
it
doesn't
do
any
of
really
of
the
server-side
integration
other
than
the
pure
server-side
laser
model
and
we're
over
the
coming
couple
of
months.
We're
going
to
figure
out
how
to
take
those
bits
and
graph
them
into
the
existing
sort
of
razor
pages,
MVC
view
razor,
etc.
There.
B
C
C
Alright,
so
this
was
neat,
this
was
at
MDC
Sydney
and
there
was
you
know,
announced
on
stage.
Barons
announced
identity,
server
as
part
of
asp
net
core,
and
then
he
tweeted
kind
of
some
stuff
about
how
its
how
it's
done
like
so
I
have
screenshots
of
code.
So
I
don't
really
have
like
anything
more
direct
to
link
to
on
this,
but
but
it
is
exciting.
Yeah.
A
C
Was
kind
of
interesting
here
this
is
how
to
disable
automatic
model,
state
validation
in
asp
net
core
to
one.
So
in
this
this
post
is
talking
about
you
know
in
a
lot
of
cases
you
will,
you
would
want
to
API
controller
is
going
to.
You
know
automatically.
Do
state
validation
in
the
case
that
you
wanted
to
do
something
like
return,
a
different
error
message
or
something.
If
you
wanted
to
customize
that,
then
this
is
talking
about
you
don't
have
to
it's,
not
all
or
nothing
you
can
go
through
and
just
suppress
the
model
state
validation.
C
B
C
Very
cool
yeah,
so
so
hello
to
you
Yemen,
so
so
hitch
hum
posted
about
you,
adding
tag
directions
so
for
a
tag
helper
component
for
languages
that
are
left
to
right
right
to
left.
You
need
to
be
able
to
specify
that
so
for
an
RTL
language,
so
spelling
out
here,
like
Arabic
Hebrew
Persian.
So
so
you
know
this
is
this
is
interesting
here
about
how
to
go
through
and
actually
specify
that
direction.
So
so
this
is
the
implementation
and
then
the
actual
kind
of
you
know
just
adding
that
in
so
so.
A
A
A
Yeah,
it's
interesting
localization
is
a
complicated
subject,
so
any
help
there
is
is
always
appreciated.
That's
good!
Oh
that's,
alright!
Well,
I
think
we
have
some
that
we
have
with
some
guests
for
a
reason.
Today
you
find
Foca
gonna
come
and
talk
to
us
about
endpoint
routing,
which
I
think
it
was
we
may
have
touched
on.
A
Our
goal
is
to
open
up
endpoint
routing
and
to
the
entire
pipeline
to
the
to
the
middle
pipeline,
so
that,
basically
anything
today
that
is
middleware
that
can
result
in
something
being
terminal
by
like
a
handler
in
the
old
world
like
something
that
actually
handles
the
requests
and
then
sends
a
response.
Any
middleware
that
does
that
is
a
candidate
to
turn
into
an
endpoint
routing.
A
Where
basically
yeah
well
endpoint,
where
we
actually
turn
we're?
Actually
you
say
that
at
lunch,
I
was
talking
to
Andrew
today
and
we
were
like
there's,
probably
a
new
name
here.
There's
like
there's
middleware
and
there's
like
end
where
or
there's
something
and
there
uses
endpoint
routing
and
so
as
an
example
signal
I
would
be
updated.
Static
files,
we're
having
discussion
right
now
is
health
checks
would
be
updated.
A
The
security
middleware
endpoints
because
they
all
have
terminating
your
URLs
if
they
hit
anything
that
you
would
want
to
either
be
able
to
generate
a
URL
for
or
you'd
want
to
go
through
a
matching
phase
early
to
say
yes,
I
this
view
RL
pattern
maps
to
this
piece
of
his
handler.
That's
going
to
run
eventually,
then
it
runs
through
the
rest
of
the
middleware
pipeline
and
then
that
handler
would
run
and
then
the
output
would
obviously
come
back
through
the
middleware
pipeline.
A
C
F
B
B
A
There's
complete
missing
gaps
like
today.
You
can
do
authorization
in
MVC
and
in
signal,
but
if
you
want
to
authorize
static
files
too
bad,
you
have
to
like
do
crazy
map
stuff
and
we
don't
actually
have
an
authorization
middle
way
like
we
don't
ship
that
card
authorization
today
is
done
by
the
endpoints.
The
things
that
want
to
off
raise
you
and
some
other
stuff
doesn't
do
it
so
in
the
future.
A
A
A
D
Brief
briefly,
it
was
global
routing
project.
Houdini,
there's
also
something
it's
sort
of
fallen
under,
but
in
point
routing
is
so
that's
final
name,
and
although
we're
talking
about
a
new
implementation
of
routing
a
lot
of
what
you
use
today,
as
still
holds
true,
especially
for
so
you'll,
still
see,
use
NBC
and
you're
still
calling
map
route
you're
still
sitting
up
conventional
right,
attribute
routing
on
your
controllers
and
actions,
but
all
the
metric
at
least
some
the
new
routing
engine
is
happening
under
the
covers.
D
So
the
way
it's
enabled
in
is
by
a
compatibility
switch
so
by
default.
If
you
upgrade
to
to
your
application,
isn't
using
it,
it
isn't
until
you
either
set
your
compatibility
version
to
latest
or
you
come
into
the
options
for
NBC.
There's
this
new,
enable
in
point
routing
and
sitting
that
true
will
also
enable
it
or
you
can
do
it
the
other
way
around.
B
Some
new
bug
fixes
other
things
like
endpoint
routing,
where
we
know
that
it's
not
a
hundred
percent
compatible.
You
have
to
opt
into
that
behavior.
You
have
to
choose
that
behavior
and
there's
a
bunch
of
these
things
that
are.
Some
of
them
are
bugs
that
we
fixed.
If
you
read
through
the
documentation
on
the
compatibility
version
you
know
or
somewhere
in
there,
I
wrote
a
novel
somewhere
in
there,
but
you
can
see
where
we've
painstakingly
documented
all
the
things
that
are
controlled
by
the
various
switches.
B
A
B
D
So,
although
in
most
of
the
new
features
are
sort
of
under
the
covers,
one
of
the
things
we
are
shipping
is
a
new
type
for
generating
links.
So
if
you
are
familiar
with
generating
links
today,
you
might
have
seen
this
I.
You
are
l
helper,
which
is
accessible
in
a
view,
so
in
this
case
we're
generating
a
link
to
an
action
so
index
on
home.
There
are
some
issues
with
this
one
being
that
it's
tied
to
NBC
and
views
was
that
accurate,
yeah.
B
I
mean
I'd,
say
some
of
the
issues
with
this
one.
This
API
has
been
around
forever
right
so
like
this
is
something
old
that
we
had
probably
MVC
one,
oh
I
wasn't
on
the
team,
then
so
it's
probably
probably
in
high
school
then,
but
the
the
main
pain
points
that
people
point
out
with
us
is.
This
request
is
actually
or
this
this
service
I.
You
are
L,
but
it's
not
actually
even
a
service.
So
you
can't
like
di
it.
B
B
So
it
works,
it
works
for
the
things
that
you
can
do
today,
right
which,
if
you're
writing
the
same
code
as
you
did
before
we
had
middleware.
It's
fine
but
I'd
like
to
think
that
we've
advanced
a
little
bit
so
we're
creating
a
new
singleton
service
as
part
of
the
endpoint
routing
feature,
so
it
won't
work
without
endpoint
routing.
Obviously,
because
it's
tied
to
that
and
this
new
feature
link
generator
is
a
singleton
service.
B
D
In
this
case,
just
because
we're
going
to
be
demoing
an
MVC
and
a
speed
on
it,
it's
part
of
a
request,
but
there
are
lots
of
overloads
on
link
generator
which
don't
require
an
HTTP
context
to
be
passed
to
it.
So
I
must
demo.
We've
got
a
link
generating
middleware.
Previously,
our
URL
helper,
it
was
you
kind
of
use
it
from
within
a
piece
of
middleware
and
all
we're
doing
is
we're
just
checking
the
path
that
path
equals
link.
D
B
Might
just
take
a
little
while
to
get
us
spun
up
and
the
hope
here
we're
interested
in
people's
feedback
on
this
as
its
developing
you'll
find
it
in
preview
3.
There
are
some
kind
of
earlier
iterations
of
it
in
preview.
1
in
preview
to
preview.
3
is
where
we
think
it
really
kind
of
comes
into
being
close
to
what
we
want
to
ship.
So
we're
interested
in
your
feedback
based
on
preview.
3
of
this
Leon.
B
A
B
A
B
Nice,
so
the
link
generator
was
accessible
for
through
controllers
and
if
you
were
smart
or
you
asked
us
probably,
if
you
asked
us
yeah,
we
could
tell
you
how
you
could
get
at
it,
but
I
want
to
emphasize
that
it
only
worked
with
in
the
context
of
MVC.
So
right
you
could
only
really
get
at
one
once
control
flow
had
entered
MVC
right.
D
So
like
now
that
we're
able
to
generate
a
link
and
you're
in
a
piece
of
middleware,
for
example,
we
could
redirect
submit
redirect
to
that
link.
So
maybe,
for
example,
you
had
a
piece
of
middleware
where
today,
if
you
are
unauthorized,
you
redirect
to
a
login
screen,
you
would
put
the
URL
and
the
configuration
now.
You
can
specify
how
you
go
to
this
controller.
Go
to
a
section.
There's.
A
A
Typically,
the
the
problem
with
that
today
is
that
it
results
in
you
having
to
take
the
like
a
string,
there's
a
string
in
your
startup
class.
That's
like
go
to
this
URL
when
any
error
occurs,
and
this
generally,
you
want
to
go
to
a
controller
or
a
razor
page.
What
you're
saying
now
is
we
could
if
we
could
go
and
update
that
middleware
support
using
this
thing
and
you
could
actually
have
a
proper
tight
way
of
getting
to
the
end
point.
Yeah
I
should
love
that
bug
will.
D
Lots
of
action
over
loads
and
methods
hanging
off
link
generator
so
before
we
got
a
path
by
rat
values.
This
is
a
helper.
Is
that
Ryan
added
just
last
night,
so
getting
a
URI
by
action
in
this
case
we're
passing
in
an
HTTP
context.
But
previously
you
saw
this
overload
didn't
and
as
well
as
getting
passed.
D
We
have
the
ability
to
get
a
URI,
so
a
fully
qualified
link
to
your
website
and
I
think
this
one
already
was-
and
in
that
case,
because
we're
not
specifying
the
address
and
the
scheme
and
that
sort
of
stuff
we're
pulling
it
off
the
HTTP
context.
But
again,
there's
lots
of
lots
of
overloads
on
this
where
all
optional
values
you.
A
B
A
B
Within
those
two
flavors,
there
are
two
flavors
there's
vanilla,
no
chocolate,
there's
with
an
HTTP
context,
means,
in
the
context
of
this
request,
so
same
host
same
scheme
same
all
that
stuff
or
there's
the
without
an
HTTP
context,
flavor,
which
doesn't
require
one
which
is
great
if
you're,
generating
email
and
a
background
task
or
something
there's
a
feedback.
We've
heard
a
lot
from
people
so
literally.
D
D
Man,
that's
pretty
much
it
for
link
generation,
so
another
new
feature
that
we're
adding
into
two
is
parameter
transformers.
So
this
is,
do
you
want
to
talk
about
parameter
transforms
like
the
yeah
okay?
So
today,
when
you're
generating
a
link,
you
have
the
ability
to
say
like
to
lowercase
people
of
us,
for
it
wouldn't
be
great
if
I
could
customize
it
further
I
make
it
lower
case,
but
I
separate
each
word
with
a
dash
or
an
underscore.
So.
B
D
So
so
now,
in
a
URL
previously,
you
would
have
seen
you
can
add
constraints.
So
you
could
say
this
ID
has
to
be
in
it.
We
have
extended
this
so
that
you
can
specify
more
than
constraints
and
your
URL
parameters.
You
can
specify
a
parameter
transformer,
for
example,
so
in
this
case
I'm
going
to
update
the
default
URL
to
slug
a
Phi,
the
controller
and
slug
a
Phi,
the
action
and
then,
when
I
run
this
and
I
look
at
the
generated
link.
D
B
How
this
works
under
the
covers
by
the
way
is
we
we
sort
of
like
rewrite
what
URL
the
routing
system
is
going
to
expect
for
this?
So
you
don't
change
your
code.
You
still
write
your
controller
name
in
your
action
name,
as
you
did
before
you
just
change
one
spot
in
the
route
or
I
believe
we
have
a
thing
on
options.
That
sort
of
like
do
this
to
all
my
routes.
Right
yeah.
We
have
a
thing.
We
have
a
thing,
that's
specific
to
MVC
that
says:
I'll,
give
you
a
parameter
transformer!
A
D
So
you
shouldn't
need
to
go
through
every
single
action
and
every
single
controller,
adding
the
slugloaf
I
think
you
can
do
it
in
one
place
and
start
up,
so
you
can
see
it's
specified
up
here.
So
the
the
way
we're
plugging
it
in
is
actually
by
the
old
constraint
system,
which
we
could
maybe
do
something
here,
but
you
know,
but
for
now
we've
got
constraint,
constraint,
met
and
then
missiles,
just
simple
an
implementation
of
the
eye
out
bound
parameter
transformer.
So
it's
just
doing
a
bit
of
regex
on
the
incoming
parameter
and
slugga
firing
it.
D
B
B
D
F
A
B
We
now
see
your
screen:
I
could
become
your
new
signature,
so
I'm
gonna,
I'm
gonna,
begin
this
a
little
bit
here.
So
let's
talk
about
tell
Damien
if
this
isn't
right.
If
this
is
too
small,
so
I'm
going
to
talk
a
little
bit
about
the
end
point
and
end
point
routing,
because
we
haven't
really
what
that
is
if
you're
curious
about
where
you
can
find
this,
if
you
think
this
is
cool
and
you
want
to
experiment
with
it
on,
you
can
on
to
to
preview
to
or
later
I'm
on
preview,
I
think.
B
So,
if
you're
curious
about
where
you
can
find
this,
you
can
actually
find
this
here
at
this
link,
and
this
is
the
index
dot
HTML.
So,
oh,
my
god,
is
that
a
thing
now
it
is
gonna
be
a
thing.
Okay,
it's
gonna,
be
a
thing.
So
I've
got
a
really
simple
little
MVC
app!
You
see,
I've
got
my
compatibility
mode
here.
I've
got
a
really
simple
app
with
an
index
and
an
error
action
on
home
controller,
and
that's
that
is
all
I've
got
here
and
I've
got
the
basic
use
MVC.
B
You
know
traditional
conventional
default
route
that
you're
used
to
seeing
here
so
I'm
gonna
begin
this
as
well.
Sorry
about
that.
So
what
I've
got
here
is
I've
got
a
little
demo
page.
Then
it's
going
to
list
all
the
endpoints
and
you
can
think
of
an
endpoint
abstractly
as
a
thing
that
can
be
routed
at
or
can
be
linked
generated
at.
B
B
I've
got
home,
I've
got
home
index
with
an
ID
parameter,
I've
got
home
air
with
an
optional
ID
parameter
and
if
you're
familiar
with
or
you
play
with
MVC
routing
before
you
know
that,
like
all
of
these
things
will
work
right
if
I
put
in
home
here
it
takes
me
the
same
place
if
I
put
in
home
index
here
it's
put
in
home
index
here,
it's
gonna.
Take
me
to
this
action
again.
If
I
put
in
home
error
here,
I'll
see
the
error
page
right.
So
everything
kind
of
I
think
those
are
routing.
B
That's
what
you'd
expect
the
way
that
this
works
is
when
you
write
this,
we
call
this
a
conventional
route
because
it
has
controller
in
action
in
in
the
names
we
denormalize
these
now
and
that's
the
way
that
we
sort
of
build
this
efficient
like
routing
table
of
event
points.
So
we
denormalize
this
route
by
performing
substitution.
B
So
we
would
substitute
for
all
the
controllers
and
for
the
actions,
the
reule
and
values
into
this
template,
and
that's
what
gets
us
this
this
list
of
stuff
and
the
reason
why
we're
doing
this
is
that
this
is
really
what
we're
after
here
and
so
we've
ended.
Up
with
this
is
this
is
a
depiction
of
what
the
implementation
is
like.
B
We
have
this
very
efficient
little
tree
here
or
try
if
you're,
if
you're
hip,
to
that
where
all
of
these
edges
are
URL
path
segments,
and
so
we
traverse
that
you
or
we
tokenize
the
URL
path
on
slashes,
and
then
we
traverse
it
based
on
the
text
and
in
each
of
these
little
nodes.
We
just
have
to
do
a
very
simple
matching
operation
and
you
could.
B
If,
at
any
point,
there
is
no
transition
out
of
the
state
you're
in
then
that's
a
404,
we
forgive
it.
We've
given
up
at
that
point
so
like
to
trace
this
path.
I
could
say
home
index
17,
because
my
my
route
is
controller
action,
ID
and
that'll
work
right.
It's
going
to
re-render
this
page,
and
so
that
path
would
look
like
well
home
and
then
index,
and
then
this
is
a
star.
So
this
would
accept
anything
and
then
I
end
up
here
right.
B
So
this
is
just
a
little
depiction
of
how
it
works
so
to
sort
of
get
a
little
deeper
here.
I've
got
this
person
controller
and
it's
not
showing
up
because
I
haven't
defined
any
actions
here.
Yet
so
let
me
just
uncomment
some
of
these
and
I've
got
HTTP
GET
HTTP,
put
so
on
in
here,
typical,
typical
API
stuff
and
I'm,
going
to
relaunch
this
and
we're
going
to
look
at
how
this
graph
and
this
list
have
changed.
So
Avinash
asks.
How
is
this
different
from
current
routing?
So
it's
not
very
different
from
the
tree.
B
Been
using
the
old,
conventional
routing
system,
you
can
think
of
the
routes
that
you
put
in
startup
code.
Here
is
one
system
and
the
routes
that
you
put
in
attributes
is
another
system
right.
Razor
pages
use
this
to
attribute
routing
system.
We
say,
attribute
routing
versus
conventional
routing
and
they're,
both
a
difference
in
how
you
configure
it
and
a
difference
in
how
it's
implemented
today.
Right
today,.
A
B
B
B
A
B
B
D
A
D
B
F
B
Some
cost
associated
with
process
as
well
yeah
processing,
individual
segments,
but
that's
fairly
optimized,
okay.
So
the
main.
The
main
worry
is
that
if
you're
feeding
us
a
lot
of
the
wrong
type
of
data,
it
could
be
expensive,
I,
say
so
unpacking
this
a
little
bit.
I've
updated
this
and
I've
added
that
person
controller.
So
you
can
see,
we've
got
another
top-level
branch
coming
off
here
and
then
there's
a
person
with
an
ID
parameter
which
is
I
believe
these
actions
so
get
an
update.
B
B
B
So
if
it's
a
get
we're
going
to
go
to
that
action,
which
is
this
get
all
action
here
and
then,
if
it's
not
something
not
that
we're
gonna
do
something
we
haven't
been
able
to
do
for
a
while
that
people
who
are
used
to
old
web
api
are
missing.
Sadly,
is
we're
going
to
return
an
HTTP,
4
or
5,
because
this
system
has
that
capability
built
in?
So
that's
a
that's
a
thing
for
if
you're
somebody,
who's
frustrated,
he's
been
frustrated
with
that
in
the
past.
D
B
D
There
was
and
many
ways
routing
was
very
decoupled
from
him
DC,
but
at
the
same
time,
logic
which
you
need
if
you're
writing
a
web
api
was
embedded
in
enemy
C.
So
I
was
both
decoupled
in
effect,
that
performance
wasn't
as
good
as
it
could
be
and
tied
together
and
that
it
was
difficult
to
use
routing
by
itself.
Yeah.
B
So
now
I've
uncommented-
these
consumes
methods
here
and
they're,
both
named
person,
crate
Jason,
which
I
think
was
just
influenced
by
James,
but
one
of
them
one
of
them,
is
meant
to
handle
XML
and
one
of
them
is
meant
to
handle
Jason.
This
is
a
somewhat
common
thing.
If
you
have
multiple
content
types
you
have
to
handle,
sometimes
they
can
be
the
same
model.
Sometimes
they
can
write.
I'm
gonna
correct
this,
so
Christian.
B
B
B
So
that's
that
sounds
like
a
people's
I,
so
consumes
is
a
feature
of
routing
in
MVC
that
will
branch
based
on
the
content
type.
So
we
can
branch
based
on
the
HTTP
method
we
can
select
based
on
the
HTTP
method.
We
can
also
branch
based
on
the
content
type,
so
that
also
gets
built
into
this
graph
can
I
make
my
own
ones
are
those
like
me.
B
E
B
B
To
see
what
people
will
build
is
this,
so
we
can
bake
into
the
graph
this
very
efficient,
little
branching
thing
of
tokenizing,
the
URL
walking
all
the
segments,
so
Oliv
n
with
respect
to
the
number
of
segments
and
then
oh
of
n,
with
respect
to
the
number
of
policies.
So
policies
are
things
like
HTTP
methods
or
consumes
you'll
notice
that
my
original
cute
little
graph
of
this
application
is
unchanged.
So
these
things
are
very
localized
like
there's
a
consumes
policy
here
and
it's
completely
pay-for-play.
B
It
only
shows
up
when
you're
rotting
to
here
doesn't
influence
the
graph
generation,
as
I
hey
this
other
stuff.
So
that's
some
of
the
stuff
we're
doing
and
we're
basically
trying
to
make
make
the
extensibility
for
this
be
scalable,
make
the
performance
of
it
be
scalable
and
make
as
much
of
MVC's
action,
selection
and
routing
stuff
be
baked
into
a
lower
layer
of
the
system
where
it's
more
introspective
and
more
reusable
yeah.
D
B
I
have
I,
have
prepared
some
slides
and
there's
a
couple
of
things
that
we're
doing
to
test
this.
One
of
the
things
that
we're
doing
to
test
this
is
we've
actually
Oh
not
going
to
go
to
the
slides.
Yet
one
of
the
things
that
we've
been
doing
to
test
this
is
we
have
taken
the
route
table
of
asher
and
the
route
table
of
at
least
their
public
API
surface.
So
I
wrote
a
handy
little
tool
here
somewhere
in
here.
It's
called
the
swag
gatherer,
so
I
wrote
this
little
tool
here
that
takes
swagger
files.
B
So
if
you're
familiar
with
the
swagger
open,
API,
the
like
API
spec
takes
a
bunch
of
swagger
files
and
then
creates
for
us
a
benchmark
that
we
can
run
for
testing
so
for
a
performance
testing
of
routing.
So,
for
instance
like
this
one
is.
This
is
a
jurors
route
table
and
you
can
see.
There's
5160,
endpoints
and
they're
all
listed
here.
So
there's
all
public
information
I'm
not
leaking
anything
secret.
B
B
Secret
police
to
my
house,
but
these
are
a
jurors
like
management.
Api
is
right.
There
publicly
documented
management.
Api
is
dumped
into
the
form
of
a
benchmark
that
we
use
for
routing.
So
all
of
our
all
of
our,
like
benchmarking
and
performance
testing
for
this
has
largely
been
based
on
real-world
stuff.
So
we
use
Azure.
We
use
github
get
hubs.
Public
API
is
significantly
smaller
because
this
all.
B
A
B
Thing
that
we're
doing
for
testing
is
we're
doing
testing
with
these
very
large
kind
of
large
medium
small
sets
of
AP,
honest
that
are
based
on
real
world
definitions.
Another
thing
that
we're
doing
for
testing
is
I
have
some
results
from
Tekken
power.
So
if
you're
familiar
with
Tekken
Power
Tekken
power
is
a
set
of
benchmarks
for
web
frameworks
and
they're
kind
of
serve
as
these
minimal
benchmarks
that
pretty
much
anybody
can
implement
and
you're.
B
B
B
B
D
A
A
B
And
most
of
the
savings
here,
weren't,
actually
URL
processing
had
something
to
do
with
it.
The
URL
processing
of
the
old
system
and
the
new
system
for
a
single
segment
was
kind
of
a
wash,
but
we
have
a
new
system
that
has
a
lot
more
features
and
a
lot
more
scalability
and
the
purpose
better
for
simple
cases
do.
B
B
B
E
C
C
B
B
B
With
more
certainty,
what
URLs
your
actions
are
going
to
match
if
you're
doing
attribute
routing
them
with
conventional
routing,
we
sort
of
have
the
technology
to
build
a
conventional
routing
experience
for
it,
but
we
haven't
had
the
we
haven't
really
seen
demand
that
justifies
putting
the
work
into
it.
Is
that
kind
of
good
you're
asking
or
yeah.
A
B
A
B
The
total,
the
the
number
you
should
be
really
interested
in
here
is
the
top
top
bar.
You
can
see
like
right
here.
We
traded
some
some
time
and
startup
code
for
some
time
on
the
first
request,
which
is
kind
of
a
wash
write.
The
number
you
should
be
interested
in
is
this
top
one,
so
tiered
jet
for
a
really
really
bare-bones
MVC
app
took
off
about
200
milliseconds
of
startup
time
for
another
one
of
the
ones.
I
looked
at
I
think
it
was
the
one
with
the
F.
The
fortunes,
tech
and
power
test
with
NBC.
B
A
F
A
Now
we
very
much
hope
to
leave
it
on
in
to
ITM
by
default,
but
they're
very
much
relies
on
us
getting
feedback
from
folks.
In
fact,
we
always
in
shipper
in
this
morning
and
there
was
a
bug
that
came
in
because
a
partner
had
started
seeing
a
particular
issue
when
they
went
eh
it
was
enabled.
So
we
need
that
type
of
feedback
to
have
confidence
that
we
can
release
with
this
on
by
default.
But
it's
fantastic
so
to
see
the
subs
and
provements.
Is
this
the
assumption
here?
A
That
we
use
befall
if
the
framework
gets
pre
jittered
before
you
even
run
your
app
isn't
particularly
good
at
doing
other
things,
and
so,
like
you,
have
to
pay
the
full
JIT
cost
to
get
things
like
generics
and
pain,
folks
and
things
to
work.
Well,
do
we
have
an
idea
what
it
is
here?
Is
it
just?
Maybe
the
lower
quality
first
run,
it's
just
faster,
and
it's
just
that's
what
all
it
is
here.
Yeah
there.
B
There's
also,
you
have
to
reckon
with
things
that
aren't
cross
trend
like
your
app
isn't
crossed
right,
right,
I,
don't
have
a
I
haven't
done
a
profiling
to
figure
it
out.
I,
just
I
looked
at
this
data
and
I
said:
James
was
this
you
and
he
said
yeah.
That
was
me
actually
I
told
him.
I
said:
hey
James
I
think
this
was
you
and
I
said:
hey
Seb.
What
do
you
think
about
this
and
he
said?
Oh,
no,
that's
huge.
It
say.
A
D
B
D
A
A
D
A
B
A
Congratulations
to
those
who
have
stuck
on
the
live
stream.
This
long,
we're
54,
55
minutes
in
now
and
we're
finally
we're
going
to
show
you
some
like
super
future
stuff.
We
haven't
talked
much
about
300
on
this
show,
simply
because
three,
oh
the
public
messaging
about
302
date,
has
all
been
about
winforms,
WPF,
obviously,
and
then
there
was
a
bunch
of
the
features
that
come
along
with
that
we're
still
busy
working
on,
and
so
we're
not
really
wanting.
A
We
don't
want
to
jump
ahead
and
start
talking
about
all
the
great
age
we
need
coolest
ring
ever
features
when
we
don't
even
know
what
they
are
yet,
because
we're
still
wouldn't
the
to
two
features.
But
a
couple
of
the
people
of
the
members
of
the
team
James
is
one
of
them
has
made
finish
their
to
work
and
is
now
looking
at
three
oh
stuff.
So.
A
D
Right
so
endpoint
routing
is
more
than
just
performance
improvements.
So
that's
what
you'll
see
in
you
also
receive
a
link
generator,
but
there
are
a
number
of
bigger
goals
around
endpoint
routing,
so
the
first
one
we'll
talk
about
is
when
you
call
use
MVC
that
happens
of
a
very
end
of
your
middleware
pipeline
and
your
routers
matched
and
it's
executed.
So
your
your
routers
match
to
an
action
and
then
action
is
executed
straightaway
right
up
a
very
end.
So
if
I
bring
up
a
PowerPoint.
D
Yeah
we
are,
he
already
knows
where
this
is
going
spoilers.
So
imagine
you
had
two
pieces
of
metal
where
you
had
your
custom
middleware
and
you
had
routing
middleware,
which
was
basically
what
happens
worth
use
NBC.
So
a
request
comes
in
slash
admin,
your
custom,
middleware
executes,
sit
and
then
flows
along
through
to
your
routing
middleware
and
the
current
routing
middleware
router
mattres
it
to
an
action.
Ms
case
admin
controller
index
at
then
execute
the
action,
and
then
the
request
flows
out
so
I
have
a
problem
with
this
today
is
the
custom.
D
Metal
ware
has
no
knowledge
of
what
the
final
action
is.
So
you
know
the
URL.
You
know
it's
slash,
admin,
you
don't
know
exactly
which
action
that's
going
to
like
someone
could
change
your
route
with
an
MVC
and
suddenly
slash
admin
is
going
instead
of
to
index.
It
could
be
going
to
a
no
home
or
few
all
or
something
else
like
we
could
just
change
the
default
action
at
that
point.
D
B
B
A
An
oops
yep
and
in
the
old
well
with
signal
prior
to
call
signal
a
hubs
had
its
own
filter
pipeline
and
there
was
an
exact
same
thing
like
you
could
plug
stuff
into
the
filter
pipeline,
but
it
was
also
a
middleware
itself
and
so
you'd
have
to
make
a
decision.
It's
like
it
took
on
the
pipeline
does
ago.
Middleware.
Do
they
work
together?
What
order
of
the
end?
This
is
all
the
same
killer,
fish
like.
D
A
Interesting
because
we're
peddling
katana
prior
to
project,
Kay
and
Enix
needs
make,
or
we
had
a
lot
of
discussions
about
these
types
of
features
and
where
does
the
metadata
about
an
endpoint
belong?
Some
some
folks
advocate
for
I
want
to
put
all
my
things
in
a
single
place
and
they
want
one
file
in
their
application
where
all
the
metadata
for
a
subsystem
like
cos
or
whatever
is
in
and
then
other
folks
are
like.
No,
no
like.
It
really
makes
sense
that
I
want
to
put
the
metadata
as
close
to
the
executing
resource
as
possible.
A
But
then
maybe
the
thing
that
actually
there
operates
on
that
metadata.
It
could
be
anywhere,
it
doesn't
matter,
it
shouldn't
have
to
be
in
the
subsystem,
and
so
they,
whether
it's
cause
the
authorization
or
routing
information
or
you
know,
Koenig
whatever
might
be.
We've
gone
back
and
forth.
I
think
it's
fair
to
say
that
as
a
team,
the
the
idiom
that
we've
kind
of
gravitated
towards
the
framework
is
Vlado,
which
is
we
kind
of
want
all
this
metadata
to
be
as
close
to
the
endpoint
as
possible.
A
So
if
you're
in
a
signal,
a
hub
which
is
a
class
you
put
attributes
on
that
hub
or
even
on
the
method,
if
you
want
some
things
to
just
be
for
certain
methods
and
same
for
controllers,
an
npc,
you
put
them
on
the
controller
class
or
you
put
them
in
the
action
method.
If
you
ever
raise
a
page,
you
can
put
them
on
the
page
model
or
eventually,
perhaps
you
can
put
them
in
your
view
start
or
something
like
that,
it
doesn't
mean
you
don't
have
a
conventional
way
of
doing
it
or
an
imperative.
F
A
A
D
The
big
problem
here
is
the
fact
that
we
match
at
the
end,
what
happens
if
we
match
of
a
cert?
So
now
we
have
endpoint
routing
middleware.
Our
request
comes
in.
We
match
it,
so
the
deer,
the
that
Ryan
showed
earlier
matches
to
a
controller
action,
then
custom
middleware,
runs
a
custom.
Middleware
is
able
to
look
at
the
context
of
request
and
see
hey.
An
endpoint
has
already
been
matched
the
matches
to
an
action
and
and.
B
D
Okay,
so
one
one
important
thing
to
talk
about
when
we're
talking
about
an
end
point
and
end
point
is
more
than
just
a
URL
and
it's
more
than
just
an
action,
so
the
annex
to
execute
the
thing
that's
been
matched
to
it's
also
bagged
metadata.
So
in
this
case,
if
we're
putting
an
attribute
on
our
action,
that
attribute
becomes
a
piece
of
metadata,
so
in
our
custom
middleware
we
can
get
our
endpoint
and
then
we
can
look
at
the
various
bits
of
metadata
and
we
can
sort
of
reason
and
change
how
the
application
work.
D
So
our
custom
middleware
could
be
cause
middleware.
So
we
could
take
a
look
to
see.
Has
the
has
the
request
actually
got
action
access
to
this
or
not
mm-hmm
cool?
So
that's
it
for
slides.
So
if
we
take
a
look
at
the
code,
we
can
see
there's
no
longer
at
use
MVC
at
the
bottom.
We
have
use
endpoint
and
at
the
top
we
have
this
user
endpoint
router.
D
So
one
thing
which
might
be
a
bit
different
to
what
you're
used
to
is
now,
instead
of
calling
mapper
out
down
at
use,
MVC
of
a
bottom
we're
calling
an
MVC
route
over
top
and
just
that's
a
conceptual
thing,
effects
that
we're
now
doing
a
matching
at
the
beginning
of
our
middleware
pipeline.
Rather
than
at
our
end
and.
B
B
D
Or
is
the
James
friction
a
temporary
branch?
Okay?
Okay,
so
if
we
take
a
look
at
our
middleware,
we
can
see.
We've
got
our
HTTP
context
and
we're
getting
from
this
a
feature
called
the
endpoint
feature
and
on
an
endpoint
feature,
live
us
an
endpoint.
So
we're
doing
this
because
if
we
weren't
match
to
anything
potentially
this
could
be
null
or
so
this
could
be
an
olaf
is
no
match
and
then,
from
our
end
point
we're
looking
at
the
metadata
and
we're
getting
our
authorization
metadata
attribute
and
we're
saying
hey.
D
Let's
only
run
this
authorization
middleware
eff,
someone
added
some
metadata
to
it
to
say
it
should
run.
It
requires
some
kind
of
role
and
then,
after
all,
is
required.
We
come
down
and
we
we
check
the
super
secret,
query,
string,
authentication
method
and
if
the
value
of
role
matches
one
of
our
valid
roles
within
the
metadata,
so
we've
got
a
some
roles
hanging
off
our
metadata.
Then
we
allow
the
pipeline
to
continue.
Otherwise
we
say
you
are
unauthorized
and
we
tell
them
what
endpoint
they
were
not
authorized
to.
D
So
how
would
we
get
metadata
on
it?
So
it
would
just
be
as
simple
as
adding,
because
are
we
running
it
would
be
as
simple
as
putting
a
attribute
on
this.
So
when
NBC
starts
out,
it
provides
a
collection
of
endpoints
to
the
routing
system
and,
as
part
of
that,
obviously
like
figures
out
all
the
creek
URLs
for
them,
but
it
also
clicks
various
bits
metadata
about
all
those
endpoints
and
one
of
the
things
that
does
is.
A
B
We
would
retrofit
pretty
much
the
things
that
you
have
access
to
today,
we'd
be
looking
to
retrofit
in
a
way
that
they
still
work
in
the
way
that
you're
familiar
with
right.
But
it's
a
system,
that's
a
little
bit
more
inclusive
and
like
lots
of
features,
get
to
play
together
in
the
system,
rather
than
it
being
a
filter
that
just
MVC
understand.
D
D
So
our
app
starts
up.
We
had
our
middleware,
so
we
can
see
we
have
a
endpoint
so
in
this
case
we're
mapping
to
this
index
action
on
the
home
controller
and
we
have
a
route
pattern.
In
this
case,
a
route
pattern
is
an
empty
string,
because
this
is
the
default
page
for
the
website
and
we
can
see.
We've
got
this
metadata
collection
and
with
them
that
metadata
collection.
We
can
then
pull
out
the
authorization
mitad
out
of
it
with
that's,
been
populated
and
to
the
metadata
by
NBC,
and
then
we're
able
to
interrogate
it.
C
A
Well,
it's
actually
interesting,
like
application
insights
today,
when
you
add
it
to
a
speed
net
call,
either
programmatically
or
via
the
light-up
features
in
Azure
it.
Actually
it
wants
to
log
what
request
is
processing
right,
but
you
have
to
think
of
the
order
of
execution
of
what's
going
on
today
and
they
souvenir
core
application.
The
MVC
action
isn't
known
until
well.
A
After
the
request
has
started,
and
after
pretty
much
all
the
other
middleware
has
already
gone
through
the
the
incoming
phase,
and
so
what
they
have
to
do
is
they
have
to
inject,
not
only
listeners
that
you
know
understand
when
the
request
actually
started
from
the
kestrel
point
of
view,
the
service
point
of
view,
but
they
then
have
to
hook
into
MVC
using
a
different
diagnostic
socialist
nür
to
understand.
Well,
what
action
am
I
going
to
be
running
against,
so
they
can
get
the
action
name
so
there,
rather
than
just
saying
all
I
hit
this
URL.
F
A
A
A
D
B
D
A
fake
one,
no
I
was
just
going
to
say
so:
that's
one
of
the
goals
of
endpoint
routing,
so
it's
to
be
able
to
break
I
would
be
able
to
break
routing
out
from
something
which
just
happens
with
an
MVC
to
something
which
happens
throughout
the
entire
quest
pipeline,
and
then
you
can
hook
into
it.
So
another
thing
is
being
able
to
easily
add
and
define
your
own,
your
own
endpoint.
So,
for
example,
health
checks,
yeah.
B
D
D
A
E
A
A
D
Exactly
yes,
yeah
exactly
so
that's
that's
exactly
if
we
come
and
look
at
the
source
code
we're
passing
in
a
T
which
in
this
case
it's
a
I
importing
convention,
Ralf
Koetter,
we're
saying
for
this
metadata.
Add
that
attribute
the
piece
of
metadata
doesn't
need
to
be
an
attribute.
This
was
just
a
demo.
A
D
A
And
in
Christian
makes
the
point
that
this
will
be
awesome
for
an
indie,
server,
swashbuckle,
etc.
They
say
any
of
the
other
systems
on
the
planet
that
want
to
know
about
all
the
stuff.
In
your
app
and
the
thing
I
was
that
thought
I
was
having
before
was
like.
Now
you
can
imagine
today
we
we
have
the
the
various
swagger
or
open
API
system
within
swag
or
swashbuckle
and
I
think
Ryan.
You
said
they
plug
into
our
our
and
put
us
at
the
metadata
API.
A
Imagine
that,
but
now
they're
plugging
into
the
endpoint
router
version
of
that,
and
so
now
they
can
get.
You
could
add
an
it.
You
could
have
Nancy
and
MVC
running
in
the
same
app
and
both
feeding
into
your
swagger
dogs,
all
via
endpoint
routing.
Rather
they
have
to
add
the
Nancy
integration
plus
the
the.
B
North,
the
North
Star
here
is
like
I,
want
to
use
some
other
component
inside
my
app.
Let's
say
a
you
know:
streaming
logs
provider
right,
an
endpoint
that
can
deliver
me
streaming
logs
to
them.
I
don't
want
to
have
to
care
what
technology
they
use
to
implement
that
right
right,
but
I
want
a
uniform
way
to
say
configure
security
or.
A
Cause
or
whatever
might
be
yeah
absolutely
sunny.
Is
she
thinking
back
in
system
web
days
we
had
like
the
location
element
in
your
web,
the
config
file,
and
because
everything
was
basically
handled
by
modules
and
handlers,
you
would
just
say:
oh
assuming
the
thing
that
you
were
trying
to
protect
or
configure
was
a
handler.
You
could
just
have
a
location
thing,
say
the
path
and
then
everything
under
they
applied
to
that
thing.
A
That
was
all
configuration
first,
it
was
a
lie:
yes,
centric
we're
kind
of
coming
full
circle
and
now
say
more
in
a
code
first
world
now,
but
we
didn't
we'd
had
this
super
flexible
pipe
line
called
middleware
where
you
just
like
stack
stuff
together,
but
it
doesn't
nothing
knows
about
anything
else.
Except
the
next
thing
that's
running
and
even
then
it
doesn't
know
where
it
is.
It's
just
it's
just
a
function
which
I
keep
going
one
step
ahead.
D
A
D
Consumes
I,
all
of
all
that
was
embedded
within
with
an
MVC
right,
so
it
should
be
possible
for
anyone
writing
a
web
application
framework
in
the
future
to
take
endpoint
routing
and
quite
easily
plug
it
in
like
all
it
is.
Is
you
just
start?
Your
framework
just
starts
defining
routes
and
then
use
endpoint
routing
will
match
up
those
routes
and
then
it
will,
when
it
executes
down
here
on
use
endpoint.
It
will
call
into
your
your
web
framework.
So
III
don't
know
if
David
wants
me
to
show
this,
but
he's.
D
This
is
a
little
web
framework
that
David
Fowler
write
could
be
called
a
micro
framework
and
micro
work.
So
if
there's
no
MVC
involved
and
just
as
a
as
a
thought
exercise
earlier
in
a
week,
we
replanted
this
on
top
of
endpoint
routing
and-
and
it
was
a
very
simple
change-
it
was
like
maybe
one
or
two
hundred
lines
of
code.
So
now
what
we
have
happen
happening
here
is
we've
still
got
our
use,
endpoint
routing.
We
have
it
as
a
different
method,
rather
than
as
a
lambda.
That's
just
syntax
again.
D
We
have
used
use
endpoint,
but
our
our
endpoint
routing
in
this
case,
rather
than
met
NBC
route.
We
have
these
sort
of
custom
methods
that
this
framework
provides.
So
it's
a
custom
way
of
saying
hey
for
verse.
Products,
API
get
all
method
go
to
this
location
and
again
these
are
just
music's
routes
and
the
answer.
D
A
Funny
I'm
Hashem
has
a
question:
can
we
use
the
link
generation
to
generate
URLs
on
the
fly
for
api's,
Docs
or
temp
URLs
for
resources
etc?
Can
we
use
the
link
generation
to
generate
URLs
on
the
fly
for
API
Docs?
Yes,
yes,
absolutely!
So,
if
your
ex
right,
if
assuming
your
app,
is
running
but,
for
example,
the
the
various
subsystems
that
produce
swagger
Doc's
live
in
the
browser
or
as
an
endpoint
would
use
this
to
generate
the.
B
A
And
he
makes
any
disavow
the
follow
up
comment.
His
rat
configuration
in
one
place
reminds
him
of
the
Razr
pages
routing,
so
razor
pages
is
actually
an
interesting
example.
It's
in
that
Ryan
said
before
it's
built
on
the
attribute
writing
system,
but
most
of
it
is
actually
convention
in
the
fact
that
the
name
of
your
file
is
what
denotes
the
route
as
in
the
path.
But
then
we
give
you
a
way
to
override
that,
but
it
is
imperative.
It's
not.
You
know
you
can't
put
an
attribute
on
anything.
A
You
have
to
go
into
your
startup
and
say
add
stuff,
so
you
do
get
this.
What
we
talked
about
before
you
can
put
it
on
the
resource,
but
in
this
case
it's
the
file
name
and
then
we
added
the
ability
into
one
to
say
app
page
and
then
override
the
right
completely
and
or
you
can
do
it,
the
code
cuz,
you
might
wanna,
do
it
more
centrally.
So
we.
B
F
A
Pull
the
cord.
Thank
you
very
much
for
coming
along
I.
Hope.
Folks
got
a
lot
out
of
this.
I
think
this
is
our
first
in-depth
look
at
this
feature.
Just
to
recap,
endpoint
routing
is
in,
but
is
exclusively
for
use
by.
Mvc.
Mvc
will
use
this
by
default
if
you
set
the
compat
mode
2
to
2,
which
obviously
new
projects
well,
when
you
upgrade
to
2
you'll
have
to
flip
that
manually.
If
you
want
to
use
the
endpoint
we're
adding
to
get
the
advantages
other
than
the
perf
improvements
you.
F
D
A
We
got
that
nice
little
URL
transformer
things,
so
you
can
do
slugga,
fication
and
whatever
create
other
crazy
things
that
you
wanted
to
turn
it
into
clean,
long
or
something
on
it,
and
so
then,
in
300
we
saw
a
preview
of
what
this
might
turn
into
in
terms
of
really
pushing
it
out
of
NBC
and
make
it
all
available
to
everybody
thanks
a
lot
for
coming
John
thanks
for
you
know,
sitting
your
office
and
not
saying
much
for
the
last
hour.
That's
great
appreciate
it.
I
was
I.