►
Description
Join members from the ASP.NET teams for our community standup covering great community contributions for ASP.NET, ASP.NET Core, and more.
Community links for this week: https://www.theurlist.com/aspnet-standup-2020-06-23
A
Hopefully
the
Internet's
happen
awesome
seem
to
CIC
microphones
moving.
How
are
you
doing
the
line
I'm
doing
great?
How
are
you
John
I'm
doing
great
myself
I
see
audio
dials
moving.
If
someone
in
the
chat
can
let
us
know
if
they
can
hear
us?
Okay,
we
will
charge
on
ahead
so
happy
to
have
you
on
you're
gonna,
be
talking
to
us
about
blazer
mobile
bindings,
yeah.
B
A
B
A
A
A
A
Here
are
the
links
for
the
week.
You
know
somebody
pointed
out
to
me
and
I
don't
actually
use
this,
but
there
is
a
QR
code
feature
and
you
know
I,
don't
know
how
likely
it
is
that
anyone
actually
wants
to
use
this
QR
code,
but
if
they
wanted
to,
they
could,
and
this
would
give
them
access
this
list
of
links.
I
will
also
just
share
it
in
the
chat,
but
this
is
what
I
got
for
you
this
week.
A
Every
week,
I'm
like
I'll,
just
do
a
few
links
and
then
go
looking
at
what
everyone's
writing
about
and
there's
a
lot
of
good
stuff.
So
I
have
grouped
these
in
terms
of
kind
of
subject
matters.
So
first,
we've
got
some
things:
dealing
with
identity
and
authentication,
so
Joseph
wood
with
a
pretty
hefty
walkthrough
of
using
the
Microsoft
identity
platform.
So
as
it
points
out
here,
this
is
a
ten
minute
read.
This
is
in
depth
and
it's
just
just
a
full-on
walkthrough
so
step
by
step
of
what
you
need
to
do.
A
There's
not
anything
really
specific
I
want
to
call
out
in
here
other
than
it's
a
great
resource
and
it's
cool
to
see
Joseph
said
he's,
you
know,
he's
been
creating
some
more
stuff
lately
he's
doing
some
live
twitch
streams
and
he's
doing
some
in-depth,
walkthroughs
and
stuff,
so
excellent,
looking
forward
to
seeing
more
all
right
christos
has
been.
He
is
working
with
with
like
the
Microsoft
craft
team
and
doing
an
authentication
stuff
lately,
and
so
here
is
a
another.
This
is
using
Azure
easy
off.
A
So
as
your
app
service
authentication
and
integration
with.net
core
3-1
again,
this
is
a
pretty
you
know.
Hefty
walk
through.
You
know
just
walking
through
everything
you
need
to
do
as
far
as
getting
it
set
up
so
easy
opt
is
really
cool
like
it's
neat
that
you
can,
you
can
integrate
it
very
easily,
but
it's
also
nice
that
you
can
do
some
more
advanced
integration,
so
good
stuff.
And
finally,
this
is
just
neat
identity
server.
A
You
know
built
into
like
the
API
templates,
the
there's,
the
single
page,
app
templates,
and
so
it's
they've
updated
their
demoed
identity,
server,
dot,
IO
to
identity
server.
For
so
what's
cool
here
this,
this
allows
you
to
go
through
like
it
gives
you
links
over
to
source
code,
but
also
as
you're
doing
local
development.
This
is
pretty
cool
that
you
can
work
directly
against
their
their
demo
server
here,
all
right
now
for
some
traditional
server-side
render
at
HTML
section
of
our
stuff.
A
So
here's
just
a
quick
walkthrough
from
Mike
and
he's
showing
how
to
integrate
the
blazer
carousel
with
Razer
pages
in
the
entity
framework,
so
he's
pulling
information
from
any
framework
and
using
it
to
select
items
that
appear
in
the
carousel,
and
you
know
it's
just
I
I
think
I
really
like
the
components
that
are
available
with
bootstrap
and
it's
neat
to
be
able
to
integrate
them
here.
This
is
pretty
straightforward.
A
Just
pulling
items
out
of
the
list
here,
he's
he's
pulling
out
employees
and
then
you
can
put
in
things
like
an
employee
picture
right
or
or
data,
so
here
he's
finding
in
the
employee
photo
and
he's
actually
using
base64
data
for
them
all
right.
This
is
neat,
so
Donathan
is
writing
up
using
a
chart
component
and
there's
a
lot
of
you
know.
Javascript
chart
libraries
out
there
what's
nice
with
this
is
he's
integrating
it
a
little
bit
more
and
he's
using
a
view
component.
So
that's
that's
kind
of
cool
there.
A
How
that's
integrated
so
here
he's
using
chart
j/s
he's
creating
a
view
component
for
that
using
and
so
here's
his
chart
component-
and
you
know
like
doing
the
integration
stuff
with
chart
j/s
and
then
he
goes
through
and
has
a
pretty
thorough.
So
I
like
this,
that
you
you
can
integrate
things
more
directly
and
using
something
like
a
view
component
to
monetize
it
so
stuff.
A
Alright,
you
head
charging
ahead
here,
he's
almost
done
with
his
twenty
six
part
series
on
asp
net
core
3-1,
and
here
he's
looking
at
XML
and
JSON
output
for
web
api's.
So
you
know
there's
the
kind
of
obvious
you
know
the
the
things
that
you
can
do
kind
of
right
out
at
the
box
and
depth
things
that
you
can
do
as
far
as
customizing.
Definitely
with
Jason
there's
a
lot
you
can
do,
and
so
he
walks
through
doing
that
and
again
I.
Don't
have
a
specific
thing!
A
I
want
to
pull
out
in
here
other
than
you
know
good
on
yuusha
head
for
writing.
These
in-depth
things
I
regularly
like
when
I'm
looking
something
that
I
wanted
to
do.
I'll
check
these
out,
because
these
are
just
a
step
beyond.
What's
in
the
docs
and
what's
neat
about
this
series
too,
is
that
he's
doing
this
with
his
net
learner
code
base?
So
he
has
taken
this
net
learner
project
and
then
all
of
his
different
themes.
He
uses
those
to
kind
of
dig
deeper
into
that
all
right,
moving
into
some
blazer
fun.
A
So,
first
of
all,
I
don't
know
if
I've
mentioned
this
before,
but
Jeff
Fritz
has
this
really
cool
project
where
he's
kind
of
implemented
web
forms
controls
in
blazer
so
for
projects
that
are
migrating
from
web
forms.
Moving
over
to
to
blazer
and
wanting
to
get
you
know,
run
a
modern
solution,
take
advantage
of
all
the
newest
stuff.
A
Then
you
know
the
this
is
kind
of
a
nice
component
to
component
translation.
So,
first
of
all,
here
he's
interviewed
on
technology
and
friends,
which
is
also
super
cool,
so
great
that
David's
but
I,
don't
even
know
how
many
episodes
David's
done
to
this.
It's
hundreds
and
hundreds,
but
so
here's
an
interview
about
that
and
then
here's
Jeff
Fritz's
repo.
A
A
You
know
like
building
a
line
of
business
application
and
what
was
cool
with
this
is
he
got
some
feedback
from
people
on
ways
it
could
improve,
and
so
a
few
things
in
here
he
did.
One
is
simple:
UI
focus
thing:
we're
working
better
with
responsiveness
and
it's
cool
that
blazer
has
all
these
features.
That's
a
kind
of
a
major
overlooked
advantage
of
building
things
with
bootstrap.
Is
it's
it's
a
lot
it's
built
for
responsive.
You
know
like
working
well
from
a
phone
all
the
way
up
to
a
very
large.
A
A
And
here
we
can
hopefully
not
blow
anyone's
ears
out,
but
it's
pretty
neat
I
always
doing
that.
So
this
is
a
he
actually
set
it
up,
so
you
can
play
it
using
the
keyboard
as
well,
and
he's
got
a
ton
of
these
out
there,
and
here
he's
he's.
This
is
the
code
for
how
he's
doing
that.
This
brings
back
good
old
memories.
B
A
That
is
the
that
is
all
the
links
I
brought
to
the
table
and
then
Alon
you
brought
a
few.
This
is
one
that
I
actually
did
share
when
it
came
out,
but
this
is
the
announcement
post
from
from
the
last
release
the
experimental
mobile
blazer
bindings.
So
so
this
is
cool,
and
you
know
I
was
happy
to
see
some
of
the
things,
especially
like
the
more
the
CSS
improvements.
A
That's
pretty
neat
and
then
two
things
that
you
pointed
out
in
here,
which
is
very
cool,
especially
because
we're
in
the
community
blog
post
section
is
one
Dylan.
Has
this
thing
about
getting
started
and
why
you
should
care?
So
this?
This
is
pretty
cool
anything
you
want
to
call
it
specifically
here
or
just
just
a
cool
post,
I.
B
A
Know
it's
interesting
I'm,
seeing
in
Dylan's
he
points
out
just
the
simplicity
in
terms
of
lines
of
code.
So
some
things
here
like
this
is
you
know
using
xamarin
forms
and
there's
no,
you
know
I
see
people
get
very
uptight
about
different
things,
a
lot
of
things
it's
just
like
hey,
which
works
better
for
you.
What's
you
know,
there's
no
like
right
or
wrong
for
a
lot
of
stuff
for
some
people
they
might
want.
They
may
just
prefer
the
you
know
the
the
zamel
mvvm
style
and
that's
cool
for
other
people.
A
B
B
A
B
You
can
use
zaman
forms
because
it's
built
on
top
of
the
salmon
platform.
What
it
does
is
it
lets
you
use.
The
blazer
syntax
is
a
replacement
for
the
sam'l
syntax,
but
using
the
same
components
the
same
functionality.
You
have
access
to
things
like
xamarin
essentials
for
using
native
device
capabilities
and
sensors,
and
you
know,
maps
and
everything
that
the
camera,
everything
that
the
device
has
to
offer.
The
idea
being
is
that
we
know
there's
a
whole
bunch
of
people
who
have
a
lot
of
web
development
skills.
B
So
that's
that's
a
little
bit
of
a
kind
of
what
mobile
blazer
bindings
is
I'm,
not
gonna.
Talk
too
much
about
that,
because
I
think
folks,
who
may
have
already
seen
that
or
you
can
watch
some
of
the
past.
There's
lots
of
talks
and
demos
out
there
that
you
can
check
out.
One
of
things
John
mentioned
is
that
in
the
most
recent
update,
which
is
just
nearly
one
month
ago,
that
we
did
for
mobile
blazer
bindings
is
improvements
to
CSS.
B
One
of
the
big
selling
points
I
think
for
mobile
blazer
bindings
is
its
support
for
real
actual
CSS.
It's
not
some
kind
of
fake
CSS
like
thing,
but
you
can
apply
CSS
styles
to
elements
in
mobile
blazer
bindings,
just
like
you
can
in
other
xamarin
forms
projects
and
potentially
even
share
CSS
Styles
between
parts
of
your
web.
App
parts
of
your
mobile
app,
so
I
wrote
up.
Some
thoughts
are.
A
B
It's
it's
the
the
answer.
I
love
to
give,
which
I
think
is
completely
true-
is
there's
a
bunch
of
really
super
smart
people
who
work
on
xamarin
and
xamarin
forms,
and
that's
where
that
comes
from.
How
does
it
actually
work?
The
short
story
is
the
your
CSS
file
gets
embedded
as
an
embedded
resource
in
the
dll
that
that
gets
compiled
and
when
you
instantiate
xamarin
forms
elements
which
is
ultimately
what
mobile
blazer
bindings
does.
Is
it
instead
of
creating
them
from
zamel?
B
B
Really
they
quickly
fixed
the
issue
and
that's
that's
out
there,
and
that
makes
for
a
really
clean
cool
story,
and
so
there's
some
docs
here
on
how
to
do
it
and
there's
one
of
the
samples
in
the
mobile
blaze.
Your
bindings,
repo,
Samer
and
/
mobile
blazer
bindings
on
github
is
the
weather
sample
and
the
weather
sample
if
I
go
into
the
UI
part
of
the
part
of
the
project
here,
oops,
and
what
am
I
clicking
on,
did
github
always
have
that
dot
doc
to
go
up
to
the
parent
directory.
B
A
A
B
A
B
A
B
Anyway,
so
here
there's
a
CSS
file
here,
it's
it's
a
real
regular
CSS
file
is
the
editing.
Experience
in
visual
studio
is
terrific,
with
autocomplete
and
you
get
intellisense
and
you
get
the
little
color
pickers
and
things
like
that.
So
it's
a
regular
CSS
file
and
then
you're
in
the
main.
Where
is
it
weather
app
dot
razor
to
consume
it?
You
embed
the
you
associate
the
CSS
file
as
in
a
stylesheet
component,
and
then
you
use
CSS,
just
like
you
would
in
HTML.
B
So
you
said
you
know:
class
equals
CSS
class
selector
or
also
you
can
use.
There
are
other
types
of
selectors
as
well
element,
selectors,
hierarchical
selectors,
to
say
all
the
buttons
inside
a
stack
layout,
I
want
to
have
this
style
and
so
forth.
Although
all
the
regular
CSS
things
that
you
expect
there
there's
a
few
exceptions,
but
for
the
most
part
it's
the
same
exact
CSS,
that
you
know
your
parents
and
your
parents,
parents.
A
B
B
That's
a
good
question.
I
think
somebody
asked
that
maybe
it's
the
same
person.
Somebody
asked
that
on
the
mobile
blazer
bindings
repo
there's
no
automatic
support
for
it
at
this
time,
but
as
long
as
your
build
system,
if
you
wire
up
the
right,
msbuild
things
to
hook
up
less
or
sass
or
whatever
CSS,
minification
or
processing,
you
want
and
hook
it
into
a
standard,
CS
proj
msbuild
file.
B
It
should
absolutely
just
work,
so
you
edit
your
your
sass
or
less
or
whatever
files
it'll
process
long
as
it
produces
the
CSS
file
in
the
end
and
that
that
generated
CSS
file
it
gets
embedded
as
a
resource
with
whatever
you
know,
file
name
or
folder
name.
So
you
know
as
long
as
you
produce,
ultimately
something
called
whether
Styles
dot,
CSS
or
whatever.
B
You
want
absolutely
should
work,
because
eventually
it
just
gets
embedded
as
a
resource
in
the
assembly,
so
how
it
gets
there
totally
up
to
you
and
what
you
want
to
use
so
kind
of.
If
you
can
get
it
to
work
in
an
asp.net
core
project,
let's
say
which
would
be
a
kind
of
the
most
natural
place
to
use
something
like
that.
I
haven't
tried
it,
but
I
cannot
think
of
any
reason
why
it
wouldn't
work,
because
it's
just
it's
just
msbuild
at
that
point
and
msbuild
certainly
has
the
power
yeah
yeah.
A
A
B
A
Last
question
is
like
CSS,
there's
a
huge
amount
of
like
new
features
and
things
coming
out.
All
the
time
and
stuff
I
use
like
websites
like
can
I
use
and
and
stuff
to
you
know
see
what's
supported
is,
is
this
kind
of
what
kind
of
like?
Is
there
support
for
grid?
And
you
know,
like
other
I
guess,
I
saw.
B
B
But
there's
a
terrific
set
of
documentation
here
on
the
salmon
forms
section
of
the
docs
website.
That
goes
into
also
certain.
There
are
custom
extensions
because
xamarin
forms
elements.
There
are
some
things
that
HTML
supports.
There's
an
orange
doesn't
have
but
they're
also
some
things
that
xamarin
forms
has
that
HTML
doesn't
have
so
everything
you
see
in
this
document
on
the
official
salmon
forms.
Css
section
should
work
as
described
here
for
sale
reforms,
but
will
also
work
on
mobile
blazer
bindings.
So.
A
B
Exactly
as
far
as
I
know,
there
is
not
currently
support
for
that.
If
again,
if
that's
something
where
there's
good
demand
for
that
and
I
could
see
why
there
might
be,
then
that's
certainly
something
we
could
look
at
I.
Don't
think,
there's
currently
support
for
isolation
of
CSS,
which
yeah
that
certainly
that
certainly
would
be
nice,
but
that's
one
of
those
things
where
people
want
it
and
it
bubbles
up
to
the
top.
Then
you
know
that's,
that's
often
health
features
get
done
sooner
rather
than
later,
or
you
know
if
at
all
and.
A
A
B
A
A
B
That's
why
he'll
probably
talk
about
like
cool
monkeys?
He
knows
all
about
monkeys
which
is
which
is
awesome
anyway.
Dotnet
Maui
is
the
dotnet
multi-platform,
application,
user
interface
I
think
that's
what
it
stands
for.
Doesn't
it
multi-platform
the
prize
stands
for
something
like
that
anyway,
so
it's
kind
of
a
you
can
think
of
it
as
a
successor
to
xamarin
form
so
for
building
cross-platform
UI
and
that's
plan
for
dotnet
6,
which
is
scheduled
for
next
year.
So
that's
you
know
a
year
away
is
both
very
far
and
it's
very
near
I.
B
Think
for
customers,
it's
like!
Oh,
we
have
to
wait
a
year
and
then
for
people
working
on
it's
like!
Oh
my
gosh.
We
only
have
a
year
so
there's
that,
and
so
we
want
to
work
on
using
experimental
mobile
blazer
bindings.
Well,
if
Donnie
Maui
is
also
for
building
mobile
applications,
then
we
want
experimental
mobile
blazer
bindings
to
have
a
story
for
dotnet
Maui
as
well.
So
that's
something
we've
experimented
with.
Don't
have
anything
to
show
just
yet,
but
rest
assured,
once
we
have
something
to
show
we'll
share
it
as
soon
as
possible.
B
Here
on
the
community
stand
up
and,
and
everybody
who
wants
to
know
about
it
will
know
about
it.
So
that's
one
because
again
a
blazer
is
a
tech,
that's
appropriate
for
just
about
any
kind
of
UI
and
we
want
to
make
sure
that
it's
represented
appropriately
with
Donette
Maui
and
then
the
thing
that
I'll
spend
the
rest
of
my
time
on
is
talking
about
blazer
hybrid
applications.
So
what
we
saw
so
far,
let
me
close.
B
It's
got
a
visual
studio
here
this.
We
have
not
this
we're
going
to
make
this
public
very
soon.
We
have
to
fine-tune
a
few
ones
and
zeros
in
the
code
and
we'll
get
this
out,
but
hybrid
application
is
one
where
you
have
a
mixture
of
true
native
UI,
like
you
might
have,
with
xamarin
forms
or
dotnet
Maui
or
WPF,
or
lots
of
different
systems
and
parts
of
your
application
are
hosted
inside
some
kind
of
webview
like
chromium
or
WebKit
that
contains
HTML
based
UI.
B
Now
we
know
you
can
use
blazer
to
build
HTML
web
apps
or
progressive
web
app.
So
we
know
you
can
use
blazer
to
build
native
web
apps
with
mobile
blazer
bindings,
but
what,
if
you
did
both
of
them
inside
the
same
application,
so
I
think
Steve
has
probably
shown
this
a
little
bit
before
or
Dan
Roth.
Other
folks
on
the
blazer
team
have
shown
this
so
I'll
show
it
for
folks
who
might
not
have
seen
it.
B
Let's
see
where
do
I
want
to
start,
let's,
let's
just
run
the
application,
so
it's
kind
of
like
a
default
template
experience.
Running
I've
got
my
Mac
sitting
next
to
me
so
that
the
iOS
this
is
so
cool
that
you
can
do.
This
I
can
run
and
debug
my
iOS
application
on
Windows
with
Visual
Studio
for
Windows,
but
it's
running
on
the
Mac
than
sitting
six
inches
away.
So
this
top
portion
of
the
application
here
it
says
hello,
world
zero
is
a
native
native
UI
built
using
mobile
blazer
bindings.
B
So
if
we
take
a
look
at
what
that
is,
we
see
here
main
dot
race
Romy's,
in
that
in
a
little
bit
yeah,
that's
a
little
bit
better
see
if
I
can
fit
this
all
on
the
screen.
So
we
have
here
hello,
world
and
a
counter
and
when
I
click
increment
counter
it
does
it
does
the
thing
that
you
expect
it
increments.
A
counter
I
think
everybody's
seen
this
in
literally
every
blazer
demo.
Ever
since
the
first
day
of
play,
is
there
hello
world
and
a
number,
but
what's
this
here
at
the
bottom?
B
Well,
I'll
give
a
hint
it's
it's
web
UI.
This
is.
This
is
HTML
faculty
even
says
it's,
my
hybrid
app
and
here
in
the
UI
definition,
you
see,
there's
a
blazer
webview,
that's
pointing
at
a
www
root
folder
and
it's
loading
this
other
blazer
component.
So
what
does
that
look
like?
Let's
start
navigating
to
this
counter?
Now
we
have
another
counter.
In
fact,
you
got
double
counter
action
here
and
as
I
increment,
this
native
one.
We
see
that
the
web-based
one
here
at
the
bottom
is
sharing
the
same
UI.
B
In
fact,
it
doesn't
matter
which
increment
button
I
click
on
they're,
both
affecting
the
same
state,
because
in
this
case
we're
getting
our
state
from
dependency
injection.
We
have
this
counter
state
object
that
is
shared
as
a
dotnet
object
between
the
blazer
code.
That's
operating
for
the
native
UI
up
top
and
sharing
down
to
the
web
based
blazer
down
at
the
bottom,
which
is
all
just
running
that
code.
This
is
not
there's
nothing
else
going
on
here.
So
what
is
that
web
portion
of
the
app
look
like
for
the
bottom?
B
Well,
if
you
kind
of
a
little
bit,
this
looks
exactly
like
a
web
based
blazer
application.
It's
going
to
dump
WT
root,
folder
with
some
static
files
and
hey,
look
John
your
favorite
folder,
the
CSS
folders,
and
this
is
using
exactly
the
same
type
of
CSS
that
you
would
use
in
a
web
app
because
it's
a
little
web
browser
window.
Essentially,
so
you
can
use
things
like
bootstrap
inside
there
and
that's
why
this
UI
looks
like
bootstrap
UI,
and
so
that's.
These
are
just
static
files.
B
I've
got
some
custom
CSS
here
that
adjacent
file,
I,
don't
know
I,
don't
think
you
really
need
a
favicon
right,
it's
there
and
then
here
you
have
some
some
razor
files-
and
this
is
now
HTML.
So
this
bottom
portion
here
so
this
menu
here
and
everything
below
it-
is
all
written
using
HTML.
So
this
is
a
real
issue,
no
because
this
is
a
web
view.
I
see
in
the
chat.
There's
some
questions
here.
It's
like
a
WK
webview
yeah.
B
So
this
is
I'll
talk
a
little
bit
more
about
that,
but
on
every
platform
that
this
runs
on
and
it
runs
on
a
lot
of
different
platforms.
It's
using
that
that
platform's
native
system,
so
on
WPF,
it's
using
edges
the
edge
edge
iam
webview
on
Android,
it's
using
androids
webview
on
Mac
and
iOS-
is
using
their
native
systems
as
well.
I
can
talk
more
about
that
and
let
me
know
if
I'm
missing
any
important
questions,
because
I'm
glancing
on
like
five
different
to.
B
B
So
you
see
you
now
see
the
totality
of
UI
source
code,
that's
representing
it
the
layout
and
things
like
that,
but
you're,
seeing
the
UI
source
code
for
both
of
these.
So
we
have
a
little
bit
of
HTML
with
some
native
elements
and
they're
completely
shared
and
yeah.
So
I
want
to
show
one
more
thing
and
then
I'll
probably
might
make
sense
to
then
go
through
a
few
questions.
Here,
that's
a
pretty
simple
application.
We
have
a
slightly
more
complicated
application
that
I'm
gonna
run
on
another
platform.
Where
is
it
start
a
project
right
there?
B
B
Next
month,
hopefully
early
next
month,
so
there's
a
little
bug
and
this
application
has
to
kind
of
close
and
open
that.
So
you
can
mention
this
a
little
email,
client
and
it
just
like
any
email
client.
You
have
a
list
of
folders,
then
you
have
a
list
of
emails
and
you
can
click
on
an
email
and
then
see
the
details
of
the
email
and
you
know,
go
back
click,
click
on
another
email
and
so
forth.
So
it's
exactly
what
you'd
expect
from
some
kind
of
email
based
application.
B
Yeah
I
think
this
is
actually
based
on
Hayes,
email,
client,
I,
think
it
looks
exactly
the
same.
Maybe
maybe
not
quite
and
I'm
not
signed
up
for
it,
so
I
don't
actually
yeah,
but
so
how
is
this
built?
Well,
I'll
give
a
little
bit
of
a
hint,
because
one
thing
that
you
can
kind
of
do
sometimes
to
see.
If
something
is
web-based
UI
is
you
can
try
to
kind
of
simply
select.
A
B
Text,
it's
like,
okay,
that's
probably
not
pure
native
UI,
because
I
can
select
text
on
there
and
then
maybe
here
I
can
select
some
text,
but
then
one
other
test
you
can
do
is
hard
to
see
what
I'm
doing
but
I
can't
select
across
them.
Why
is
that?
Well,
we
actually
have
here
is
native
mobile
blazer
bindings
based
on
standard
forms,
UI
for
kind
of
the
frame
and
the
navigation,
so,
for
example,
this
menu
button
here
and
this
navigation.
B
This
is
native
navigation
using
xamarin
forms,
and
then
we
have
one
hybrid
portion
over
here
for
this
menu
on
the
left
and
then
a
second
hybrid
web
view
over
here
for
hosting
web
base
place
here.
So
when
I
click
on
an
email,
this
is
one
you
can.
It
was
one
control.
Then
we
have
one
here
for
the
menu
for
other
controls.
You
can
embed
multiple
ones
of
these
as
well
and
they
can
all
share
state.
B
It's
all
net
code
that
all
kind
of
talks
to
each
other
and
using
all
the
same
blades
or
features
you
always
want.
So
you
have
your
at
and
jects
to
share
the
counter
state
object.
That
has
keeps
track
of
the
current
count
and
wherever
you
want
to
use
that
from
whether
using
it
on
your
native
UI
or
your
web-based,
UI
works
all
together.
B
Actually,
one
last
thing
I
want
to
show
actually
back
to
and
close
back
to
this
one.
So
this
is
the
kind
of
default
project
time.
Let's
make
sure
that
that
still
compiles
okay
yeah
this
one
here
shows
how
I
can
fetch
some
data.
It's
actually
not
going
to
a
web
service.
It's
just
local
data,
but
I
want
to
show
a
really
neat
thing.
So
this
is
HTML
based
UI
here
at
the
bottom.
Let's
go.
Take
a
look
at
that
UI.
So
this
is
here
shared.
This
is
in
fetch
data.
B
A
B
B
B
Fingerprint
the
login
yes
yeah,
exactly
exactly
so
now,
when
I
go
fetch
data,
it
should
show
locations.
Okay!
Well,
that's
that's
this
neat,
but
that's
not
particularly
interesting.
What
I
can
show
here
now
is:
let's
say
we
want
to
integrate
with
some
native
functionality.
So
I
can
have
a
button
here.
That
says
no
sorry
not
up
there.
B
It's
can
be
a
button
and
this
is
an
HTML
button.
It's
a
regular
good
old
HTML
button.
What's
gonna
show
the
location,
but
in
the
on
click,
I'm
gonna
do
is
call
go
to
forecast
dot,
location,
I
got
that
right
and
then
I'm
gonna
cheat
and
I
already
wrote
the
code.
I
don't
know,
I
think
it
was
like
2:00
a.m.
B
A
B
A
B
B
B
B
Yeah
I
I
can't
hear
on
my
side.
I
I
take
the
blame
for
Douglas
I
apologize.
We
tried
fiddling
with
all
two
microphones
that
I
tried
to
a
different
microphone
I
apologize.
We
could
not
figure
out.
What's
making
this
high
pitch.
I
can't
hear
it
so
I
have
a
hard
time
debugging
it
so
I
apologize
for
that.
So
now,
when
I
click
on
Boston,
hey
yeah,
so
this
is
from
the
web
part
of
my
UI.
B
A
B
B
Closed
a
while
ago,
didn't
it
yeah,
yeah,
I,
guess
I
went
long
enough
ago.
It
was
still
open,
oops
I,
just
oh
I,
assumed
something
anyway.
So
that's
kind
of
showing
al
just
a
little
taste
of
what
a
hybrid
application
can
do.
You
can
go.
You
can
use
CSS
on
both
sides.
You
can
use
HTML
for
parts
where
you
want
to
use
HTML.
You
can
have
some
native
UI
wrapping
around
that
you
have
the
full
power
of
xamarin
forms
to
use
things
like
xamarin
essentials
and
other
xamarin
forms
components.
B
It's
it's.
This
just
beautiful
combination
of
the
best
of
all
the
worlds
where
you
get
to
use
all
the
tech
in
a
very
rich
and
powerful
way,
and
because
it's
blazer
on
both
sides
of
the
kind
of
the
frame.
If
you
will
you
get
to
use
your
same
skills
and
it's
all
net
coats,
you
get
to
use
everything
that
you
can
use
from
net.
You
can
use
from
either
part
of
your
application.
It's
it's
it's!
What
you
built
the
UI
part
of
your
application
in
has
no
bearing
on
what
powerful
functionality
is
available
to
you.
B
A
B
A
It
so
that
shows
kind
of
the
the
some
of
the
value
proposition
and
some
of
the
developer,
like
advantage
of
their
using
HTML
I'm,
also
able
to
use
like
if
I've
got
existing
CSS
or
HTML
from
other
things,
but
I'm
able
to
then
Holland
a
native
api's.
That
is
slick.
Oh
oh,
okay,
let
me
see
there's
some
questions
coming
in
here.
So
one
question
was
about.
A
One
was
saying
they
thought:
webview
was
bad
practice,
but
I
guess
I
mean
it's.
It
all
depends
right
on
what
what
you're
trying
to
build
and
it's
a
it's
a
trade-off.
I,
don't
so
I
wouldn't
expect
that
there
would
really
necessarily
be
any
kind
of
performance
impact,
but
I
guess
it
depends
on
what
you're
building
yeah.
B
Oh
there's
there's
a
few
things
that
we're
trying
to
achieve
here.
One
is
just
for
ourselves
internally
within
Microsoft.
It
kind
of
evaluates
the
prospects
of
this,
but
then
by
showing
it
here
on
the
community
stand
up
with
everybody,
who's
watching
right
now
or
everybody's
watching
in
the
future
and
kind
of
starting
the
discussion
around
this.
We
think
it's
very
interesting.
We've
heard
from
many
customers
that
this
is
what
they
want
and
when
we
get
these
bits
public
in
July,
hopefully
early
July
people
actually
play
around
with
it
and
really
get
a
feel
for
it.
B
B
Did
almost
the
whole
will
work
for
this
I
did
the
Android
port
of
this
Oh
Steve
Steve
did
the
rest
of
it
so
credit
to
him
for
all
that
and
getting
into
the
hands
of
customers
is
the
most
important
thing
and
as
far
as
to
the
specific
question,
is
webview
a
good
practice
or
not
a
good
practice
or
does
have
performance
problems.
Well,
I
could
tell
you
that
least
running
on
this
iOS
simulator,
it's
buttery
smooth.
It
is
it
you
you
couldn't
you
couldn't
tell
the
difference.
B
I
am
having
some
weird
problem
with
Android
performance.
I
think
I
suspect
why
I
ran
the
profiler.
It
did
not
give
me
any
hints,
but
I
think
I
might
know
why
that's
happening.
It's
not
specific
to
webview,
though
it's
some
other
problem
on
WPF
that
we
saw
that
that
kind
of
mail
program
that
I
showed
that's
on.
Tell
you
PF,
buttery,
smooth.
It's
you
you,
you
I,
don't
think
you
could
tell
the
difference
between
it.
Now
these
are
very
small
applications.
So
a
lot.
A
A
B
Oh
you'll
have
$500
it's
slow,
it
wouldn't
really
make
any
sense,
but
yeah
from
my
experience.
So
far,
it's
not
too
bad.
I
have
heard
of
some
growing
pains
and
some
other
platforms
that
try
to
do
similar
things,
and
my
hope
is
that
these
things,
whatever
problems
we
find
my
hope
is
that
we
can
just
solve
them
so
far.
B
So
sharing
code
between
the
two
different
parts
within
my
application,
it's
completely
trivial!
That's
what
this
simple
are
not
as
well,
yes,
yeah!
This
one
does
was
a
counter
that
I
showed
all
right.
It
can
be
any
service
at
I
mean
at
that
point.
It's
just
dotnet
code
calling
other
net
code.
That's
that's!
That's
the
story
there.
B
The
web
blazer
portion
of
your
hybrid
application
for
mobile
I
think
it
would
just
work.
I
haven't
tried
that
I
can't
think
why
it
wouldn't
work.
Of
course,
there's
a
lot
of
things.
I
can't
think
of
this.
That
effects
reality.
Unfortunately,
but
in
theory
you
should
be
able
to
share
way
more
than
ever
before.
What
about
in
terms
of.
A
Between
and
I
understand,
a
lot
of
this
is
covered
by
like
dotnet
Maui,
but
like
or
code,
that's
specific
to
different
iOS
or
whatever,
oh
I.
Guess
what
I'm
wondering
is
the?
How
do
you
set
up
your
solution
and
how
do
you?
How
much
because
there
was
a
question
on
that
to
you
know
like
how
good
things
be
included,
and
how
do
you
break
apart?
What
needs
to
be
a
separate
project
and
what
doesn't
yeah
you've.
B
Ever
done
any
Ameren
forms
projects,
including
mobile
blazer
bindings,
which
is
based
on
the
same
tech.
It
has
that
exact
same
feel.
So
let
me
show
on
this
application
here.
What
that
looks
like
so
typical
application
will
have
one
shared
UI
project,
so
that'll
be
the
one
that
kind
of
without
a
suffix
my
application,
and
then
you
have
all
these
different
platform
specific
ones.
So
here
we
have
an.
B
Ios
Mac
bus
and
the
windows,
these
four
projects
are
very,
very,
very
small
right
now,
because
they
for
the
most
part,
all
they
do
is
say,
load
the
shared
UI
and
then
that
does
all
the
salmon
forms
stuff
and
it
loads.
The
webview
for
doing
the
web
stuff
like
I,
can
show
it
here
like
these
are
folders
are
mostly
just
empty,
so
it
references
things
like
that
asset
kind
of
there's
no
assets
in
here,
but
it
I'll
see
when
it
comes
time
to
publishing
it
out
to
an
app
store.
B
You'll
want
the
icons
and
setting
up
the
permissions
and
things
like
that.
Those
are
all
device
specific
and
then
there's
only
two
c-sharp
files
here
that
are
very,
very
short
and
they're.
Just
template
code
at
this
point
anyway.
So
the
app
delegate
that
loads
up
the
main
page
of
that
of
the
application
and
then
main
dot
CS.
That
just
has
this
kind
of
one
new
line.
That's
a
little
bit
of
a
hack
and
that's
it
there's
two
lines
of
code
here,
neither
of
which
is
interesting.
A
B
Might
end
up
with
more
code
in
here,
like
so,
let's
say
on
iOS,
you
want
to
use
face,
ID
or
Apple
pay,
or
some
other,
let's
say
for
iOS
14.
If
you
want
to
integrate
with
any
of
the
new
iOS
14
or
whatever,
whatever
that
thing
is
they
announced
this
week,
yeah
that
would
be
iOS
specific
code
and
that
would
go
in
here
and
then,
if
there's
some
Android
specific
thing,
you
want
to
use
yeah
that
that
would
go
in
there
or
Windows
Mac
OS,
but
that's
that's
the
stuff.
B
That
would
naturally
be
separate
anyway,
and
then
everything
else
goes
in
here,
especially
with
the
web
UI,
where
the
web
UI
is
really
not
going
to
vary
between
the
platforms.
That's
that's
kind
of
a
whole
point
in
the
web
UI,
but
even
the
rest
of
your
UI,
because
you're
using
the
same
informs
components.
B
A
B
B
A
B
Elements
well,
yeah
it'll
apply
to
all
the
HTML
and
anchor
elements
in
your
in
the
native
part
of
your
application
as
well,
except
there
aren't
any
because
the
native
parts
are,
you
don't
have
any
elements
called
HTML
or
a
or
app.
Now
these
select
these
selectors
that
go
based
off
of
class
name
like
BTN
primary.
If
you,
you
applies
this
same
class
in
your
HTML
and
in
the
native
party
application
yeah
you'll
get.
B
A
B
We're
rzz
yeah
yeah,
but
anyway
these
things
will
work.
There
are
some
things
that
might,
for
example,
just
like
Fleck
stuff
I,
don't
know
if
that
works
aside
from
this
element
doesn't
exist
anyway,
but
I'll
see
some
things
won't
work,
but
you
can
share
them,
but
as
I'm
saying
there
are
cases
where
might
not
make
as
much
sense
to
do
it
because
they're
there
they
are
different.
B
B
Yes,
so
in
this
in
this
example,
here
it's
being
embedded
using
this
blazer
webview
and
then
here's
that
the
web
component
to
be
embedded
being
embedded
inside
that.
But
this
is
all
blazer
and
side
of
blazer.
This
other
sample
app
here
and
unless
Steve
objects
will
have
this
same
sample
here.
There's
the
outer
part
of
the
application
is
sam'l,
and
then
the
inner
part
of
the
application
is
razor,
and
so
inside
these
pages
here
it's
using
that
same
type
of
blazer
webview
component.
B
But
this
is
the
the
sam'l
version
of
it
and
then
the
mobile
blazer
binding
one
wraps
this
and
make
enables
it
to
be
used
in
Blazer.
And
so
yes,
you
could
do
this
as
well.
You
could
have
a
sam'l
and
you
know:
there's
regular
xamarin
forms
sam'l,
so
you
have
the
the
code
behind
here.
You
can
have
your
shared
app
states
and
things
like
that
and
embed
the
blazer
web
portion
of
the
application
inside
sam'l
or
inside
more
blazer,
which
I
think
is
bananas.
Yeah.
A
B
B
So
the
the
simplest
way
I
can
describe
that
is
you
would
do
it
in
the
natural
way
you
would
do
it,
regardless
of
what
you
were
doing
with
blazer.
So
if
you
forget
about
the
fact
that
it's
this
weird
hybrid
thing,
okay,
how
would
you
do
it
if
it
was
just
all
native
or
all
all
mobile,
blazer,
bindings
native
or
all
web-based
native
well
in
blazer?
So
let
me,
let
me
run
the
application
again.
B
Just
everybody
kinda
has
a
feel
for
what
what
we're
talking
about
here
so
sack
funnel
this
weird
bug
with
that
may
doesn't
show
up
so
I
can't
actually
click
on
any
of
those,
but
when
I
click
on
an
email,
it's
in
theory,
if
I
clicked
on
this,
it
should
show
a
different
folder.
It's
not
actually
wired
up
to
anything
so.
B
What
would
that
actually
do?
Well?
I
would
well,
let's
I,
don't
think
we'll
actually
be
able
to
do
it,
because
this
this
app
is
a
little
too
faked
up
to
actually
do
we
had
too
much
meaningful
stuff,
but
the
in
general
I
would
go
because
this
is
this.
Is
web
UI
with
sauce
kinda,
you
can
see
it's
HTML
I
can
select
the
text.
So
that's
the
that's
the
folder
list,
so
I
were
turn
all
of
these
into
buttons
right.
B
A
B
Was
to
go
to
you
doing,
go
to?
Oh,
that's!
Okay,
I
didn't
write
that
method.
No,
so
that's
why
it's
not
working
and
then
here
I'd
have
at
code.
You
note:
have
a
private
async
task
go
to
string,
folder,
name
oops,
folder
name,
and
so
it
would
be.
You
know
this
is
kind
of
the.
This
is
the
start,
and
so
I'll
just
try
to
rerun
that
just
to
see
it,
they
need
to
make
a
thing
where
I
feel
you
rerun
a
Windows
app.
It
kills
it
first.
Otherwise,.
A
B
A
B
Okay,
yeah,
so
here
actually
very
theoretically,
we
can
do
this.
So
my
app
state,
my
global
app
state
object:
it's
not
global
per
se,
but
it's
going
through
a
dependency
injection,
it's
available
to
all
pages
of
UI,
and
this
has
a
current
folder
string.
And
so
what
I
would
do
here
is
I
would
say
app
state
current
folder
equals
folder
name,
and
actually
this
is
not
actually
a
sync.
So
we'll
just
make
that
like
that.
So
now
it's
setting-
oh
it's
read-only,
okay,
well,
I-
can
fix
that.
B
Okay,
so
now
we
can
set
that
and
okay
at
this
point,
I,
don't
think
I'm
going
to
write
too
much
more
of.
But
what
this
setter
would
probably
need
to
do
is
raise.
Some
state
has
changed
or
equivalent
type
thing,
or
maybe
using
cascading
values
there
and
one
way
or
another
transmit
that
message
using
standard,
blazer
stuff,
there's
nothing
to
do
with
web
or
native
or
anything.
B
B
B
B
B
And
the
funny
thing
is
cuz
I'll
be
on
I,
had
to
kind
of
wrap
my
head
around
this
as
well.
The
first
time
you
see
this.
It's
like
you,
don't
even
know
what
you're
looking
at
and
what
I
found
is
don't
think
of
it
as
two
different
applications.
It's
not
because
it's
not!
It
is
one
application.
It's
just
like
mixing,
zamel
and
blazer,
or
blazer
native
with
blazer
web.
All
these
different
things.
It's
it's
all
running
the
same
net
code
in
the
same
process
on
the
device.
It's
it's
one
application
its
share
state.
B
A
A
B
B
Wherever
it
was
that
I
did
weren't,
where
is
it?
Where
is
it?
Where
is
it
in
fetch
data,
where
from
HTML
I'm
calling
a
c-sharp
method,
which
is
that's-
that's
not
unusual
in
the
blazer
world,
but
it's
calling
it
to
xamarin
essentials
to
open
a
map
yeah
so
yeah,
oh,
but
of
course
I
can
do
that
before
I
did
I
was
like
wait,
but
will
this
well?
This
is
gonna
work.
Cuz
I'm,
like
in
a
web
page
yeah.
A
B
A
B
B
Absolutely
as
long
as
you're,
following
like
the
usual
dotnet
suspects
on
twitter
or
github,
or
the
blog
and
things
like
that,
you'd
have
to
be
hiding
under
a
rock
its
kind
of
not
not
hear
about
when
we
when
we
share
this
and
hopefully
in
a
couple
of
weeks,
we
have
too
few
bugs
if
to
work
through
get
some
Doc's
written
up,
get
the
project
templates
set
up,
but
the
code
is
mostly
already
there
and
you'll
see
it
checked
into
the
repo.
Hopefully
even
this
week.
A
Okay,
well
we're
at
time.
For
the
week
we
have
tomorrow,
we
have
the
entity
framework,
stand
up
they're
moving
to
every
other
week
now,
which
is
which
is
pretty
crazy,
and
then
we
also
have
coming
up
on
Thursday.
We
have
the
visual
studio.net
community
stand
up
so
we're
really.
These
community
stand-ups
are
happening.
You
know
three
days
this
week,
so
that's
exciting
so
and
thanks
a
bunch
alone.