►
Description
Azure Static Web Apps now has first-class support for Blazor WebAssembly and .NET Functions in preview, available in all supported regions. We'll have some fun new demos from Anthony Chu, live Q&A, community links and updates, and more!
Community Links: https://www.theurlist.com/aspnet-standup-2020-10-06
Featuring: Safia Abdalla (@captainsafia), Anthony Chu (@nthonyChu), Daniel Roth (@danroth27)
#Blazor #aspnet #dotnet #Azure
A
A
And
hello:
welcome
to
the.net
community
stand
up,
the
asp.net
community
stand
up,
and
this
is
the
first
of
a
new
thing,
we're
doing
the
blazer
monthly
series
we're
doing
enough.
Blazer
shows
it's
like
why
not
just
make
it
a
monthly
blazer
party,
and
so
as
part
of
that
super
excited
to
welcome
safiya
as
co-host
of
the
blazer
monthly
club.
A
A
As
always,
we
share
these
out,
so
someone
always
asks
yes,
we'll
share
them
out,
and
actually
I
can
put
them
in
the
chat,
because
why
not
so
here's
the
links
I'm
going
to
be
sharing
and
there's
so
much
good
stuff?
I
focused
on
blazer
stuff
pretty
much
completely
this
week,
so
here's
a
few
cool
ones
that
I
just
saw
come
by
these
are
some
you
know.
People
are
building
tons
of
cool
components,
and
so
this
is
a
grid
and
I
love
seeing
how
people
build
these
kind
of
more
complex
things.
C
A
D
A
A
A
Stuff,
and
so
anyhow,
this
is
neat
congrats
to
kristen
and
team
okay.
This
is
about
so
gerald
he's
been
doing
some
cool
posts
lately
on
blazer,
and
this
is
on
javascript
isolation
and
blazer
components.
So
this
is
a
theme
that
I've
been
seeing
lately
and
the
whole
kind
of
isolation
and
there's
you
know
the
css
isolation
and
there's
the
you
know.
I
I
hadn't
seen
anything
before
welcome
back
dan,
so
so
this
is
looking
at
javascript
isolation.
A
This
is
honestly
one
thing:
javascript
componentization
moves
quickly
and
I
have
trouble
keeping
up
with
it.
So
I
read
this
once:
I'm
gonna
need
to
read
through
this
again
personally,
but
this
I
don't
know
it
looks
interesting
and
and
like
I
was
saying,
the
whole
theme
of
componentization
either
of
you
folks
want
to
hop
in
on
that,
like
anyone,
any
of
you,
yeah.
B
Some
of
this
javascript
isolation
stuff
was
actually
again
a
work
that
our
intern
mckinnon
did
and
it's
been
really
cool
to
see
some
of
the
ways
that
people
have
been
building
on
it
over
the
past
few
months
we
shipped
it
alongside
css
isolation
or
maybe
shortly
after
css
isolation
as
one
of
the
net
five
previews,
so
cool
stuff
and
again
another
gift
from
mckinnon.
Our
intern.
A
Very
nice
cool
all
right.
Let
me
see
I
have
too
many
screens
and
too
many
okay.
This
was
this
is
just
a
small
little
call
out,
while
we
were
waiting
for
the
show
to
start
dan
reminded
me
that
there
is
a
community
out
on
reddit
for
blazer.
So
this
is
neat.
If
you're
part
of
the
blazer
community
looks
like
cool
place
to
kind
of
keep
up
with
stuff
and
share
some
links
chat
with
the
with
the
blazer
community,
yeah
yeah.
A
A
We'll
see
if
we
get
enough
likes
on
this,
whatever
no
I'm
not
gonna
buy
those
boots,
so
this
is
cool.
This
is
drag
and
drop
uploading
from
roman
using
input
file
component,
so
he's
been
doing
some
some
cool
stuff,
just
in
general,
with
like
with
input
files
and
uploads,
and
things
like
that.
So
this
is
cool
to
see.
Wrapping
input
file,
as
I
continue
to
you,
know,
try
and
keep
up
with
with
the
piece
of
blazer
and
all
the
exciting
things
going
on
in
blazer
land.
D
And
for
the
most
part,
they
behave
like
the
html
equivalents.
They
just
they
give
you
some
some
niceties
on
top
of
them
to
like
help
you
with
like
validation
and
it's
basically,
it's
basically
validation
is
the
main
feature,
but
for
the
most
part
you
can
think
of
them
as
their
html
equivalent
and
add
the
same
attributes
on
them
that
you
would
add
to
the
html
equivalent.
A
I
tried
that
recently
I
was
working
on
something
I'm
like
could
I
put
in.
I
forget
it
was
a
placeholder
or
something
I
just
typed
the
html
and
it
all
works
so
yeah
good
stuff,
so
neat
to
see
with
this
the
wrapping
wrapping
that
to
add
in
drag
and
drop
support.
So
definitely
you
know
you
need
to
write
some
code,
but
I
don't
know
pretty
neat.
D
Yeah,
drag
and
drop
is
one
of
those
areas
that,
like
we
had
actually
hope
to
to
maybe
do
something
about
that
in
dot
net
five
we
didn't
quite
get
to
it.
Dominant
five
was
a
fairly
compressed
release
for
the
blazer
team
because
of
the
blazer
web
assembly
released
in
may,
but
it
is
something
that
we've
been
doing.
Some
some
thinking
on
and
hopefully
for.net
6,
maybe
we'll
we'll
have
something
in
that
area.
A
Cool,
so
to
balance
off
with
that
previous
one
where
it
took
a
decent
amount
of
code.
This
is
under
10
lines
of
code
for
a
simple
tool,
tip
component
and
again
this
whole
thing.
This
theme
of
like
componentizing
stuff,
so
there's
plenty
of
stuff
that
you
can
do
with
browser
standards
and
it
often
can
take
like
a
little
bit
of
work
and
you
got
to
write
some
css
and
all
that,
so
the
componentizing
here
with
the
css
for
the
tooltip
seems
really
nice.
So
this
is
just
a
very
simple.
A
You
know
just
dropping
it
in
and
there
you
go
so
very
nice
all
right.
This
is
from
michael
washington,
pretty
sure
his
name's
michael
washington.
I
forget
when
people
put
their
he's
a
deaf
web
server,
he
writes
so
much
cool
stuff.
So
this
one
is
a
simple
survey,
and
so
the
idea
here
is
you
know
it's.
You
can
go
through
and
you
create
a
survey.
You
know
and
have
different
types.
A
A
A
Thank
you,
cool
and
last
one
here,
john
hilton
and
once
again
wrapping
cool
stuff
making
it
blazerified.
So
this
is
rendering
diagrams
in
blazer
application.
So
this
is
using
graphis
and
let
me
let
me
we're
fighting
over
who's
sharing
the
stream.
Let
me
share
just
the
rss,
so
this
is
this:
rendering
a
diagram
and
all
he's
doing
there.
What's
cool
graphiz
uses
svg
and
so
that
this
is
kind
of
the
end
result.
A
B
One
of
those
that
I'd
like
to
highlight
is
actually
something
that
landed
in
rc1,
which
is
improvement
to
the
reconnect
overlay
in
blazer
server.
If
you've
ever
developed
a
blazer
server
application,
you
might
have
noticed
that
sometimes,
if
the
circuit
disconnects
you
get
this
display
that
it's
reconnecting,
but
it's
not
that
helpful.
So
it's
really
great
to
see
juan,
take
the
initiative
and
ship
some
improvements
to
this.
B
It
includes
the
ability
to
see
which
reconnect
attempt
it's
making
as
well
as
an
actual
loader
icon.
So
you
know
that's
something's,
going
on
under
the
hood.
So
again,
thank
you,
juan
for
taking
the
time
to
make
these
improvements
really
helps
improve
the
quality
of
life
for
everyone,
who's
building
on
top
of
blazer
server.
B
Cool
now,
if
you're
wondering
how
can
I
get
a
chance
to
be
showcased
in
a
community
spotlight?
Oh
or
there's
an
opportunity
for
you,
we
have
our
monthly
blazer
development
sprints.
They
happen
on
the
second
tuesday
of
the
month.
That
means
the
next
one
is
going
to
be
this
thursday.
Actually,
on
october
8th,
so
you
can
go
ahead
and
participate.
You
can
find
more
information
at
aka,
ms
blazer
sprints.
It's
super
chill.
It's
basically
an
opportunity
for
you
to
work
on
some
issues
that
we've
labeled
as
new
contributor
friendly
on
blazer.
B
B
Now,
there's
one
last
thing:
I
want
to
leave
you
with
and
it
actually
touches
on
something
that
dan
talked
about
a
little
bit
previously
around
net
six.
So
I
know
we're
about
to
ship
dot
net
5ga
in
a
few
weeks,
but
we're
already
thinking
about
what
we're
gonna
do
with
net
six,
and
this
is
a
great
opportunity
for
you
to
make
your
voice
heard
about
what
should
be
prioritized
and
what
you'd
like
to
see
happen
in
dot
net
six.
So
how
can
you
do
that?
B
B
D
Yeah
on
the
acemic
core
repo,
we
do
look
at
these
reactions
as
a
way
to
help
us
prioritize
items.
We
have
noticed
that,
though
we
don't
get
quite
as
many
on
that
repo,
as
we've
seen
on
like
the
like
the
dot-net
runtime
repo,
the
andy
framer
core
repo,
we're
trying
to
figure
out
what
we
can
do
to
better
engage
with
the
community
and
hear
your
voice.
So
this
is
our
invitation
to
participate
more.
D
B
E
C
E
Right
yeah,
it's
amazing!
So
on
the
azure
function
side,
I'm
also
the
pm
of
dot
net
azure
functions
as
well.
So
I'm
very
excited
to
see
that
see
this
happen.
So
yeah,
I'm
just
going
to
kind
of
dive
into
a
few
slides
and
just
talk
about
why
we
want
to
do
this
and
why?
Why
would
you
why
you
want
to
deploy
blazer
assembly
to
azure
static,
web
apps
and
then
we'll
just
kind
of
spend
the
rest
of
the
time
doing
a
demo
how's
that
sound.
E
All
right,
if
I
know
how
to
advance
my
slides
or
even
better
okay,
so
so
like
this,
is
traditionally
how
you
would
deploy
a
blazer
app
with
asp.net
core
today.
So
you
have
an
asp.net
core
app
on
the
server
and
its
job
is
to
serve
up
the
blazer
app
as
well,
as
you
know,
serve
up
any
api
endpoints
that
you
might
want
to
expose
to
your
application.
E
Now
you
have
your
net
code
running
in
the
browser
using
laser
web
assembly,
and
then
you
know
once
in
a
while
it'll
make
an
api
call
to
the
server
and
that's
where
the
asp.net
core
actually
does
some
work
with
azure
static
web
apps.
What
you
can
do
and
what
we
allow
you
to
do
is
we
provide
you
a
way
to
kind
of
just
really
easily
serve
up
a
bunch
of
static
files
and
that's
what's
a
blazers
assembly
app?
Is
it's
just
html
css
some
web
assemblies
and
dlls
and
some
javascript?
E
E
So
so,
when
I
got
to
talk
about
some
of
the
features
of
azure
static
web
apps,
so
I
kind
of
already
talked
about
the
static
file
hosting,
as
well
as
the
serverless
apis.
One
of
the
things
that
you
also
get
with
it
is
they
both
kind
of
live
behind
the
same
domain
name,
so
you
don't
have
to
worry
about
cores
or
anything.
Everything
can
kind
of
get
served
by
kind
of
the
same
endpoint.
E
If
you
kind
of
want
to
think
about
that
way-
and
it's
really
easy
to
build
and
deploy
these
things
using
github
actions
and
I'll
show
you
that
in
the
beds
using
in
the
demos
and
then
we
support
custom
domain,
so
you
can
bring
your
own
custom
domain
and
add
it
to
azure
static
web
apps.
And
then
we
also
give
you
a
free,
ssl
cert
for
it
as
well.
E
So
this
is
kind
of
particularly
important
for
single
page
applications
like
blazer
or
react
or
view
where
you
have
these
kind
of
client-side
routes.
That
routes
are
only
known
that
they're
only
known
to
the
side
application.
So
if
somebody
actually
like
bookmarks
that
route
that
happens
to
be
in
the
browser
and
then
they
go
to
it,
it's
actually
going
to
go.
Ask
the
browser
is
going
to
ask
the
server
for
for
that
route
and
it's
going
to
be
like.
Well,
that's
not
there,
because
that's
not
a
real
route.
E
It's
actually
known
only
to
the
client
side
app,
so
you
can
actually
set
up,
what's
called,
what's
called
a
fallback
route
so
that
you
can
actually
serve
up
your
app,
no
matter
which
route
the
the
customer
or
like
the
the
browser
decides
to
hit
and
then
within
the
app.
That's
that
that's
served
up,
they'll
understand
how
to
actually
navigate
to
to
to
that
route.
So
so,
typically,
that's
pretty.
E
You
know
a
pretty
typical
thing
that
you
want
to
do
in
in
a
static
web
app
like
this,
so
we
make
that
pretty
easy
for
you
to
do
and
also
with
with
with
an
app
hosted
on
github.
Quite
often,
we
get
pull
requests
and
things
like
that,
either
from
the
community
or
from
other
team
members,
or
just
even
just
yourself,
working
on
an
app
so
for
every
pull
request.
We
will
stand
up
a
staging
site
for
you
and
then
that
staging
site,
your
you
can
actually
kind
of
preview.
A
Y'all,
I
mean
just
one
comment:
I
guess
it's
like
a
lot
of
that
stuff.
You're
sharing
on
the
previous
slide.
We've
seen
you
could
do
this
before,
but
you
had
to
do
it
all
manually
right.
You
had
to
go,
get
your
cert,
you
had
to
renew
your
cert
and
you
had
to
set
like
the
the
thing
you
were
talking
about
with
the
wild
card
routes.
Like
that's,
amazing,
that's
a
pain
in
the
neck,
and
it's
always
like
oh
shoot.
I
got
to
deal
with
that.
A
E
Absolutely
all
right,
so,
let's
go
and
jump
to
the
demo,
so
the
demo
that
I'm
actually
going
to
do
is
actually
based
on
a
pretty
old
demo
by
the
asp.net
team
to
kind
of
show
off
some
of
the
capabilities
of
signalr.
So
there's
a
asp.net
core
app
here.
That's
that
basically
will
use
the
browser
to
take
control
your
camera
and
then
turn
your
video
image
into
basically
a
bunch
of
ascii
representation
of
your
video
and
then
stream
it
to
others
around
the
world.
E
So
to
do
that,
I
think
I
have
I'll
kind
of
just
quickly
walk
you
through
the
app
and
then
we'll
just
go
ahead
and
deploy
it,
and
so
the
app
is
pretty
simple.
I
have
an
api,
that's
basically
an
azure
function,
app
and
here's
the
functions
right
here.
The
main
part
is
this:
send
frame
async
function.
So
all
we're
doing
is
that
we're
taking
like
four
times
a
second
in
the
browser,
I'll
kind
of
show
you
the
the
browser
side
of
things
in
a
bit.
E
We
will
send
the
ascii
representation
of
your
video
four
times
a
second
to
this
azure
function
and
then
this
azure's
function's
only
job
is
to
take
that
take
that
frame
and
then
send
that
off
to
azure
signal
or
service
and
then
your
client
side,
laser
app,
is
also
connected
to
azure
signalr
service
and
it's
receiving
all
these
frames.
So
the
more
people
that
are
connected
to
this
app,
the
more
kind
of
video
frames
that
you're
seeing
in
real
time.
E
So
that's
this
is
like
the
entire
function,
app
itself
like
40
lines
of
code.
To
do
all
this
work,
there's
really
nothing
more
to
it
and
then
I'll
I'll
kind
of
show
you,
the
the
blazer
web
assembly
side.
So
it's
a
pretty
standard
web
blazer
web
assembly
app.
I
literally
just
went
on
that
new
blazer
wasm
and
it
kind
of
gave
me
this
app,
some
of
the
things
that
the
interesting
parts
are
probably
here
in
the
index
dot
razor
page.
So
you
can
see.
E
So
this
is
the
same
signalr
library
that
you
would
typically
pull
in
to
a
blazer
app,
and
so
I'm
just
creating
a
hub
builder,
giving
it
the
url
of
my
function
app
and
then
I'm
also
setting
up
a
handler.
Whenever
I
receive
a
new
frame,
I
will
basically
just
add
it
to
a
list
of
frames.
Probably
could
be
done
a
better
way,
but
but
this
is
the
way
I'm
doing
it
right
now
and
then
I'm
just
starting
the
connection.
E
E
E
A
B
E
Yeah,
it
wasn't.
Okay,
there
we
go
yeah.
The
code
is
so
simple:
yeah
like
it's
really
literally,
not
doing
anything
so
I'm
like
so
this
is
the
javascript
code
calls
this
gives
it
the
ascii
string
and
then
I'm
just
building
up
an
object
and
just
posting
that
to
the
azure
function,
so
pretty
simple
and
then
the
rest
of
it
is
just
code.
So
you
know
100
something
lines
of
code
to
build
this
app.
E
E
F
E
E
So
this
is
how
kind
of
kind
of
how
it
works
so
so
yeah.
So
this
is
this
is
the
app
that
we're
going
to
deploy
now
any
questions
before
we
kind
of
start
deploying
actually,
let's
start
deploying
first
and
then
we'll
answer
some
questions
about
what
kind
of
wait
for
things
that
happen
in
the
cloud
all
right,
so
the
to
deploy
the
app.
I
have
it's
already
pushed
to
my
github
repo.
E
So
if
you
kind
of
go
to
anthony2
serverless
streamer
blazer,
I'm
going
to
deploy
this
demo
branch,
I
have
a
few
other
branches
on
here
as
well.
So
you
can
see.
This
is
just
the
same
code
that
I
have
on
my
machine,
but
now
in
github,
and
I'm
just
going
to
go
ahead
and
deploy
this
so
to
do
this.
Let's
just
go
to
the
azure
portal.
I'm
gonna
go
ahead
and
create
a
resource.
E
E
E
So
the
next
thing
I'll
do
is
I'll
sign
into
github.
So
after
I've
done
that
it
pulls
back
all
the
organizations
I'm
part
of,
and
then
it
pulls
back
all
the
repositories
that
I
have
so
actually
I'm
just
gonna
search
for
it
there.
It
is
I'm
going
to
go
and
pick
my
branch,
which
I
think
I
said
I
was
going
to
do.
The
demo
branch.
A
E
So
this
is
where
the
next
part
comes
in,
so
so
you
can
actually
tell
the
service,
which
in
turn,
tells
the
github
action
where
to
find
your
function
app,
as
well
as
your
blazer
app,
and
also
where
the
build
output
is
so
and
that's
kind
of
taken
care
of
by
this
preset.
So
blazer
shows
up
here.
So
if
you
choose
blazer,
we
kind
of
just
have
some
conventions
currently
and
we're
going
to
try
to
make
this
a
little
bit
smarter
and
that
will
start
hopefully
sometime
in
the
future.
E
Actually
we'll
probe
your
project
actually
try
to
figure
out
where
these
things
are.
But
for
now
we
have
just
some
smart
defaults
and
because
I
know
what
these
defaults
are,
I
made
my
app
the
same
as
well
so,
but
you
can
you're
free
to
change
these
so
so
the
client
is
where
the
the
blazer
app
is
api
is
where
the
function
app
is
and
then
we're
just
saying
that
the
blazer
app
gets
compiled
to
triple
w
and
that's
the
thing
that
we
want
to
deploy.
E
Yeah,
that's
exactly
right!
All
right,
then
we're
just
gonna
go
ahead
and
create
it,
so
it
doesn't
take
long
to
create.
So
what
we're
doing
is
just
creating
the
static
web
app
resource
and
then
once
that's
done
or
although
I
guess
I
guess
at
the
same
time,
what
we're
doing
is
we're
adding
a
github
action
on
behind
the
scenes
for
you.
So
if
I
now
refresh
this
page,
you
can
see
that
it
added
a
workflow
in
here
and
then
in
here
I'll
try
to
make
this
a
little
bigger
as
well.
E
Here's
the
github
action
some
stuff
in
it.
You
typically
don't
even
have
to
know
what's
going
on.
Unless
you
need
to
go
ahead
and
change
these
values
that
you
put
in
earlier,
then
you
kind
of
have
to
kind
of
go
in
here
and
figure
out
what
to
modify,
but
for
the
most
part
you
don't
have
to
worry
too
much
about
it.
E
You
can
see
that
the
action's
already
started
and
then,
if
we
go
in
here,
you
can
see
that
it's
actually
building
and
deploying
the
app,
and
now
we
wait.
So
it's
going
to
take
about
a
couple
of
minutes.
Thankfully,
it's
not
running
on
my
machine,
so
I
don't
have
to
worry
about
it
taking
super
long,
but
it
seems.
A
Let's
get
some
questions,
okay,
so
one
that
came
up
and
and
dan
answered
part
of
it.
Let
me
see
why
azure
static
web
apps
as
opposed
to
github
pages
or
other
kind
of
hosting.
I
know
I
know
that
some
of
this
was
already
I
mean
you
talked
through
some
of
the
things,
but
what's
the
kind
of
the
main
things
here.
E
Yeah,
I
think
there
there
is
quite
a
bit
of
overlap,
I
would
say,
but
I
would
but
but
for
static
web
apps
and
azure
static
webs
in
general.
Some
of
the
things
that
you
do
get
that
are
on
top
of
what
you
get
with
something
like
github
pages,
is
kind
of
like
the
integration
with
azure
functions.
So
I
kind
of
talked
about
a
little
bit
earlier
that
you
behind
the
same
domain.
E
You
have
basically
your
static
assets
as
well
as
your
function
app,
so
that
allows
us
to
share
authentication
between
the
static
assets
as
well
as,
as
as
the
api
app
powered
by
functions.
It
also
allows
you
to
kind
of
bypass
things
that
you
typically
spend
most
of
your
time,
doing
when
you're
building
an
app
like
cores
and
trying
to
make
it
work
properly
and
then
eventually
just
put
a
star
there
anyway,
just
just
to
make
it
work.
So
don't
do
that
yeah.
D
E
Right
but
yeah,
so
so
those
are
kind
of
like
the
main
things
and
then
the
other
one
is
like
this
app
that
I'm
showing
you
here.
It's
also
it's
using
more
services
than
just
functions
and
just
static
assets.
It's
also
going
to
use,
in
this
case
signalr
service,
which
is
a
service
in
azure.
Also.
It
also
has
a
free
tier,
just
like
static
web
apps,
so
we
can
deploy
this
to
azure
and
basically
pay
nothing
to
start.
D
D
Azure
static
web
apps
knows
a
little
bit
more
about
the
fact
that
this
is
a
blazer
app,
so
it
can
do
some
additional
things
like
it.
It
knows,
for
example,
that
blazer
web
assembly
apps,
when
you
publish
them,
we
do
a
pre
pre-compression
step
to
produce
a
bunch
of
broadly
pre-compressed
files
as
part
of
the
app
so
that
it's
as
small
as
possible
and
azure
static
web
apps
knows
how
to
redirect
requests
to
those
pre-compressed
files
on
the
fly
for
you
transparently.
D
So
you
get
that
additional
size
shrinkage
out
of
the
box
without
you
having
to
do
any
work.
If
you
tried
to
do
that
on
github
pages,
you'd
have
to
add
some
like
javascript
code
on
the
client,
or
you
have
to
do
some
sort
of
shenanigans
in
order
to
to
get
pre-compression
to
or
any
sort
of
compression
really
to
work.
For
you,
you
also
get
a
full
fallback
routing
system
right.
It's
like
like
on
github
agents.
D
D
With
the
fallback
routing
problem,
this
is
like
a
deep
link
right
like
I
want
to.
I
want
to
put
a
link
right
to
the
counter
page
in
order
for
that
to
work.
If
you
just
load
up
slash
counter,
you
need
to
actually
redirect
that
to
the
the
root
of
the
app
so
that
the
blazers
routing
system
can
kick
in
azure
static.
Web
apps
has
a
full
routing
system
that
you
can
use
to
handle
that
problem.
E
Yeah-
and
this
is
one
of
the
things
I
kind
of
did
forgot
to
show
a
little
bit
earlier.
This
is
the
routing
file,
so
you
can
see
the
my
routing
configuration
it's
pretty
simple,
I'm
just
blocking
access
to
the
function
that
can
be
used
to
send
a
frame
unless
you're
authenticated,
and
this
is
the
fallback
route
that
we're
talking
about.
So
it's
just
a
rule
that
says
anything.
That's
that
that
doesn't
match
anything
on
my
search
on
the
server
just
serve
the
index
page
and
return
to
200.
A
E
Yeah
so
so,
currently
we're
supporting
javascript
dot
nets
as
well
as
python
functions.
We
still
have
plans
expand
to
the
rest
of
the
languages
that
we
support
and
then
the
other
kind
of
limitation
to
the
functions
that
the
kind
of
like
the
flavor
functions
that
we
support
right
now,
if
you're,
if
you're
an
existing
functions
user,
is
that
we
only
support
http
triggered
functions
currently.
D
E
Yeah
for
sure
so
yeah
so
starting
out,
like
kind
of
like
the
target
audience
that
we
initially
wanted
to
kind
of
appeal
to.
I
guess
or
kind
of
make
it
easy
to
use
for
are
folks
that
are
kind
of
more
javascript
focused,
so
they
tend
to
be
using
github
and,
I
would
say,
like
dotnet
folks,
they're,
probably
using
a
lot
of
github,
but
we
do
have
a
lot
of
customers
who
are
using
azure,
devops
and
also
other
kind
of
ci
cd
systems.
E
So
we
are
in
the
process
of
kind
of
decoupling,
azure
static
web
apps
from
github
itself,
so
that
you
can
kind
of
be
able
to
kind
of
configure
it
with
other
ci
cd
pipelines
as
well.
So
that
includes
working
like
we're
currently
working
on
a
azure
devops
task
so
that
you
can
actually
get
the
same
functionality.
That's
in
the
github
action.
So
not
only
are
we
able
to
deploy
the
the
static
web
apps
and
the
functions
for
you.
We
can
actually
detect
and
build
your
app
for
you
as
well.
A
E
Yeah,
that's
yeah
functions
are
totally
optional,
although
I'm
a
little
biased
being
on
the
functions
team.
I
think
every
app
should
have
functions
in
it,
but
yeah
we
can
actually
go
ahead
and
click
on
this
app
right
now
to
see
what
happens.
So
one
of
the
things
that
I'm
expecting
to
see
is
the
error
that
you
might
see
on
the
bottom
here
and
that's
because
it's
trying
to
connect
to
the
function
app
and
that
function
app
needs
to
talk
to
signal
our
service
and
needs
the
key.
E
E
A
E
E
F
E
E
E
E
We
are
working
on
it,
so
so
we're
well
aware
that
that
that
dotnote5
is
going
to
rtm
next
month,
so
we're
working
on
actually
building
a
brand
new
worker
for
functions.
So
so
for
those
of
you
who
use
functions
today,
this
might
make
a
little
bit
more
sense,
but
currently
dotnet
functions
run
in
the
same
process
as
the
azure
functions
host,
whereas
all
the
yellow
languages
that
we
support.
We
actually
run
them
in
a
separate
process
and
they
talk
over
grpc.
E
So
some
of
the
things
that
folks
have
run
into
in
this
current.net
model
that
we
have
is
that,
because
they
run
in
the
same
process,
if
you
kind
of
like
try
to
load
into
the
dlls,
perhaps
that
that
we're
loading
as
well,
sometimes
they're,
collisions
and
sometimes
you're
going
to
resolve
them.
Sometimes
you
may
not
be
able
to
so
so
by
separating
them
into
separate
processes.
E
E
Hopefully
most
of
those
will
go
away
and
then
the
other
thing
that
you'll
have
that
you'll
see.
That's
different
is
that
in
this
new
model,
because
it's
a
separate
process,
you
actually
kind
of
get
to
what
we
call
kind
of
quote-unquote
own
main.
So
you
will
actually
have
a
program
cs
in
your
app,
so
you
have
full
control
over
how
the
function
app
starts
up.
E
We're
also
looking
into
things
like
you
know.
Can
we
support
things
like
middleware
and
things
like
that
in
your
function?
Apps,
so
because
we're
kind
of
building
this
from
the
ground
up,
we
can't
necessarily
commit
to.
Actually
you
know
having
something:
that's
ga
quality
by
the
time
that
don
f5
is
rtm,
but
we
want
to
have
at
least
a
preview
out,
hopefully
not
too
much
later
than
say
a
few
weeks
after
don
f5
rtms.
E
D
Yeah,
I
was
typing
a
response
to
that
with
the
you
can
use
don
five
in
in
azure
app
service
like
right.
Now,
you
could
do
that
by
deploying
a
self-contained
application
by
basically
deploying
dot
five
with
your
app
and
then
dot
five
will
be
deployed
to
azure
app
service
very
soon
after
dot
net
5
ships.
Later
this
year,
cool.
A
E
No,
it's
done
deploying,
so
we
could
actually
because
there's
a
bit
of
a
delay.
We
can
send
people
to
this
url.
While
we
answer
more
questions,
okay,
so
the
url
is
blazer
demo
dot
and
issue
dot
com.
I
know
there's
a
way
of
actually
me
yeah
zooming
in
on
the
screen
here
or
is
there
a
chat
like
what
a
yeah
I'm
sending.
D
B
D
E
So
we're
still
kind
of
working
out
the
details
in
terms
of
what
these,
what
the
free
tier
looks
like
I'm,
currently
the
free
tier
that
we
offer
it's
actually,
the
only
tier
that
we
offer
have
some
pretty
strict
limitations
in
terms
of
app
size.
So
you
can
deploy
both
the
kind
of
like
the
static
assets
as
well
as
the
function
app
size.
E
So
we
just
have
a
bunch
of
protections
in
place
as
we're
a
preview
service,
but
hopefully
going
forward
we'll
have
a
better
free
tier
as
well
as
other
tiers.
If
you
need
kind
of
you
know,
maybe
more
bandwidth
or
some
other
things
we're
just
trying
to
work
work
out
some
of
the
details
in
terms
of
what
goes
into
these
plans.
A
D
C
A
E
So
hopefully
that
will
ship
soon
and
we're
also
working
on
a
much
better
local
development
experience.
You
kind
of
saw
that
that
I
had
to
start
up
the
my
front
end
app
as
well
as
the
function
app
locally.
What
you
didn't
see
is
actually
the
setup
cores
between
the
two,
so
it's
kind
of
an
annoying
experience
to
kind
of
develop
it
locally.
E
E
Give
you
a
lot
of
the
functionality
that
you
have
in
the
cloud,
so
you
kind
of
be
able
to
search,
so
you
can
serve
the
front
end
app
as
well
as
your
function,
app
locally
behind
the
same
endpoint
and
also
have
some
sort
of
an
emulation
for
the
authentication
as
well
as
the
routing.
So
you
can
kind
of
see
how
your
app's
gonna
work
without
deploying
it
and
more
so
we're
working
on
a
lot
more
stuff.
E
One
really
good
place
to
kind
of
keep
up
with
what
we're
working
on
is
at
our
kind
of
github
repo.
Currently,
this
repo
is
just
being
used
for
issues,
but
if
you
go
to
the
issues,
page
you'll
see
kind
of
all
the
things
that
people
are
asking
for,
go
ahead
and
kind
of
give
you
a
thumbs
up
or
thumbs
down.
I
guess
and
and
yeah
like
in
any
new
kind
of
requests,
and
things
like
that
you
can
put
there.
E
You
go
to
docs
on
microsoft.com
azure
static
web
apps.
There's
a
lot
of
docs
here
that
you
can
use
to
get
started.
Usually
a
good
place
to
start
is
the
overview
page
kind
of
walks
you
through
all
the
features
that
we
have,
as
well
as
in
general,
how
everything
works
and
then
kind
of
go
into
one
of
the
quick
starts
for
blazer.
We
have
a
tutorial.
That's
that's
built
just
for
blazer,
as
well
as
a
learn
module
in
microsoft.
A
G
A
A
It's
time
to
share
all
these
links,
and
then
I
can
add
these
into
the
into
the
roll
up
thing
with
the
community
links
too.
So
I'm
having
trouble
or
I'm
it's
taking
me.
We
have
to
find
it.
If
you
just
go
to
to
learn,
then
you
can
search
through
on
blazer
and
static
web
apps
awesome.
Well,
I
think
we've
covered
all
the
questions.
We've
got
the
roadmap
and
where
to
go
next
we
had
an
amazing
demo.
A
For
having
me
reminder
again,
safiya
shared
earlier
we're
doing
it's
a
it's,
a
monthly
blazer
focus
show
now
and
she
shared
out
the
information
on
how
you
can
get
involved
in
the
developer
in
the
dev
sprints,
and
that's
an
amazing
opportunity
to
work
directly
with
the
blazer
team
and
contribute
and
be
featured
here
and
and
show
off
your
exciting
cool
stuff.
You're
doing
for
the
community
too.
So
yeah.