►
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 the week: https://www.one-tab.com/page/nWJFdgZ5QF27LfdAG4XIBw
B
A
B
A
B
They're
there
it's
a
really
cool
community,
really
tight,
like
family.
There
I,
don't
know
I
I
kind
of
got
my
start
in
both
some
open
source
stuff
and
like
that
was
my
first
non
I
worked
in
like
corporate,
you
know
back-end
shops
and
then
this
I
actually
worked
in
a
consulting
thing
with
Phil,
hack
and
and
some
friends,
and
we
built
like
websites
and
we
used
enn.
So
so
it
was
cool
at
giving
the
keynote
and
being
able
to
like
kind
of
call
back
to
some
of
that
stuff.
Very.
C
A
Ever
we
do
have
will
let
it
secret
that
the
viewers
in
on
a
secret-
you
couldn't
hear
us
when
we
done
before
so
we
had
to
change
you're
currently
running
through
a
different
microphone
you're
using
the
crappy
little
camera
microphone
up
there
to
hear
us,
but
that
doesn't
affect
him
watching
the
stream.
So
you
know
whatever
you
gonna
do.
So
what
is
I
was
on
vacation
last
week,
so
we
would
be
working
on
this.
I
was
in
sunny
Hawaii
wondering
why
people
go
skiing
when
they
could
go
to
the
beach
and.
A
C
B
D
B
A
A
Can
see
juxtapose
that
with
what
I
dealt
with
the
week
before
my
bid
would
to
break
to
Hawaii
where
no
one
was
at
work
here
and
my
kids
were
at
home
because
we
were
all
snowed
in
under
four
feet
of
snow
and
I
had
to
dig
out
my
driveway
every
morning
for
three
or
four
days
in
a
row.
So
yeah
we
just
weren't
that
interested.
But
some
people
went
and
saw
more
snow
because.
B
A
B
B
B
A
A
A
B
A
B
A
B
A
So
we
we've
yet
to
integrate
all
the
a
spinet
core
and
dotnet
core
stuff
into
that.
The
way
that
we
want
to
that
won't
happen
until
further,
along
in
the
dotnet
core
three
sort
of
milestones.
So
right
now
you
have
to
choose
I
mean
it's
like
it
always
has
been
right.
You
Tues
a
spinnaker
application.
Then
you
get
the
one
a
spinet
dialog,
where
you
then
choose
other
stuff,
and
we
don't
want
that
to
be
the
way
moving
forward.
A
You
should
be
able
to
type
in
the
new
search
experience
and
say:
hey
I
want
to
build
an
API
and
it
should
filter
and
give
you
the
API
template
that
doesn't
work
today
right
so
a
couple
more
months
before
we'll
get
that
type
of
stuff
working
but
yeah.
The
other
thing
that's
jarring
me
actually
talking
about
this
is
the
the
c-sharp.
A
Editor
has
new
colorization,
and
I
mean
it's
great,
but
my
brain
still
can't
get
use
of
the
fact
that,
like
instance,
methods
are
all
brown
now
I
use
the
normal
theme,
not
the
dark
theme
and
like
okay.
My
keywords
are
like
magenta,
like
if
an
Elsa,
magenta
and
then
other
keywords
blue
and
they
method
names.
This
brand,
like
I
said,
is
brown
and
static
methods
have
a
different
color.
It's
it's
very
colorful,
I'll,
put
that
and
so
I'm
still
my
muscle
memory,
I
memory,
my
ocular
memory
isn't
quite
there
yeah.
That's
good,
interesting.
B
C
C
B
C
B
Know
just
kind
of
a
nice
little
reminder
and
for
people
that
are
kind
of
like
put
off
by
that
I
think
it
is
good
to
kind
of
you
know,
look
at.
It's
not
I,
think
what
you
folks
did
with
baking
in
dependency
injection
in
a
nice
way
into
the
startup
and
then
just
everywhere.
It's
just
available
everywhere.
I!
Think
to
me.
It
feels
like
if
dependency
injection
is
something
I
have
to
wire
up
myself,
and
it's
only
in
places
that
I've
hooked
it
up.
It's
less
useful,
but
because
dependency
injection
is
everywhere
by.
A
A
We
took
a
bit
right
like
we
took
a
pun
on
it.
We
said
it's
not
that
we
kind
of
baked
it
in
and
gave
you
good
support
like
we.
It
is
the
foundation
of
the
hosting
model
like
the
container,
is
the
foundation
of
everything
and
you
get
a
container
for
each
host
and
everything
has
to
be
configured
in
there
for
our
framework.
You
want
to
use
MVC,
you
want
to
use
middleware
options
or
you
can
create
instances
of
options
and
pass
them
to
middleware
directly,
but
you
know
the
web
server
itself
is
in
the
container.
A
B
I'm
fan
cool,
let
me
see
scroll
the
top
here.
This
is
interesting.
This
is
one
of
those
little
hidden
features
of
asp
net
core
I
didn't
know.
Is
there
Scott
points
out?
You
know
if
you
have
something?
That's
maybe
dynamically,
setting
a
content,
type
for
a
download,
so
say,
for
instance,
in
a
database
or
it's
you
know,
file
system.
It's
something
generated
on
the
fly
right.
You
need
to
set
the
content
type
right.
C
B
D
D
B
A
A
A
B
So
this
is
interesting,
and
this
is
one
of
those
kind
of
like
I,
didn't
think
of
doing
this,
and
maybe
it's
used
for
maybe
it's
not
interested
in
your
thoughts.
So
here
gunner
peoplein
set
up
an
asp
net
core
application
running
on
Windows
sandbox,
so
Windows
sandbox
is
this
built
into
Windows
Windows
10?
Now
it's
not
yeah
right!
Isn't
this
him,
like
yeah.
A
A
B
B
It
first
or
whatever
it
is,
or
maybe
it's
just
like
some
line-of-business
stupid
app.
You
got
to
use,
but
you
don't
you
know
whatever
it
is.
So
this
allows
you
to
get
kind
of
this
lightweight,
desktop
isolation,
I
think
it's
mostly
useful
for
like
a
desktop
app,
but
here
he's
showing
using
this
for
running
an
asp
net,
core
application.
C
B
Yeah
so
here
he
shows,
you
know,
he's
he's
building
these
kind
of
batch
files
he's
doing
a
self-contained
deployment
and
then
he's
running
it
and
he's
got
here's
here's.
This
is
peanut
core
app
running
here.
I
get
now
from
my
thoughts.
This
might
be
useful
for
kind
of
testing
out
a
self-contained
deployment
making
sure
that
it'll
work,
because
here
you
have
kind
of
the
isolation
from
the
base
so
kind
of
similar
to
docker,
but
then
I'm
not
sure
why
you
would
use
this
over
just
using
docker,
so
I
don't
know
it's
well.
B
B
One
is,
you
know
the
actual
kind
of
tools
the
packages
there
for
that,
and
then
you
also
including
a
link
to
the
protobuf
honor
to
the
proto
file
there.
So
then
he
goes
through
and
wires
up
the
server
not
a
whole
lot
of
code
here,
because
it's
sort
of
self
describing
yeah,
because
because
of
that
schema
and
then
here
he
generates
a
client.
This
is
a
excuse.
Me
here
he's
got
a
Kestrel
for
serving
and
http2
that's
nice
to
see
and
then
he's
generating
a
client
down
here.
B
A
B
B
That's
great,
so
I
gave
a
little
teaser
and
then
you
can
begin
heretic,
perfect
right,
great
okay,
Thomas
on
the
OMA
blog,
actually
a
lot
of
good
posts
here
recently.
This
is
one
I
picked
out.
This
is
an
interesting
thing
of
what,
if
you
have
several
people
on
a
team
and
they're
all
pointing
at
different.
You
know
databases
for
whatever
reason,
or
they
have
individual
settings
that
they
need
to
do
so.
B
He
you
know,
there's
a
lot
of
different
ways
you
can
go
through
and
do
this
his
example
from
an
app
settings
Jason
perspective,
so
here
first
he
starts
by
talking
that
through
and
pointing
out
what,
if
you
have
different
settings,
you
want
to
do.
One
approach
here
is
using
environment
variables,
so
you
know
go
through
and
just
set
it
directly
in
an
environment
variable
on
each
machine,
that's
user,
specific
and
something
you've
kind
of
got
to
go
into
week.
B
Every
time
here's
something
shows
also
is
using
just
like
a
an
individual
like
app
setting
dot
your
name
JSON
file,
and
then
using
this
you
know,
apps,
environment,
machine
name
and
basically
pulling
that
in
mm-hm.
So
then,
you
know
just
using
the
kind
of
standard
you
know
app
setting
system.
It's.
It
just
pulls
that
right
in
right.
So
this
that's
an
idea.
It's
already
easy
to
do.
B
A
The
same
thing
or
I
wonder
if
it's
a
different
I'm
treating
the
docs
I
haven't
looked
at
this
before,
because
it's
interesting
that
that
screenshot,
you
just
showed
it
had
two
options.
One
was
real
time
and
one
yeah
real
time
database,
which
is
what
firebase
was
so
you
know
famous
for
and
then
it
has
fire
store.
I
was
the
next
generation
there
you
go.
It's
the
better
one
yeah.
This
looks
like
it's
the
new
firebase
all
right.
If
you
go
to
the
website,
it's
like
it's
firebase,
google.com,
slash,
Doc's,
slash
fire
store
so
yeah.
B
Ahead
here
he
continuing
his
his
mega
series
here,
he's
looking
at
handling
errors
in
asp
net
core.
This
is
a
soup
to
nuts
on
handling
errors,
so
he
starts
with
basic
error:
handling
in
C
sharp,
like
just
the
basic
error,
handling,
try
catch
stuff,
building
all
the
way
out.
So
looking
at
I'm
kind
of
gonna
skip
ahead
a
little
bit
here.
Air
handling,
an
MVC
reminders
about
the
error
model
and
error
view.
B
B
A
Oh,
that's
good!
It's!
Actually!
It's
interesting!
We
just
did
a
just
an
experience
review
of
some
stuff
in
three
Oh
in
the
meeting
before
this,
and
one
of
the
things
out
that
I
have
to
log
is
we're
going
to
make
some
improvements.
Some
Long's.
The
improvements
were
willing
to
do
for
a
while
around
the
exception
page
and
the
error
handler
middleware
there
we're
like.
We
still
have
that
issue
where,
if
you're
doing,
for
example,
API
development
and
you're,
you
throw
an
exception,
you
get
back
the
developer
exception
page,
which
is
HTML.
B
A
A
Cuz
we
have
problem
details,
support
now,
which
we
added
in
you
know
tu1
and
tu2.
We
improved
it,
and
so
we
have
a
proposal
for
how
we
can
hook
all
those
things
together
in
three.
Oh,
so
that
both
the
developer
exception
page
and
the
the
error
handler
middleware
can
work
in
conjunction
with
other
things
in
the
system.
So
the
think
and
register
and
say
hey,
I
can
handle
the
exceptions.
Please
call
me
back.
A
If
you
see
an
exception,
give
me
the
context
and
given
the
exception
and
I'll
tell
you
whether
I
can
handle
it
that
way.
It'll
make
the
system
a
lot
more
pluggable
and
one
of
the
things
we'll
be
able
to
achieve
is
yeah.
If
the
client
doesn't
support
HTML,
we
won't
return
HTML
and
if
it
was
API
that
failed
will
do
Koenig
for
you
and
we'll
run
it
through
a
formatter
we'll
do
a
problem.
A
Details
response
which
would
be
in
your
template
would
be
in
the
app
you
return,
a
problem
details
or
an
exception,
and
then
it'll
run.
The
format
of
pipeline
you'll
get
the
right
response
for
the
clients
calling.
So
we're
actually
gonna
fix
that
in
three
eyes.
That's
one
thought
that
is
what
I'm
asserting
today.
Hopefully
that's.
B
D
B
A
B
In
tax
and
yeah,
so
there
you
go
that
updated
cool,
so
good
job
Chad!
That's
awesome
this
one!
This
is
from
Phillip,
and
here
he's
talking
about
a
few
tips
on
handling
JSON
requests
in
asp
net
core.
This
is
kind
of
a
you
know
down
to
the
to
the
metal
one
a
little
bit.
It
seemed
like
to
me,
but
he's
talking
about
you
know
some
things
like:
don't
buffer
to
string,
don't
do
sink.
He
goes
through
some
specific
things
in
here
for
Kestrel
for
disabling
synchronous
at
I/o.
There's.
A
Synchronous
and
asynchronous
IO
right,
like
we
all,
hopefully
by
now,
understand
the
difference,
and
if
you
don't
then
making
it
a
synchronous,
I/o
is
where
you
make
a
call
to
some
system
that
does
input/output
over
the
network
or
a
database
or
file
and
you've
block
the
thread
until
that
has
finished
asynchronous
I/o
is
the
same
thing,
except
instead
of
blocking
the
thread.
You
release
the
thread
while
that
I/o
operation
is
running
and
then
when
the
I/o
operation
finishes,
the
system
will
schedule
your
completion,
which
is
usually
the
rest
of
the
statement.
A
After
the
await
keyword
in
C
sharp
to
run
on
a
thread,
it
may
not
be
the
same
third
it'll
be
a
different
thread
will
get
scheduled
right.
The
thread
pool
will
handle
that.
Okay,
so
is
the
problem
a
lot
of
the
time
with
async
and
we've
talked
about
this
in
the
talks
that
David
and
I
have
done,
and
also
David
has
a
great
repo
with
a
bunch
of
examples
of
these
things
that
can
detect
you
can
trip
you
up.
A
Is
that
sometimes
you
can
end
up
doing
synchronous
blocking
I/o,
even
when
you
don't
realize,
because
of
the
way
that
certain
things
get
wrapped
so,
for
example,
if
you
you
might
be
writing
to
a
response
stream
of
some
sort,
and
then
you
intend
to
flush
asynchronously
or
you're
writing
asynchronously,
okay,
but
then
it
hasn't
actually
flushed.
Yet
because
of
the
way
buffering
works.
And
then
you
don't
call
a
discrete
flush
async,
you
just
kind
of
let
it
happen
and
then
the
thing
unwinds
and
then
eventually
gets
disposed.
A
But
dispose
is
asynchronous
call,
and
so
you
end
up
having
data
in
the
buffer
that
hasn't
been
written
yet
to
the
underlying
stream,
because
you
went
through
a
structure
that
will
be
disposed
eventually
and
you
didn't
explicitly
flush
it
ahead
of
time.
So
the
dispose
call
actually
makes
a
call
to
flush,
async
and
blocks
on
your
behalf,
which
you
didn't
realize
right,
and
so
those
type
of
things
make
it
very
difficult
to
say.
Yes,
I've
moved
all
my
code
to
async
and
I'm,
not
good
and
hence
I
will
not
hit
any
of
those
scale.
A
Is
that,
instead
of
using
one
thread
to
complete
the
item
for
that
period
of
time,
you
can
actually
end
up
using
multiple
threads
like
three
or
four,
even
more,
depending
how
deep
the
stack
goes
to
do
the
same
amount
of
work,
and
so
you
end
up
saying
instead
of
running
out
of
threads
in
you
know,
time
n
you
can
run
out
of
threads
in
four
or
five
or
six
times
quicker
than
you
would
have
otherwise
done.
Because
of
this,
the
way
these
things
interact,
and
so
in
oh
I,
think
was,
or
maybe
was.
A
So
I
said
why
don't
we
just
block
synchronous
I/o
by
default
in
custard,
so
they
tried
they
added
the
feature
you
can
see
it
here.
The
problem
is
when
we
set
it
to
true.
Very
few
things
worked
so
anything
anything
real
as
soon
as
you
plugged
in
MVC,
and
you
try
to
read
a
JSON
request,
because
the
JSON
serializer
itself
is
synchronous,
it
would
end
up
blocking
and
it
would
end
up
trying
to
read
synchronously
from
the
stream,
because
the
way
it
works
is
to
create
the
JSON
serializer.
You
pass
at
the
request
stream.
A
So
here
I
want
you
to
deserialize
from
this
stream,
and
then
it
reads
from
the
request
stream
as
its
serializing
right,
but
it
doesn't
do
it
asynchronously.
It
just
calls
stream,
don't
read
effectively,
and
so
you
end
up
getting
a
synchronous
read.
Even
though
you
were
going
through
the
right
mechanisms
in
the
framework
and
the
dayson
serialize
it
just
wasn't
the
only
one,
there's
a
whole
bunch
of
places
I
end
up
doing
this.
So
you
know
this
is
fast
forward
to
today.
A
We're
actually
looking
to
turn
this
on
by
default
in
three,
oh
and
we're
work.
We've
systematically
worked
through
all
these
areas
that
have
that
prevented
us
doing
it
last
time
in
one
of
them
being
building
a
new
JSON
serializer.
To
ensure
that
you,
we
can
have
a
good
experience
out
of
the
box
that
and
have
synchronous,
I/o
turned
off
by
default.
I'm,
not
saying
you
won't
hit
a
problem
like
we
still
find
things
in
the
framework.
A
Our
customers
find
things
in
the
framework
and
we
get
them
fixed
for
the
next
version,
where
some
API
that
looks
like
it's
async
ends
up
going
down
into
a
stack
that
is
actually
doing
a
synchronous
block
on
top
of
an
async
API,
which
is
really
bad,
and
that
causes
massive
scale
issues,
and
so-
and
in
this
case
it
would
mean
it
would
potentially,
depending
on
what
it
was
doing.
It
might
just
fail
budgets
or
an
exception,
because
cash
will
go
nope.
You
tried
to
call
synchronous,
API
we're,
not
gonna,
let
you
so
annoying.
A
B
B
Context,
yeah
good
stuff,
okay,
two
more
we've
got
one
from
Andrew
Locke,
so
I,
you
know
most
of
the
time
his
have
been
pretty
and
deaths
lately
pretty
advanced.
This
is
a
great
kind
of
overview
of
asp
net
core
razor
pages.
This
is
a
good
intro
for
if
you
or
your
team
is
you
know
not
not
using
razor
pages
or
is
more
vici,
and
this
kind
of
explains
the
thinking
and
and
I
like
his
got
lots
of
great
diagrams
in
here
kind
of
mapping.
B
B
B
A
A
A
A
B
B
A
A
B
You
did
yeah
so,
but
what
he's
doing
here
I
think
this
is
a
little
bit
kind
of
front
area.
This
is
a
nice
approach
here,
he's
doing
using
Azure,
DevOps
and
he's
versioning
based
on
the
date,
and
so
what
that
ends
up
giving
you
is
a
nice
little.
Your
version
that
you,
you
know
that
you're
stamping
is
like
20
1902,
Oh
7.1,
no,
it's
kind
of
yeah,
so
you
know,
and
it's
incremental
by
a
day,
so
you'll
you'll
get
you
know
if
you
have
multiple
builds
in.
A
The
days
he
does
that
as
the
Assembly
version,
yeah,
okay,
so
I
mean
you
have
to
be
careful
with
that.
With
regards
to
what
you
apply,
that
to
I
think
the
applications
is
probably
perfectly
fine,
but
for
libraries,
if
they
use
don't
on
a
framework,
and
things
like
that
assembly
version
has
semantic
meaning
when
it
comes
once
you
throw
strong
naming
and
all
types
of
other
stuff
in
the
servicing
and
by
really
most
of
this
stuff
applies
more
to
the
stuff
that
we
ship
than
it
does
to
the
general
public.
A
You
know
assembly,
binding,
binding,
redirects
and
all
those
type
of
things
that
you
know.
Many
folks
complain
about
all
the
time,
because
when
it
works,
it's
fine
and
when
something
goes
wrong,
it's
horrific.
Those
things
are
based
on
these
versions,
and
so
you
want
to
make
sure
you
think
very
consciously
about
what
you're,
using
for
your
assembly
versions
as
I
said
for
apps.
Typically,
it's
fine.
You
can
change
it
every
single
build
and
that
that's
different
in
white
thing.
That's
what
you
want
to
do
so.
A
We,
the
assembly
version,
generally
matches
the
branding
version,
so
you
201
202
203
I'm,
using
semver
as
close
as
we
can
for
the
component
and
then
the
information
version
we
stamp
in
the
new
get
packaged
version
which
can
be
different
because
if
it's
a
preview,
the
new
get
packaged
version
will
have
preview
on
it,
which
you
can't
put
in
the
Assembly
version
right,
because
the
Assembly
version
is,
is
a
dotnet
idiom.
It's
a
thing.
A
It
doesn't
support
previews
and
semantic
versioning
to
that
extent,
and
then
there's
an
extra
field
that
we
use
to
stamp
in
Lange.
As
the
assembly
description
we
stamp
in
the
get
shot,
so
we
use
a
series
of
different
fields
to
do
so.
What's
nice
about
some
of
these
fields
that
you
may
or
may
not
know
is
that
if
you
have
the
assembly
in
Windows
Explorer,
you
can
right
mouse
click
on
the
assembly,
go
to
the
file
properties
and
then
there's
a
tab.
A
D
B
Yeah
yeah,
that's
awesome,
well,
cool,
so
that
that's
that's
useful
to
know,
and
so
here,
like
you
said,
if
you're
sitting
at
the
top
of
the
stack
and
you
conversion
at
the
assembly
here,
you
know
nice
kind
of
pretty
I'll
put
there
so
yeah,
very
cool
and
I
think
yeah,
that's
it!
The
last
thing
here
is
the
for
you
source
I.
A
No
more
community
love
to
give
Ethan
quick
someone.
Well,
so
what
have
we
been
doing
so?
I
have
sweet.
I
mean
we
shipped
to
right.
That
was
in
early
December,
which
was
kind
of
my
focus
for
a
while,
and
then
we
you
and
I
and
a
whole
bunch
of
us
actually
went
to
London
and
we
did
n
DC
London
in
January,
and
we
taught
how
our
famed
workshop.
No,
we
taught
our
workshop.
It
was
fun
new
version
of
our
workshop.
We
updated
it
for
2.2
which
took
us
some
time
to
do.
B
A
A
A
People
had
had
updated
the
workshop
as
part
of
delivering
it,
and
so
we
got
to
see
some
of
those
updates
for
the
first
time,
but
we
didn't
apply
the
updates
that
you
know.
Perhaps
we
would
have
as
the
feature
owners
go
in
and
know
about
those
features,
so
it
was
good
to
get
back
in
there
and
go
oh
now.
Let's
change
it
to
do
this,
and
this
and
this
and
we
got
there
the
material
and
and
then
we
had
a
good
workshop.
Adding
me
at
like
17
people
was
about.
A
Interaction-
and
it
was,
it-
was
a
different
sort
of
group
to
last
year
in
London
like
last
year,
I
think,
it's
fair
to
say.
We
had
folks
who
were
somewhat
quite
familiar
with
dotnet
core.
Generally
speaking,
we
always
have
a
few
newcomers.
This
time
out
of
the
17
I
mean
like
15
of
them,
were
all
done,
their
framework
developers
who
hadn't
really
done
a
dotnet
core
yet
and
they
were
bringing
enterprise-e
style
developers
coming
from.
You
know
all
over
Europe,
and
so
it
was
a
very
different
vibe
and
it
was
really
good.
A
So
we
had,
you
know
a
lot
of
those
sort
of
well.
How
do
I
do
this
and
don't
their
core
questions,
and
why
did
we
make
those
changes,
type,
questions
and
folks
sort
of
seeing
a
lot
of
the
changes
for
the
first
time?
You
know
in
anger,
in
this
type
of
in
this
type
of
space.
So
and
then
we
had
a
couple
of
people
who
were
a
little
more
advanced,
and
so
they
offered
a
different
perspective
when
we
got
you
know
different
questions
from
them,
so
it
was.
It
was
a
really
really
good.
A
I
think
it
was
a
good
iteration
of
the
workshop
that
we've
done
and
then
because
it
was
that
type
of
crowd.
We
ended
up
not
even
getting
through
all
the
modules
I
think
in
the
full
two
days
we
end
up
getting
to
the
end
of
module
six,
but
there's
a
seven
and
an
eight
and
we
didn't
even
get
to
there.
We
and
they're
designed
it's
designed
to
work
that
way.
So
it's
designed
that
you
can
cut
it
off
for.
A
So
I
think
it
went
really
well
and-
and
you
know,
there's
still
things
about
the
app
I
would
change
and
we
will
continue
to
do
so.
More
will
teach
it
again,
but
it
went
really
well
and
then
we
did
a
couple
talks.
I,
don't
know
if
you
share
this
in
the
previous
ones
at
all,
but
most
of
them
alive
now,
which
I
think
you
also
went
live
this
week,
I
tweeted
it
yesterday
yeah.
A
A
B
B
A
B
D
D
B
Likely
you'll
want
to
use
and
then,
at
the
very
end
of
it,
I
show
how
to
create
your
own
project
template.
You
know
using
the
template
system,
and
so
it's
a
really
cool
like
hey.
We
just
spent
an
hour
but
look
how
we
can
shrink
it
down.
You
can
reuse
this
and
right
as
I
was
showing
that
my
computer
restarted
even
a
blue
screen.
It
just
restarted,
it
wasn't
a
Windows
Update.
It
was
just
a
for
the
heck
of
it
and
I
have
not
had
my
computer
do
that
in
maybe
years
I.
A
That
is
super
office,
so
I'm,
sorry,
but
we
had
a
lot
of
other
talks.
We
had
I
actually
did
another
works.
We
went
to
workshops
for
the
first
time
from
our
team
later,
so
we
had
a
blazer
workshop
for
the
first
time
and
this
wasn't
a
razer
components
workshop
like
the
stuff
for
shipping
it
through.
This
was
a
genuine
blazer
workshop,
and
so
we
had
Steve
Sanderson
and
Dan
Roth
and
Ryan
Novak.
A
A
Oh
and
then
Steve
gave
his
very
now
very
now
very
polished,
blazer
talk,
which
kind
of
introduced
his
blazer
and
what
it's
all
about
and
why
it
exists
and
how
whoever
certainly
works
on
all
the
type
of
sequence
of
call
and
then
you're
handsome
and
gave
he
is
one
of
his
diabetes
hacking,
diabetes,
talk,
I,
think
any
given
of
the
Microsoft
weapon.
Sauce
journey
talk
as
well,
and
then,
who
else
I
saw.
Meds
gave
a
talk
about
c-sharp
stuff
in
c-sharp,
eight
I
think
Phillip
Carter
was
there
I?
A
A
Wagner
Bill
Wagner
sorry
did
another
c-sharp
talk
and
then
he
also
was
saying
there
was
a
whole
bunch
of
us.
Our
set
Juarez
was
there
I,
don't
know
if
he
did
a
talk.
Did
he
do
it?
Rob
Connery
was
there
I
believe
he
did
a
talk
as
well
yeah.
So
there
was
a
there's
a
lot
of
good
content
this
year
and
then
obviously
there
was
a
lot
of
great
content
from
the
non-microsoft
speakers
as
well
as
they're
always
here.
A
So
those
videos
are
all
up
on
YouTube
now
and
I
think
you
can
get
to
them
through
the
embassy
website
as
well.
You
can
just
search
on
youtube
to
do
so
so
yeah,
so
that
happened
and
then
now
I'm.
My
focus
is
really
on
three.
Oh,
so
we've
shipped
what
two
previews
we
shipped
the
second
preview
like
while
we
were
there.
The
third
preview
is
imminent.
It
was
gonna
come
out
this
week,
but
I
think
it's
been
delayed
because
we
had
a
build
issue
or
something
so
they're
hoping
now.
A
Third
preview
will
come
out
next
week
and
our
intent
is
to
get
a
preview
out
roughly
every
month,
so
and
I
gonna
be
a
blog
post
coming
out
very
shortly
that
talks
about
this
for
three:
oh,
we
want
to
be
a
little
bit
more
open.
We
tend
to
have
a
little
back-and-forth
marketing.
It's
like
how
open
can
we
be
about
when
we
plan
to
release
well,
we
want
to
hold
some
stuff
for
inner
spaces,
so
we
try
to
come
up
with
words
that
keep
both
sides
of
the
of
the
company
happy.
A
But
if
you
just
watch
github,
it's
pretty,
you
can
usually
figure
out
where
things
gonna
happen,
but
we're
gonna
have
a
number
quite
a
number
of
previews
for
three.
Oh,
so,
if
you
think
back
to
the
100
days,
we
have
like
eight
beaders
I
think
we
called
them
feeders
back
then,
before
we
did.
The
first
RC
it'll
be
more
like
that
for
three.
Oh
we're
gonna
try
and
get
a
preview
out
pretty
much
every
month
right,
so
we're
the
first
one
in
December
we
did
the
second
one
in
January.
A
B
A
And
then
there
will
be
more
previews
after
that,
and
then
we
still
intend
to
try
and
get
three
a
three
Oh
finished
later
this
year.
I
think
was
like
I,
think
we're
saying
about
late
q3,
so
q3
means
the
third
quarter
of
the
year,
so
sometime
from
July
to
September
but
late
I,
don't
like
think
summer.
Sometimes
we
say
we
do
the
North
American
thing
or
the
Northern
Hemisphere
and.
A
To
you
in
fall
or
coming
to
you
in
late
summer-
and
you
know-
that's
not
very
friendly,
because
there's
half
of
the
world
that
doesn't
have
the
same
seasons
as
us,
so
yeah
so
late
q3
is
what
we're
currently
shooting
for.
It's,
not
a
promise,
though,
for
three,
oh,
so
the
next
preview
preview.
Three
I
have
a
build.
It's
not
the
bill
because
there's
a
bunch
of
stuff
held
up
in
the
build
system
right
now,
but
I
have
like
Friday's,
build
I,
think
and
Friday's
build
has
some
stuff
that's
worth
showing.
A
So
let
me
switch
over
and
some
of
you
may
have
seen.
Fowler
has
been
tweeting
a
couple
of
these
things,
a
little
few
snippets
like
generating
some
excitement,
which
is
great.
So
let
me
show
you
some
stuff,
so
we've
all
seen
the
file
new
and
via
2019
by
now,
and
if
you
haven't
you
have
now
because
it's
right
here,
I'm
gonna
click
create
new
project.
A
So
this
is
the
new
what
they
call
the
in
DP
or
the
MPD,
the
new
project
dialog
in
nvs,
and
it's
TN-
it's
very
much
different
than
what
it
was
before,
rather
than
a
huge
tree
view
on
the
left
and
they're
trying
to
simplify
it
and
just
give
you
a
list
and
let
you
search,
we
have
not
properly
integrated
with
this
yet,
and
we
will
do
that
as
part
of
the
300
wave.
But
3oh
does
not
ship
with
vs
2019.
Now
that
should
have
been
obvious
based
on
everything.
A
I
just
said
for
the
last
five
minutes,
because
you
just
got
finished,
saying
that
VR
2019
will
ship
on
April,
2nd
and
I
just
got
finished,
saying
that
dotnet
core
3
will
ship
in
late
q3.
Those
are
obviously
different
dates,
so
if
you
didn't
think
they
were
going
to
land
together,
I'm
sorry
they're,
not
they
were
never
intended
to
land
together,
and
so
we
will
integrate
into
this
experience
better
after
vs
2019
ships
all
right
so
because,
for
example,
if
I
type
razor
in
here
you
you
get
some
stuff
like
it.
A
Actually,
it
just
says
you
can
build
next
minute
called
web
application,
that's
because
it
says
crate
razor
pages,
but
if
I
want
to
find
something
like
G
RPC,
which
I
know
exists
now
it
doesn't
is
no
template
for
it
here,
which
is
a
lie.
There
is
actually
a
G
RPC
template,
but
it's
hidden
behind
the
one
asp
net
dialogue,
so
I
have
to
go
in
and
say
a
spinet
core
web
application
hit.
A
Next
accept
these
things
and
then
I
get
the
one
asp
net
core
dialogue,
where
we
have
a
further
set
of
templates,
write
a
slight
refinement
on
what
you
selected.
So
we
are
going
to
basically
move
all
of
these
templates
from
here
into
that
first
screen
is
the
what
not
all
them
we
might
do,
some
consolidation,
but
generally
speaking,
so
that
these
will
all
interact
with
the
new
experiance.
A
So
there
it
is
the
G
RPC
service
that
we
talked
about
they're,
also
going
to
take
a
chance
to
rename
a
lot
of
these
and
will
reorder
them,
because
it's
all
a
bit
higgledy-piggledy
right
now
we
haven't
really
given
it
the
attention
it
needs
to.
Yet
in
at
this
stage,
you
can
see
that
this
one
is
using,
the
same,
icon
is
empty,
which
is
probably
wrong,
and
Razor
component
is
higher
than
web
application,
which
is
also
probably
wrong.
Oh,
my
goodness,
is
that
a
handsome
man
I
see
conjuring
before
us
I.
A
A
A
A
A
To
acknowledge
your
presence
here,
all
right
so
back
to
what
I
was
talking
about,
so
we
have
yeah.
So
we
got
some
work
to
do
on
these
templates
yeah,
but
they
are
there
in
the
next
preview.
You
will
see
a
couple
new
things.
We
added
rates
the
components
in
preview
too,
but
we
now
have
G
RPC
and
we
have
the
all-powerful
all
new
worker
service
template,
so
we're
basically
introducing
a
completely
new
workload,
type
or
project
type.
We
call
them
workloads
internally
like
well.
What
workload
is
that?
Is
it
wind
forms
or
is
it
mobile?
A
Is
it
you
know
xamarin
or
whatever,
so
worker
service
is
an
acknowledgement
that
there
is
a
type
of
app
that
you
build.
That
is
a
console
app,
but
has
what
you
want?
You
don't
just
want
a
console
app!
That's
like
do
everything
yourself
right,
like
it's
a
console
app
that
uses
the
power
of
all
the
eight
it
core
Microsoft
that
extensions
stuff.
Okay,
so
here
I
am
inside
my
program
in
my
program.
A
We
had
those
before
they
were
just
not
very
well
known,
because
we
didn't
have
a
template
for
it,
there's
only
minimal
Doc's,
but
this
is
an
acknowledgement
that
there
are
architectures.
Where
you
have
many
of
these
styles
of
apps.
They
don't
have
a
server
in
them.
They
sit
in
a
kubernetes
pod
or
they
sit
as
a
national
function
or
they
sit
as
a
VM
or
just
an
apple
web
job,
maybe
in
Antares,
and
they
sit
there
and
they
go
every
two
minutes.
A
I'm
gonna
wake
up
and
check
to
see
if
there's
any
email
to
send
from
this
database
table
or
they
subscribe
to
an
azure
table,
storage
queue
and
they
guys
are
storage,
queue.
Sorry
and
they
go
oh
I'm
gonna.
You
know
DQ
messages
and
I'm
gonna.
Do
some
processing
I'm
gonna,
send
it
over
to
this
other
thing
or
they
react
to
storage
changes
using
event
grade
in
Azure,
or
you
know
whatever
it
might
be.
The
point
is
that
they're
apps
that
are
long-running.
They
say
you
want
lifecycle
for
them.
You
want
dependency
injection.
A
D
A
A
that's
a
perfectly
reasonable
and
valid
feedback.
So
let
me
pull
it
apart.
A
little
bit
I!
Don't
explain
why
that
is.
But
then
you
can
tell
me
that
that's
garbage
and
we
should
change
anyway.
So
the
worker
in
this
case,
is
the
thing
that
does
the
work
right
in
this
case.
So
my
worker
class
is
in
this
project
and
this
worker
doesn't
do
much.
It
just
sits
in
a
while
loop
and
asynchronously
waits
every
second
and
then
prints
out
a
message
right.
It's
the
most
basic
worker.
A
You
could
do
in
the
world
the
hosted
necessary
go
back,
the
hosting
part,
this
part
at
a
hosted
service.
This
is
a
this
is
a
primitive
of
our
DI
system,
so
an
our
hosting
system,
the
application
hosting
system.
So
you
can
say
India
I,
want
you
to
add
a
class
that
conforms
to
a
particular
interface,
and
in
this
case
it
is
the
I.
Its
background
service
and
background
service
implements
I,
hosted
service.
I,
hosted
service
is
simply
a
class.
That's
registered
in
di
that
will
get
notified
about
the
lifetime
of
the
application.
A
Okay,
it's
as
simple
as
that.
So
it
is
a
service
that
is
hosted
by
the
host,
so
that's
kind
of
the
very
core
layer,
and
then
you
can
build
multiple
workload,
types
on
a
hosted
system,
so
we
build
web
apps
on
this
same
hosting
infrastructure.
Ok
and
then
we
build
worker,
apps
or
G.
Rpc,
apps
or
signal
are
apps
all
on
this
same
hosting
idiom,
so
yeah.
So
you
could.
A
We
know
there
are
customers
today
using
web
applications
that
have
hosted
services
in
the
background
that
just
do
things
in
the
background
of
the
web
application
that
doesn't
make
them
worker
apps.
So
this
is
more
for
into
the
term.
Worker
is
more
being
used
to
describe
when
you
have
a
specific
application.
That
job
is
just
to
sit
there
and
do
a
thing
that
isn't
be
a
server.
Alright,.
D
D
A
A
A
Paradigm,
you
need
application
model,
so
this
is
the
application
model
for
these
types
of
applications.
If
you
wanted
to
build
a
console
app
that
boots
up
does
some
work
and
then
exits
immediately,
but
you
wanted
di
as
the
composition
model
for
doing
that.
You
could
do
that
with
this,
you
would
just
have
to
hook
up
the
end
part
you
would
have
to
have.
D
A
And
so
they
again,
we
kind
of
intend
what
we're
seeing
customers
do
this
already.
A
lot
of
this
is
about
Abdallah
geing,
where
customers
are
already
so
I've
said,
I'll,
be
introducing
a
new
workload.
Glad
we've
learned
about
what
we're
really
doing
is
Co
defined
what
people
are
doing
already
and
then
looking
at
what
they're
doing
and
just
making
it
better
as
in
saying
well
we're
going
to
reduce
the
boilerplate
by
building
some
idioms
for
you
in
the
platform
that
do
that
and
just
recognizing.
This
is
the
type
of
project
that
people
do.
A
So
when
we
talk
to
customers
who
have
large
sort
of
distributed,
/
microserver,
c-style
architecture
applications,
you
will
often
end
up
with
projects
or
applications
running
in
that
system
that
do
this.
They
just
sit
there
and
they
DQ
from
some
type
of
event,
grow
anything
and
then
they
post
to
a
sequel
database,
and
that's
all
they
do.
This
is
that
this
is,
for
those
type
of
things
all
right
now
and
I'm
sure
that
people
will
look
at
this
and,
as
you
just
said,
go
well.
A
If
I
pulled
apart
this
bit,
though,
I
can
use
it
in
this
other
stuff
as
well
greatness,
that's
fantastic!
We
may
not
have
a
template
for
you
out
of
the
box.
That
looks
exactly
like
that.
But
now
we've
got
one
more.
That
is
much
easier
to
get
going
with
and
starting
with
a
console
app
like
you
said,
you're,
starting
with
a
web
app
and
then
removing
all
the
web
stuff,
which
you
know
is
not
much
fun
alright.
So
the
other
new
one
I
wanted
to
show
quickly
was
G,
RPC
and
so
John.
A
A
Taneous
RPC
calls
it
come
and
then
it
uses
protobuf,
which
is
the
binary
serialization
format
and
then
dot
proto
files
as
the
specification
for
the
message,
types
that
you
go
for
them
back
with.
So
if
I
create
one
of
these-
and
there
is
a
gr
PC
solution
for
dotnet
today,
it
says
its-
it
doesn't
use
any
a
spinet
course
stuff
like.
If
you
go
and
get
gr
PC
dotnet
today
from
google,
it
it
is
a
hot
eater.
It's
a
thin
veneer
of
managed
code
that
calls
out
into
all
their
native
libraries.
A
Done
as
anywhere
near
as
integrated
as
that
right
yeah,
it's
quite
light
code
yeah,
and
that-
and
that's
kind
of
that
was
the
philosophy,
and
so
what
we've
done
is
like.
Well,
you
know,
customers
already
using
jar,
PC
or
they're,
asking
what
should
I
use
for
RPC,
because
there's
no
WCF
and
on
their
core,
and
so
we're
like
well,
let's
embrace
that
something
that's
already
out
there
and
doing
really
well,
and
so
we've
actually
working
with
the
Google
folks
and
we're
building
stuff
that
is
going
into
their
repository.
A
So
if
I
go
and
look
at
the
dependencies
of
this
project
over
here,
so
I've
this
one
at
the
moment,
this
template
creates
you
both
a
server
and
a
client,
because
G
RPC
includes
a
tooling
story
as
part
of
the
stack
that
generates
you
the
server
code
and
generates
you
the
client
proxy
or
the
client
agent,
to
call
that
server.
Okay,
it's
very
tightly
coupled
because
again,
that's
why
it's
RPC!
It's
not
HTTP
in
plus
Jason
style,
loosey-goosey
right!
It's
very
much!
A
A
So
how
does
that
work
actually
here?
So
what
that
means
is
that
it's!
This
is
an
ace
Mineko
application.
If
I
go
to
program,
it's
the
same
type
of
stuff.
We
saw
before
it's
using
a
web
and
it
has
a
startup
class.
If
I
go
to
the
startup
class,
it
is
middleware.
You
can
see
the
middleware
right
here
and
then
I
have
in
my
routing
call,
which
is
the
new
endpoint
routing
in
3oh
that
we've
talked
about
a
couple
times.
A
Let
me
just
zoom
in
a
little
bit
here
for
you,
then
we've
got
this
map
GRP
service
and
so
I've
got
a
strongly
typed
service.
My
greeter
service,
which
is
right
here,
which
is
a
class
in
my
project
which
is
in
the
services
folder,
and
it
inherits
from
the
generated
code
that
the
G
RPC
toolchain
created
for
me
from
that
code
base
now
I'm
getting
an
error
because
I
haven't
built
it
yet
and
that
code
doesn't
exist
until
the
tool
chain
runs
and
it
doesn't
run
yet
until
I
build.
A
A
If
I
f12
on
that
you'll
see
it
goes
into
a
file
that
very
much
looks
like
it's
been
auto-generated
and
if
I
hover
over
the
file
name
up
here
and
zoom
in
you'll,
see
that
this
file
actually
is
a
c-sharp
file,
but
it
only
exists
in
the
obdurate
in
the.net
sort
of
build
here,
mechanics.
So
if
I
clean
that
goes
away
right
and
says,
do
not
edit
this,
it
was
generated
by
at
all
right
classic
thing,
so
my
code
lives
in
this
class
startup.
A
So
I
can
edit
this
to
my
heart's
content
and
it's
all
good.
As
long
as
it
derives
sorry,
I
lost
my
code
as
long
as
it
derives
from
the
greeter
base,
and
this
is
all
I
have
to
do.
I've
got
my
say,
hello
method,
which
is
overriding,
the
one
that
was
generated
for
me
and
then
I
implement
what
it
is
that
I
I
want
to
go
ahead
and
do.
But
this
is
running
in
a
spinet
core.
This
is
G
RPC
as
an
AIDS
clinic
or
middleware.
So
I
was
using
kestrels
HTTP
to
support
okay
and.
D
A
This
is
releasing
as
part
of
three
R
and
it
will
be,
and-
and
it
will
be
in
a
package-
though
it
won't
be
in
the
three
Oh
said
framework,
but
the
template
will
be
in
the
300
SDK.
So
this
is
going
to
be
a
supported,
offering
phrase
files
do
well
I
used
on
their
core
three
great.
There
is
a
G
RPC
offering
in
neck
or
three.
A
D
A
Is
all
this
is
very
much
a
they're
likely
and
more
loved
the
better?
They
have
implementations
for
like
any
everything
on
the
planet,
and
so
like
Wade,
great
yeah.
Well,
we'll
build
an
a
spirit,
core
implementation
and
we'll
give
it
to
you
and
we
will
ship
it
in
dotnet
core
3
as
a
precontemplation
for.
A
A
Yeah,
so
the
typical
use
case,
as
I
understand
it
is,
is
for
when
you're
doing,
process
to
process
communication
so
yeah
it's
a
IPC
like
inter
process
communication
or
distributed
communication
between
machines
or
between
processes
running
on
either
machines,
and
you
want
a
strongly
typed
contract
based
RPC
style
of
invocation.
So
you
could
do
that
obviously,
but
not
have
any
of
the
things.
I
said
at
the
end.
A
You
could
just
do
HTTP
Plus
Jason
and
do
restful,
but
that's
not
contract
based
or
you
could
do
graph,
QL
right
and
but
then
you
use
a
separate
tool
chain
to
figure
out
how
to
generate
the
clients
and
under
that
G
OPC
gives
you
an
end-to-end.
So
it's
like
I
start
with
the
proto
file,
which
is
here
so
if
I
go
back.
This
is
what
you
start
with.
You
define
the
messages
and
we
don't.
A
A
A
D
D
Gp
g
RPC
integration
is
great
work.
We
like
it
because
it
helps
us
do
our
jobs.
It's
not
glamorous
like
a
web
server
platform
background
services
for
the
wind,
both
of
the
people
who
are
still
listening,
love
it
nice,
very
good,
very
good
they're,
so
quiet
I,
just
I,
think
that
let
me
just
give
you
a
little
bit
of
my.
A
D
Where
my
friends,
who
are
on
the
on
the
comments
here,
we
could
have
a
million
views
and
we
would
all
go
good
job
million
views.
But
if
we
had
a
hundred
good
comments,
you'll,
even
like
that
even
more
we
we
want
engagement,
we
want
to
talk
to
humans.
So
anyone
who
wants
to
put
a
comment
just
say
hello.
We
appreciate
you
more
than
the
anonymous
views
of
the
other
eighty
people
who
decided
to
show
up
and
then
leave,
and
they
just
left
YouTube
streaming
while
they
went
home.
That's
true,
you.
A
A
A
We
haven't
done
that
yet
so
we
kind
of
we
went
there
and
then
we
pulled
out
a
little
bit
when
we,
when
we
kind
of
spoke
to
that
team,
and
we
looked
at
it
and
we
decided
well,
maybe
it's
too
much
to
give
all
that
straight
off
the
bat
and
also
it
has
an
unfortunate
an
on
cloud
agnostic
name.
It's
called
Asia
web
Jobs.
Where
is
nothing
as
her
about
the
SDK
at
all,
the
SDK
will
run
anywhere,
and
so
there
was
just.
A
It
was
just
a
bit
of
a
mismatch,
and
so
we
said,
let's
start
with
a
basic
work,
a
template
that
describes
this
type
of
reactor
to
let
you
start
with
this
type
of
workload.
It's
it's
a
console
application
that
uses
our
hosting
model,
with
our
configuration,
di
extensions,
etc
our
background
hosting
thing,
and
then
we
can
explore
adding
more
stuff
the
eventual
long
term
goal.
A
Second
part:
creating
the
empty
template
with
the
infrastructure
I
showed
you
is
pretty
straightforward,
adding
the
azure
specific
stuff
with
all
the
config
and
pointing
to
your
subscription
and
like
what
file
you're
monitoring
a
blade
over
there
and
what
a
package
do
you
have
to
add,
because
you
need
to
know
the
right
one
with
the
SDK
in
it.
That
part
is
the
bit
that
is
complicated
today
and
you
have
to
go
and
read
a
bunch
of
Doc's
and
then
you're,
not
really
sure.
A
If
you
read
the
right
doc
and
then
you
got
is
the
code
up
to
date,
honor
there's
a
new
version,
Y
SDK!
Don't
do
that!
Do
this
and
said
what
we
would
love
is
that
you
do
what
I
did
and
then
you
just
have
a
button
like
a
scaffolding.
Type
thing
like
imagine,
you
write
master,
he
say,
add,
add
a
storage
event
handler
right
and
then
it
just
does
the
stuff
in
your
project.
A
That's
required
to
get
that
to
work,
and
so
we
have
this
working
name
for
that,
like
smart
scaffolding,
and
we
kind
of
want
this
to
be
a
thing
beyond
three
years.
This
one
landed
three.
Oh,
this
is
a
thing
that
we're
thinking
longer
term,
and
this
is
how
we
kind
of
would
evolve
this
type
of
application
development
so
there
rather
than
you
having
to
go
and
do
a
bunch
of
documentation
reading
just
to
get
the
most
basic
hello
world
sort
of
cloud
distributed
computing
based
thing
to
work,
the
tooling
would
help
you
get
there.
A
I
wouldn't
just
be
vs.
Obviously
there'd
be
a
command
line.
Experience
for
this
as
well,
and
so
that's
something
we
are
it's
extremely
early
thinking,
but
the
things
that
we're
building
in
three
are
now
our
building
blocks
towards
us,
adding
this
type
of
functionality
in
the
future.
So
yeah,
so
that's
all
I
have
time
to
show
really
it's
we're
an
hour
in.
Does
anyone
have
any
questions
online
that
they
want
me
to
answer
in
the
next
few
minutes?
I
guess
I
could
just
go
and
look
now
because
I'm
not
actually
presenting
yeah
yeah.
A
D
A
And
rebooting
blazer
was
the
name
that
Steve
coined
when
he
created
the
initial
prototype.
Like
you
know,
two
and
a
half
years
ago,
which
melded
a
web
assembly
dotnet
runtime
that
he
found
on
github
or
sorry,
it
was
a
CD
at
runtime
that
he
ran
through
the
heatwave
assembly
compiled
chain
to
build
a
web
assembly
done
a
run
time,
and
then
he
built
a
spar
framework
on
top
of
it.
A
He
was
all
like
browser
and
razor,
let's
call
it
a
blazer
and
it's
cool
and
it
kind
of
stuck,
but
when
it
came
to
saying
well
what
do
we
actually?
What?
What
are
the
steps
to
shipping
that
product,
rather
than
just
let's
just
ship
blazer
like
we
can't
just
ship
blazer
like
that,
like
it's
building
a
done
at
runtime
that
runs
in
web
assembly
is
a
lot
of
work,
but
there's
a
lot
of
value
in
the
component
model
and
the
programming
model
that
blazer
brings.
And
so
we
said
why
don't
we
ship
that?
A
Why
can't
we,
it's
already
been
architected
and
built
the
way
that
Steve
did
in
the
end
the
team
did
it
so
that
those
things
are
separate.
You
can
run
the
razor
components
engine
anyway
right
and
we've
seen
examples
where
they
run
it
in
electron,
with
donek
or
instead
of
web
assembly
and
because
everything's
remoted,
and
so
we
said
well,
why
don't?
A
We
had
always
wanted
shortly
after
we
did
tank
helpers
we'd
always
wanted
to
move
Razer
to
a
more
component
focused
system.
We
have
a
few
components
in
MVC
in
a
spirit
core,
but
frankly
they're
not
great.
We
don't
generally
recommend
people
use
them
and
and
moving
forward.
We
would
very
much
tell
people
to
use
Razer
components.
A
Instead,
what
we
wanted
was
the
experience
you
give
the
authoring
experience
you
get
with
C
HTML,
coupled
with
the
strong
type
strong
type
and
build
system
that
you
get
with
c-sharp
right
today
and
raising
you
don't
get
that
we're
tag.
Helpers
aren't
referred
to
as
a
type
they're
referred
to
with
the
directive,
whether
you
have
a
string
that
gets
passed
and
stuff
and
Razer
is
a
good
job
of
melding
c-sharp
and
an
HTML
together
in
one
file.
A
A
Right
and
then
you
pull
it
out
again,
the
other
side.
It's
Arabic.
It's
been
like
that
forever.
It's
been
like
for
10
years
that
we've
always
wanted
to
do
more,
and
we
said
a
component
system
where
razor
was
a
little
bit
more
like
Nizam
all
producers,
types
Ryan,
you
compile
it,
you
get
types
out.
The
other
side
and
types
can
refer
to
types.
A
That's
how
razor
components
works,
that's
how
blazer
works,
and
so
we
took
that
and
we
shoved
it
into
nickel
three
and
support
it
running
in
a
screen
air
core
on
the
server
side,
and
then
we
said
well
what
great?
How
do
you
integrate
razor
views
and
pages
with
razor
components?
And
we
have
a
model
for
that
as
well,
so
razor
views,
slash
pages,
can
host
razor
components,
so
you
can
have
a
razor
component
as
a
self-contained
units
like
a
component.
A
So
you
can
have
you
know,
migrated
over
time
or
just
have
part
of
parts
of
your
apps
use,
razor
components,
because
it's
a
better
programming
model
for
that,
but
stick
with
razor
pages,
because
you
want
to
do
a
request
response
because
rays,
the
components
as
a
real-time
stateful
based
system,
whereas
rays
of
views
and
rays.
The
pages
are
based
on
a
request
response,
star
system
right,
you
have
a
model,
its
bounding
coming.
A
You
have
an
outgoing
model,
there's
model
validation
and
bottle
validation,
errors
and
editor
there,
and
you
get
a
request,
context
and
blah
blah
blah.
You
don't
get
any
of
that
razor
components.
Razor
components
assumes
you
have
a
connection
use
with
a
circuit,
a
component
circuit
as
it's
called
and
everything's
just
stateful.
You
just
your
handle
events
right,
it
doesn't
know
about
requests
and
responses
and
stuff.
A
It's
designed
to
be
a
stateful
UI
system,
because
you
want
it
to
run
in
a
client,
that's
hot,
the
whole
point
or
if
there
is
no,
if
you're
not
running
in
the
client,
you
want
it
to
appear
like
it's
running
in
the
client
over
whatever
connection
mechanism
you're
using
between
where
the
rendering
engine
is
and
where
the
actual
rendering
occurs
and
we're
using
signaler
for
that
in
Ind
on
the
core
3.
So
yeah,
that's
the
story
there.
So
we
said
when
it
comes
to
doing
that.
A
We
don't
want
to
call
that
blazer,
because
blazer
as
a
name
in
our
mind,
refers
to
raise
a
component
model
running
in
the
browser
on
webassembly
where's
razor
components
are
the
components
that
you
build.
You
create
a
dot
razor
file
which
is
coming
in
preview
3
by
the
way,
create
a
dot
razor
file
that
gets
compiled
into
a
type
which
is
a
razor
component
type,
and
then
you
can
host
that
either
in
a
server-side
application
in
dotnet
go
3
or
in
a
blazer
application
in
the
client
running
on
web
assembly.
B
A
Quickly
give
some
answers
here.
Are
we
going
to
see
any
new
features
templates
around
hosting
view
Jas,
since
this
popularity
is
increasing?
For
the
most
part,
node
services
is
cutting
it?
No,
we
don't
men,
EEP
lands
right
now
to
add
anything
to
the
spa
stuff
we
intend
to
remove.
We
did
intend
to
remove
the
spa
templates
from
the
SDK
because
we
were
finding.
A
So
we
would
find
like
we'd
get
two
versions
of
angular
behind
before
we
had
a
release
of
dotnet
core,
where
we
could
update
those
templates
but
I
think
we're
going
to
do
a
feature
in
three
others
going
to
let
us
Rev
those
templates,
a
band
and
so
you'll
still
be
able
to
have
like
an
angular
template
in
the
box,
but
we'll
be
able
to
update
it
and
it'll.
Tell
you
when
there's
new
version
of
stuff,
so
we're
hoping
that
that's
going
to
land
but
there's
per
view.
A
A
Yes,
a
strong
set
of
community
members
who
love
using
view
with
the
node
services
and
the
asp
net
core
stuff
that
we
have
then
I'd
encourage
them,
and
we
will
promote
them
up
the
wazoo
to
to
put
together
a
great
template,
and
you
know
a
v6
extension
that
you
can
install
and
have
those
templates
show
up
in
the
right
place
and
then
you've
got
a
great
view.
Template
that's
maintained
by
the
people
who
use
it.
A
We
did
angular
and
rate
and
react
and
redux,
because
they
were
very
clearly
the
most
popular
ones
and
customers
were
very
or
asking
for
them
and
they
were
the
logical
ones
to
do
when
we
built
the
features.
Most
of
our
time
is
spent
building
the
stuff
in
300
right
now,
and
templates
are
quite
expensive
to
maintain
to
do
well,
especially
for
the
ones
that
we
have
to
include
in
the
box.
I'd
go
as
far
as.
B
A
For
the
community
projects
that
are
maintaining
templates,
they
don't
have
to
quite
go
to
the
same
lengths
and
the
amount
of
work
that
we
have
to
go
to,
and
we
include
a
template
like
we
have
to
put
them
through
accessibility,
checking
and
localization
and
and
security
checking,
and
that
it
always
suffers
so
yeah.
It's
good
practice
to
do
all
those
things,
but
we
have
to
do
those
things
and
they're
very
expensive
and
so
keeping
them
up
to
date
and
and
assigning
enough
people
to
do
that
work.
D
B
A
A
Everything
like
I,
wouldn't
even
attempt
to
try
and
say
that
there's
a
lovely
acronym
that
you
know
turns
into
a
word
that
we
could
say:
oh
yeah,
we
see
the
fant
stack
or
something
they'd
be
all
over
the
place
right,
f-sharp,
+,
Apache,
+,
donate
+,
tensor
I,
don't
know
I
just
made
this
up.
We
know
like
we
see
customers
doing
everything.
The
reality
is
that
once
you
have
a
once,
you
have
an
application,
that's
been
in
use
for
a
while
or
you're
in
place.
A
That's
had
gone
through
a
series
of
cycles
of
application
development
thinking.
You
often
end
up
with
all
different
types
of
technologies.
You
know,
and
I
came
from
that
world,
like
you
know,
10
years
ago,
with
that,
that's
what
I
did
for
a
long
time
and
it
wasn't
unusual
to
have
extremely
heterogeneous
environments
where
you
had
dotnet
talking
to
Oracle
with
some
other
enterprise
service
bus
products.
It
coupled
with
some
hardware
device
with
an
SDK
the
coupled
with
laboratory.
You
know
before
you
even
before
the
cloud
now
you've
got
the
cloud.
A
Then
you
add
you
multiple
cloud
providers
to
those
things
and
multiple
sputtering
works
and
some
customers
like
homogeny
a
little
more
and
so
some
customers
will
be
a
little
more
prescriptive
and
they
will
ask
for
prescription.
And
you
know
we
try
to
codify
our
prescription
as
the
little
that
we
give.
Typically
in
the
templates,
the
experiences
in
the
documentation
that
we
give
and
then
beyond
that
it's
really
an
exercise
for
the
the
customer
to
decide
what
is
best
for
them
and
their
needs
and
yeah.
A
A
Yet
some
person
like
sitting
behind
the
keyboard
like
they're,
not
some
company,
didn't
pay
them
any
money.
That's
you
know
that's
what
community
projects
and
open-source
is
all
about.
Sorry,
so
I'll
get
off
my
soapbox.
What
else
plays
electron
Sam
yeah?
There
is
a
blazer
Tron
sample.
There's
a
PR
out
right
now
to
move
that
to
the
ASB
labs
repo.
It
exists.
It's
been
around
for
a
while.
There
is
a
blaze
of
an
electron
sample.
A
If
you
go
to
the
ASB
labs,
repo
I
believe
there's
an
open
PR
right
now,
if
it
has
not
already
been
merged.
That
has
that
in
there
maxima
asks.
Are
there
any
updates
to
the
identity,
server,
out-of-the-box
integration,
4
to
2
or
3?
Oh,
the
update
is
I,
saw
an
email
yesterday
where
I
believe
Brock
and
Dominic.
The
only
server
folks
have
some
sample
of
a
new
thing
that
they're
doing
that
they
want
to
show
us,
and
then
we
were
going
to
review
what
we've
built
with
them.
A
We
had
initially
planned
to
get
previews
of
that
out
to
use
on
top
of
that
might
still
be
the
case,
but
given
where
we
are
in
the
3o
cycle,
depending
on
the
outcome
of
the
next
round
of
feedback
on
that
integration,
piece
that
we've
done,
we
may
make
the
decision
to
just
roll
that
into
the
300
timeline.
Instead,
I'll
reserve
judgment
on
that.
A
Yet
because
it's
still
in
flight,
but
the
code
does
exist,
the
templates
do
exist,
they're,
just
not
in
a
release
form
yet
so
I've
seen,
for
example,
the
new
spar
templates
that
include
the
identity,
server
or
the
dock
token.
Orth
based
system
that
for
angular
and
for
react
that
will
off
with
an
a
submit
course
server.
That's
hosting
identity,
server,
+
the
glue
piece
that
with
it
that
we
created
so
it
does
exist.
It
is
being
worked
on.
A
Anything
new
with
progressive
web
app
speed
appears
nothing
specific.
You
know,
PW
is
a
great.
We
talk.
It
comes
up
in
the
context
of
blazer
quite
a
bit.
There
is
opportunity
in
PW
a
definitely
the
we
could
do
more
things
we
haven't
had
a
lot
of
customer.
Ask
there's
made
a
lot
of
custom
demand
to
really
have
us
put
more
PW
a
focus
stuff
in
the
offering
so
like
api's
or
templates
or
anything
most
of
it.
A
A
It's
not
full
VB
support,
that's
changing
in
three,
oh,
so
three
hours
is
bringing
a
more
full-fledged
VB
support,
as
you
would
expect
with
the
my
namespace
and
all
the
other
VB
isms
that
just
don't
work
on
dr
core
today,
because
we
have
to
bring
those
over
to
make
vb
WinForms
and
vb
WPF
applications
impossible
to
port
to
donate
core.
What
will
never
happen?
A
There's
no
support
for
that
today.
The
only
project
system
that
supported
that
in
Visual
Studio
was
the
old
asp
net
website
project
system,
which
actually
allows
you
to
have
different
folders,
with
dot
VB
files
and
dot
CS
files,
and
that
would
actually
work,
but
that
doesn't
work
in
the
project
system,
and
so,
even
if
you
do
that
today,
your
razor
files-
it
is
one
of
the
other-
has
to
be
a
VB
project
or
a
c-sharp
project.
A
It
can't
be
both
right,
and
so
you
have
to
pick
one
and
then
you'll
get
intellisense
for
that
language
and
that
language
only
so
it's
just
not
something
that
we
it's
not
enough.
People
who
would
do
that
to
warrant
the
work
would
take
to
make
that
work.
That's
not
of
our
official
position
on
that
right
now.
A
Speaking
of
template's
is
a
plan
to
have
templates
based
on
MSA
l4,
as
your
adv
to
end
point,
I
saw
an
email
about
that
this
week,
so
I
believe
we're
currently
discussing
with
that
team.
What
the
best
approach
is
for
changing
our
MSA
and
aad
authentication
story
with
regards
to
our
templates
and
libraries
to
be
whether
it
should
be
just
open,
ID
connect
based
or
whether
it
should
still
be
a
wrapper
library
of
some
sort
that
etc,
etc
and
based
on
M
cell.
So
we're
looking
at
that
right
now.
A
I
don't
have
firm
plans
yet,
but
it's
something
that
we
are
looking
at.
Blazer
100,
yeah
I,
don't
have
any
dates
for
blazer
1,
oh
it'll
be
after
300,
and
we
don't
know
we
just
don't
know
your
blazer
100
depends
on
the
webassembly
story
or
for.net
and
that's
still
very
much
a
work
in
progress.
When
we
know
we
will
let
you
know
good
to
do.
A
Okay,
any
chance
proper
sample
of
Doc's
of
using
a
client
framework
angular
react
with
social
off
an
asp
net
and
identity.
So
that's
effectively
what
the
template
that's
currently
being
worked
on
for
the
identity
server
integration
is
going
to
allow
you
to
do
now.
Identity,
server,
folks,
have
those
Doc's
there's
my
understanding,
so
you
should
be
able
to
go
the
add
any
identity,
server
repo
and
do
that.
A
So
I
mean
that's
something
that
we
could
potentially
do,
but
it
effectively
is
just
you
start
with
a
standard
application
with
your
server
based
social
authentication,
so
Facebook
or
Thor
whatever
it
might
be,
and
then
you
add
the
spire
application
into
the
same
one,
and
then
you
share
the
cookie.
It's
basically
it
now
then
like
what
you
do
in
the
spar
plication
to
do.
Authorization
is
where
it
gets.
We
don't
have
anything.
A
There
is
more
on
that
coming
and
then
that
old
nugget
it
would
be
good
to
have
a
template
that
supports
globalization,
best
practices
out
of
the
box.
Yes,
I've
heard
that
ask
for
fifteen
years
again
is
one
of
those
things.
I'll
refer
to
my
previous
answer.
Where
we
have
the
localization
system
in
that
in
the
in
the
Box,
there
is
no
template.
I
did
maintain
a
sample
at
one
point,
tradesmen
and
more.
B
A
Still
there
it's
in
the
same
entropy
repo,
wherever
it
might
be
and
I
think
I
have
said
this
numerous
times.
That
is
another
great
example,
I
think
of
where
a
community
template
a
community
project
that
maintains
our
templates
but
fully
localized
versions
of
those
with
all
the
changes
required
to
make
them
localized
would
be
a
fantastic
community
project
for
folks
to
own.
We,
it's
just
something
we
haven't
been
able
to
prioritize
when
it
comes
to
n
to
the
amount
of
work
required
to
do
it
to
the
standard
that
we
would
have
to
do.
A
B
Have
seen
some
good
community
efforts
in
there
recently
I
showed
some
Damian
Bowden
did
a
series
were
and
has
a
hub
repo
where
and
it's
using
identity
is
been
localized
and
they've
gone
through
and
they've
had
pull
requests
like
Chinese
foreign
languages
and
stuff
yeah?
So
again,
that
localization
is
a
good
area
for
community
to
jump
in
and
and
do
that
right
and
you
know
it
seems
interesting
to
that's
something
where
people
could
potentially
with
Razer
components.
Also,
do
some
localization
raise
your
class
libraries,
sorry
right,
yeah,
so.
A
I
thirst,
nation
dubs,
just
following
up
on
his
question
regarding
the
author
of
social
off
yeah.
So
that's
what
we're
building
that's
exactly
what
we're
building,
which
is
where
you
have
a
an
API
application
that
is
secured
using
identity
server
and
is
using
jot
tokens,
and
then
you
have
a
spire
application
that
needs
to
authenticate
with
that.
That
is
literally
the
templates
that
are
currently
being
built
being
built,
stay
tuned,
alright,.
B
A
A
All
the
hours
there's
a
question
over
on
twitch
how
usually
they
secure
an
RPC
call
compared
to
normally
to
it.
So
my
understanding
I
asked
the
security
question.
This
will
blast
one
I'll
answer.
The
I
answered.
I
asked
the
security
question
with
G
RPC
and
the
answer
I
got
back.
Was
you
don't
do
that?
A
Do
you
PC
they
typically
it's
over
HTTP,
so
you
can
secure
it
using
whatever
you
use
to
secure
the
HTTP
to
channel
which
could
be
certificate
or
you
know
dude
over
HTTP
and
you
certificate
or
for
authentication
there's
type
of
things,
but
it's
kind
of
intended
more
for
RPC
style
scenarios,
where
both
sides
trust
each
other.
Now
I
may
be
complete.
I
may
be
wrong.
Maybe
I
got
the
wrong
information.
I
I
heard
it
wrong.
A
So
if
people
on
the
stream
know
more
by
all
means
correct
me,
but
GI
PC
is
over
HTTP
at
HTTP,
but
it
kind
of
takes
over
the
connection
right
so
like
the
passing
of
each
request
is
used
to
resolve
which
the
RPC,
endpoint
or
method
to
call
but
the
authentication
it
would
be.
And
if
that's
true,
then
the
authentication
would
typically
be
done
at
the
at
the
transport
layer
right.
So
you
would
use
a
certificate
or
something
like
that.
So
that's
my
understanding.