►
From YouTube: Building dynamic applications with blazor
Description
About the session -
Blazor is a revolutionary single-page app framework for building interactive web apps with .NET Core. Underpinning Blazor's ability to create interactive web UIs using C# instead of JavaScript is a robust component model which offers exciting new opportunities for developers to create dynamic web applications. In this session we will demonstrate dynamic application development using an open source modular application framework for Blazor named Oqtane.
About the speaker -
Shaun Walker has 25+ years professional experience in architecting and implementing enterprise software solutions for private and public organizations. Shaun is the original creator of DotNetNuke, a Web Application Framework which is one of the pioneering open source software applications native to the Microsoft platform. He was one of the original founders of DNN Corp, a commercial software company providing products, services, and technical support for DotNetNuke, which raised 3 rounds of venture capital from top tier Silicon Valley investors. Based on his significant community contributions he has been recognized as a Microsoft Most Valuable Professional (MVP) as well as an ASPInsider for over 10 consecutive years. He was recognized by Business In Vancouver as a leading entrepreneur in their Forty Under 40 business awards, was a founding member of the Board of Directors of the Outercurve Foundation, and is currently the Chairman of the Advisory Council for Microsoft's .NET Foundation.
A
Hello,
everyone
welcome
to
a
new
session
on
building
dynamic
applications
with
blazer,
and
today
we
are
here
with
the
new
speaker,
sean
walker.
So
I
hope
you
all
people
are
excited
about
this
particular
session,
because
you
know
we
all
know
that
you
are
pretty
excited
to
watch
the
session
of
sean
in
blazercon
boom
nishwa.
But
somehow
we
missed
him,
but
we
got
him
back
so
welcome
sean.
B
Now
I
really
appreciate
the
opportunity
to
be
able
to
share
some
information
about
blazer.
I
was
very
disappointed
that
with
myself
that
I
somehow
missed
the
session
at
the
the
conference
that
happened
recently,
so
I'm
very
grateful
that
you
invited
me
to
to
share
some
information
with
your
audience
today.
B
B
It
was,
of
course,
built
on
some
legacy:
microsoft,
technology-
you
know
web
forms
all
those
things
that
we
we
loved
so
much
in
that
time
frame.
I
created
a
company
around
the
open
source
project
called
dnn
corp
with
three
other
co-founders,
and
we
actually
raised
venture
capital.
It
was
an
interesting
experience
to
go
through.
I
was
a
microsoft
mvp
for
many
years.
I
think
for
probably
12
years,
I'm
no
longer
a
microsoft
mvp
for
like
the
last
five
years.
I'm
hoping
that
maybe
someday
I'll
be
a
microsoft.
B
Mvp
again,
I'm
a
member
of
a
group
called
the
asp
insiders
and
we're
going
to
talk
today
about
octane,
which
is
a
new
open
source
project
that
I've
created,
and
I
also
am
the
chair
of
the.net
foundation,
project
committee
and
I've
actually
been
involved
with
the.net
foundation
since
it
started
in
2014.
as
a
volunteer.
B
B
So
obviously,
blazer
is
a
single
page
application
framework
for
building
interactive
web
applications
with
net
core.
I
think
the
the
the
main
thing
here
is
that
you
can
build
a
single
page
application
in
a
full
stack
manner
right
so
using
c-sharp
both
on
the
front
end
and
the
back
end.
That's
really
the
the
main
differentiator
that
blade
blazer
brings
to
the
table
over
some
of
the
other
single
page
application
frameworks
which
exists
today.
B
B
Basically,
the
original
single
page
application
architecture
involved
a
javascript
framework
which
was
running
on
the
client
and
that
javascript
framework
was
responsible
for
updating
the
user
interface
and,
typically,
then
you
would
use
you
know
ajax
to
make
calls
to
back
to
the
server
to
get
data
very
much.
This
is
this
is
a
popular
model
because
it
emulates
some
of
the
characteristics
of
a
desktop
application
right.
So
you
get
it's
a
web
application
with
the
user
interface
characteristics
of
a
desktop
application,
because
it
feels
very
responsive
to
the
end
user,
as
opposed
to.
B
B
So
I
think,
from
a
business
perspective,
the
things
that
comes
to
mind
is
one
of
the
challenges
that
we're
seeing
recently
is
around
resource
shortages
right.
So
what?
When
people
want
to
build
a
single
page
application
using
the
traditional
tools?
They'll
say?
Oh,
you
know,
I
want
a
full
stack
developer
and
what
does
that
mean?
B
So
that
leads
to
this
model.
Where
you
end
up
having
to
split
the
roles,
so
you
end
up
having
front-end
developers
and
back-end
developers
and
from
a
customer
perspective,
that
means
the
size
of
the
team.
That's
required
to
build.
Your
applications
has
maybe
not
doubled,
but
it's
certainly
grown
quite
significantly.
That
means
the
cost
of
developing
applications
has
gone
up,
and
so
those
are
some
of
the
resource
challenges
that
that
exist
today,
because
of
the
difference
in
the
technologies
that
are
being
used
on
the
front
end
and
the
back
end.
B
Certainly
many
companies
are
and
there's
many
projects
that
are
doing
this
successfully
today,
but
it
is
a
constant
challenge,
and
so
I
think
the
goal
behind
blazer
is
that
if
you
could
use
a
a
single,
consistent
stack
of
technology
for
both
the
front
end
and
the
back
end,
you
could
avoid
a
lot
of
these
problems
that
we're
seeing
here,
and
so
that
is
the
fundamental.
You
know
goal
behind
blazer
and
I
believe
it
does
achieve
that
goal.
B
B
Like
four
years
ago
there
was
a
conference
in
oslo,
one
of
the
mdc
conferences,
which
are
you
know,
one
of
the
very
popular
developer
conferences
that
have
been
around
for
many
years
and
at
that
conference,
steve
sanderson,
who
is
a
microsoft,
employee,
who's,
obviously
quite
famous
for
his
work
on
many
different.
You
know
web-based
development
frameworks
for
microsoft.
I
I
think
the
most
famous
one
is
probably
knockout.js,
which
was
one
of
the
early
like
javascript
frameworks
that
developers
used
for
you
know
for
more
intensive
work
on
the
front
end.
B
Actually
it's
probably
more
for
data
transfer,
but
anyways,
so
steve
wanted
to
demonstrate
some
up-and-coming
technologies,
and
one
of
the
technologies
that
he
wanted
to
demonstrate
was
how
you
could
build
applications
using
web
assembly
with
c-sharp,
and
so
he
came
up
with
this
proof
of
concept.
All
in
his
own,
actually,
he
hadn't
really
shared
anything
about
this
proof
of
concept
with
even
with
his
managers,
and
so
he
did
the
demonstration
at
this
ndc
oslo
event
and
kind
of
blew
everyone
away
because
they
couldn't
believe
what
he
was
capable
of
achieving.
B
But
the
community
was
really
interested
in
this
technology
and
there
was
a
lot
of
capabilities
that
it
brought
to
the
table
that
probably
weren't
even
imagined
in
the
early
stages
like
some
of
the
adaptability
of
the
technology
which
we're
going
to
talk
about
in
a
minute
but
anyways.
Once
we
got
to
april
of
2019.
Microsoft
said
that
it's
no
longer
experimental,
it
is
now
an
official
product,
so
blazer
is
official
and
they
were
planning
at
that
point
they
announced
that
they
were
going
to
ship
it
as
part
of
net
core
3.0.
B
B
But.Net
quarter,
3.0
shipped
in
september
of
2019
blazer
was
shipped
along
with
it
and
that,
of
course
only
included
blazer
server
and
we'll
talk
about
the
differences
between
blazer
server
and
laser
web
assembly
in
a
minute.
But
net
core
3.1
came
along
in
december
of
2019,
and
that
was
a
long
term.
Support
release,
so
blazer
server
has
long
term
support
already
dot
net
core
3.2,
which
came
in
may
of
2020.
B
So
last
year
was
the
general
availability
of
blazer
web
assembly
and
then.net
5,
of
course
came
along
a
bit
later
november
of
2020
and
that
it
was
still
a
you
know,
a
ga
release,
and
so
laser
web
assembly
is
still
deemed
to
be
ga.
It
doesn't
have
long
term
support
on
it
quite
yet,
but
coming
up
this
november
will
be.net
six
and
both
flavors
of
blazer,
both
server
and
web
assembly
will
be
deemed
to
be
lts.
At
that
point,
so,
like
I
said,
there's
the
two
flavors
of
blazer.
B
The
interesting
thing
is
when
you
do
development
in
blazer,
everything
is
based
on
this
component
model.
This
razor
component
model,
which
has
been
re
introduced
and
the
cool
thing,
is
that
you
can
adapt
that
razor
component
model
to
host
your
applications
in
multiple
ways.
So
you
can
right
now,
there's
obviously
support
for
blazer
server
and
blazer
webassembly,
but
there's
also
additional
hosting
models
that
will
be
coming
in
the
future.
B
We're
gonna
talk
a
bit
about
blazer
server
first,
because
it
was
the
original
release
that
microsoft
made,
and
this
is
actually
you
know
where
some
people
get
a
bit
confused.
The
original
proof
of
concept
for
blazer
was
based
on
webassembly.
That
was
what
steve
sanderson
demonstrated
and
that's
what
got
people's
attention.
However,
microsoft
actually
shipped
blazer
server
first
and
there's
some
reasons
why
they
did
that
which
we're
going
to
talk
about
laser
server,
leverages
that
same
razer
component
model
that
I
talked
about
it
utilizes
a
server-side
hosting
model.
B
So
that
means
that
the
actual
code
that
you
write
is
running
on
the
server
and
it's
communicating
with
the
with
the
browser
through
signalr
through
websockets.
So
there's
like
a
continuous
communication
channel,
that's
established
between
the
browser
and
the
server
and
that
allows
the
application
that's
running
on
the
server
to
still
have
very
responsive
characteristics
and
make
it
appear
to
the
end
user,
like
it's
still
a
very
streamlined
single
page
application
experience.
B
We
look
at
a
diagram.
We've
got.
You
know,
blazer
server,
so
the
razer
components
written
in
c,
sharp
running
on
the
server
communicating
with
the
browser
over
signalr-
and
I
just
to
be
clear
here,
because
this
is
another
area
of
confusion-
sometimes,
is
that
there
still
is
javascript.
That's
involved
in
this
solution
right.
There
is
a
dom
differencing
kind
of
capability
that
exists
in
the
browser.
That's
part
of
blazer,
and
so
signalr
is
actually
interacting
with
that.
B
B
The
only
work
that
needed
to
be
done
was
to
do
some
improvements
related
to
signalr
when
it
comes
to
you
know,
connections
that
are
dropped
and
need
to
reconnect,
but
for
the
most
part,
the
the
debugging
experience
for
blazer
server
almost
existed
from
from
day
one,
the
other
benefit
of
blazer
server.
Is
it
supports
legacy
browsers
so
browsers
that
don't
support
webassembly
and
there's?
B
Actually,
you
know
if
you're
using
modern
browsers,
then
that's
not
so
much
of
an
issue,
but
there
is
of
course,
environments
where
they
use
older,
browsers
or
browsers
that
are
like
less
full-featured
or
less
functional
and
in
those
environments,
laser
server
is
an
option
that
can
be
used
and,
of
course
it's
got.
You
know
official
lts
support
more
of
the
benefits
you
can
as
compared
to
writing
an
application
using
blazer
web
assembly.
B
B
You
can
call
the
file
system
directly,
whereas
when
you're
writing
web
assembly
laser
web
assembly
applications,
that's
a
true
client
server
application
where
you
actually
have
a
client
application
that
needs
to
communicate
with
the
server
over
http
I
mean
so
that
involves
more
code
and
more
complexity
in
your
application,
but
it
also
has
additional
benefits
when
it
comes
to
scalability
and
other
things.
So
that's
just
something
to
be
aware
of
when
you're,
when
you're,
comparing
these
applications,
blazer
server
tends
to
be
an
easier
environment
if
you're
porting
an
existing
asp.net
application.
B
There
is
a
perception
just
generally
in
the
industry
that
server
based
applications
are
more
secure
than
client
server
applications,
and
so
that
might
be
another
reason
why
you
choose
blazer
server
and
by
some
webassembly
is
still
viewed
as
experimental,
but
I'm
going
to
explain
in
a
minute
that
webassembly
has
actually
been
around
for
a
long
time
and
it
has
a
huge
amount
of
industry
support.
So
I
don't
know
if
this
argument
really
is
valid
anymore.
B
Some
of
the
challenges
around
blazer
server,
so
there
is
latency
right,
so
every
user
interaction
that
happens
when
you're
running
a
blazer
server
application
involves
a
network
call
right.
So,
whether
you're,
you
know
clicking
a
button
in
the
user
interface
or
that
that
application
has
to
get
data.
There's
always
communication,
that's
happening
between
the
client
and
the
server
and,
depending
on
the
quality
of
your
connection,
there's
going
to
be
latency,
which
is
going
to
affect
your.
You
know
your
performance
and
scalability
there's
also
no
offline
support,
meaning
you
know.
B
If
you're
wanting
to
build
an
application
that
runs
in
the
browser,
it
doesn't
require
a
server
connection.
I
mean
there's
certain
there's,
there's
plenty
of
application
scenarios
that
are
like
this.
You
couldn't
use
blazer
server,
because
the
only
way
it
functions
is
by
having
the
signalr
connection.
So
once
a
single
connection
is
lost,
your
application
is
not
functional
from
a
scalability
perspective.
B
The
server
must
manage
multiple
client
connections,
so
every
single
client
obviously
has
a
persistent
signalr
connection
that
is
running
and
managing
you
know
the
state,
and
so
there
is
scalability
implications
of
that
type
of
an
architecture.
Initially
people
when
they
looked
at
blazer
server.
They
thought
okay.
Well,
this
you
know,
based
on
the
architecture
that
I
just
described.
B
So,
even
a
fairly
basic
azure
instance
like
a
standard
azure
instance
with
one
cpu
and
three
and
a
half
gigs
of
ram,
could
handle
over
5000
concurrent
users,
which,
in
5
000
concurrent
users,
is
actually
pretty
significant.
So
if
you're
building
you
know
a
line
of
business
application,
for
perhaps
you
know
within
your
for
usage
within
a
company
which
is
a
pretty
common
scenario.
B
So
as
your
application
that,
like
as
the
number
of
concurrent
users
increases,
so
does
the
memory
footprint
and
then
some
people
have
said
like
why
did
microsoft
create
this,
you
know
is
a
server
single
page
application
framework,
even
a
good
idea.
Obviously
the
technology
is
pretty
functional.
It's
very
capable
there's
already
a
lot
of
applications
being
built
on
it.
But
like
is
this
a
microsoft
only
thing
and
is
microsoft
committed
to
this
in
the
long
term?
B
Well,
it
was
quite
interesting
because
the
the
creators
of
ruby
on
rails,
which
is
sort
of
you,
know,
base
camp
which
was
formerly
known
as
37
signals
came
out
with
their
own
server
side,
single
page
application
solution
in
2021
called
hotwire
and
hotwire
actually
mimics
a
lot
of
the
same
technology
that
blazer
server
uses,
meaning
like
it
is
using
web
sockets.
It's
trying
to
avoid
the
use
of
javascript
it's
running
for
the
majority
of
the
workloads
running
on
the
server.
B
So
with
that
we'll
transition
over
to
laser
web
assembly
now
and
talk
a
little
bit
about
the
history
of
that
solution.
So
main
thing
to
note:
it's
not
microsoft
silverlight!
So
you
know
it
is
not
like
microsoft
taking
the
the
ip
that
they
created
with
microsoft,
silverlight
and
had
you
know,
deprecated
back
in
2013
and
repurposing
it
in
a
new
way.
It
is
not
that
right,
it
is
blazer.
Webassembly
is
a
completely
brand
new
technology
that
was
built
from
the
ground
up
to
take
advantage
of
some
new
industry
standards.
B
I
guess
the
other
thing
that
people
sometimes
get
hung
up
on
when
it
comes
to
blazer
webassembly.
Is
you
know,
because
of
the
way
that
that
microsoft
silverlight
was
basically
abandoned
by
microsoft,
kind
of
abruptly
and
a
lot
of
folks
had
you
know
bought
into
it
started,
building
applications
on
it
and
then
we're
like
kind
of
left
with
no
migration
path?
There
is
concern
about
whether
microsoft
is
committed
to
blazer
webassembly
in
the
long
term
as
well,
and
of
course
only
time
will
tell
it
remains
to
be
seen.
B
So
the
main
thing
here
is
that
you
know
there's
been
a
lot
of
technologies
over
time
that
have
been
introduced
by
you
know:
different
companies,
different
organizations
to
run
natively
in
the
browser,
so
this
has
long
been
a
goal,
is
to
be
able
to
run
applications
natively
in
a
browser
and
the
reasons
behind
that
are
because
you
know,
if
you
can
run
in
the
browser
you
have
native
performance
right.
You
have
the
fastest
performance
characteristics
possible
if
you're
running
natively
in
the
browser.
B
Obviously
javascript
runs
natively
in
the
browser,
but
there's
some
it's
not
able
to
achieve
that
like
the
fastest,
most
optimal
performance,
because
of
the
way
that
basically
javascript
works,
which
I'll
explain
in
a
minute
as
well,
but
so
we've
had
activex,
we
had
flex
flash
silverlight
and
there's
been,
you
know,
even
attempts.
You
know
more
recently
darts
and
you
know
google
and
acl.
There's
there's
been
a
lot
of
attempts
of
coming
up
with
some
kind
of
a
solution.
B
The
the
biggest
problem
traditionally
has
been
that
not
all
of
these
solutions
that
were
intended
to
run
natively
in
the
browser
would
run
on
all
browsers
and
typically
they
would
require
a
plug-in.
So
the
the
user
would
have
to
download
a
plug-in,
install
that
plug-in
and
then
their
application
could
run
in
the
browser
and
the
industry
kind
of
moved
away
from
this
concept
of
really
supporting
plug-ins
and,
of
course,
that's
what
led
to
the
death
of
microsoft.
Silverlight
is
there
was
this
perception
well,
and
maybe
it
wasn't
a
perception
that
you
know
these.
B
These
plug-ins
could
cause
performance
issues
and
security
issues,
and
because
of
that,
the
hardware
vendors
decided
that
they
weren't
necessarily
a
great
idea
so
stop
supporting
them.
So
anything
that
was
like
a
pro
credit,
a
proprietary
plug-in,
was
no
longer
deemed
to
be
a
really
viable
solution.
B
In
2011,
google
announced
the
nacl,
the
native
client,
which
was
their
attempt
at
creating
like
a
technology
that
would
allow
you
to
run
native
code
in
the
browser
at
near
native
speeds
and
google.
You
know
pushed
this
for
a
while
created
a
number
of
applications
around
it,
but
it
never
really
caught
on
and
they
decided
to
abandon
this
in
2016
in
favor,
actually
of
webassembly.
B
Mozilla
was
really
one
of
the
pioneers
behind
webassembly
and
back
in
2013
mozilla
created
a
more
a
library
called
asm.js,
which
was
you
know
it
wasn't.
The
full
didn't
have
the
full
capabilities
of
the
javascript
language.
It
was
a
subset
of
javascript,
but
it
could
be
used
more
as
a
low-level
environment
like
a
target
for
compiling
applications
using
encrypted
and
llvm.
B
So
using
this
approach
they
were
able
to
demonstrate
that
you
could
run
c
and
c
plus
applications
natively
in
the
browser
using
the
asm.js
javascript
engine.
To
accomplish
that
and
then
a
lot
later
came
webassembly
and
so
webassembly
was
the
successor
to
asm.js
and
again
so
mozilla
was
you
know.
Mozilla
foundation
was
one
of
the
real
pioneers
behind
webassembly
and
it's
often
referred
to
now
as
the
fourth
official
language
of
the
web.
So
along
with
html
css
javascript
webassembly,
has
really
received.
B
So
the
fact
that
it's
so
widely
available
means
that
you
know
anyone
can
take
advantage
of
it
and
they
don't
have
to
worry
about.
You
know
browser
support,
which
is
one
of
the
one
with
one
of
the
major
issues
when
it
comes
to
previous
technologies
that
required
plug-ins
and
it
runs
super
fast
so
and
then,
if
we
could
fast
forward
a
little
bit
more.
So
in
2019
there
was
an
announcement
about
a
web
assembly
system
interface
initiative.
B
The
goal
of
that
was
to
standardize
how
webassembly
code
interacts
with
operating
systems
outside
of
the
browser.
So
I
mean,
even
today,
most
people
are
focusing
on
webassembly
for
running
applications
in
browsers,
but
there's
no
reason
why
it
can't
be
used
for
running
applications
outside
of
the
browser
as
well,
and
that
was
what
the
wasi
was
formed
around
to
create
some
standards
so
that
you
could
run
it.
You
know
on
on
like
operating
systems
as
well
outside
the
browser,
so
that
I
think,
will
be
something
that
will
be
interesting
to
to
follow.
B
So
if
we
look
at
javascript
for
a
moment
and
like
why
javascript
can't
run
as
fast
as
something
like
web
assembly
or
something
that
is
truly
native,
so
how
javascript
works
under
the
covers.
Of
course,
you
have
your,
you
know
your
inline
javascript
in
your
html
page
or
you
have
external
resources,
which
are
your
javascript
libraries.
B
B
So
all
of
that
parsing
work,
that's
done
and
compiling
work
is
fairly
intensive
and
that's
a
major
limitation
in
terms
of
javascript
runtime
performance.
How
web
assembly
works?
Is
it
basically
bypasses
the
the
parsing
and
the
compiling
of
the
javascript
and
it
provides
the
instruction
set
in
exactly
the
format
that
the
browser
needs
to
process
it?
B
So
if
we
look
at
like
the
amount
of
time
it
takes
for
performance,
javascript
processing,
you
know
takes
a
long
a
much
longer
period
of
time,
because
it
has
to
do
the
parsing
and
compilation,
whereas
web
assembly
just
does
some
basic
decoding
and
then
it
can
execute.
So,
if
you're
wanting
to
build
a
very
high
performant
web
application,
clearly
web
assembly
is
going
to
provide.
You
know
better,
better
capabilities
for
you,
because
it
just
doesn't
have
to
do
as
much
work
as
javascript.
Does
the
other
thing
to
keep
in
mind?
B
Is
you
know,
blazer
web
assembly?
Isn't
a
microsoft
thing
again?
It's
you
know.
It's
based
on
webassembly
webassembly,
also
known
as
wasm,
has
a
lot
of
industry
support,
so
there's
already
solutions
that
are
being
created
for
most
of
the
mainstream
programming
language
that
exists
today.
So
things
like
rust,
java
go
python.
There
is
solutions
there
for
webassembly
for
all
of
these
languages,
so
microsoft
and
the
blazer
solution,
obviously
focused
on
c
sharp
is
just
is
one
of
many
solutions
that
rely
on
web
assembly.
B
I
think
the
cool
thing,
though,
with
blazer
webassembly,
is
that
the
fact
that
microsoft
got
in
early,
you
know
with
the
proof
of
concept
by
steve
sanderson
back
in
2017
and
has
built
a
complete
and
robust
kind
of
tool
set
around.
It
means
that
they,
you
know.
Typically,
microsoft
is
accused
of
being
more
of
a
follower
than
a
leader
when
it
comes
to
new
technology,
and
I
think
in
this
case
you
know
they.
B
B
B
So
you
could
write
a
c
sharp
application
and
in
order
to
do
that,
you
needed
a
a
run
time.
A.Net
framework
runtime
that
was
compatible
with
webassembly
that
could
then
run
in
the
browser
and
dotnet
anywhere
did
provide
that.
However,
like
I
said
it
was
you
know
that
is
that
was
not
the
solution
for
the
future.
That
was
a
proof
of
concept.
B
So
how
does
blazer
webassembly
work
when
a
browser
connects
to
the
server
it
downloads,
the
the
blazer
web
assembly?
Well,
it
basically,
it
downloads
your
assemblies
to
the
browser,
and
then
it
actually
runs
those
assemblies
natively
in
the
browser
by
using
the
the
mono.wasm.
So
the
the
the
webassembly
compiled
version
of
the
dot
net
framework,
essentially
and
all
of
the
interactivity
that
happens
with
that
application
occurs
in
the
browser
itself.
So
this
does
this
solution.
B
It
does
emulate
the
traditional
single
page
application
architecture
more
closely
because
like
if
you're
running
an
application
using
something
like
react
or
angular,
of
course,
that
javascript
framework
is
running
natively
in
the
browser
and
doing
all
the
user
interface
updates
in
the
browser
itself,
and
that's
the
way
that
blazer
web
assembly
works
as
well.
The
only
time
that
it
would
call
back
to
the
server
is
to
retrieve
data
right
so
making
you
know,
ajax
calls.
B
B
I
guess
of
the
current
single
page
application
frameworks
that
are
based
on
javascript
or
they
are
there's,
there's
criticisms
of
them
that
they're
becoming
bloated
over
time
right.
They
like
this
is
an
example
here
you
know
14
500,
you
know
files
that
are
part
of
like
the
node
modules
folder
it's
so
these
frameworks
have
become
very,
very
powerful
over
time
with
a
lot
of
capabilities,
but
as
a
result
of
that,
like
any
software,
they
start
to
become
bloated,
and
because
of
that,
you
know
that
all
that
has
performance
characteristics.
B
The
larger
footprint
has
memory.
You
know
impacts
it
takes
longer
to
download
to
the
browser
so
that
latency
to
the
you
know
the
the
application
spinning
up
takes
longer.
So
there's
a
there's,
a
lot
that
comes
from
app
from
these
frameworks
being
bloated.
So
what
are
some
of
the
challenges
around
laser
web
assembly?
Well
dot
net
libraries.
B
So
if
you're
imagining
that
in
when
you're
running
blazer
webassembly,
those
dlls
need
to
be
downloaded
to
the
browser,
and
if
you
think
about
this
traditionally
dll
dlls
were
never
expected
to
be
transferred
anywhere
right.
They
were
meant
to
sit
in
the
application,
bin,
folder
and
just
be
processed.
So
so
the
size
of
the
dlls
was
never
really
an
issue
in
the
past.
B
Well,
now
that
you're
wanting
to
transfer
those
to
the
browser,
that
is
an
issue
you
certainly
don't
want
big
bloated,
dlls
being
transferred
over
the
wire
and
the
and
the
end
user
waiting
for
those
to
be
received
in
order
to
actually
see
their
application
being
rendered.
So
there's
been
a
lot
of
work
by
microsoft
to
try
and
optimize
the
size
of
these
dlls,
so
that
the
you
know
it
requires
less
time
to
transfer
them
to
the
browser
there's
all
kinds
of
like
so
I'll.
B
If
you
have
the
time
to
explore
this,
I
mean
you
can
look
at
they're
using
compression
right,
so
they're
using
gzip
and
other
forms
of
compression
bot
lay
compression
they're
also
doing
tree
trimming
right.
So
they're
trimming
unnecessary
aspects
of
libraries
from
from
the
code
which
is
being
transferred
using
il
trimming,
which
was
you
know,
a
big
feature
in
dot
net
five.
So
all
of
these
things
that
they've
been
doing
lately
around
reducing
the
size
of
dlls
is
largely
because
of
blazer
web
assembly.
B
B
Which
means
that
if
you're
creating
blazer
web
assembly
applications,
you
might
not
have
the
full
set
of
features
from
the
dot-net
framework
or
well
or.net
core
that
you
are
looking
for
right.
So
you
have
to
be
aware
of
that.
There
is
more
limited
debugging
support
for
blazer
web
assembly.
Microsoft
has
tried
to
make
some
improvements
in
this
area.
I
think
it
dot
at
five.
They
announced
some
improvements,
but
it's
still
not
a
great
debugging
experience.
B
Actually,
for
this
reason,
when
I'm
doing
development
in
for
blazer,
I
typically
will
build
the
application
and
debug
it
using
blazer
server
and
then,
if
I
intend
to
run
it
on
blazer
webassembly
I'll,
just
flick
the
switch
to
run
it
on
blazer
web
assembly
at
runtime
later-
and
it's
also,
I
guess
the
other
thing
with
laser
web
assembly-
is
it's
not
an
in
as
part
of
an
lts
release.
Yet
right,
it'll
be
it'll,
be
part
of
an
lts
release
this
november
as
part
of.net
6..
B
Then,
of
course,
there
is
the
the
benefits
of
this
razer
component
model
being
so
adaptable
that
it
can
be
used
in
many
ways,
and
so
we
already
have
blazer
server
and
blazer
web
assembly.
You
can
already
create
a
progressive
web
application
based
on
blazer
the
the
microsoft
blazer
web
assembly.
Template
has
a
pwa
capability
kind
of
enabled
in
it.
B
Within
the
you
know,
a
mobile
scenario
and
then
blazer
native
would
actually
be
running
like
a
blazer
or
razor
components
as
part
of
a
desktop
application
scenario
in
something
like
an
electron
shell
or
something
even
more
native
than
that,
and
so
with
with
all
of
these
different
hosting
scenarios,
you
could
you
know,
have
a
single
code
base
that
you
could
run
anywhere
from
web
all
the
way
to
desktop
and
mobile
natively,
which
is
pretty
cool.
I
mean
this
is
very
adaptable
technology
that
I
think
we've
been
waiting
for
for
a
long
time.
B
B
I
don't
know
if
that
means
it's
part
of
maui
or
it's
a
separate
thing
from
maui,
but
I
believe
it
is
supported.
In.Net,
six,
I'm
going
to
skip
through
a
lot.
I
think
of
this
content,
because
the
blazer
fundamentals
are
things
that,
if
for
most
of
you,
who
have
experimented
with
blazer,
already
you're
already
familiar
with
so
how
to
get
blazer,
what
razor
components
are
the
component
model
behind
blazer?
I
think
you're
familiar
with.
Obviously,
razer
components
are
chunks
of
ui
and
those
uis
have
capabilities
where
they
can
handle
routing.
B
They
can
handle
the
passing
of
parameters,
there's
a
vent,
binding
property
binding
and
then
some
life
cycle,
events
that
are
part
of
the
overall
component
model.
You
get
familiar
with
this
concept
and
you'll
be
up
and
running
on
blazer
in
no
time
component
rendering
and
how
it
works.
I
guess
is
just
a
little
bit
more
detailed
on
how
the
actual
interactions
happen,
which
we've
already
kind
of
described,
but
if
you're
running
on
webassembly,
your
entire
application
is
running
in
the
browser
itself,
so
all
of
the
user
interface
interactions
are
happening
in
the
browser.
B
So
you
get
a
very
rapid
sort
of
refresh
loop
within
the
browser
itself,
so
that
and
that
you
know,
provides
that
interactivity
for
the
end
user
in
blazer
server.
You
have
your
c
sharp
code
running
on
the
server
and
interacting
with
the
browser
through
signalr.
So
there
is
a
bit
more
of
a
latency
and
consideration
at
play
here
how
to
use
components,
I'm
going
to
yeah
I'm
going
to
skip
through
these
pretty
quickly,
but
obviously
you
build
your
components
and
you
utilize
them
as
if
they
were.
You
know,
standard
kind
of
tags.
B
B
B
I
think
one
thing
to
note
is
under
the
covers,
if
you're
interested
in
how
this
works
so
the
way
that
you
develop
your
blazer
applications.
As
you
write,
you
know
standard
c-sharp,
using
the
the
type
of
logic
that
you
you
would
expect
for
a
web
application
and
then,
under
the
covers,
when
you
com,
when
that
application
is
compiled,
it
actually
produces
an
intermediary
file
which
you
can
find
in
the
in
the
obj
debug
folder.
B
If
you
look
inside
of
your
your
blazer
application
and
you'll
see
like
if
you
actually
take
a
look
at
the
difference
between
your
your
razer
file
and
the
intermediary
file,
that's
created
by
blazer,
it's
quite
interesting.
So
everything
is
converted
into
using
this.
Build,
render
tree
method
which
is
kind
of
the
the
fundamental
of
how
razer
components,
work
and
then
you'll
see
this
builder
and
all
of
the
markup
is
you
know,
kind
of
built
up
using
all
these
very
verbose
commands.
B
You
can
write
this
yourself,
like
you,
could
write
the
code
like
your
blazer
code
in
this
manner,
if
you
wanted
to,
but
obviously
it's
not
nearly
as
readable
or
maintainable
as
the
the
standard
code
that
you're
used
to
so
the
one
thing
that
I
found
valuable,
though,
is
there's
situations
where
you're
just
wondering
how
blazer
is
doing
something
under
the
covers
and
or
maybe
wiring
up
some
different
events
or
things,
and
by
opening
you
know
the
dot
g
dot
cs
file.
That's
the
intermediary
file,
that's
created!
B
You
can
see
how
blazer
does
things
under
the
covers,
which
is
quite
powerful
in
some
ways,
laser
obviously
or
razer
components
support
routing,
just
using
a
simple
app
page
directive.
They
support
layouts
using
like
you,
can
inherit
kind
of
like
the
master
page
concept,
so
you
can
inherit
from
a
a
layout
sports
data
binding
just
by
declaring
variables
in
your
code
block
and
then
referencing
those
variables
with
an
at
sign.
B
All
this
is
very
like.
So
if
you're
familiar
with
like
razer
syntax
and
you've,
been
building
like
razor
pages,
then
all
of
this
should
be
very
familiar
to
you
and
I
think
that
microsoft
developed
it
in
in
this
way,
so
that
it's
a
pretty
easy
migration
pathway.
If
so,
if
you're,
a
c-sharp
developer
and
you've
been
building,
mvc
or
razer
pages,
moving
to
to
blazer
is
is
not
a
big
challenge
at
all
sporting
events.
B
With
for
most
of
the
major
events,
you
can
just
provide
a
method
like
at
on
click
or
at
on
change,
and
then
specify
the
name
of
your
method
that
should
be
called
when
that
happens,
and
it's
pretty
easy
to
wire
things
up.
Net
core
in
general
has
a
big
focus
on
dependency
injection
and
so,
of
course,
blazer
has
full
support
for
for
dependency
injection
as
well.
It's
got
the
the
standard.net
core.
B
So
that's
pretty
powerful,
so
you
can,
you
know,
call
javascript
and
that
javascript
method
could
even
return
a
value
which
would
come
back
to
your
c-sharp
code,
and
you
can
also
do
vice
versa.
So
you
can
actually
call
c
sharp
from
javascript
as
well.
So
this
opens
up
a
lot
of
possibilities
for
developers
who
need
that
interactivity
between
their
the
c-sharp
code,
which
is
running
in
the
browser
and
javascript
code,
which
is
running
in
the
browser,
as
well,
so
pretty
powerful,
stuff,
dynamic
components.
B
So
most
of
the
examples
you'll
see
from
microsoft,
at
least
in
terms
of
their
documentation
or
their
templates
that
they
provide.
You
are
all
based
on
very
static
kind
of
examples
where
everything
is
kind
of
hard-coded,
meaning,
like
the
the
examples
that
I
just
showed
like
your
routes
are
hard-coded
in
your
in
your
page.
In
your
razer
components,
your
your
tags
are
hard-coded,
that's
not
always
what's
needed
when
you're
building
a
more
robust
application,
and
so
there
is
the
ability
to
build
dynamic
components
as
well.
B
I'm
going
to
show
you
octane
in
a
minute
and
octane
is
100
dynamic
and
it
uses
this
methodology
for
almost
everything
that
it
does
question
that
comes
up.
Is
you
know
it's
it's
pretty
cool
that
that
blazer
supports
multiple
hosting
models
right?
It's
it's
supports
laser
server
and
blazer
webassembly,
and
it's
going
to
support
other
hosting
models.
So
can
you
write
one
application
and
have
it
run
in
multiple
hosting
models?
And
the
answer
to
that
question
is
yes,
you
can.
B
So
let's
say
you
built
a
blazer
application
and
you
built
it
using
blazer
server
kind
of
techniques,
meaning
your
razer
components,
calling
the
your
database
directly,
because
it's
on
the
server,
no
problem,
it's
calling
the
file
system
to
you
know
get
a.
You
know
read
a
file
directly.
That's
no
problem!
B
Then
you
decide
that
you
want
to
take
that
application
and
you
want
to
run
it
on
webassembly.
Well,
it's
going
to
download
that
dll
to
the
browser
and
then
the
browser
is
going
to
execute
it
and
the
code
is
going
to
try
to
access
the
database,
which
it
can't
do
because
it
can't
directly
access
the
database.
It's
not
possible
because
at
that
point
it's
running
in
the
browser
sandbox.
So
in
order
to
access
the
database,
it
has
to
call
an
http
service
which
exists
on
the
server.
B
So
those
are
the
things
that
you
have
to
keep
in
mind.
So
if
you
want
to
build
an
application
that
runs
on
both
hosting
models
without
like
any
code
changes,
you
need
to
build
it
in
a
client
server
manner.
So
even
your
blazer
server
application
would
need
to
still
utilize
http
services
or
have
some
kind
of
an
architecture
that
it
could
dynamically
figure
out
what
it
needs
to
do
at
runtime
right
to
either
call
a
service
or
call
the
database
directly.
B
You
also
have
to
pay
attention
to
the
fact
that-
and
I
mentioned
this
earlier-
that
not
the
full
capabilities
of
net
are
not
available
in
both
hosting
environments.
Right,
you
have
a
limb,
more
limited
set
of
functionality
when
you're
running
on
blades
or
web
assembly.
Although
I
wouldn't
say
it's
very
limited
at
all,
it's
it's
it's
pretty
robust
right.
It
just
doesn't
have
the
very
latest
net
enhancements
you
do
have
to
get
familiar
with
http
client
and
there's
a
new
json
parser.
That's
been
introduced,
system.txt.json,
as
opposed
to
using
json.net.
B
So
thinking
about
so
blazer
itself
is
an
application
framework
right
and
what
are
application
frameworks
designed
to
do
well,
they're
designed
to
accelerate
web
development
right
and
they
try
to
provide
some
standardization
and
they
try
to
automate
the
overhead
of
creating
applications.
So
I'm
sure
you
could
build
webassembly
applications
from
scratch
right
without
the
use
of
blazer.
But
it
would
require
a
whole
lot
of
work
and
you'd
be
responsible
for
all
that
infrastructure
that
needs
to
be
created.
B
So
blazer
is
great
in
that
you
know
it
provides
you
a
complete,
a
framework
that
you
can
build
on
to
build
applications
that
run
on.
You
know,
web
assembly
that
use
a
component
model,
but
there's
limitations
to
every
framework.
So
a
framework
like
blazer
only
goes
so
far
in
terms
of
providing
a
set
of
services.
B
B
B
I'm
also
focusing
on
the
fact
that
octane
is
is
an
application
framework
for
building
applications,
not
necessarily
an
application
for
building
web
sites
like
content,
rich
websites,
so
where
dot
net
nuke
was
used
in
multiple
ways
right,
it
was
some
people
would
use
it
as
an
application
framework
and
other
people
used
it
just
as
a
cms
right,
a
content
management
system
for
building
websites.
I
am
not
focused
on
the
content
management
capabilities
at
this
point
in
time
for
octane.
B
B
It
has
full
localization
capabilities
that
are
built
into
it
now,
and
it
provides
a
lot
of
capabilities
that
are
not
currently
available
in
blazer.
Well,
what
are
those
capabilities?
Multi-Tenancy
is
a
big
one,
so
there's
many
many
cases
where
you're
building
web
applications
and
they
need
to
be
multi-tenant,
meaning
you
want
to
run.
B
B
B
Octane
has
capabilities
to
create
much
more
granular
permissions.
You
can
build
themes
that
are
customizable
so
much
different
than
I
guess.
The
the
just
the
basic
layout
capabilities
that
that
standard
blazer
provides
the
theming
capability.
That's
available
in
octane
is
more
advanced.
It's
got
a
whole
administrative
user
interface.
That's
already
built
out.
That's
part
of
the
the
framework
itself
for
managing
a
lot
of
the
the
you
know,
the
standard
configuration
of
the
framework,
but
because
all
the
code
is
available
and
it's
open
source.
B
It
gives
you
a
great
example
of
a
whole
lot
of
different
razor
components
and
how
razor
components
are
built.
So
from
an
education
perspective,
the
octane
framework
is
very
valuable
in
terms
of
showing
you
how
to
do
many,
many
different
types
of
things
within
blazer
itself.
It's
a
client
server
architecture.
So
it's
got
a
full
headless
api
that
the
client
interacts
with,
and
it
supports
multiple
databases
which
I'll
show
in
a
minute
here,
but
from
an
architecture
perspective
it
is
client
server.
B
B
It
actually
has
an
isolated
tennessee
model
model
that
it
supports
as
well.
So
you
can
have
multiple
databases,
so
you
can
have
an
independent
database
for
each
tenant.
That's
still
managed
out
of
the
same
application
framework
instance.
So
that's
just
that's
a
a
capability
that
didn't
exist
in
dnn.
That's
more
advanced,
I
guess
in
octane
octane
has
a
full
rest
api
support
for
swagger.
B
It
also
uses
the
I
scheduled
service
capability,
in.net
core,
to
allow
you
to
run
scheduled
jobs.
So
if
you
have
asynchronous
processing
that
needs
to
be
done
on
the
server,
you
can
build
a
scheduled
job
that
will
run
and
you
can
manage
the
schedule
for
that.
And
then,
if
we
switch
over
to
the
client,
it's
all
based
on,
of
course,
razer
components.
So
we
can
run
on
blazer
server
or
blazer
web
assembly.
B
And
then
you
can
spin
up
as
many
still
still
uses
the
notion
of
a
site
as
being
sort
of
the
the
grouping
mechanism
for
a
tenant
and
each
site
can
have
its
own
database
or
being
a
shared
database.
And
then
you
have
your
your
modules
right.
So
these
are
your
independent
modules
and
modules
are
built
using
standard,
razer
components.
B
In
the
octane
2.1
release,
which
was
just
over,
I
think,
just
over
a
month
ago,
the
big
feature
that
was
released
was
support
for
multiple
databases.
So
originally,
when
octane
was
created,
it
only
supported
sql
server,
and
so
one
of
the
big
pieces
of
feedback
was
that
you
know
it's
a
net
core
based
application.
It's
so
it
can
run
on
multiple
platforms
right.
B
It
can
run
on
windows
or
linux
or
mac,
but
the
fact
that
it
only
supported
sql
server
kind
of
limited
its
its
usefulness,
and
so
it
would
be
better
to
support
the
most
popular
relational
databases
on
you
know
other
platforms,
other
than
windows
as
well,
so
support
was
added
for
sql,
lite,
mysql
and
post
grass
sql,
and
that
was
like,
I
said
in
just
octane
version
2.1,
so
that
that
capability's
only
been
available
for
about
a
month.
But
it's
actually
pretty
cool
in
that.
B
If
you're
building
modules
for
octane,
you
build
them
using
ef
core
and
you
build
them
using
the
standard,
ef
core
migrations
and
behind
the
scenes
I
mean
this.
Your
module
would
be
capable
of
running
on
any
of
these
four
databases
where
there's
providers
that
are
that
have
been
built
for
octane.
So
it's
this
notion
of
you
know.
You
only
need
to
write
one
set
of
database
code
and
it'll
work
on
multiple
databases.
B
I
think
that
that
was
always
the
vision
behind
ef
core,
but
I
haven't
seen
too
many
really
solid
implementations
of
that,
and
so
I'm
really
proud
that
that
we're
able
to
have
that
in
octane.
It
was
actually
one
of
my
colleagues
that
I
worked
with
closely
from
dnn
charles
nurse,
who
was
actually
one
of
the
chief
architect
for
dnn,
who
added
this
capability
in
in
octane
2.1,
so
pretty
happy
with
that.
The
community
and
code
for
octane
is
available
on
github.
B
So
if
you
can
go
to
the
the
octane
framework
repository,
the
most
recent
release
was
version
2.2,
and
that
was
earlier
this
week
and
a
lot
of
that.
That
version
included
support
for
upgrading
to
bootstrap
5
from
bootstrap
4.,
but
yeah
there's
a
lot
of
capabilities
that
you
can
take
advantage
of
so
to
actually
show
you
the
application
and
then
to
demonstrate
something.
B
B
The
files
module
has
a
number
of
components
that
are
part
of
it.
The
jobs
module
has
a
number
of
components,
so
you
can
look
at
these
razor
components
and
you
can
see
how
they're
structured
and
it's
just
standard
razor
components,
and
it's
using
the
you
know
the
standard
model
that
microsoft
has
where
you've
got
your
your
markup
here
and
then
you've
got
your
code,
of
course,
at
the
bottom
as
well,
and
so
got
a
lot
of
examples
of
razor
components
that
you
can
look
at
that
are
part
of
the
open
source
project.
B
It's
also
got
the
service
layer,
so
all
of
the
services
for
calling
back-end
apis
there's
you
know
services
that
have
been
defined
for
them.
So
this
would
be
the
you
know,
the
apis
that
you
could
take
advantage
of
just
by
using
dependency
injection
and
pulling
in
the
necessary
services
into
your
razor
components.
B
I
think
that's
all.
I
want
to
show
there
and
then,
of
course,
your
your
shared
project
contains
your
models,
so
the
models
that
are
shared
between
the
the
client
and
the
server,
so
it
doesn't
use
back
end
models
and
view
models
for
the
front
end.
It
uses
one
one
set
of
models.
This
was
just
an
architectural
decision
that
was
made
early
on
and
the
whole
application
kind
of
is
based
on
this
model.
B
So
if
we
look
at
this
server
project
and
we
go
into
the
app
settings.json
file
which
is
open
here-
we
can
see
that
it's
got
pretty
minimal.
I
guess
amount
of
information
in
it,
I'm
going
to
go
ahead
and
I'm
going
to
remove
this
connection,
string
and
save
it
and
now
and
we're
so
noticing
we're
running
the
run
time.
So
it's
for
supporting
the
different
hosting
models
for
blazer
there's
a
runtime
node,
which
is
in
the
app
settings.json
file
where
you
can
specify
server
or
webassembly.
B
So
I'm
going
to
be
running
it
on
server
initially
here
by
not
specifying
a
connection
string,
the
application
is
going
to
recognize
when
it
runs
that
it
needs
to
create
a
database.
So
it's
going
to
basically
do
a
new
installation
and
it's
going
to
provision
the
database
for
me.
So
if
I
run
this
application
now,
it's
going
to
come
up
with
a
wizard
which
is
going
to
show
me
the
parameters
that
I
can
enter
for,
creating
my
my
initial
installation,
so
version
2.2.
B
I
can
see
here
that
by
default
it
chooses
localdb,
which
is
you
know,
the
sql
server
local
db,
but
you
also
have
the
ability
to
choose
mysql,
postgresql
or
sql
lite.
If
you
want
to
so,
you
can
run
on.
You
could
set
up
your
initial
installation
on
any
of
these
databases
by
default.
I'm
just
going
to
accept
the
default
values,
I'm
going
to.
B
Let's
use
personal
email
all
right.
So
if
I
enter
this
basic
information
and
I
say
install
now,
it's
going
to
go
ahead
and
it's
going
to
create
the
database
for
me
and
it's
going
to
provision
it
with
the
schema
using
the
migrations
and
it's
going
to
create
some
initial
content
for
me.
So
it
created
a
few
pages
for
me
by
default
with
some
content,
which,
of
course
I
can
remove.
B
B
B
If
we
look
at
some
of
the
user
interface
functionality,
if
I
click
on
this
pencil
icon,
the
user
interface
changes-
and
it
shows
me
the
different
areas
of
the
page
which
are
available
for
me
to
inject
content
into
so
by
default.
I
everything
is
in
this
admin.
Pane,
there's
a
module
here,
another
module
here,
another
module
here
and
then
down
below
you've,
got
all
these
different
panes
that
you
could
move
in
modules.
B
To
so,
let's
say
I
want
to
move
this
module
instance
to
the
right
pane
right,
so
it
actually
moved
it
it's
sort
of
instantaneously
for
me,
so
that's
how
you
can
move
content
around
within
the
within
your
theme
when
you're
in
edit
mode.
You
also
have
ability
to
manage
things
like
settings
for
this
particular
module.
If
I
go
in
there
I
can
see
I
can
manage
the
title
of
that
module.
B
B
B
You
also
have
the
ability
to
add
modules,
so
additional
module
instances
to
the
page
so
by
just
by
choosing
the
module,
and
so
let's
go
to
the
admin
dashboard
now
so
in
the
admin
dashboard.
This
is
what
I
was
talking
about,
so
all
the
administrative
modules
that
come
as
part
of
the
framework
so
to
manage
different
aspects
of
the
framework
itself.
So
I
can
go
into
my
insight
settings
right.
I
have
the
ability
to
specify
a
lot
of
different
configuration
for
the
site
I
can
specify,
which
you
know
what
the
logo
is.
B
If
I
have
a
fav
icon,
the
theme
that's
being
used,
I
can
specify
my
smtp
settings
for
doing
notifications,
which
got
a
whole
capability
in
the
system
for
managing
for
sending
notifications.
I
can
enable
this
as
a
progressive
web
application.
If
I
want
to-
and
it
tells
me
some
information
about
this
tenant
as
well
and
like
we
were
using
a
local
db
here,
just
with
integrated
security,
so
there's
a
lot
of
functionality,
so
you
can
manage
your
pages
manage
users.
B
You
can
manage
profiles
which
are
your
user
profiles,
so
you
can
specify
an
arbitrary
like
as
many
different
profile
settings
as
you
want
that
can
be
collected
through
the
user's
profile
and
each
of
these
have
you
know
a
lot
of
different
and
ways
that
you
can
specify
whether
they're
required
what
their
length
is.
You
know
you
can
lay
out.
Basically
your
user
profile,
page.
B
You
can
set
up
your
roles
and
assign
them
to
your
users.
You
got
a
full
file
management
capability
as
well,
where
you
can
specify
folders,
where
you're
going
to
be
able
to
upload
content,
and
you
have
the
there's
different
types
of
folders.
So
when
you
add
folder,
you
have
the
ability
to
specify
that
the
folder
is
either
private
or
public.
B
Private
folders
means
the
files
are
going
to
be
stored
in
a
location
that
are
inaccessible
unless
the
user
has
access
permissions,
provided
you
also
have
a
public
folder
where
again
there,
the
essentially
the
files
are
private,
but
if
the
user
knows
the
url,
they
can
actually
get
access
to
it
because
it's
stored
in
the
www
root
area
but
yeah.
This
is
basically
a
full
sort
of
asset
management
capability
for
uploading
files,
and
you
can
take
advantage
of
that.
B
You've
got
a
full
event
log
to
keep
track
of
all
of
the
different
events
that
are
happening
within
the
application
itself
and
it's
filtered,
of
course,
by
by
site.
So
these
are
all
of
the
different
events
that
have
happened
on
this
site.
So
it's
got
like
basically
a
full
auditing
capability.
That's
part
of
the
the
application.
B
If
I
look
at
the
details
for
this
it'll,
tell
me
all
of
the
information
about
this
particular
event,
including
like
things
like
what
url
you
know
was
invoked,
and
it
uses
the
the
seralog
type
of
format.
Where
you
know
it,
you
can
define
a
template
and
the
values
are
are
reflected
in
the
in
the
event
login
preserved.
In
the
event,
log.
B
Module
management,
oh
so,
actually,
site
management.
So
if
you
want
so
like,
I
said
it's
multi-tenant.
So
if
you
want
to
add
additional
site
right
now,
there's
only
one
default
site
that's
been
created,
I
can
say
I
want
to
add
a
site
uses
the
dnn
concept
of
aliases,
so
you'd
have
to
have
a
unique
way
of
act
like
of
accessing
a
site,
and
so
you
can
create
a
site
and
then
for
the
alias.
I
could
use
this
localhost
address
which
I'm
running
on,
but
I
can
actually
put
a
subfolder
on
it.
B
So
when
I
choose
what
what
tenant
this
site
is
going
to
be
created
in,
I
can
say
I
want
to
create
it
in
the
master
tenant,
which
is
the
the
default
database
that
we
created
when
we
installed,
or
I
can
say,
create
new
tenant
and
when
I
say
create
new
tenant,
I
can
give
it
a
new
tenant
name
and
I
could
actually
create
this
tenant
in
sql
light.
If
I
wanted
to,
if
I
provide
the
details
for
sql
lite.
B
So
this
is
how
you
can
create
sites
that
have
different
databases
and
not
just
not
the
same
database
engine
but
even
different
database
engines.
So
that's
how
you
can
create
multiple
sites,
module
management.
So
this
is
a
list
of
all
of
the
different
modules
that
are
part
of
this
particular
installation.
B
B
So
this
was
a
blog
module.
That
was
obviously
you
know,
created
separately
from
the
framework
itself.
I
just
have
to
say
I
want
to
download
it
and
once
I
download
it,
then
I
can
click
to
install
it,
and
so
there's
like
the
seamless
installation
experience,
and
I
would
expect
that
there's
going
to
be
a
lot
more
modules
that
are
created
over
time
that
people
who
are
building
applications
can
take
advantage
of
for
for
additional
functionality.
B
Similarly,
if
I
go
into
theme
management,
I
can
see
that
these
are
all
the
different
themes
that
I
have
installed.
Currently.
If
I
want
to
install
another
theme,
there
would
be
a
list
of
them
here
as
well,
but
I
have
already
there's
only
sort
of
one
theme
right
now
did
that
boot
swatch
theme
and
I've
already
installed
it.
B
Language
management,
so
obviously,
by
default
it
has
english.
I
can
add
additional
languages
if
I
want
to,
and
there
is
an
actual
translations
repo,
that's
in
the
octane
organization,
on
github
and
there's
a
number
of
languages
that
have
already
been
created.
I
think
six
or
seven
languages.
So
I
think
there's
french.
B
German
swiss,
like
there's
a
lot
persian,
I
mean
there's
a
lot
of
language
that
have
already
been
created.
So
localization
is
a
key
part.
You've
got
the
ability
to
schedule,
create
scheduled
jobs,
like
I
already
mentioned,
before,
sql
management.
So
if
I
want
to
manage
directly
like
if
I
want
to
interact
with
my
backend
database
through
the
user
interface,
I
can
do
that.
I
just
have
to
specify
which
tenant
I
want
to
interact
with,
and
then
I
can
execute
sql
commands.
B
I
can
see
system
info
related
to
this
site,
so
I'm
running
the
octane
framework,
2
2
on
dot
net
5
tells
me
some
information
about
my
installation.
I
also
have
the
ability
to
specify
some
different
configuration.
If
I
want
to
enable
some
things
you'll
see
here
that
swagger
is
enabled
by
default.
I
can
access
swagger
by
clicking
this
link
and
I've
got
my
full
swagger
api
ui.
That's
rendered
here.
B
And
then
it
does
have
a
system
update
capability
as
well,
where,
basically,
if
you
want
to
update
the
framework
using
the
latest
version,
it'll
tell
you
if
there's
a
version
available
and
it
can
actually
update
the
framework
in
a
really
seamless
way.
Much
like
you
can
do
with.
I
guess,
like
wordpress
or
other
types
of
you
know,
frameworks
that
have
this
capability.
B
So
it's
got
a
lot
of
robust
functionality,
that's
available
in
the
admin
area
as
far
as
getting
started
with
development,
and
I
think
that
probably
michael
washington
covered
a
lot
of
this
in
his
session
that
he
did
at
the
conference.
But
one
of
the
goals
behind
octane
was
you
know
it's
a
development
framework,
so
we
need
to
make
it
easy
for
developers
to
get
up
to
speed
quickly,
so
we've
created
a
module
creator
capability.
B
B
So
let's
say
I
want
to
create
a
module
and
I
just
enter
some
basic
information
about
the
module.
So
this
is
like
the
you
know:
who
owns
the
module?
Actually,
I
should
probably
say
it's:
you
know
that
give
it
a
module
name
and
then
I
can
select
a
template
by
default.
There's
only
one
template,
that's
provided
the
default
module
template.
B
And
I
can
select
which
framework
version
of
octane.
I
want
this
module
to
be
built
on
and
I'm
going
to
use
2.2,
which
is
the
one
I'm
running
right
now,
and
it
tells
me
where
it's
going
to
create
this
the
source
code
for
this
module,
because
it's
going
to
scaffold
out
a
whole
set
of
source
code
for
me,
and
so,
if
I
say,
create
module,
it
says
the
source
code
for
my
module
has
been
created
at
the
location
specified
below.
B
So
let's
take
that
location
and
then,
of
course,
it
needs
to
be
compiled
in
order
to
make
it
functional.
So
if
I
go
into,
let's
go
whoops:
let's
go
in
here,
let's
go
to
that
location
and
we
can
see
that
it
created
for
me
a
whole
lot
of
scaffolded
code,
a
solution
file
created
all
of
my
client
project,
my
server
project
and
my
shared
project.
So
let's
go
ahead
and
open
this.
B
I
got
a
client
project
and
if
I
open
that
we
can
see
that
it
created
some
razor
components
for
me
in
the
rate
format.
If
I
look
at
my
server
project,
it
created
basically
a
controller
project.
For
me
it
created
my
repository
for
me
and
it
created
migrations
for
me,
so
it
created
everything
I
need
to
basically
create
a
module.
B
If
I
go
into
my
index
page
here,
see
that
it's,
you
know
just
standard
razor
markup.
The
idea
with
this
as
well
is
it
makes
it
really
easy
to
compile
and
get
your
assets
in
the
appropriate
location.
So
there's
this
package
project
which
is
created
as
well
when
I
compile
this
module
in
debug
mode,
it's
going
to
as
a
post,
build
step.
It's
going
to
execute
this
debug.cmd
file.
B
If
we
look
at
that
file,
it's
going
to
x
copy
the
dlls
and
pdb
files
that
are
part
of
this
module
to
my
octane
server
instance,
so
that
the
octane's
framework
is
aware
of
them
and
can
utilize
them.
Similarly,
if
I
compile
this
module
in
release
mode,
it's
going
to
execute
this
release.cmn
cmd
file,
and
in
that
case
it's
actually
going
to
pack
the
the
results
of
this
module
into
a
nuget
package
using
this
new
spec
that
was
generated
for
me
so
including
all
of
the
dlls
and
pdbs
that
I
need
so
so.
B
This
is
the
easiest
way
to
create
a
releasable
package
and
it
actually
copies
that
package
to
my
octane
framework
so
that
it
can
be
installed
by
default.
So
I'm
going
to
I'm
going
to
go
ahead
and
just
use
the
debug
method
and
I'm
going
to
build
this
so
build
this
solution
and
by
building
the
solution
it's
going
to
build,
you
know
various
dlls
and
then
copy
them
over
because
of
that
debug.cmd
file.
So
it
says
it
worked.
B
So
when
you
run
octane
on
startup,
it's
going
to
automatically
recognize
hey,
there's
a
new
module
that
exists
in
the
bin
folder
and
if
there's
any
database
related
migrations
that
need
to
be
run,
it's
going
to
run
them
automatically
for
you,
so
that
this
module
is
fully
functional.
So
if
I
go,
let's
go
to
my
private
page.
I
go
to
my
admin
dashboard,
I'm
going
to
look
at
my
modules
and
I
see
I
have
my
test
module
here.
B
I
choose
my
test
module,
I'm
going
to
add
an
instance
of
that
module
to
my
page,
so
it
added
it
right
now,
there's
obviously
no
content,
but
it
the
fact
that
it
shows
no
test
to
display.
It
means
that
it
interacted
with
the
database
to
check
the
the
table
that
was
created
to
see
if
there
were
any
tests
and
there
weren't
any
I'm
going
to
add
a
test.
B
So
I'm
just
going
to
add
some
basic
content
here,
save
it,
and
so
basically
I
have
a
fully
functional
database
driven
module
that
is
running
fully
in
octane,
simply
by
creating
the
scaffolded
module.
And,
of
course,
you
know
once
you
have
a
great
starting
point,
you
can
go
back
and
you
can
customize
that
module
to
actually
do
you
know
what
your
specific
business
purpose
is.
B
So,
similarly
with
modules,
you
can
do
the
same
thing
with
themes,
so
you
can
go
in
and
you
can
create
a
theme
using
the
theme
creator
and
you
can
choose
the
default
theme.
Template
and
it'll
be
able
to
create
a
theme
for
you
as
well,
in
exactly
the
right
format,
with
all
the
scaffolded
bits
that
you
need
and
then
you
can
customize
it.
So
you
really
wanted
to
make
it
easy
for
developers
to
get
up
and
running
quickly.
B
Yeah,
I
think
that
I
mean
there's
a
lot
of
functionality
to
take
advantage
of
as
part
of
the
framework,
and
it
provides
like
some
very
powerful
building
blocks
so
that
you
don't
have
to
build
a
lot
of
you
know:
custom
capabilities
yourself.
You
can
rely
on.
You
know
things
on
building
blocks
that
are
already
part
of
the
framework
yeah.
A
A
A
Sure
so
before
or
before
going
to
the
q
a
there's,
something
that
I
have
for
our
attendees,
so
two
lucky
attendees
will
stand
a
chance
to
win
an
ebook
of
web
development
with
blazer
written
by
jimmy
angstrom
from
our
sponsors
back,
so
you
know,
so
how
does
it
work
is
most?
Moreover,
like
you
know,
sean
gets
to
select
two
of
his
favorite
questions
that
I
speak
to
him,
so
the
person
who
have
asked
that
they
are
going
to
get
this
particular
ebook
from
us.
So
guys
please
stay
with
us.
A
A
A
Maybe
his
question
is
more
towards
plays
server
side
and
so
sorry,
can
you
repeat
the
question
again,
I'm
not
sure
I
caught
the
taste
of
it.
I'll
repeat
it
again.
So,
as
I
said
that
using
signalr
for
every
communication
is
not
a
good
practice,
so
do
you
think
that
this
will
be
a
success
using
the
same
fundamentals.
B
B
I
think
that
in
a
recent
survey
that
I
saw
of
people
who
are
using
blazer
already,
it
was
pretty
much
an
even
split
of
those
folks
who
are
using
blazer
server
versus
blazer
web
assembly.
So
you
know,
50
of
the
people
are
actually
building
solutions
on
blazer
server.
I
think
that
that
it's
not
really
a
limitation
that
it's
using
signalr
signalr
is
very
powerful
right
and
it
is
a
very
responsive
technology
and
there
are
certain
benefits
that
you
get
with
laser
server.
B
So
and
that's
not
even
utilizing
like
the
the
more
serious
like
you
can
utilize
the
the
azure
signalr
backplane
service
right,
which
is
like
a
really
robust
enterprise
level
service
for
scalability.
But
what
I
was
talking
about
in
those
metrics
that
I
shared
was
just
a
standard.
Azure
instance
right
a
standard
app
service,
so
it
can
even
scale
pretty
well
with
that.
So
I
don't
so
I
I
think
blazer
server
is
a
viable
technology
that
is
here
to
stay.
A
B
A
B
B
Because
when
you
build
a
blazer
application,
essentially
blazer
owns
the
dom
at
that
point,
and
so
it
will
do
some
interesting
things.
So,
if
you've
included
javascript
like
inline
javascript
code
within
your
razer
components,
sometimes
it'll
just
ignore
most
of
the
time.
It'll
just
ignore
it
altogether.
Sometimes
it'll.
I
think
there
are
some
tricks
to
try
and
get
it
to
to
actually
recognize
it.
But
it's
really
not
a
supported
method.
It's
it's!
B
A
I
hope
I
hope
it
answers
lee
camps
and,
let's
move
on
to
the
next
question,
so
it's
again
reprint
so
he's
asking
that
do
we
need
to
specifically
use
laser
server
with
laser
web
assembly.
Can
we
have
some
permutation
combination
with
server
as
dotnet
framework
or
code
and
laser
web
assembly?
I
think
this
should
be
possible
right.
Yeah.
B
Yeah,
so
you
have
to
choose
one
hosting
model
that
you're
going
to
run
your
application
in
whether
it's
webassembly
or
server,
unless,
unless
the
person
who's
asking
was
saying,
could
you
be
able
to
like
within
the
same
application
mix
and
match
right,
have
some
components
that
are
running
on
webassembly
and
some
that
are
running
on
server?
That's
not
possible.
B
A
Well,
if
it
is
about
reusability,
then
definitely
we
can
like
we
can,
if
you
know,
while
building
our
laser
server
applications,
we
take
into
the
consideration
that
you
know.
We
want
to
port
this
components
again
in
a
web
assembly
app
then,
if
we
design
it
well,
then
we
can
reuse
our
components
in
our
piece
of
webassembly
app,
as
well
as
the
servo
app
so.
B
A
B
Yeah,
absolutely
yeah,
there's
no
reason
why
you
couldn't
use
microservices,
I
mean,
I
think,
that
the
notion
of
microservices
is
sometimes
kind
of
fuzzy
right
people.
I
don't
know
specifically
what
he
might
be
referring
to
by
microservices,
because
sometimes
people
have
different
definitions.
But
if,
if
you
have
independently,
I
guess
hosted
apis
that
there's
no
reason
why
your
blazer
application
can't
call
them.
B
The
only
thing
that
you
have
to
make
sure
that
you
put
in
place
is
some
kind
of
a
you
know,
a
security
mechanism
right,
so
that
you'd
have
to
have
some
kind
of
an
authentication
system
or
authorization
system
that
would
flow
between
the
blazer
application
and
the
the
back
end
microservices.
But
I
mean
obviously
those
those
technologies
exist.
So
yeah,
there's
no
reason
why
you
couldn't
the
same
way
that
you
build
like
there's
no
reason
like
so
you
can
build
a
react
or
an
angular
front-end
that
uses
microservices.
A
B
So
micro
front-end
solve
a
number
of
different
problems
right.
So
basically
one
of
the
traditional
problems
with
single
page
applications
is,
you
know:
you'd
have
one
big
monolithic
front
end
and
then
you'd
have
your
back
end
split
out
into
micro
services,
and
so
with
micro
front
ends,
you're
breaking
up
your
user
interface
into
smaller,
reusable
or
smaller
deployable
pieces
as
well
right,
and
then
that
those
pieces
are
being
combined
together
in
to
form
a
a
larger
like
user
interface
at
runtime.
B
That's,
actually
what
octane
is
doing
as
well.
I
mean
each
of
like
that
module
that
we
just
created
completely
separate
backend
and
user
interface
and
then
at
runtime
it's
actually
rendering
the
user
interface.
So
it's
essentially
a
micro
front-end
capability
right
it.
The
only
difference.
Is
it's
not
using
javascript,
it's
using
blazer,
so
compiled
c-sharp
right.
So
I
guess
it
depends
on
what
your
definition
of
an
of
a
micro
front
end
is
because
it
seems
that
what
I
just
showed
you
seems
to
seems
to
demonstrate
a
micro,
front-end
capability
right
from
a
conceptual
perspective.
A
B
B
A
B
Yeah,
so
obviously
there's
like
the
four
databases
that
are
supported
right
now,
and
there
is
a
way
that
you
could
build
an
additional
providers
and
a
provider.
You
know
someone's
asked
already
about
building
an
oracle
provider,
so
you
could
build
a
provider
and
then
you
also
provide
the
front-end
razer
component
for
capturing
the
configuration
details
that
are
specific
to
that
database,
and
then
you
would
also
need
to
include
config
the
configuration
for
that
in
the
database.
B
So
I'll
show
you
like
here
the
available
databases
in
the
app
settings.
It
defines
like
all
of
the
different
databases
that
are
supported
and
it
has
sort
of
two
types
right.
This
is
the
provider,
and
this
is
the
ui
that's
being
used,
and
so
that's
all
that
would
have
to
be
provided.
So
you
could,
you
could
create
another
one,
for
you
know
any
any
other
database.
You
wanted
to
support.
B
Yeah,
I
just
don't
know
what
the
what
the
complexities
might
be
because,
like
I
said,
cosmos
db,
is
a
nosql
solution
right,
so
it
it
might
have
some
challenges
in
in
order
to
make
that
work,
because
the
other
d,
all
of
these
database
providers,
are
all
relational
and
the
application
framework,
like
the
framework
itself,
relies
on
some
of
the
intrinsic
capabilities
of
relational
databases,
for
example
like
cascading
deletes,
and
things
like
that
are
all
all
of
these
database
providers.
Support
that,
and
so
octane
framework
relies
on
that.
A
B
A
B
A
B
No,
so
that's
that's
something.
That's
still
on
the
roadmap
is
support
for
other
authentication
methods.
Right
now
it
only
has
like
a
well.
It
uses
the
net
core
identity
system,
and
you
know
it
has
local
user
accounts.
You
can
log
in
it
uses
cookie-based
authentication
but
yeah
it.
That's
something.
That's
on
the
roadmap
that
will
be
in
a
future
version
is
support
for,
like
at
least
azure
ad
b2c,
a
lot
like
social
logins
like
being
able
to
log
in
using
your
facebook
or
your
twitter.
You
know.
A
B
A
B
A
B
So
that
must
be
an
octane
question,
so
yeah
yeah
yep
you
can
you,
can
you
can
write
standard,
yeah,
sql
queries
and
it
executes
it
against
that,
so,
whichever
you
have
to
choose
the
tenant,
so
you
have
to
be
kind
of
aware
of
the
nuances
right
of
the
sql
dialect
of
that
tenant.
So
if
it's
you
know,
if
if
the
tenant
is
using
sql
server,
then
you
you
know
you
use
that
flavor
of
sql.
If
you're
using
my
sql,
then
it
would
be
that
flavor
of
sql
but
yeah.
B
B
B
B
B
Can
I
write
raw
sql
queries?
Absolutely
you
can
there's
no
there's
nothing,
restricting
you
from
doing
that
in
fact
like.
If
you
want
to
build
a
module-
and
you
want
to
instead
of
using
ef
core
migrations,
you
want
to
use
sql
scripts
right
and
actually
write
a
a
sql
migration
script
manually.
You
can
do
that.
It
has
support
for
that
as
well,
because
that's
actually
how
octane
was
originally
working
prior
to
adding
the
support
for
multi
databases.
B
So,
of
course,
if
you
go
down
that
path,
you
you're
not
going
to
be
able
to
do
you're
not
going
to
be
able
to
have
the
multi-database
support
right
as
soon
as
you
start,
using
sql
scripts
and
using
raw
sql,
most
likely
you're,
limiting
yourself
to
a
specific
database,
and
that
might
be
just
fine
because
you
might
have
no
intention
of
using
anything
but
that
one
database
anyways
so
but
yeah.
It
doesn't
restrict
you
in
what
you
can
use
for
data
access.
A
That's
great,
it
allows
you
to
you
know,
extend
your
application
depending
upon
your
requirements.
So
let's
move
on
to
the
next
question,
so
it's
again
by
leonardo.
So
can
I
combine
other
blaze,
laser
ui
frameworks
with
octane,
maybe
something
like
blazard
or
laser
eyes,
or
else
you
know
something
from
telerake?
Yes,
absolutely
so.
B
B
However,
a
lot
of
people
want
to
use
things
like
you
know
the
third
party
ui
controls
from
infogistics
or
telerik,
or
sync,
fusion
or
or
others
and
and
there's
also
a
lot
of
new
ones
that
are
specific
to
blazer
as
well
like
the
ones
that
you
mentioned,
and
you
can
absolutely
use
those
with
octane.
There's,
there's
a
number
of
articles
that
have
been
written
that
actually
michael
washington,
who
presented
at
the
conference
on
on
octane.
A
A
B
B
A
A
Let's
move
on
to
the
next
question:
okay,
so
it's
from
yes,
so
he's
saying
that
there's
a
lot
of
confusion
about
blazer,
as
you
said,
laser
needs
javascript,
but
some
say:
there's
no
need
javascript
or
angular.
So
what
should
we
learn?
Laser
or
angular
like
where's
the
future?
Maybe
he's
confused
over
there
with
the
road
map
like
how
should
he
approach
things?
Well,
I
think
that.
B
So
microsoft
recognizes
that
angular
is
a
very
like
popular
solution
and
there's
a
lot
of
industry
support
for
it's
been
around
for
a
long
time.
It's
very
mature.
So
I
think
that
microsoft
still
has
to
provide
guidance
on
how
to
build
net
applications
using
angular
right.
So
there
there
still
is
templates
that
they're
providing
for
how
to
spin
up
a
you
know
a
a
single
page
application
using
angular
on
the
front
end
and
c
sharp
for
your
services
on
the
back
end,
but
then,
as
an
alternate
they're
providing
blazer.
So
it's
it!
B
B
What's
the
best
technology
for
their
case,
like
let's
say
you
have
a
bunch
of
back
end
developers
right
and
you
need
to
migrate
an
existing
application
well,
making
them
learn,
angular
and
expecting
them
to
be
like
very
becoming
immediate.
Experts
on
javascript
is
probably
not
realistic,
so
maybe
that's
a
case
where
they
would
be
better
off
using
blazer,
whereas,
like
maybe
you're
an
agency
that
does
a
ton
of
javascript
and
you
don't
you're,
not
really
strong
on
back
end
development
techniques.
B
A
Okay,
I
was
a
mute,
so
that
makes
sense
in
a
way
because
you
know
even
I
had
some
trouble.
You
know
working
with
javascript
in
the
beginning
of
my
career,
so
blazer
makes
my
work
really
easy,
like
I
made
my
whole
blog
app
using
a
blazer
itself,
so
you
know
it
helped
me
fill
it
up
in
seven
weeks.
Sorry,
seven
days
in
a
week,
so
you
know
it
increases
your
productivity
as
a
developer,
so
there
are
javascript
somewhere.
So
you
need
to
have
the
ornaments.
B
Yeah
and
I've
found
like
because
of
the
javascript
interrupt
capability
like
so,
for
example,
octane
does
have.
Let
me
show
you
something
here
so
in
octane
there
is
a
like
if
we
look
in
the
javascript
there's
an
interop
file
here
and
there's
a
lot
of
general
sort
of
javascript
functions
that
are
in
here
like
getting
and
setting
cookies
or
if
I
want
to
update
the
title
of
the
page
right
or
if
I
want
to
update
the
metadata
like
but
and
it
rather
than
having
the
developers
write.
B
This
javascript
there's
also
a
front
end.
Nice
wrapper
around
it.
If
I
look
in
the
ui
folder
interrupt
here,
so
if
I
want
to
call
set
cookie
from
my
razer
component,
I
just
call
a.net
method
and
it
in
turn,
of
course,
calls
javascript.
But
this
is
so
instead
of
having
to
write
javascript,
there's
probably
going
to
be
more
and
more
sort
of
library
methods
that
will
be
available
for
dotnet
developers
so
that
they
don't
actually
have
to
deal
with
javascript
itself
right
they'll
be
calling.net,
a.net
method,
but
and
under
the
covers
it's
using
javascript.
B
A
B
Yeah,
I
know
that
in
dot
net
5
microsoft
already
increased,
like
the
number
of
methods
right.
That
sort
of
that
use
javascript
under
the
covers,
but
just
making
it
easier
for
developers
to
to
just
you
know,
call
framework-based
methods
to
do
what
they
need
to
do
within
blazer
and
not
have
to
write
the
javascript
themselves.
A
That's
true,
that's
true
indeed,
but
the
js
interop
also
comes
in
handy.
If
you
already
have
a
huge
chunk
of
what
you
say,
your
own
custom,
javascript
library,
which
you
use
across
your
projects,
you
can
always
leverage
that
instead
of
you
know
reinvesting,
you
know
more
effort
more
time
and
building
all
those
stuff.
B
B
A
B
A
True,
maybe
maybe
we
may
not
have
some
components
that
are
there
and
angular,
because
angular
is
very
old.
To
be
honest,
with
respect
to
blazer
is
pretty
old,
so
there
can
be
a
lot
of
you
know
third-party
libraries
components
that
are
out
there
in
the
marketplace
it
doesn't
have,
but
you
can
always
make
one
if
you
need
it
yeah
and
I.
A
A
B
I
have
not
played
with
maui
yet
no,
and
I
know
that
there's
all
the
you
know,
the.net
6
previews
are
out
I've
been
reading
the
blogs,
but
I
actually
haven't
installed
a.net
6
preview.
Yet,
although
the
goal
would
be
to
have
a
version
of
octaneon.net
6
available
in
november,
so-
and
I
I
mean
the
transition
from.net
core
3.1
to
5.9-
was
actually
super
easy.
B
There
was
no
breaking
changes,
so
I'm
hoping
that
it'll
be
a
similar
progression
to
net
six.
I
I
don't
foresee
any
challenges
there,
but
I'm
excited
for.net,
six
because.net,
six,
the
fact
that
it's
an
lts
release
right
for
both
laser
server
and
blazer
web
assembly
that'll,
probably
encourage
more
people
to
to
jump
on
right.
It's
people
sometimes
don't
they.
They
feel
that
there's
too
much
risk
around
using
ga
releases
and
they
want
those
lts
releases,
especially
large
enterprises.
So
it'll
be
nice
to
have
done
at
six.
A
That
makes
sense-
indeed
you
know,
since
you
have
mentioned
about
you
know,
you
know
the
skepticism
with
people
in
working
around
with
the
current
releases
that
are
even
though
they
are
in
ga.
So
you
know
there
was
one
particular
question
that
I
faced
on
normal
conferences.
Wherever
I
go,
you
know
where
I
host
and
blazer
application.
Please
any
any
talk
on
blazer.
They
asked
me
this
one
particular
question
can.
A
B
And
yes,
there
are
definitely
are.
I
don't
have
a
list
of
that
I
can
provide,
but,
like
yeah
like
I
mean
I,
I
have
obviously
a
number
of
public
sites
that
are
running
on
blazer.
I
guess
they're
looking
for
more
notable
examples,
maybe
more
expensive
yeah.
I
asked
actually
I
reached
out
to
dan
roth
right
who's.
The
program.
B
For
blazer-
and
I
I
said
that
that
this
question
keeps
coming
up
and
he
said
that
microsoft
is
working
on
it,
that
you
know,
because
they
and
there's
the
two
different
types
of
aspects
to
that
question.
Usually
like
there's,
there's
people
who
are
looking
for
quantity
of
of
sites
that
are
running
on
a
particular
technology
right.
That
kind
of
proves
that
there's
a
broad
adoption
and
then
there's
other
folks
that
are
looking
for
like
deep
detailed
case
studies.
B
Right
like
tell
me
all
the
details
about
all
the
complexities
of
of
it
and
what
were
the
benefits
and
like
like
white
paper
kind
of
stuff,
and
so
it
takes
a
lot
of
work
to
create
all
of
that
information
and
make
it
available
so
and
because
I
think
blazer's
new
there's
just
not
a
lot
of
it
available
yet.
But
I
think
that
that,
like
having
that
information
available
would
really
help
with
well.
For
those
of
us
right
who
have
to
deal
with
those
questions.
A
B
Yeah,
oh
yeah
yeah.
We,
we
are
developing
blazer
applications
absolutely,
but
in
a
lot
of
those
cases,
those
they
can't
be,
the
the
details
of
them
can't
be
shared
because
they're
they're
like
they're,
sometimes
they're,
internal
or
they're.
You
know
there's
like
experimental
confidentiality
reasons
right
where
you,
you
can't
share
information
about
the
technologies
that
certain
customers
are
using.
So.
A
A
True
enter
enterprise.
Adoption
is
actually,
you
know,
always
a
concern,
because
you
learn
a
new
technology
and
you
want
you
know
you
want
it
to
use
in
your
work
at
least
right.
That's
why
you
learn
it
at
the
first
place.
Hobby
is
there,
but
still
adoption,
always
you
know
at
an
enterprise
gate
all
this
helps
now
it
keeps
you
motivated
to
learn
more
about
this
tech.
B
Yeah,
I
think
so.
The
other
thing
is,
I
even
did
some
searching
like
you
can
use.
You
know
built
with
right
and
search
for
certain
technologies,
but
it's
not
even
in
there
it's
not
easy
to
identify
blazer,
I
don't
think,
or
maybe
they
didn't
even
have
an
option
to
identify
it.
I
think
that
you
could
look
for
a
web
assembly,
but
that's
that's
only
part
of
the
picture
right
that
doesn't
that
wouldn't
reveal
any
of
the
laser
server.
B
A
Hopefully,
fingers
crossed
yeah,
so
I
I
would
like
to
give
a
shout
out
to
jeremy,
our
friend
jeremy,
who
has
been
you
know,
answering
questions
throughout
the
whole
session
and
thank
you,
jeremy,
for
you
know,
helping
us
a
lot
throughout
the
session
by
answering
some
of
the
questions.
So
it
was
really
helpful
and
do
mention
your
email
address
in
the
chat
window.
We
have
something
up
for
you,
it's
pretty
exciting
and
I
know
that
you
have
been
working
on
blizzard
for
some
time
now.
A
You're
excited
about
it
and
I
have
something
more
exciting
for
you.
So
now
it's
it's
the
important
time
to
pick
up
the
two
winners
who
are
going
to
get
the
book
on
web
development
with
laser
by
jeremy.
You
know
which
is
sponsored
by
our
sponsor
pack,
so
sean,
which
way
the
two
most.
You
know
interesting
question
that
you
found
throughout
the
q
a
session.
B
B
A
A
A
A
So
this
is
a
pretty
new
book
that
is
sponsored
by
our
sponsor
pack,
so
I
hope
you
find
it
exciting
and
thank
you
for
joining
in
so
before
we
close
on,
we
have
been
going
pretty
overboard
now.
Thank
you.
Thank
you,
sean
for
being
patient,
and
this
is
this
is
one
particular
question
that
I
would
like
to
ask
you
like
often
is
an
open
source
project
right
yep.
A
B
I
used
to
build
them
only
for
myself
and
then
I
guess
it
was
with
dnn
that
I
realized
that
by
sharing
those
frameworks
with
others,
you
know
it
actually
provides
a
lot
of
value
for
not
just
myself
but
a
lot
of
other
people,
and
you
know
I
went
through
the
whole
sort
of
life
cycle
with
dnn
and
then
I
think
when
I
left
dnn
corp
in
2014,
I
didn't
think
I
would
probably
do
another
or
create
another
open
source
project.
I
was
kind
of
burned
out.
It's
a
lot
of
work.
It's
yeah!
B
It
takes
a
lot
of
commitment,
but
then,
for
whatever
reason
in
2018
it
was
actually.
I
was
thinking
that
there
weren't
very
many
there
weren't
enough
frameworks
for
net
core
that
were
available
and
scott
hunter
actually
reached
out
to
me
and
asked.
If
I
had
taken
a
look
at
blazer
and
after
I
looked
at
it,
I
was
pretty
excited
because
I
think
it
had
a
lot
of
the
characteristics
that
I
had
been
missing
in
some
of
the
earlier
microsoft,
tooling
and
yeah
from
there.
B
It
just
kind
of
grew
into.
I
think,
even
when
I
created
the
initial
proof
of
concept,
I
wasn't
sure
that
I
wanted
to
release
it
as
an
open
source
project,
but
then
I
did-
and
here
we
are
so
but
yeah,
it's
it.
Definitely
I
don't
know
it's.
I
have
a
passion,
I
guess
for
technology
and
it's
fun
to
share
that
technology.
B
A
B
A
So
it
seems
like
leonardo
and
friends
have
shared
their
email
address,
but
there
is
some
reason
with
you
to
chat
window
policies.
We
are
unable
to
see
that
so
I
request,
leonardo
and
prince
to
you
know,
send
me
a
message
with
my
linkedin
profile
and
I
I'll
just
you
know,
connect
with
you
and
share
the
e-copies
over
there.
A
I'm
sorry,
I
I'm
unable
to
see
your
email
address
to
be
honest
and
after
the
stream
ends,
I
won't
even
have
access
to
any
of
the
things.
So
just
drop
me
a
message
over
there
and
I'll
connect
with
you
and
share
the
e
copies,
and
thank
you
folks
for
joining
in
on
a
weekend.
You
know
spending
your
time.
Learning
about
a
new
technology
completely
is
not
new,
but
it's
relatively
new.
So
so
thanks
again
thanks
everyone
for
joining
in
and
thank
you,
jeremy
and
I'll
definitely
reach
out
to
you.