►
From YouTube: Windows Desktop: .NET Standup - August 22nd 2019 - App Center for Desktop apps, XAML Tools & WinUI
Description
Join members from the .NET teams for our community standup covering great community contributions for WinForms, WPF, and UWP.
Suggest an idea for a standup: http://aka.ms/dotnet-standup-suggestion
A
All
right-
and
we
are
live-
welcome
folks,
watching
out
there.
My
name
is
Dimitri
Lila
and
welcome
to
the
Dartmouth
desktop
community
stand
up,
I'm
really
excited
to
have
a
buncha
guests.
Here
we
have
a
lot
of
great
demos
on
topics
today.
We're
gonna
be
talking
to
the
App
Center
team.
That's
here
with
me
in
the
studio
and
the
winuae
team,
with
Stephen
on
on
the
camera
here
in
his
office,
in
a
famous
building
one
one,
foreign
campus,
where
the
developer
platform
for
Windows
is
actually
worked
on.
So
that's
pretty
cool.
A
B
C
A
Awesome
well,
thank
you
guys
for
being
here
and
again
just
my
name
is
Dmitry
Leland
I'm,
the
p.m.
on
zamel
tools
for
the
BPF
and
uwp
developers
and
I
work
really
closely
with
Stephens
team
on
the
windows
side,
I
work
with
App,
Center
and
I
also
work
with,
basically
any
anything,
that's
required
to
get
your
app.
It's
you
know
constructed
published,
build.
You
know
the
design
and
everything.
That's
the
tools
are
in
my
team
and
then
the
platforms
and
the
services
support
that
I
was
going
to
have
some
demos
today.
A
B
Thanks,
let
me
share
real
quick,
let's
see
so
to
start
out,
let's
get
rid
of
this
guy
to
start
out.
I
wanted
to
first
show
you
the
windows,
UI
Twitter,
real,
quick.
This
is
where
we
have
a
whole
bunch
of
information
about
Windows
UI
for
folks
that
don't
know
when
UI
is
our
as
our
new
get
packaged
and
set
of
documentation
instead
of
a
set
of
code,
that's
all
open
source
and
it's
about
creating
UI
for
Windows,
10
and
so
to
start
it
off.
B
You
know
if
you
want
to
get
more
information
about
when
UI
we're
on
twitter,
at
when
windows
UI.
I
also
wanted
to
share
the
github
repo
about
when
UI.
So,
if
you
go
to
a
KMS
slash
when
UI
that'll
take
you
to
the
Microsoft
UI
sam'l
github
repo-
and
this
is
where
you
can
see
all
of
our
new
code
for
things
like
our
new
controls
or
styles
or
animations,
and
so
that's
that's.
The
Microsoft
UI
Zemel
github,
repo
yeah.
A
There
I
guess
one
of
the
important
things
to
remind
folks
watching
is
that
when
you
y2
is
already
up
there
in
the
working
shape
right,
you're,
actually
working
on
when
UI
to
in
the
library,
Po
and
you're
publishing
you
get
packages
all
that
this
is
the
way
to
get
those
bug,
fixes
and
new
controls
that
are
in
that
pack
and
then
eventually,
when
you
I
will
expand,
but
it's
basically.
This
is
the
place
that
will
evolve
over
time.
Yep.
B
That's
exactly
right,
that's
exactly
right
and
for
folks
that
are
super
excited
about
when
UI
3
or
even
you
know,
when
you
I,
you
can
always
provide
input
at
this.
When
UI
3,
developer
experience
and
tooling
input,
you
can
also
file
new
issues
for
feature
requests.
It's
it's
a
really
great
place
to
like
this
is
this
is
where
our
team
puts
all
of
our
code
and
all
of
our
new
features,
so
that
that's
a
that's
a
great
resource.
But
let's
say
that
you
want
to
see
the
the
controls
and
the
the
stuff
in
action.
B
B
So
you
know
we
got
media,
we
got
scrolling,
we
got
a
whole
bunch
of
different
categories
for
different
controls,
and
the
really
great
thing
about
these
controls
is
that
you
can
use
them
in
uwp
apps,
but
you
can
also
use
them
in
zamel
islands
to
bring
these
sorts
of
modern
UI
elements
into
your
existing
WPF
or
windows
forms
or
win32
applications.
So
this
is
a
we.
A
A
You
see,
post-loss
app,
take
advantage
of
when
you
I'd
that
episode
and
blogs
by
McGill
and
other
things
can
help
you
get
started,
and
my
team
is
actually
working
on
tooling
41.0
GA
that
we
have
late
coming
later
this
year
right
now,
zamel
islands
unfortunately
has
some
manual
steps
to
get
through
in
order
to
implement
them,
and
my
team
will
make
sure
that
there's
no
manual
steps,
hopefully
by
end
of
the
year
here,
so
we
are
reactively
working
at
it
when
questions.
Even
where
can
folks
get
the
thing
you're
showing
how
do
yeah.
B
A
B
So
I
wanted
to
share
with
you
our
hot
off
the
presses,
tab,
view,
control
and
so
to
have.
You
is
a
way
to
it's:
it's
a
control
that
allows
you
to
have
multiple
tabs
of
content,
and
so
you
can
imagine
that
you
have.
You
know
several
pages
several
documents
you
want
to
be
able
to
add
new
ones
or
even
close
them.
So
tab
view
is
a
long
requested
feature
for
you
WP,
and
we're
really
excited
to
have
the
opportunity
to
to
share
it
with
you.
B
So
the
tab
view
pay
inside
here
also
has
a
whole
bunch
of
code.
I
know
it
might
look
like
a
lot.
Some
samples
are
a
little
bit
more
complicated
than
others,
but
this
sample
shows
how
you
can
wire
up
keyboard
accelerators,
like
ctrl,
T
and
ctrl
W
to
open
and
close
tabs.
We
also
show
how
you
can
create
experiences.
B
Some
of
you
might
be
familiar
with
the
new
Windows
terminal
that
the
Microsoft
is
producing
super
excited
and
there's
a
small
sample,
say
of
showing
how
you
can
create
full-color,
bitmap
icons
inside
your
tab
view
similar
to
what
the
Windows
terminal
does,
or
you
know,
setting
the
accent,
color
background
on
the
tab
strip,
and
so
the
tab
view
control.
We're
really
excited
about
and
part
of
the
reason
we're
really
excited
about.
It
is
because
the
first
customer
is
actually
the
the
Windows
terminal.
B
B
A
B
A
A
Is
it's
going
to
keep
growing
and
at
some
point
you're
literally
gonna,
you
know
add,
and
you
get
package
to
your
app
and
get
all
the
controls
from
you
get
as
opposed
to
some
of
them
being
in
platform
and
some
of
them
being
in
win
UI
right
now,
the
story's
a
bit
split,
but
that's
something
that
they
know.
Your
team
is
working
very
hard
and
very.
A
Literally
spending
day
of
meetings
in
1,
1
4
as
part
of
that
conversation-
and
we
really
want
to
make
sure
tooling-
is
gonna
work
really
great
all
right.
So
thank
you
very
much
and
there
are
some
questions
around
the
uwp
and
Zemel
islands
future
in
the
chats.
We
really
don't
have
anybody
from
zamel
Islands
right
now,
as
part
of
this
conversation,
so
I
would
say:
take
a
look
at
the
previous
livestream,
Moshe
and
I.
Think
a
lot
of
the
questions
are
answer
there
in
terms
of
uwp
and
life
support.
That's
just
not
our
view.
A
I
know,
there's
been
some
talk
about
that.
We
we
have
a
lot
of
things
that
we're
working
on
for
you
WP
and
the
platform
in
general.
So
if
you
look
at
the
control
the
tab,
control
I
mean
this
is
for
e
WP.
As
you
know,
as
much
as
it
is,
for
example,
islands
for
win32
applications,
so
we
definitely
are
continuing
to
invest.
Then
you
know
we
have.
Unfortunately,
nobody
from
several
islands
or
leadership
here
to
talk
in
detail,
but
I
just
wanted
to
kind
of
address
that
a
little
bit
I
think.
B
A
And
then
you're
doing
it
in
open.
So,
as
as
things
evolve,
you
can
see
more
and
more,
especially
if
folks
take
a
look
at
the
Winnie
UI
3
specification.
That's
up
on
that
github
repo,
the
future
plans,
the
roadmap,
I
guess,
is
the
right
word.
I'm
looking
for
the
roadmap
talks
about,
like
all
the
things
we're
going
to
do,
to
make
uwp
better,
bringing
out
input,
sample,
composition,
controls,
putting
them
up
and
you
get
making
making
it
much
easier
for
the
team.
A
You
want
to
take
advantage
of
we're
also,
you
know
really
hard
hard
at
work
and
trying
to
make
these
things
as
compatible
as
possible.
So
I
think
in
the
past,
which
version
of
Windows
customers
were
on
was
really
impactful.
You
know
in
the
current
stack
of
things
and
that's
something
we're
trying
to
improve
we're,
trying
to
make
it
easier
for
developers
to
build
an
app
and
know
that
this
there's
a
wider
range
of
OSS
and
Windows
10
landscape
that
they
can
target.
So
all
of
that
is
things
we
talked
about
in
the
last
livestream.
A
So
definitely
take
a
look.
It's
up
on
the
dotnet
Foundation
YouTube
or
on
Channel
Nine's,
but
not
community,
stand
up
channel
and
you
can
find
it
all
there
all
right,
Steven!
Thank
you.
So
much
for
joining
us
hang
out
or
drove
off
whatever
makes
it
the
easier,
and
we
hope
to
have
you
on
again
as
more
control.
Stuff
changes
all.
A
C
Absolutely
so
for
those
of
you
who
aren't
familiar
with
App
Center,
yet
we
are
a
integrated
developer
solution.
We
try
and
integrate
a
bunch
of
different
tools
that
you
might
need
right
after
you.
You
know
check
in
your
code
so
that
you
can
really
deliver
the
best
app
for
your
users.
So
if
you
look
at
this
page,
this
is
the
app
center.
C
Ms
homepage,
where
you
can
kind
of
see
what
we
offer
today
continuously
built
us
release
and
monitor
for
apps
of
various
platforms,
and
so
today,
Matt
and
I
will
be
talking
about
our
support
for
WPF
and
WinForms
apps,
which
we
released
about
a
few
weeks
ago
now.
So
it's
really
exciting,
we'll
be
demoing
three
services,
which
is
distribution,
analytics
and
Diagnostics.
If.
A
And
there's
some
history
here
because
hockey
app,
which
kind
of
started
to
have
Center
back
in
and
they
had
some
support
and
we
had
some
customers
right
using
some
desktop
SDKs,
I
guess
with
technology,
just
absent
er
needed
to
catch
up,
as
we
were
think
bringing
things
over
and
now
I
have
Center
lights
of
all
the
previews.
For
that
today,
yeah.
C
A
A
A
A
D
Our
primary
goal
at
this
point
for
sure
we
are
also
targeting
uwp,
hopefully
in
the
next
month,
will
come
out
and
be
added
to
the
set
of
three
things
and
I
might
get
in
trouble
for
holding
ourselves
accountable
to
this,
but
we're
hoping
to
have
the
support
and
when
we
show
the
demo
I
think
this
will
make
sense.
Support
for
net
core
3
at
the
council
level
levels
will
be
cross-platform,
not
just
the
WPF
win
for
maps.
D
C
So
today,
I'll
be
showing
what
you
can
do
in
App
Center
with
their
three
services
that
we
support,
so
that's
distribution,
diagnostics
and
analytics,
and
then
Matt
will
actually
go
through
all
of
this
stuff
and
maybe
like
under
five
minutes
or
so
and
show
everyone
how
you
can
actually
get
this
set
up
and
running
so
right
here,
you'll
see
kind
of
the
instructions
just
how
to
get
started.
How
to
integrate
the
new
kit
packages
once
you've
done
that
these
are
the
services
that
you
can
use
a
little
bit
slow.
C
So
distribution
is
a
service
that
allows
you
to
easily
release
your
app
to
your
end-users,
so
whether
these
are
untested
like
beta
testers
or
your
primary
end-users.
We
allow
you
to
make
these
release
so
that
your
users
can
easily
install
your
app
and
you
can
easily
manage
which
version
which
groups
are
currently
using
and
so,
for
example.
This
is
the
distribution
groups
page.
So,
as
I
mentioned,
you
can
create
your
distribution
groups
here
and
just
invite
users
via
email,
so
you
can
easily
manage.
Who
is
actually
getting
your
application?
C
D
Is
kind
of
a
corollary
to
the
old
passer
on
the
thumb
drive
to
get
an
app
or
though
the
one-click
deployment
share
and
it's
the
same
general
idea
right,
you're
just
getting
the
app
out
and
about
but
regulating
who
it
can
go
to
when
you
can
see
it
having
control
over
upgrading
versions
and
what
wind
things
you
pushed
out
is
is
I
think
a
whole
different
ballgame
than
a
lot
of
the
tools
that
may
be
available
right,
cool
yeah.
So.
C
This
is
the
releases
page,
so
you
can
see
which
releases
you've
made
to
whom,
how
many
downloads
and
things
like
that,
the
next
service
we
have
is
Diagnostics.
So
once
you
integrate
our
SDK,
you
will
be
able
to
see
when
your
apps
are
crushing.
If
you
want,
you
can
catch
some
handled
errors,
and
this
is
a
really
great
way
just
to
understand.
You
know
what
went
wrong
and
why
you
know
once
your
app
is
out
in
the
wild.
You
definitely
want
to
make
sure
it's
not
crashing.
A
C
Hopefully
not
too
many
crash
reports,
yes,
so,
for
example,
if
I
click
into
the
crashes
tab,
I
can
see
the
number
of
crashes
how
many
users
are
affected
if
I,
actually
click
into
one
of
these
crash
groups,
I
can
see
a
little
bit
more
details
and
the
stacktrace
I
can
click
on
the
reports,
tab
and
actually
look
at
the
individual
reports
and
for
some
more
like
customizable
functionalities.
You
can,
you
know,
track
events
that
occurred
before
a
crash.
C
D
An
from
a
developer
point
of
view,
right
like
this
is,
if
you
say
you
write
a
desktop
app
and
you
strip
to
tens
of
thousands
of
people,
and
you
don't
have
access
to
the
logs
in
those
machine
join
em
exit
that
data
right.
This
is
analogous
with
log
aggregation,
but
it's
really
a
much
richer
set
right.
We're
taking
the
data,
we're
processing
it
for
say
u,
WP
apps
were
converting
that
into
from
from
binary
from
dotnet
native
to
human
readable.
D
You
know
text
same
for
like
Apple
and
Android
things
like
that,
and
then
we
can
group
those
we
can
identify
devices
and
types
and
give
you
that
metrics
and
analytics
that
you
wouldn't
really
be
able
to
pull
out
of
a
set
of
logs
and
so
I
know.
For
me,
when
I
joined
App
Center
about
two
years
ago
right,
starting
to
think
about
my
crash
data,
and
my
my
Diagnostics
data
in
this
rich
set
really
makes
it
hard
to
go.
Look
at
logs
right.
It
just
really.
D
Happened:
I
want
it
to
be
augmented,
I
want
it
to
be
detailed
and
and
enough
that
I
can
go
through
it.
Actually,
it's
much
more
analogous
to
looking
for
me
to
looking
at
a
crash
and
inspecting
it
in
visual
studio
than
it
is
looking
at
logs.
It's
kind
of
what
we're
hoping
to
bring
to
the
table
for
people
here
that
might
not
be
familiar
with
this
yeah.
A
It's
very
cool
I
think
anything
we
can
do
to
just
make
things
glanceable
and
more
accessible
to
a
wider
range
of
developers
is
for
the
awesome
and
bringing
the
support
to
that
net
framework
and
done
with
core.
Just
gets
me
really
excited
just
makes
so
many
more
developers
be
able
to
use
this
great
product.
We've
like
I've,
been
working
with
the
apps
interesting
for
a
while.
Now
so
I
know
the
great
product
you
build,
but
I
think
the
more
platforms
we
bring
and
board
the
more
more
people
can
actually
use
this
as
excited
yeah.
D
It's
it's
I
mean
I,
say
it
I'm,
slightly
biased,
I
swear
like,
but
but
again
it's
developer,
who
was
outside
Microsoft
doing
development
for
a
number
of
years
like
this.
This
is
a
really
cool,
especially
in
this
world.
Where
so
many
apps
are
not
just
on
your
server
right
or
you
know,
running
co-located.
It
really
is
a
whole
different
ballgame
and
it's
pretty
cool
to
be
a
part
of
it.
Yeah.
C
Last
service
I
want
to
show
is
our
analytic
service.
It's
all
the
data
you're
seeing
here
is
just
out
of
the
box,
so
once
you
integrate
our
SDK
you'll
start
seeing
this
data
flow
in
number
of
active
users.
This
really
gives
you
a
better
idea
of
like
who's
using
your
app
and
how
they're
using
it
so
that
you
can
really
just
understand
how
you
want
to
build
your
app
and
and
really
deliver
the
best
user
experience
there.
If
you
would
like
to
have
some
more
customized
ability,
you
can
also
attach
these
custom
events.
C
A
Adding
telemetry
to
a
real
world
app
in
a
lot
of
cases
is
really
the
only
way
to
know
if
that
you
know
decisions
you've
made
and
some
update
actually
being
utilized
by
customers.
You
know
crash
data,
can
only
give
you
so
much
information
right.
This
custom
like
implement,
implement
the
flow
around
your
app
that
you
want
to
track
and
then
be
able
to
use
absent
if
you
go
and
report
against
that
it
just
makes
it
so
much
easier.
A
There
are
some
questions
coming
in
in
the
chat,
so
one
of
the
questions
is
around
application
insights
and
how
this
you
know,
compares
to
application,
insights
or
there's
going
to
be
an
emerging
like.
Is
there
any
plans
to
reconcile
but
to
because
there
are
similar
features
in
both
now
because
of
that
yeah.
C
There
are
no
plans
as
far
as
I
know,
to
merge
the
two.
We
do
have
a
future
and
it
doesn't
show
up
right
here,
but
you
can
export
all
your
analytics
data
into
application
insights,
so
application
insights
does
have
a
more
robust
feature
set.
So
it
allows
you
to
create
better
graphs,
query
things,
and
so
you
can
just
export
all
this
data
you're
getting
from
the
App
Center
SDK
into
application
insights.
If
you
want
to
use
those
features
to
you,
know
kind
of
customize
what
you're
looking
for
there?
Okay.
D
D
A
D
Fine,
and
so
one
of
the
things
for
me,
it's
it's
great
to
hear
about
this
stuff,
but
I
like
I
like
to
see
it
and
I
like
to
be
able
to
know
that,
like
the
we
try
to
make
the
barrier
for
entry
as
low
as
possible,
and
one
thing
that
came
out
of
our
last
session,
it
be
as
toolbox
was.
This
is
a
free
service.
Diagnostics
analytics
the
crash
reports
is
all
is
all
free.
This
is
all
just
part
of
how
is
helping
you
make
your
app
the
best
be
so
that's
worth
noting.
D
D
There
are
future
plans
for
that,
so
I
still
have
to
build
the
package
and
then
I'll
publish
it
and
upload
it
once
I've
done
that
I'll
be
able
to
make
it
crash
and
see
the
reports
kind
of
flow
in,
but
I
can
also
send
it
to
Winnie,
and
we
can
show
that
distribution
piece
where
it's
pretty
cool,
that
I
can
push
it
through
App
Center
to
her.
She
can
run
it
and
then
we
can
also
see
those
analytics
start
flowing
in
and
crashes
from
her
device.
That's
great!
So
yeah.
Let's
give
that
a
shot
yeah.
D
Let's
do
it
all
right,
so
I
want
to
start
with
if
you're,
if
you're
a
developer
in
the
wild.
Trying
to
do
this,
you
know
App,
Center
DMS
has
links
to
our
documentation.
We
have
a
page
here
and
getting
started
with
winforms
WPF
and
the
the
basic
steps
here
are
create
your
project.
Add
new,
get
references,
build
it,
add
your
UI
code
to
make
it
crash
or
hopefully
not
make
it
crash,
and
in
this
case
we're
gonna
make
the
crash.
D
Because
that's
you
know,
that's
the
fun
stuff
and
then
ship
it
and
and
that's
really
all
there
is
to
it
right.
So
you
see
it
says
you
need
the
dotnet
framework,
says
you're
going
to
create
your
app
in
App,
Center,
add
the
SDK
modules
and
then
go
from
there
and
so
I'm
going
to
do
just
that.
So
I
have
a
bunch
of
apps
in
here,
I'm
gonna,
add
a
new
app.
Let's
call
it.
D
D
A
D
D
When
we
generate
this
information
for
you
on
App
Center,
we
actually
give
you
all
the
credit
keys
to
integrate
your
app
with
the
SDK
on
this
page.
So
it's
customized
to
your
app
and
so
I'm
gonna
go
ahead
and
put
the
one
with
my
key
for
this
app
in
place.
There
you
go
you'll,
see
it's
complaining
about
analytics
and
crashes.
So
now,
if
I
look
at
the
getting
started
documentation,
the
next
step
is
to
integrate
the
SDK
modules
just
going
to
go
to
new
get
packages
for
the
WPF
and
inform
stuff
our
new.
D
Your
packages
are
in
preview,
so
we're
trying
to
get
this
all
finished
up.
Somebody
go
to
browse
I'm,
going
to
search
for
app.
Oh
I've
done
that
before
alright
and
so
I'm
going
to
install
the
crashes
nougat
package
and
the
analytics
cuz
kind
of
fun
to
see
them
work
together,
although
you
can
do
either/or
and
there
are
other
other
pieces
and
other
packages
you
can
install
as
well
so
we'll
let
that
do
its
thing.
D
And
so
addressing
some
comments
from
the
previous
video
we
did
have
someone
mentioned
that
they
thought
there
was
a
pretty
large
amount
of
data
and
packages
added
to
the
app
and
I
know.
We
have
a
github
issue
for
that.
So
if
anyone
else
sees
that
or
is
issue
with
that,
there
is
an
issue
you
can
reference
and
we'll
see
where
we
sit
with
that
and
what
we
can
do
to
make
that
manageable.
If
those
packages
are
are
too
big
you
can
see
it
is
adding
quite
a
bit
of
stuff
in
there.
D
And
then
also
gonna
have
analytics,
which
should
have
most
of
the
same
stuff,
and
so
once
this
is
all
up
and
running
around
the
app
make
sure
we're
we're
able
to
start
and
so
from
there.
Let
me
just
run
it.
I
should
have
a
blank
app,
we'll
verify
it's
working
before
we
go
any
further
call
this
our
passing
test.
A
D
A
D
So
here
I'm
going
to
do
a
couple
things
so
I'm
gonna
add
some
controls.
My
app
in
this
case
I
just
want
some
basic
buttons.
You
again
probably
wouldn't
have
buttons
that
say
crash
my
app,
but
you
might
might
want
to.
That
sounds
like
an
amazingly
honest
button.
Yes,
no
I
mean
that's.
We
try
and
live
in
transparency
yeah.
So
let
me
replace
this
grid
with
the
way
I
copy
and
paste.
D
Got
it
alright,
so
there's
my
buttons
so,
and
one
of
the
things
we
want
to
demonstrate
is
that
there
are,
you
know
your
app
might
crash
in
multiple
different
ways.
We
said
we
we
bucket
eyes
and
enrich
the
data.
We
want
to
see
that
and
then
there
is
the
Condors
concepts
we
have
an
app
Center,
both
unhandled
and
handled
airs
on
handle
airs.
Is
I
/
0
or
a
seg
faulted?
My
app
crashed.
We
actually
the
next
time.
The
app
starts
will
send
that
log
up.
D
We
found
that
trying
to
do
date
do
things
while
the
app
is
in
a
faulty
state
is
not
great
for
the
app
or
for
getting
the
data
to
us.
So
when
it
crashes,
we
actually
capture
a
snapshot,
a
tech
snapshot
of
what
happened
and
then
send
that
up
on
the
next
start.
The
other
alternative
is
a
handled
error
which
is
kind
of
like
an
aired
out
log
statement.
Right
you
couldn't
access
the
server
you
needed,
or
there
was
a
file
that
was
the
thought,
would
be
there
that
wasn't
there.
D
A
In
an
application,
one
time
before
I
joined
Microsoft,
where
until
we
we
added
some
analytics-
and
this
was
way
before
absences
at
the
time
we
had
no
clue
the
application
was
crashing
for
customers
on
a
daily
basis
in
a
way
that
they
could
recover
from
it
and
they
never
reported
it.
They
just
learned
to
work
around
the
problem
if
we
started
app
or
whatever
they
have
to
do
once
we
added
analytics.
It
was
just
like
mind-boggling
that
we
had
errors
coming
in
every
day
and
really
cause
nobody
complaining
about
it.
A
D
When
I
run
it,
we
should
be
able
to
go
ahead
and
crash
the
app
we
can
see
that
it
catches
it
I'm
gonna,
let
it
run
I'll
start
it
up
again.
So
we
we
your
board
set
off,
and
so
one
thing
we're
not
demonstrating
here,
that's
useful
to
see
there
are
hooks
into
the
SDK
to
customize
what
happens
to
like
augment
override
the
air
handlers.
So
you
can
do
what
you
need
as
well.
In
addition
to
sending
that
information
to
App
Center
and
let's
do
a
throw
a
handle
there.
Yeah.
A
D
We'll
throw
a
stack
overflow
in
there
as
well
that
one
takes
two
seconds
all
right.
Yeah
continue
all
right,
so
I'm
gonna
go
back
over
to
App
Center
and
with
any
luck
we'll
see
the
data
we
just
created
in
our
app.
So
if
I
go
down
to
Diagnostics
and
I
take
a
second
to
flow
through
also,
we
should
probably
check
that
I
actually
copied
and
pasted
the
right.
A
We've
got
a
question
why
you
looking
at
that
coming
in
somebody
asked
about
all
flying
capabilities.
You
know
it's.
The
question
is
I'm
little
behind
in
the
stream,
but
we'll
AB
Center
work
offline.
We
develop
enterprise
apps,
where
devices
aren't
online
and
I'm
gonna,
guess
that
that
might
be
a
problem
if
there's
no
connectivity
whatsoever,
but
it
but
but
I
feel
like
we.
We
almost
need
a
little
bit.
You
know
a
little
more
detail
right
like
what
does
it
mean
by
offline
yeah,
so.
D
What
we
do
do
is,
since
we
don't
send
the
logs
until
the
app
restarts
right.
If
your
app
had
an
error.
Well,
it
was
not
connected
to
a
network
and
crashed
it
would
we
would
write
that
log
and
when
you
restarted
and
had
network
connectivity,
it
would
try
and
send
it
I,
don't
I,
don't
know
off
the
cuff
we'd
have
to
ask
the
the
SDK
team
if
it
will
retry
when
it
fails,
sending
I
believe
there
is
some
retries
in
there
so
like.
D
D
D
D
So,
while
we're
waiting
for
this
a
couple
things
to
mention
like
we
said
right
now,
I'm
doing
this
with
a
dotnet
standard
framework,
as
of
today
and
I,
just
hadn't
tested
it
before
this
thing,
so
I
did
being
nervous,
didn't
want
to
do
it
live
yeah,
the
new
SD,
the
new
newest
version.
F
ck
does
support
net
core
3,
and
so
that
would
that
would
get
you
up
and
running
there
and
like
I
said
our
hope
are.
Our
theoretical
goal
in
the
near
term
is
to
uncouple
this
from
the
WPF
WinForms
framework.
D
C
We're
also
pretty
active
on
github,
so
you
can,
you
know
for
those
of
you
watching
live
or
who
are
watching.
My
video
afterwards
feel
free
to
send
us
a
feature
request.
Look
at
our
roadmap.
I'll
show
the
link
in
a
little
bit
when
we
switch
back
to
my
laptop
leader
yeah,
but
that's
probably
the
best
way
to
reach
either
of
us.
The
engineering
PM
team.
We
actively
monitor
or
get
a
repo,
so
feel
free
to
check
us
out
over
there.
So.
D
The
handle
bears
all
the
different
pieces
that
run
there
and
then
under
analytics
in
that
video.
What
we
would
see
is
that
there
is
one
user
and
then
when
had
done
this
cheer
when
I'll
share
this
with
Winnie
in
a
second
she'd
come
in
as
well
so
I
wanted.
You
know
sometimes
the
interweb
to
get
clogged
up
and
it's
hard
to
get
stuff
through
them.
But
let's,
let's
go
back
to
this
once
more
before
I
publish
it
20,
yep
I'm,
not
sure.
D
What's
got
the
pipes
clogged
today,
but
we
can
go
ahead
and
publish
this
and
definitely
distribute
this
to
Winnie
and
see
how
that
runs
on
her
side.
So
let's
go
ahead
and
stop
over
here.
So
I'm
just
gonna
go
to
build
published
a
tonight
community
and
I'm
gonna
upload
this
to
my
desktop
for
now,
so
that
I
can
find
it
and
right
there
finish.
So
that
should
give
me
a.
D
A
D
C
So
I
just
got
an
email
saying:
there's
a
new
app,
it's
very
exciting
if
I
click
on
this
install
button.
Here
it
will
take
me
to
the
install
portal
which
you
can
kind
of
think
of
this,
as
like
my
own
personal
App
Store
with
apps
that
I
can
download.
So
I
see
Matt's
comment
here:
the
version
click
download
open.
A
We
have
a
question
in
chat
about
sort
of
the
automatic
nature,
there's
the
case
and
the
things
that
crash
reporting,
without
maybe
users
inherently
knowing
about
it,
but
I,
guess
the
way
I
would
answer
that
I'd
love
to
hear
the
team's
perspective
on
it
as
well
as
that
the
app
you're
implementing
you
can
do
a
lot
of
good
things.
You
can
do
a
lot
of
bad
things.
A
The
app
you're
implementing
could
be
on
there
various
regulations,
whether
they're,
government
or
industry,
and
it's
really
up
to
each
developer
to
to
make
sure
their
customers
get
privacy
statements
and
disclosures
in
the
way
that
that's
relevant.
That's
what
that's,
how
I
would
think
about
it
right,
you,
you
know
just
because
I've
sent
to
does
something
technical
doesn't
mean
we're
forcing
it
on
your
customer.
If
you're,
taking
advantage
of
this
decay,
I
think
it's
important
that
you
consider
all
those
things
that
make
your
app
be
as
transparent
as
possible.
Is
that
some
fair
yeah.
D
Totally
and
that's
actually
what
I
was
referencing
earlier,
we
have
hooks
that
you
can
actually
flag
that
you
have
to
receive
a
user
acknowledgement
before
we
will
send
the
report.
We
have
hooks
that
allow
you
to
do
any
custom
handling,
whether
it's
your
own
air
reporting
or
other
user
data
gathering,
and
so
right.
I
think
that
our
intention
is
to
give
our
users
as
much
flexibility
as
they
need
to
and
want
to
give
their
users
to
live
in
that
transparency.
Awesome.
A
C
D
A
A
D
D
So,
in
a
happy
world
where
this
just
works
right,
install
so
I'm
running
by
exe-
oh
you
know
what
I
my
bad,
you
don't
have
the
newest
version.
Of.Net
framework
I
need
to
publish.
So
this
is
great
yeah.
This
is
a
great
tester
scenario.
We
totally
did
this
on
purpose.
Yes,
so
I
actually
need
I,
believe
Winnie.
Whitney's
machine
only
has
net
45
on
it
and
I
published
four
four
seven:
let's
go
ahead
and
redo
this
and
yes,
I'm
gonna,
read
you
that
so
I'm
going
to
somebody
to
get
package
or
your
installed.
D
C
D
All
right,
I
go
back
to
my
desktop
there.
You
go
now
I've
gotten
that
community
I'm
going
to
add
this.
Send
this
to
a
present
builder
boom
go
back
to
App
Center.
So
this
is.
This
is
a
good
example
of
welcome
releases.
So
hey
I
sent
it
to
my
tester.
My
app
wasn't
right.
You
know
totally
on
purpose.
Do
we
need
someone
to
use
like?
Is
it
just
that
file
that
file
it
should
be?
E
C
A
D
C
E
C
D
So
one
thing
that's
worth
mentioning:
I
suppose
we
strive
for
data
showing
up
almost
instantaneously
as
quickly
as
possible.
There
are
times
and
I'm
still
open
the
idea
that
I,
you
know.
Maybe
I
didn't
drink
enough
coffee
this
morning.
I've
done
something
wrong
here,
but
sometimes
it
can
move
a
little
slower
to
get
like
I
said
all
the
bits
transferred
through
to
be
just
completely
honest,
I'm,
a
little
surprised
that
it
hasn't
shown
up
yet,
but
in
a
perfect
world
it
would
show
up,
as
I
showed
the
vs
toolbox
one.
D
So
that
said,
it's
a
great
time
to
share.
If
you
were
experiencing
problems,
we
had
this
little
blue
button
in
the
right
hand
corner
and
you
can
get
yourself
connected
with
our
customer
care
team
and
then,
if
there's
an
issue
that
needs
resolved,
sent
back
to
work
with
the
dev
teams.
So
we
can
get
your
issue
up
and
running.
If
you
were
not
seeing
data,
that's
what
you
would
do
since
I'm
one
of
the
people
to
answer
this.
I
won't
bother
myself
today,
but
I
think
that
would
be
the
general
general
pattern.
D
A
C
So
we
actually,
you
can
get
in
touch
with
our
support
team,
like
Matt
just
showed
off
with
a
little
chat
bubble
right
there.
You
can
also
go
and
github
if
you
just
google
search,
github,
App,
Center
or
I'm,
currently
showing
this
on
my
screen.
We
are
very
active.
We
public
publish
our
road
map.
You
can
see
what
we
have
planned
each
month.
You
can
file
a
issue,
a
future
request
and
we
will
actively
monitor
this
and
definitely
take
this
into
account
when
we're
prioritizing.
The
next
features
so
definitely
drop
us
a
note.
D
A
A
D
A
You
so
much
for
being
here
and
thank
you.
Everybody
who
joined
us
online
keep
the
questions
coming
via
Twitter,
the
github
in
other
places
that
you
need
to
reach
us
and
we
are
building
these
products
for
you
to
make
you
productive.
So
it
doesn't
want
to
back
and
I.
Think
it's
much
for
watching,
join
us
next
month.
We'll
have
more
topics.
Sorry,
we
didn't
get
to
demo
tools
to
today.