►
Description
Community links for this week: https://www.one-tab.com/page/fgfXIOXGRUGB7lm3Coq-eg
A
C
D
A
E
D
A
A
C
A
A
A
C
A
C
A
C
Well,
we
do.
We
are
in
the
middle
of
pushing
a
release
right
now
and
so
we're
in
the
middle
of
pushing
a
second
preview
of
2.1.
Some
folks
may
have
noticed.
Packages
went
live
last
night.
The
releases
aren't
a
binary
thing.
They
like
a
wave
of
stuff,
it
has
to
happen
before
we
can
flip
the
announcement
and
you'll
see
it
show
up
on
blogs
and
on
the
download
page.
So
all
my
I
am
told
all
the
actual
software
and
all
the
assets
are
in
the
places
where
they
have
to
be
so.
C
Packages
went
live
last
night.
The
Download
Center
has
the
new
SDK
and
run
time,
installers
docker
hub,
actually
I,
don't
know,
I
didn't
ask
I'm,
assuming
the
doctor
tenders
have
been
pushed
or
if
not,
they're,
gonna
go
live
very
soon
and
then
Lee
my
release
p.m.
will
be
working
on
is
working
on
the
getting
the
download
links
updated
very
shortly.
It
might
even
happen
during
the
middle
of
the
show.
I
already
have
it
installed,
but
the
eagle-eyed
follow
with
my.
A
C
That's
the
overall
dotnet
core
release.
The
SDK
is
always
has
you
know
it's
versioning
scheme.
So
it's
two
one
three
hundred
is
the
SDK
version
right
so,
which
is
what
it
was
before.
So
it'll
be
two
one
300
preview,
because
it
was
two
one
three
hundred
preview
one
before
and
then
they
have
a
build
number
after
and
the
build
number
is
devised
from
the
date
and
some
other
garbage
right,
but
whatever
the
one
that
goes
out
I
mean
I
have
installed
so
I
can
literally
just
type
dotnet
info
and
how
about.
A
C
A
C
So
the
site
extent
is
no
there's
no
automatic
update
facility
for
site
extensions.
You'll
have
to
go
and
go
to
the
site.
Extension
gallery
in
your
site
and
it'll
tell
you
there's
not
that
available.
If
you
do
that,
assuming
it's
been
pushed
by,
then
by
the
time
you
get
to
the
hotel,
then
you
can
apply
the
update,
that'll
change,
your
runtime
version
on
as
your
app
service
web
apps
to
preview
to
your
alternative,
obviously
is
to
publish
that
self-contained
right.
You've
always
got
that
option
right.
C
If
you
want
to
avoid
the
scourge
of
managing
versions
on
your
target
server
or
your
target
environment,
you
can
always
do
a
self
contained
deployment
and
you
own
your
own
destiny
right.
It's
just
there's
the
slightly
more
few
moving
parts
and
you
own
your
own
destiny.
So
you
have
to
make
sure
that
you
understand
all
that
stuff.
A
C
Portal
know
that
the
site
extension
mechanism
in
Azure
app
service,
just
like
the
new
get
package
manager
in
vs
like
that
dialog.
If
you
open
it,
it'll
tell
you
if
there
are
updates
available
for
things
you
have
installed.
If
you
go
into
the
portal
and
you
navigate
to
the
site
extensions
blade
of
your
site
in
the
portal,
it
will
tell
you
that
there
is
a
new
version
available
of
that
package
of
that
site.
Extension.
It's
not
automatic
from
anyway.
Basically.
A
C
Much
yeah
install
the
SDK
change
the
package
versions
and
then
go
from
there,
and
then
we
there
will
be
a
blog
post
coming
out
for
your
net
core
that'll
enumerate
all
the
changes
all
the
new
stuff
there.
Hopefully
there
isn't
anything
that
breaks
you
from
preview
under
preview
I'm,
not
aware
of
anything.
There
are
some
things
in
preview
to
that
itself
are
broken
because
it's
a
preview.
C
So
there's
a
couple
things
some
known
issues
that
will
be
documented,
but
most
of
the
changes
in
preview
are
refinements,
based
on
your
feedback
and
your
further
investigations
that
we
have
done
based
on
the
preview
one
bit
so
I'm
happy
to
give
people
a
rundown
of
those
prior
to
the
blog
post
going
live
during
this
call.
But
maybe
we
can
leave
that
until
after
the
community
links.
C
A
C
So
they're
installing
the
SDK,
which
is
you
know
the
main,
install
you
put
on
your
developer
machine.
There
will
be
a
series
of
what
were
previously
project
tools
that
will
now
be
pre-installed
effectively
as
global
tools
like
so
we,
author
of
them
as
global
tools,
but
they
effectively
get
bundled
into
the
SDK.
You
can't
override
them
that
they
become
SDK
commands
for
all
intents
and
purposes.
C
So
things
like
done
there
watch
dotnet,
dev,
certs,
I,
don't
know
EF,
dotnet
watch
I
think
you
said,
there's
a
couple
other
ones
and
then
there's
some
external
ones
that
we
own
but
go
to
new,
get
they're,
not
built-in.
They
will
not
be
available
in
preview
to
do
to
a
late
find
that
we
had.
They
will
come
back
in
the
next
release,
which
we
are
planning
on
being
the
release
candidate,
the
RC
RC
one.
So
those
include
the
a
spirit,
scaffold
er,
which
you
can
use
in
vs.
C
C
A
C
C
A
D
A
Thing
says:
oh
you're,
using
this
raw
yours,
this
version
of
jQuery
on
this
page,
but
you
don't
need
it
on
that.
Other
page
I,
just
put
in
a
partial
I,
put
in
a
render
partial
required
call
a
rest
render
section
rather
required
balls
and
I
moved
it
around.
It
was
like
30
seconds
and
then
I
removed
like
a
half
a
half
a
second
off
of
my
load
time.
Just.
B
A
A
C
That
was
nice,
John
menthe
is
yeah,
is
my
boss's
boss
and
also
Scott's
was
a
splice.
You
take
yeah,
even
if
you're
in
the
middle
of
a
live
string
awesome.
So
it's
always
nice
to
hear
nice
things
from
Scott
when
he
uses
their
stuff,
because
you
know
Scott
is
one
of
those
people
who,
when
he
gets
a
chance,
will
go
and
use
our
product,
which
is
fantastic
because
that's
yeah.
C
We
all
we
all
love
to
do
that
when
we
get
the
opportunity
to
work
at
one
of
our
own
things
using
our
stuff
and
then
obviously,
obviously
has
fantastic
feedback.
So
it's
great
when
we
get
really
good
feedback
like
that,
which
is
oh
I
mean
we
like
the
the
constructive
feedback
as
well.
They
get
me
wrong.
We
get
plenty
of
that.
It
is
nice.
The
Razr
pages
is
making
him
so
happy
because
I
know
he
was
one
of
the
champions
of
simplifying
a
lot
of
that
stuff
and
keeping
the
power.
D
Have
to
like
Scott
saying
it's:
it's
not
the
that
it's
dumb
down,
but
it
makes
easy
things
easy
like
yeah.
So
what
I
forget
the
saying,
but
you
want
things
that
you
know
make
easy
things
easy
without
making
like
you
want
to
make
hard
things
easier
without
making
easy
things
too
complicated
right
and.
B
D
D
C
Absolutely
and
all
the
yeah
most
of
the
conventions
are
controllable.
So
if
something
really
offends
you
about
the
way
that
we
decide
to
make
it
work
by
default,
you
can
get
in
there
and
like
write,
you
know
30
lines
of
code
in
the
right
place
and
change
it
completely.
Right
like
like
folks,
there's
a
whole
bunch
of
folks.
You
like
feature
folders
for
MVC
organization,
and
you
just
write
a
bit
of
code
today
and
you
can
use
feature
folders.
C
D
D
C
B
D
Should
be
a
thing,
that's
just
automatically
you
kaufe
special
way
and
it
like
audio
senses
it
and
just
locks
on
that
string.
You're,
like
you
just
like
clap,
twice
or
something
alright
Dalton
Chanin
he's
announcing
so
previously
known
as
Botwin.
It
is
basically
it's
Nancy
style
routing
for
asp
net
core
and
what
came
up
over
time
was
people
were
so
botwins
been
out
for
a
while,
but
people
were
confused
by
the
name
of
it
they
were
like.
Is
it
a
bot
for
windows?
D
Isn't
let
you
know
what
does
this
name
mean
so
so
they've
they've
kind
of
rebranded
it
and
also
kind
of
set
up
some
community
centered
stuff
bit.
So
there's
a
community
repository
and-
and
you
know
just
some-
some
kind
of
new,
exciting
stuff
going
on
there,
so
yeah
so
Carter
community
is
so
it's
Renea
sure
they
said
that
it's
renamed
as
Carter.
So
yeah
neat
thing,
there's
that
this
was
a
neat
tweet
I
saw
come
in
today,
so
Kristoff
was
testing
this
out.
This
is
the
docker
work
or
well.
D
D
All
right
so
yeah
here
was
his
thing
running
through
the
core:
I
went
through
and
cloned
it
and
you
know
ya,
need
to
see
it.
So
that's
cool
yep.
This
is
third.
In
this
series
we've
been
calling
out
from
phys.
This
is
on
graph
QL
with
asp
net
core,
so
he
had
kind
of
worked
through
part.
One
was
the
kind
of
just
very
much
basics
getting
started.
Part
two
was
building
it
into
middleware
and
then
part
three
is
these,
injecting
that
middleware
so
kind
of
its
yeah
so
kind
of
a
standard?
D
D
There's
the
old
style
or
the
you
know,
traditional
password
authentication,
username
password
that
kind
of
thing:
there's
a
hostile
there's
some
multi-factor
authentication,
where,
like
TOTP
providers,
there's
also
a
thing
that
you'll
see
like
on
slack
or
medium,
where,
basically,
you
go
in
you
put
in
your
username
or
email
and
then
it
emails
you
a
login
like
alright.
So
it's
a
one-time,
login
and
so
here
he's
gone
through
and
shown
how
to
do
that.
Oh
cool.
D
Cool
alright,
so
Fabian
had
previously
written
this
up.
This
is
an
angular
application
using
ASP
net
core
and
signal
are,
and
he
is
updated
this
to
use
the
angular
CLI.
So
this
is
using
all
the
new
bits
neat
little
things
showing
this,
but
you
know
just
kind
of
a
standard
to
angular
apps
and
showing
them
working
between
each
other
and
keeping
in
sync.
So
this
is
the
all
the
new
bits
you
know
update
with
all
the
new
bits,
including
the
angular
CLI
stuff.
D
So
when
you're
working
with
multiple
micro
services
or
multiple
different,
you
know
more
complicated
stacks,
you
can
use
a
correlation
ID
in
your
logging
to
kind
of
trace
to
tie
a
bunch
of
things
together
and
so
what
Steve's
done
previously
was
he
had
a
version
he's
got
a
library
that
helps
with
doing
that
and
so
he's
released
an
update
for
that.
So
that's
basically
yeah.
D
C
Did
a
bunch
of
work
into
our
around
this
as
well,
so
we
there's
a
concept
inside
net
now
called
activities
which
is
effectively
this
idea
of
having
a
context
and
arbitrary
context
that
flows
across
arbitrary
code
execution
across
threads
across
processes
across
machines,
and
you
can
use
this
activity
ID
in
the
context
associated
with
an
activity
to
to
get
for
distributed
tracing
type
stuff.
So
that
you
can,
you
know,
add
data
to
this
to
this
activity,
that
in
a
property
bag,
so
that
when
you
log
it
out,
logging
systems
can
detect.
C
If
there
is
an
activity,
a
present
active
right
now
and
if
so,
they
can
grab
all
the
information
from
the
activity
they
can
add
stuff
to
it
or
they
can
grab.
It
then
emit
it.
So
we
do
this
by
default
in
a
submit
course.
So,
basically,
we
have
a
couple
of
triggers
that
if
we
detect
certain
circumstances,
when
a
request
comes
in,
then
we
will
create
an
activity
or-
and
furthermore,
if
we
detect
that
the
incoming
request
has
a
special
header
that
is
itself
basically
an
activity,
ID
header.
C
That
was
making
the
original
call
and
have
them
all
be
tied
together
from
a
tracing
and
correlation
point
of
view.
So
we
have
a
lot
of
this
plumbing
in
the
framework
now
most
of
it
lights
up
when
you're
using
stacks
like
application
insights,
they
can.
They
can
reason
about
these
things
by
default
and
they
know
what
to
look
for.
Anyone
could
could
integrate
to
this.
So
if
you
have
your
favorite,
you
know
third
party
tracing
or
logging
system.
C
They
can
do
the
same
thing,
whether
it's
something
like
exception
lists
or
Elmar,
or
what's
the
one
that
Nick
raver
does
those
things
they
can
find
these
things
through
Diagnostics
sauce
and
discover
when
these
things
take
place
and
then
sort
of
add
this
data
to
their
to
the
things
that
they're
capturing
so
yeah.
This
is
another
example
of
doing
that:
cool.
D
D
So
several
things
community's
been
doing
Blazers
interesting
because
it's
kind
of
its
experimental,
it's
people
are
just
figuring
things
out
right
and
it's
some.
Some
things
are
similar
and
some
things
are
kind
of
different
patterns
and
stuff.
So,
first
of
all,
oh
gosh,
I'm
I,
forget
Brian,
wrote
this
up,
so
panes
of
glass
Ryan
wrote
up,
so
he
has
an
f-sharp
guy
and
he's
written
up
is
P
net
blazer,
rendering
with
f-sharp.
So
this
is,
this
is
a
spike.
This
is
him
just
starting
on
this,
and
blazer,
of
course,
is
also
experimental.
D
D
D
I,
didn't
click
anything
I,
just
you
know
it.
Does
this
weird
thing:
I
swear
I'd,
like
the
crazy
person.
That's
like
see.
Didn't
you
see
that
crazy
thing
I've,
never
like,
okay,
so
jeunesse
right,
he
wrote
up
this
thing
and
it's
relatively
complex.
The
work
here
to
use
c-sharp
await
against
JavaScript
promises.
What
I'm
pretty
sure
I
remember
seeing
after
this,
though
discussion
on
Twitter
was
that
I
think
it
was
Steve
Sanderson
jumped
in
and
said
this
is
cool.
You
won't
have
to
do
this
by
the
release.
D
D
This
is
cool,
so
low
hiss
wrote
up
so
he
took
the
late
well.
He
took
tour
of
Heroes,
which
is
kind
of
the
hello
world
for
angular,
and
he
has
built
this
out
using
blazer.
So
I've
talked
to
other
people
who
were
thinking.
This
would
be
a
neat
idea
to
do
and
so
Louis
actually
gone
through
and
done
this.
So
that's
that's
cool.
D
It's
interesting,
you
know,
tour
of
Heroes
is
kind
of
a
it's
a
canonical
like
it's
it's
it's
small
enough
that
it's
bite-sized,
but
it's
does
just
enough
where
it's
like
it
exercises
the
platform
a
bit.
You
know
as
a
single
page
app
platform,
so
this
is
cool
to
see
this
implement.
Okay,
and
this
is
from
talking
net,
and
this
is
on
creating
a
credit
app
using
blazer
in
asp
net
core.
D
So
the
you
know
the
work
here
required
to
do
that,
so
pretty
cool,
there's
one
other
one
that
I
had
actually
when
I
want
to
mention
this
here.
This
is
something
we've
got.
This
is
linked
off
the
dotnet
Foundation
site,
we're
starting
to
kind
of
promote
it
more.
This
is
our
dotnet
presentations,
it's
an
organization,
so
it's
multiple
repos,
of
course,
Damian
you're,
familiar
with
the
asp
net
core
app
workshop.
We
have
some
others
in
here.
Maria
put
together
this
one
recently,
which
is
asp
net
core
for
beginners.
D
So
the
idea
with
this
is,
if
you
work
lately
new
to
asp
net.
You
know
your
student
nurse,
you
know
just
getting
started
programming.
This
is
kind
of
this
is
a
approachable
half-day
one,
also
starting
to
put
in
some
other
ones
like,
for
instance,
we
have
a
what
is
net.
We
have
secure
net
is
security,
an
identity.
This
is
from
barry
and
then
we
also
have
his
authorization
and
authentication
workshop.
D
These
are
the
ones
we're
gonna,
try
and
keep
up
to
date,
and
you
are
welcome
as
a
community
to
contribute
to
them
to
grab
them
and
steal
two
or
three
slides
out
of
wherever,
like
this
is
a
resource
for
everybody,
so
awesome,
yeah
cool
so
and
it's
you
know
to
be
clear,
like
I've
done,
I've
done
a
pretty
good
amount
of
work
on
some
of
these
and
almost
no
work
on
others,
other
than
kind
of
pinging
people
and
saying
hey.
That
was
a
cool
presentation.
C
D
C
They
include
workshops
that,
like
you
know,
were
originally
started
out
by,
like
I.
Think
the
one
of
the
first
ones
was
David
and
I
taught
an
internet
call
workshop
over
the
last
couple
years
and
then
we've
rehash
it
a
couple
times
they
bounced
around
a
whole
bunch
of
different
people's
repos.
It's
turned
into
this
one,
the
a
spirit
core
app
building
workshop,
which
is
now
finally
house
in
a
global
location
on
the
dotnet
presentations
thing,
which
is
this
thing
yeah
one.
E
D
D
C
D
C
This
one
was
designed
around
like
a
workshop
scenario,
so
you
might
have
like
a
few
dozen
people
in
front
of
you.
You
have
an
instructor
and
then
you
instructor,
like
everyone,
gets
all
the
code
and
everyone
gets
the
notes,
but
the
instructor
basically
leads
the
class
through
each
session.
Each
shutting.
C
D
So,
like
oh
and
this
one
also
I
think
I'd
mentioned,
but
Shane
we
built
out
this
whole
front
end.
So
this
is
an
angular
single
page
app.
It's
got
update
that
that's
actually
I'm
in
a
weird
spot,
because
I
want
to
update
to
2.1,
but
I
need
to,
like
anyhow,
that'll,
be
updated
when
that
with
the
2.1
template,
yeah.
C
D
E
C
We
go
there,
we
go
see
that
did
a
wasn't
quite
so
dig
so
as
whispering
all
right.
So
here's
the
issue
that
you
people
don't
usually
see
all
you
focus
it's
in
our
private
repo.
This
is
tracking
all
the
blog
posts,
so
these
are
the
blog
posts
we
did
for
the
preview
features
in
2.1.
Obviously,
all
that
stuff
still
applies
so,
if
you're
just
checking
in
to
try
it
the
previews.
Now
you
can
go
and
read
those
blog
posts
that
on
the
ACE
connect
or
web
dev
and
tooling
blog
as
its
called.
D
C
Really
should
turn
off
my
alerts
so
for
preview,
there's
a
whole
bunch
of
stuff.
So,
as
I
said,
most
of
these
are
kind
of
smaller,
alright,
and
so
we
have.
Let
me
just
do
your
mail
I,
basically
just
went
through
and
queried
all
the
issues
for
things
marked
enhancement
that
we're
closed
and
then
made
sure
they
had
like
your
actual
commits,
and
so
we've
done
a
couple
of
improvements
to
the
API
controller
stuff
that
we
shipped
in
preview
one
around
how
we
bind
to
parameters
by
default.
C
We
constructed
model.
Oh
so
we've
improved
the
partial
tag
helper
to
support.
The
scenario
where
you
want
to.
This
is
provide
constructed
model
type
to
the
partial
token,
but
this
is
for
the
scenario
where
you
want
to
pass
a
like
an
object
that
you
have
already,
rather
than
giving
it
a
reference
to
something
on
the
model
you
can
do
so
you
know
how
hard
is
it
to
suppress
these
flippin
warnings
these
days,
like
I,
find
it
like
I
go
here.
That's
like
great.
How
do
I
turn
these
off.
C
C
C
D
C
Helpful
we've
added
an
analyzer
is
one
of
our
first
analyzers
in
the
product
to
warn
about
using
HTML
DeParle,
and
so
we
don't
have
a
particularly
solid
strategy
for
deprecating.
Ap
is
obsolete
in
them
they
can
be
quite
impactful
to
add.
You
know
we
have
an
existing
absolution
attribute,
but
it
can
be
impactful
to
builds
because
it
ends
up
failing
the
build,
often
and
can
be
difficult
to
turn
off
and
whatnot,
and
so
we're
trying
out
using
analyzer
to
do
this
instead.
C
So
now
that
razor
views
are
compiled
by
default
on
build
analyzers
we'll
be
included
by
default
in
these
projects,
and
so
if
you
use
HTML
des
partial,
that
is
the
non
async
version
of
those
api's,
you
will
get
a
warning
now.
It'll
be
an
analyzer,
basically,
failure,
ok,
because
there's
a
Dane
using
the
non
async
versions
of
those
because
Razer
execution
is
now
async.
If
you,
you
know,
execute
a
partial
that
itself
calls
in
to
anything
that
is
asynchronous,
then
you
can
end
up
quite
easily
deadlock
in
your
application.
C
You
can
cause
well
technically,
it's
not
a
real
deadlock,
but
if
you
continue
adding,
if
you
have
a
persistence,
that'll
load
on
the
app
it'll
never
recover,
and
so
we
wanted
to
ensure
that
people
are
using
the
right
API.
The
idea
is
that
in
a
future
major
version,
we
would
delete
these
API
s,
and
so
the
analyzer
that
we're
introducing
now
is
to
encourage
people
to
get
off
using
theirs
api's.
Now,
okay,
we
have
added
an
option
to
the
templates.
C
Now,
as
we
talked
about
into
one
preview
one,
the
templates
are
HTTP
by
default
now,
so
there's
now
an
option
during
file
new
and
visual
studio
and
at
the
command
line
to
opt
out
of
that.
If
you
want
to,
there
are
some
scenarios
where,
obviously
you
don't
want
HTTP,
although
those
scenarios
are
also
shrinking,
but
you
can
turn
it
off
now.
We've
made
some
small
improvements
to
API
Explorer.
They
were
mostly
bug
fixes.
That's
not
really
that
interesting.
C
We've
had
multiple
customer
feedback
about
this,
and
so
we
decided
it
was
important
enough
that
we
had
to
make
that
change.
We
updated
all
I
dependencies
adjacent
on
a
11,
the
next
major
version.
Now
that
James
has
really
set.
So
that's
good.
We
added
the
existing
web
api
to
a
client
package
to
the
dot,
app
and
dot
all
meta
packages.
So
this
is
the
package
that's
been
around
since
we
shipped
web
api
all
the
way
back,
but
it
was
recently
updated
to
support
net
standard.
C
So
you
can
now
use
the
web
api
client
package
in
your
dotnet
core
applications
that
gives
you
all
those
nice
convenience
measures
messages
like
senders,
Jace
posters,
Jason
Rivas
Jason.
So
we
include
that
in
the
meta
package
now,
because
it's
actually
really
really
nice
to
work
with.
There
is
support
for
32
and
Alpine
coming
in
this
release
as
well.
So
if
you're
interested
in
running
Eastern
air
corps
on
out
on
32,
you
can
do
that
now.
With
that
package
there
will
be
a
shared
framework.
C
The
packages
will
work,
so
you
can
run
on
the
raspberry
pi.
We
did
some
perf
I,
don't
know
if
you
saw
the
tweet
a
couple
weeks
ago,
run
on
the
Raspberry
Pi
and
got
some
pretty
good
numbers
close
to
50,000
requests
per
second
for
plain
text,
which
was
pretty
good
and
then
Alpine
supporters
for
folks.
Looking
at
you
know
for
super
small
docker
base
images,
the
other
advantage
of
images
like
Alpine's,
because
they're
so
small
with
so
few
dependencies.
C
They
can
be
attractive
from
a
security
point
of
view,
because
there's
a
lot
less
in
the
images
so
they're
much
generally
much
easier
to
pass
a
security
scan
when
your
image
is
so
small
to
start
with.
So
that's
some
feedback
that
we've
had
so
we've
done
that
work
to
support
alpine.
We
have
basically
removed
the
a
spinet
core,
docker
images
and
we've
well
the
sdk
image
specifically
and
we've
now
sort
of
rationalize
with
the.net
core
image.
So
if
you
just
want
to
build
dotnet
core
apps,
you
now
should
just
use
the
dotnet
core
sdk
image.
C
Previously
we
had
an
ace
phonetic
called
build
image
which
included
things
like
node
and
Bower
and
a
bunch
of
other
stuff,
but
the
best
way
to
do
that
today.
If
you
do
need
to
use
those
things,
is
to
configure
a
multi-stage
build
using
those
features
in
docker,
where
you
have
a
container
set
up
to
use
node
to
do
that
stage
of
the
build
and
have
a
different.
C
And
then
you
see
a
spinet
core
or
the
dotnet
core
sdk
image
in
order
to
do
the
dotnet
part
of
the
build,
and
so
we
have
done
that
change
they're,
still
an
ace
when
they
call
run
time
image
because
we
have
the
shared
framework.
Now
so
there's
a
spinnaker
app
shared
framework,
and
so
you
have
a
separate
docker
image
for
that
and
but
they're
all
in
the
same
repo.
Now.
C
The
identity,
the
moving
of
the
default
identity
UI
into
packages,
has
been
complete.
So
we
did
that
for
individual
off
in
preview,
one
if
you
recall
so
that
username
password
and
all
a
star.
Now
you
don't
have
to
have
all
the
UI
in
the
app
it
comes
from
the
Rays
from
the
library
we've
extended
that
to
all
the
other
or
Thaksin's.
So
if
you're
using
Azure
ad,
you
know
single
log,
multi
org
or
the
other
options
that
we
have.
They
are
also
now
come
in
packages
which
is
nice.
C
We
also
updated
the
scaffold
ER
for
the
individual
or
stuff,
but,
as
I
said,
we
had
to
pull
that
very
late,
so
the
work
has
happened.
It
just
hasn't
shipped
and
so
you'll
see
that
in
the
next
release,
you'll
be
able
to
use
the
visual
studio
experience.
Actually
you
will
be
able
use
that
now.
I
think
so,
hang
on.
Let
me
try
it.
Here
I
am
in
an
app
here's,
an
app
I
created
earlier.
This
one
doesn't
have
off,
but
I
think
think
I
can
come
in
here.
A
C
I
can
say,
add
so
I
can
add
identity
retrospectively,
so
see
this
if
I
had
identity
already.
So
what
this
will
do
is
it'll
add
the
identity,
UI
package,
which
gives
you
all
the
UI
right,
but
then
you
can
choose
to
override
any
of
those
things
from
the
default
UI
by
saying
it
and
I
want
this
file
in
my
app,
which
overrides
the
one
in
the
library
so.
D
C
C
True
I
should
get
them
to
change
that
string
anyway,
so
it
added
the
package
which
contains
the
scaffolder
itself.
Mm-Hmm
did
the
project,
and
now
it's
actually
running
the
scaffolder
generating
code
and
oh
there
we
go
and
then
I
get
a
little
readme.
That's
like
hey.
You
may
have
to
go
and
change
some
stuff
alright.
So
if
we
go
over
to
the
right
here,
it
added
my
area
but
identity.
Then
it
added
what
is
required
in
order
to
override
the
stuff
that
I
asked
to
override
okay.
C
And
then
your
app
will
find
this
because
of
this
assembly
tag
here
and
we
attribute
the
eighty
net
will
find
this
class
automatically
without
you
having
to
call
it
from
your
startup
class
manually,
and
it
will
run
all
this
as
part
of
a
startup
code.
Alright,
so
I
mean
if
some
of
these
things
end
up
running
twice,
but
their
item
potent.
So
it
doesn't
matter.
So
this
sets
up
identity
right.
This
adds
all
the
identity
stuff
and
then.
C
Majors
written
so
under
account
and
under
login,
alright,
so
there's
the
login
page
so
now
I'm
Frieda
to
override
the
login
page,
but
all
the
other
stuff,
the
account
management.
Everything
is
coming
from
the
library,
so
I
don't
have
it
in
my
app
ok.
So
that
is
the
idea
behind
this.
So
we
would
like
folks
to
try
this
out
and
give
us
feedback.
We
know
there
are
some
usability
issues
with
it.
At
this
point
couple
scenarios
don't
work
as
well
as
we'd
like
or
at
all
like.
C
If
you
start
from
empty
right
now,
I
think
and
you
run
the
scaffolder-
it
emits
code
that
doesn't
compile.
You
have
to
go
and
fix
it
in
a
bunch
of
places
which
will
we'll
get
all
this
fixed.
But
this
is
the
state
of
it
in
preview
too.
So
yeah,
that's,
definitely
an
improvement
and
so
gives
you
an
idea
of
the
direction
we
want
to
go
on
this
one
thing.
D
To
show
you
that
I'm
not
completely
paying
attention
to
you,
but
just
looking
at
shiny
things,
okay,
that
scaffold
or
UI
looked
kind
of
cool
and
modern,
but
a
little
different
than
some
of
the
other
dialogues
I'm
used
to
invested
I
did
know
in
a
good
way,
but
I
mean
like
it
just
looks:
sullen
yeah
look.
Center,
oh,
is
it?
Is
it
built
kind
of
WPF.
C
D
C
C
Exactly
like
a
check
box
tree
exactly
yeah
anyway,
so
that
that's
in
there,
which
is
good,
so
we've
got
that
in
that
improvement,
what
else
the
keeper
file.
So
this
is
what
was
previously
known
as
the
docker
configuration
provider
or
the
container
configuration
provider.
So
a
couple
of
different
container
orchestrators
like
docker,
compose
and
kubernetes
support
this
idea
of
supplying
secrets
or
compare
secret
configuration,
or
you
know
just
file
based
configuration
for
the
container
generally.
Why
having
a
special
folder,
that's
mounted
volume
mapped
into
your
container
generally.
C
That,
then,
has
a
file.
/
configuration
key,
so
I
have
a
value
called
foo
with
a
value
of
bar,
so
I'd
have
a
file
name
of
foo
and
inside
that
would
be
a
value
of
bar
right.
So
we
built
a
configuration
provider
for
our
configuration
system
that
supports
this
convention
is
called
the
I,
think
it's
keeper
file
configuration
provider
and
you
would
typically
use
it
in
container
deployments.
That's
the
idea
flow,
there's
some
new
stuff
and
identity
around
this
personal
data
attribute.
C
This
is
designed
to
make
it
in
in
systems
where
you're
extending
the
identity
system
to
contain
profile
information.
So
like
this
person's
favorite
color
or
the
name
of
their
first
dog,
or
you
know
that
type
of
stuff
or
whatever
information
you
want
to
store
about
a
user
and
you're
doing
it
through
identity,
you
can
now
attribute
those
properties
on
your
model
with
the
personal
data
attribute,
and
then
that
marks
it
as
something
that
might
be
potentially
sensitive
when
it
comes
to
things
like
legislation
like
great
so.
C
Of
that,
and
then
this
can
be
flowed
through
encryption
and
all
those
type
of
things.
So
it
gives
you
metadata
that
you
can
then
inspect
at
the
right
point
in
the
in
your
app.
In
order
to
do
the
right
thing,
we
had
to
pull
out
or
postpone
the
workaround
NCM
that
we
were
doing
so.
We've
talked
about
the
improvements
to
NCM
that
we're
working
on
to
make
it
in
process
hosting
and
to
make
it
more
resilient
to
version
changes
in
the
future,
because
currently
it's
a
global
native
module.
We
had
to
pull
that
out.
C
C
Okay,
so
you
don't
have
to
wait
necessarily
for
like
the
next
minor
release
and,
however
much
time
we
want
to
try
and
continue
the
NCM
work
in
a
non
impactful
way,
so
that
you
can
install
it
side
by
side
with
the
production
sort
of
current
version
of
a
in
cm
and
not
worry
about
breaking
yourself.
These
wait.
D
C
C
Like
the
danger
was
literally
because
a
NCM
today
is
a
global
component.
If
we
want
to
change
it
to
improve
2.1,
you
risk
breaking
100,
apps
and
one
one.
Apps
are
200
apps
right,
and
so
we
have
a
new
plan
which
literally
starts
versioning
a
NCM
side
by
side
like
the
rest
of
dotnet
core,
which
yeah
it
means.
There's
a
couple
more
moving
pieces
and
like
it's
making.
C
C
Soon,
as
you
put
a
doorbell
camera
on
your
house
right,
is
that
all
the
kids
learn
and
they
distract
you
during
the
day
yeah
the
razor
pages
and
controller
feature
where
you
can
have
properties
that
are
backed
by
temp
data.
We've
now
extended
that
to
support
view
data
as
well.
This
is
particularly
useful
where
you
want
to
have
like
pages
or
views
set,
the
title
of
the
page,
and
that
has
to
go
through
the
view.
Data
dictionary
all
the
way
to
the
layout
page
and
it's
all
just
magic
strings.
C
So
now
at
least
you
can
set
it
from
your
page
model
on
a
property
or
you
controller
on
a
property
marketers
view
data.
You
can
reference
it
the
view
in
a
strongly
typed
fashion,
because
it'll
be
a
property
and
then
the
only
place
you
have
to
reference
it
by
string
is
in
the
layout
page,
and
then
we
have
a
issue
logged
that
for
a
future
version.
We
can
get
rid
of
the
string
and
the
layout
page
as
well,
and
hopefully
have
it
nicely
sort
of
strongly
typed
all
the
way
through.
C
So
we've
made
some
improvements
there
as
well,
and
then,
lastly,
in
kestrel
we
have
made
the
decision
to
switch
Kestrel
to
the
sockets
transport
by
default.
So
that's
true
in
preview.
It's
not
libuv
by
default
anymore,
it
is
sockets.
Libuv
is
still
available
as
a
package
for
folks
who
would
really
want
to
use
it.
There's
really
not
much
more.
C
It
gives
you
in
terms
of
flexibility
or
configuration
so,
but
there
are
some-
and
there
are
some
very
nice,
a
consensus
where
you
might
want
to
use
it
over
sockets
today,
but
sockets
is
now
the
default
and
we
added
support
for
sni
or
server
name
identification,
which
lets
you
actually
have
an
email
here
which
talks
about
that
which
I
have
to
put
in
the
blog
post
here
from
Chris
server
name.
Identification
is
basically
the
feature
that
lets.
You
have
multiple
HTTPS
certificates
registered
in
a
single
application
for
different
host
names.
C
All
listening
on
the
same
IP
address
right.
So
typically,
when
you
before
S&I,
you
would
have
to
have
a
separate
IP
address
or
port
on
the
server
I
think
it's
actually
yeah,
one
of
the
other
usually
don't
want.
People
have
to
change
the
port
right
because
it's
all
four
four
three,
so
you
don't
have
to
type
a
separate
IP
address
in
each
of
the
domains
that
you
want
to
register
for
a
given
application
so
that
they
can
learn
a
different
certificate.
S&Amp;I
lets
you
do
this
in
a
light
bound
way.
C
All
right
is
has
supported
this
since
version
7,
I
think
7.5
and
Internet
Explorer
I
got
this
support
in
IE,
9
or
something
so
if
there's
have
been
around
forever,
but
we
didn't
have
it
in
dotnet
core.
So
we've
now
got
the
changes
in
dotnet
core
itself
in
the
SSL
stream
to
support
this
and
we've
plumbed
this
through
to
guest
all.
So
this
is
the
type
of
code
you
see.
Basically,
when
you
configure
kestrel
in
this
case,
this
application
has
three
domains
that
it
listens.
C
On
localhost,
example.com
and
sub
example:
com
there's
a
separate
certificate
for
each
one.
Obviously,
because
they're
separate
domain
names,
then
it
configures
a
dictionary.
This
happens
once
per
application
so
that
they
can
look
up
the
certificate
per
domain
and
then,
when
a
connection
comes
in,
this
callback
gets
called
by
kestrel
and
it
basically
says
hey
which
certificate
should
I
use
for
this
connection,
all
right
and
then
you
can
look
up.
C
It
passes
you
the
name
but
the
host
it
came
in
on
and
then
you
can
use
that
to
go
and
look
up
the
correct
certificate
and
return
the
correct
certificate
or
return.
None
if
you
don't
want
a
certificate
to
be
used.
Okay,
so
that's
a
nice
development,
a
sort
of
a
late
feature
that
we
got
into
one
for
folks
who
need
that
type
of
capability
go
done
and
I
have
a
meeting
to
go
to.
Okay,.
D
C
C
C
Quinton
does
ask:
where
can
they
find
out
about
UF
core
on
two
point,
one
there
will
be
a
blog
post
on
EF
core
on
the
dotnet
blog,
hopefully
by
the
end
of
June,
a
assuming
that
the
release
gets
live
by
the
end
of
eight.
Today
we
get
the
download
page
updated,
then
you'll
be
able
to
get
that
blog
post
I'll
be
alive
today,
I'm
looking
at
the
page
right
now
and
the
link
is
lock-on
live
yet
so
alright.