►
Description
Join members from the .NET Desktop teams (WinForms, WPF & UWP) for our community standup covering MS Build 2020 announcements and the latest desktop news.
Community Links: https://www.theurlist.com/dotnet-desktop-5-8-2020
A
A
Love
everyone
hi
welcome
to
our
community
to
stand
up
desktop
series.
Today
we
have
a
big
crowd,
so
let's
go
ahead
ahead
and
introduce
our
cells
one
by
one.
I'll
start
with
myself.
My
name
is
olya
garish
and
I
am
p.m.
on
a.net
team
working
on
vim
forms
and
WPF.
They
have
Dmitry
with
me.
Dmitry
go
ahead.
B
A
A
B
A
Okay
and
we
also
have
a
command
that
olia
sound
is
good
and
everyone
else
is
not
very
good,
so
guys
yell
that
everyone
can
hear
you
all
right.
Okay.
So
today
we
wanted
to
talk
to
you
about
the
biggest
thing
that
happened
since
the
last
time
is
Microsoft
built
comm
I.
That
was
a
huge
thing
and
we
had
so
many
interesting
topics.
A
A
If
you
go
to
channel
9
in
events,
you
can
find
Microsoft
Bill
2020.
We
have
six
nine
episodes
so
go
ahead.
You
will
find
all
the
announcements
holding
you
greatest
and
latest
fears
to
be
released.
I
would
recommend
to
check
out
Scott
hunter
and
Scott
Hanselman
dotnet
talk
like
net
keynote,
and
there
were
so
many
other
and
I'm
sure,
Edward
and
Parvati
will
tell
us
about
their
announcement
as
well.
A
Be
one
I
would
like
to
start
with
is
announcement
of
dotnet
5
preview,
for
there
is
a
blog
post
by
Scott
hunter,
and
there
are
so
many
amazing
things
in
this
preview.
What
impressed
me
well,
of
course
there
was
C
sharp
9
and
F
sharp
5,
but
also
there
were
so
many
performance
improvements.
I
will
my
breakfast
also
a
new
single
file,
publish
types
and
now
you
can
publish
your
applications.
A
single
is,
he
exists,
I've
been
for
Windows
arm.
A
Sixty-Four
supports
both
development
status
and
deployment
of
client
apps
on
customer
beans,
and
we
have
a
new
TF
Rams
target
free,
a
target
framework.
Monica.
Let
me
show
you
this
one
before.
If
you
open
the
project
file,
you
would
see
this,
and
this
is
our
target
framework
for
dotnet
or
a
trip
on
its
at
core
app.
Now
it
will
be
just
met
five,
so
no
net
core
app
many
letters,
many
abbreviation,
so
this
will
substitute
net
core
app
and
dotnet
standard.
A
You
just
create
a
new
bin
forms,
WPF
app
in
Visual
Studio.
That
will
be
done
by
visual
okay.
What
else?
What
I
like
here?
My
engineering
part
of
me
usually
wanders
when
we
release
a
new
version,
I
think.
So
what
exactly
did
we
change?
What
did
we
add?
What
did
we
remove
and
I
really
like
this,
the
blog
post,
its
difference
between
our
three
one
and
that
fun
over
here.
A
Another
big
announcement
ice
in
VIN
forms
world
yeah,
it's
the
VIN
form
designer
in
they
release
channel
Studios.
Now
you
don't
have
to
be
on
the
preview
version
to
be
able
to
use
the
designer
it's
available
in
all
visual,
just
starting
from
6
and
in
the
release
channel.
It's
still
a
preview
feature,
so
don't
forget
to
go
to
tools,
options,
environment
and
here
check
this
chip.
A
You
think
that
we
are
still
working
on
is
the
project
resources,
full
support
for
localization,
inherited
controls
and
dialogues,
data,
Biden
scenarios
and
the
big
effort
for
us
right
now
is
the
work
with
control
vendor
the
we're
working
with
amazing
companies
like
Alaric,
DevExpress,
infra,
gistic,
active
prosecution,
they're
making
sure
all
their
controls
are
available
for
doesn't
and
with
crystal
Eric
we
had,
especially
like
close
partners.
We
basically
worked
in
the
same
repo.
We
have
weekly
calls
and
idea
bill
in
my
Oh
forms.
A
B
B
A
You
so
much
for
telling
me,
because
I
have
a
directional
mic
over
there
I'm
trying
to
show
the
demo
on
the
other
machine.
So
that's
probably
the
issue
make
sure
I
turned
my
head
yep.
So
here
you
can
see
it.
This
thing
has
a
different
theme:
it's
a
full
support
of
designer
actions
and
they
have
control
vendors
already
in
our
designer
and
we're
working
first,
one
will
probably
be
progressed
to
lyric,
and
then
we
will
expand
and
work
with
all
other
control
vendors
and
make
sure
all
your
favorite
third-party
controls
are
there.
A
A
B
B
A
B
A
B
B
A
A
A
C
D
C
C
C
You
can
find
it
by
going
to
Microsoft
wack
github
actions
for
desktop
apps
and
in
here
you're
gonna,
be
able
to
find
everything
that
you
need
basically
to
set
up,
CI
CD
workflows
for
your
WinForms
or
your
WPF
applications,
there's
a
pretty
hefty
example
and
instructions
here
that
that
is
pretty
easy
to
follow.
So
I'd
encourage
you
to
take
a
look
at
it
and
I'm
gonna
go
ahead
and
just
kind
of
demo.
It
really
quick.
So
in
Visual
Studio
we
have.
C
We
have
the
option
of
creating
a
test
project,
and
so
I've
got
I've
got
some
tests
here.
That
are
testing,
for
you
know
some
kind
of
output
that
says
not
packaged
and
so
I
can
actually
go
into
my
the
app
info
and
I
can
change
this
to
say
something
else
like
you
know,
app,
not
packaged
right.
So
now,
I'm
gonna,
I'm
gonna
expect
my
test
to
fail.
So
now,
when
I
go
and
go
to
my
my
app
here,
let's
see
here
get
status,
you
can
see.
C
I've
got
a
change
in
both
of
these
main
windows
is
the
is
the
main
one
so
get
Ad
and
we'll
go
ahead
and
do
the
main
window
and
then
get
commit
and
just
some
message
and
get
push
so
we're
gonna
push
this
up
and
you'll
be
able
to
see
kind
of
this
in
action.
So
if
you
click
on
either
actions
or
if
you
go
to
your
pull
request,
you'll
be
able
to
see
this
actually
happening
for
your
your
CI
here.
C
So
we
go
to
a
pull
request
and
you
can
see
automatically
that
some,
it's
saying
that
some
checks
haven't
completed
yet.
So
this
is
how
you
access
the
the
CI,
so
we
can
go
in
here
and
we
can
take
a
look
at
the
details
and
you
can
kind
of
see
everything
that
needs
to
happen.
So
we
have,
you
know
we
can
set
up
a
job.
We
check
out
the
the
repository
we
you
know
install
in
that
core
and
that
kind
of
thing.
C
C
Everybody
see
it:
okay,
okay,
cool
all
right
awesome,
it
looks
like
everybody
says
they
can
hear
me
and
they're
interested
in
CI
CD
great.
So
as
you
can
see
now,
because
we
pushed
to
the
repo
we're
automatically
running
our
CI
workflow.
So
now
down
and
I'm,
not
gonna
I'm,
not
gonna,
wait
around
for
all
this.
That
happens,
so
I
actually
already
have
kind
of
the
the
the
end.
Here.
C
You
can
see
that
that
when
we
tried
to
execute
the
unit
test,
we
failed
on
it
and
we
have
you
know
an
x86
build
and
an
x64
build
is
what
I'm
doing
right
now
and
the
x64
build
actually
didn't
execute
all
the
way,
because
we
failed
on
the
x86.
So
this
is
cool
because
it
means
that
you
don't
end
up
wasting.
You
know
your
precious
resources
to
build
this.
So
let's
see
here,
if
we,
if
we
go
back
so
now,
what
I'll
do
is
I'll
demonstrate
kind
of
changing
something
so
that
that
is
gonna
succeed.
C
So
we
can
change
our
unit
test
back
and
if
we
go
to
main
window
we
can
actually
change
the
color
palette
here
and
that'll
kind
of
show
up
in
the
in
the
app
when
when
we
install
it.
So
let
me
just
go:
grab
the
the
color
palette
here
and
we'll
change
that
to
like
a
purple-
and
this
is
a
new
feature
actually
that
we
just
released,
which
is
that
you
can
actually
see
a
preview
of
your
color
right
in
the
writing.
C
C
So
again,
if
we
go
to
actions,
we
can
kind
of
see
all
the
actions
that
we've
run
and
that
we've
queued
in
the
past
and
you
can
kind
of
get
an
idea
of
what's
past
and
what
hasn't
passed
and
then
we
can
also
look
at
what
was
just
queued,
and
so
these
were
just
queued
and
so
I'm
gonna.
Let
this
run
again,
and
this
takes
about
seven
minutes.
I
would
say
from
my
build-
and
this
is
a
pretty
small
app.
C
So
you
know
you
you,
if
you
have
a
large
app
it
may
take
a
while
longer,
but
I'm
not
going
to
make
everybody
wait
for
that.
So
you
can
see
this
is.
This
is
a
changed
color
version
and
we
passed
the
execute
unit
tests.
We
actually
built
the
Windows
application
packaging
project.
We
signed
the
application
and
what's
really
cool
about
this,
is
that
we
got
artifacts
so
as
a
developer.
C
And
while
we're
waiting
for
that,
I
could
just
kind
of
show
you
really
quick
the
code
in
here.
So
you
know
your
workflows
if
and
get
with.
Github
actions
are
defined
in
this
github
whack
workflows,
folder
and
I
have
a
CI
an
to
see
a
CD
pipeline
that
are
in
here
and
for
the
CI
pipeline.
You
can
see
that
we
trigger
on
every
push
or
every
pull
request,
and
we
actually
have
a
matrix
of
target
platforms
that
we're
doing
so.
C
We
could
do
x86
x64,
we
could
do
arm
or
arm
64
as
well,
and
what's
really
cool
here,
especially
for
net
core
users,
is
that
you
could
do
it
on
Windows
latest.
You
could
do
it
on
a
boon
to,
and
you
could
do
also
do
it
on
Mac
OS
and
if
you
wanted
to
add
those
to
the
matrix,
you
could
have
it
run
on
all
three
of
them,
which
is
pretty
cool
too,
and
then
you
can
see
kind
of
you
know.
We
have
execute
unit
tests.
C
We
decode
our
encoded
pfx,
which
is
sort
of
best
practices
for
using
a
security
certificate.
Signing
certificate
and
I
have
all
that
in
the
in
the
readme
and
then
eventually
we
upload
the
MSI
X
package,
and
we
have
that
available
right
here.
So
I'll
go
ahead
and
copy
this
stuff
and
I'm
gonna
put
it
in.
C
We
go
ahead
and
update
the
app
because
it's
already
been
installed
and
please
work,
it's
working
cool
and
we
open
it
up
and
unfortunately,
I
totally
forgot
to
show
you
what
it
looked
like
before
hand.
But
this
is
what
it
looks
like
afterwards,
so
you
can
see
that
we've
changed
our
heading
from
the
orange
color
to
the
purple
color.
So
it's
that
easy
for
developers
to
test
it
and
I
also
have
a
CD
pipeline
in
here
as
well,
and
that
actually
creates
a
release.
C
And
that's
down
here
at
the
very
end
of
that
and
what's
great
about
the
releases,
creates
the
release
here.
What's
great
about
the
release,
is
that
once
you've
already
tested
your
your
you're
dead
version
and
you
want
to
go
ahead
and
release
something?
It
goes
ahead
and
it
adds
the
code
to
this
releases
tab
right
here
and
then
the
releases.
It
actually
has
all
the
different
releases
that
you
have
so
we
have
store.
We
have
side
load
for
x86
and
x64,
so
you
could
have
arm.
You
could
do
anything
that
you
wanted
here.
C
So
that
shows
that
and
I
wanted
to
show
one
last
thing,
and
that
is
this
new
project
that
I
worked
on,
which
is
a
workflow
template.
So
if
you
click
on
new
workflow
here
in
your
github
action
and
get
a
project
now,
dotnet
desktop
developers
can
select
the
net
core
desktop
workflow.
So
you
don't
have
to
copy
all
the
code
that
I
had
in
my
sample
app
anymore.
C
You
just
click
on
set
up
this
workflow
and
it
automatically
adds
the
the
yamo
file
for
you
so
that
you
can
get
started
now,
there's
a
little
more
work
that
you
have
to
do
around
signing
certificates
and
things
like
that.
But
I
tried
to
make
the
instructions
as
easy
as
possible,
so
I
would
love
some
feedback
on
this.
A
B
Awesome
well
glad
to
be
here.
So
let's
talk
about
them
a
little
bit
so
today,
I'm
gonna
talk
about
a
couple
of
things.
I'm
gonna
share
my
screen
here
and
I'm
gonna
basically
go
through
a
bunch
of
partner
announcements.
This
is
kind
of
the
Bill
2020
recap
episode,
so
we
want
to
talk
about
the
big
announcements
at
Build.
Developers
should
be
caring
about
and
I
want
to
start
talking
about.
Maui
a
project
that
I'm
also
now
working
on
is
one
of
the
things
on
my
list.
B
So,
while
I'm
not
gonna,
go
deep
into
this
I
just
wanted
to
point
it
out,
then
you
can
find
the
link
in
our
show
notes
where
this
blog
post
talks
about
all
the
things
that
we're
doing
with
Maui
the
timeline
to
that
we
hope
to
sort
of
meet
to
get
it
out
there
by
dotnet.
Six,
all
the
improvements
we're
making
with
the
project
system
simplifying
how
the
projects
are
constructed,
making
it
be
an
both
mvvm
and
mb
mvu
capable.
So
it's
really
a
great
great
announcements.
B
I
really
hope
folks
will
take
a
look
at
it
if
you're
looking
at
doing,
cross-platform
definitely
take
a
look
at
Maui.
We
also
had
an
announcements
from
our
friends
in
the
windows
organization,
where
they
released
a
new
preview
of
something
they
call
Winnie.
Why
three?
This
is
again
an
evolution
of
something
that
you
know
used
to
be
known
as
uwp,
so
this
is
their
take
on
bringing
uwp
forward,
and
this
first
preview
release
is
the
first
time
that
they're,
enabling
this
type
of
project
to
work
in
desktop
mode.
B
So
imagine
having
a
uwp
app,
that's
running
outside
of
the
sandbox.
It
has
fluid
controls.
It
has
all
of
the
API
capabilities
of
Windows
10.
It
has
the
ability
to
to
use
all
the
modern
controls
and
all
the
performance
improvements
and
everything
else
that
comes
with
it,
and
now
you
can
run
all
of
that
as
a
true
desktop
application.
Instead
of
having
to
have
it
be
in
a
sandbox
mode.
There's
certainly
lots
of
issues
with
the
first
preview.
B
It's
a
really
early,
first
preview,
but
definitely
again
if
you're,
if
you're
looking
at
you
know
what
kind
of
desktop
applications
you
can
build
in
the
future.
When
you
write
three
is
definitely
an
important
part
of
that.
So
definitely
take
a
look
at
it
and
they
have
in
here
a
great
link
to
a
getting
started
guide.
So
they
can
walk
you
right
through
you
know,
building
a
project
and
such
in
there.
We
also
had
an
announcement
from
the
Windows
community
toolkit
they
released
another
version
of
their
toolkit
windows.
B
Community
toolkit
is
a
set
of
capabilities
that
used
to
be
for
just
you,
WP
developers,
controls
and
such
and
now
they're,
making
it
available
for
win
UI
as
well,
so
that
team
is
helping
the
windows
team
bring
some
of
that
capability
over
to
when
UI
developers.
So
if
you
need
more
controls
or
anything
else,
that's
in
the
toolkit
definitely
take
a
look.
B
So
my
team
has
been
working
really
hard
and
making
sam'l
experiences
better
for
for
desktop
developers
and
Xiamen
forms
developers
wherever
we
can
sort
of
cover
both
sides
and
in
this
blog
post
I
recap:
everything
that
we've
done,
starting
with
16
7
preview
1,
which
is
their
released
I,
got
released
a
build,
but
also
I
recap
what
we
shipped
in
16
5
and
16
6
as
well.
So
this
is
like
the
one
blog
post
you
can
go
to.
B
So
in
this
blog
I
go
ahead
and
I
talk
about
improvements,
we're
doing
to
data
binding
the
troubleshooting
in
Diagnostics,
with
this
new
experience
that
I'll
demo
in
a
second
and
visual
studio,
we
also
talked
about
the
fact
that
we've
added
a
long
requested
feature
which
is
the
inline
color
visualizers,
and
then
the
blog
post
will
go
into
other
things
that
I've
showed
in
other
previous
community
standard
meetings.
Things
like
our
improvements
to
sam'l
designer
suggested
actions,
and
there
is
feature
improvements.
B
We've
done,
Azam,
ohad,
reload
code,
editor
designer
packaging
lots
of
stuff
in
here
definitely
take
a
look.
I
won't
cover
every
detail
here.
So
let
me
switch
to
visual
studio
for
a
second
and
just
show
two
of
the
features
that
are
in
the
latest
release
of
Visual
Studio
16
7.
The
first
feature
is
this
inline
color
visualizer,
so
the
before
we
just
didn't
have
this.
B
B
Blue
is
easy,
but
the
violet
like
what
would
blue
violet
look
like
so
now,
when
you
select
it,
the
visualizer
is
right
there
for
you,
you
can
get
a
preview
of
what
blue
violet
will
look
like
and
I
will
also
point
out
that
we've
actually
had
this
inside
of
the
properties
panel
for
a
while.
But
you
know
you
don't
always
have
this.
You
know
available
to
you
like
a
lot
of
times.
I
run
these
in
a
much
more
kind
of
code,
centric
mode
like
this
and
then
I
wouldn't
see
the
visualizer.
B
B
B
And
you
say
suggest
a
feature
we
will
bring
up
the
right
place
for
you
to
do
that
inside
of
this
window,
that
pops
up
and
once
it's
a
fennec
ated
you
can,
you
can
go
ahead
and
do
that.
So
definitely
use
this
to
report
problems
to
suggest
features,
and
we
triage
this
literally
on
a
daily
basis.
So
every
piece
of
feedback
gets
looked
at,
not
every
feature
request
gets
built.
Some
things
mean
you
know
really
good
good
reasons
for
us
to
sort
of
invest
into
it.
We
need
sometimes
multiple
people
to
request
it.
B
Awesome
so
here's
my
running
application,
so
basically
I
just
hit
f5
and
just
to
show
you
the
new
demo,
binding
troubleshooting
feature
that
we've
added.
So
this
is
completely
new.
We've
had
now
added
an
icon
into
the
in-app
toolbar.
That
shows
you
when
bindings
have
failed
in
your
application.
So
just
to
give
you
the
contrast
of
what
the
experience
used
to
be
before
we
added
this
feature
before
you'd
run,
the
application
you'd
have
binding
failures.
B
So
it
was
really
hard
to
even
see
the
binding
failures
were
happening,
and
now
we
let
you
know
right
in
the
in-app
toolbar
and
this
icon
will
get
better.
It's
a
horrible
icon,
so
preview
we're
gonna,
make
the
icon
much
better
and
when
you
highlight
it
show
you
the
number
of
binding
failures
and
if
you
click
on
this
button,
we
take
you
to
the
sam'l
binding
failure
panels
and
it's
a
new
window
inside
a
visual
studio
that
is
a
rich
UI
for
showing
the
binding
failures
that
were
again
previously
just
here
in
the
output
window.
B
Now
it's
in
a
dedicated
experience,
if
you
don't
prefer
this
experience,
it's
all
controlled
based
settings.
You
can
go
ahead
and
disable
it
and
I
talked
about
those
settings
in
the
blog
post
in
terms
of
tourney's
feature
on
enough,
so
they
definitely
want
to
give
customers
choice.
If
we
build
a
new
experience,
you
don't
like
it.
You
can
continue
using
the
old
experience
as
well.
B
But
if
you
do
like
this
experience
and
do
use
it
and
know
that
we're
we're
just
in
the
early
stage
in
you're
building
it
we're
still
refining
this
this
window,
we're
gonna,
make
it
have
more
capabilities,
such
as
grouping
things
in
different
ways,
we're
adding
all
sorts
of
you
know,
kind
of
like
more
interesting
right-click
menu
commands
for
copying
out
the
original
error
and
doing
other
more
advanced
separations.
So
we're
working
on
that,
but
even
in
this
preview
and
already
is
pretty
powerful.
B
So,
for
example,
if
I
just
want
to
see
all
the
binding
failures
that
are
related
to
tooltip
and
if
I
type,
tooltip
and
I
hit
enter
the
filter
works
right
here
we
can
filter
down
the
tooltip.
It
would
have
done
the
same
thing
if
I
would
have
entered
the
sam'l
data
provider,
it
would
have
shown
me
if
I
don't
misspell
it
the
way.
That's,
oh
sorry,
XML
there
you
go
datum,
so
I
could
actually
filter
down
to
the
exact
error.
B
We
also
today
group
the
errors
as
they're
happening,
so
this
error
happened
twice
and
it
was
the
same
exact
binding,
because
if
my
template
is
failing
over
and
over
and
over
again,
I
do
not
want
to
see
the
error
50
times
in
this.
In
this
new
panel,
I'd
like
to
just
see
it
one
time
with
the
count
of
how
many
times
it
failed.
So
that's
another
improvement
that
we're
doing
and
something
that
people
will
definitely
try
to
do
and
fail.
B
So
I
want
to
bring
it
up,
which
is
if
you,
if
you
click
on
this,
nothing
happens
like
if
I
click
on
the
errors,
because
we
don't
have
the
right
sort
of
the
agnostic
information
today
to
know
where
to
go.
We
can
only
show
you
the
information,
that's
available
in
the
and
we'll
get
better
and
better,
but
basically
clicking
the
code,
navigate
the
source
code
really
difficult
to
do
from
a
technical
standpoint
and
we're
hoping
that
we
actually
get
this
working
soon.
B
For
at
least
maybe
one
of
the
frameworks
we're
trying
to
partner
with
xamarin
on
that
to
see
if
we
can
make
it
possible,
they'll
have
to
make
changes.
We'll
have
to
make
changes
and
see
if
it
all
comes
together,
but
we
are
working
on
it
and
we
hope
to
bring
navigate
the
source
to
more
and
more
platforms
as
more
and
more
partners
kind
of
come
online
for
this
and
yeah
those
are
the
bigger
features
so
give
it
a
shot.
Let
us
know
what
you're
thinking
we
really
value
your
feedback,
that.
A
Is
awesome
yeah?
Thank
you
so
much.
It
all
looks
amazing
and
we
had
a
few
questions
in
the
chat.
I
think
one
advert
already
answered.
There
was
an
important
question
about
mind
me
tree
I
think
you
are
qualified
to
answer
that
the
question
was:
can
Maui
scene
like
in
Moana
and
since
you
have
a
little
baby
I
believe
you
can
take
this
one.
B
A
B
A
D
D
D
You
know
just
their
ease
of
use
with
HTML,
CSS
and
JavaScript,
but
on
the
same
time
you
know
they're
not
as
powerful
as
are
more
native
technologies
like
dotnet,
and
you
know,
native
apps
in
general
have
better
functionality
like
windowing
taskbar
management.
Things
like
that,
and
so
what
my
team
is
doing
is
we're
announcing
a
web
view
to
control
that
is
trying
to
allow
developers
to
take
the
best
of
both,
and
we
call
this
a
more
hybrid
approach.
So
let
me
explain
more
about
what
a
web
view
is.
D
So
web
view
allows
you
to
embed
HTML,
CSS
and
JavaScript
or
web
content
in
your
application.
So,
for
example,
here's
an
app
you
can.
You
know
build
part
of
it
in
terms
of
in
a
web
view,
and
you
know
in
this
sort
of
section
the
sidebar
here
in
this
application
it
can
be
programmed
with
HTML,
CSS
and
JavaScript
and
that
gets
embedded
into
the
application.
So
you
can
kind
of
you
know,
use
a
web
view
as
a
one
component
of
the
application.
D
D
Another
big
feature
of
webview,
as
opposed
to
other
similar
technologies,
is
it
allows
for
incremental
adoption,
as
I
sort
of
you
know,
walk
through
in
the
previous
slide.
You
know
you
don't
have
to
replace
the
entire
application
or
the
whole
UI
with
web
stuff.
You
can
kind
of
just
have
part
of
it,
be
a
webview
and
render
with
web
content
and
kind
of
build
component
by
component.
D
If,
as
you
want
to
adopt
it,
because
you
know
there
are
definitely
certain
times
where
native
UI
is
preferred,
so
there
are
a
few
legacy
webview
offerings
that
have
existed
on
windows
for
quite
some
time.
The
first
one
was
the
web
browser
control,
which
was
built
maybe
10-15
years
ago,
and
that
was
based
on
the
MS
HTML
engine
and
Internet
Explorer.
The
benefit
of
the
web
browser
control
has
always
been
that
it's
supported
across
all
Windows
operating
systems,
so
from
Windows,
7,
Windows,
8
and
all
versions
of
Windows
10.
D
So
it
was
only
able
to
run
an
application
on
the
latest
versions
of
Windows
10
and
there
was
no
support
for
Windows
7
or
Windows
8,
and
so
what
we
constantly
heard
from
developers
who
are
often
trying
to
leave
the
you
know
more
legacy.
Web
browser
control
was
that
they
wanted
a
web
view
like
capability
with
the
modern
standards
of
you
know
what
we've
come
to
expect
with
the
web,
but
also
be
able
to
run
in
applications
across
Windows
7.
D
D
The
webview
control
is
unique
in
the
fact
that
it
targets
a
common
runtime
on
Windows
computers,
and
we
can
you
know
we
update
that
regularly,
every
six
weeks
to
keep
it
in
cadence
with
the
rest
of
the
chromium
project,
but
for
some
developers
who
don't
want
to
you
know,
have
that
six
week
update
cadence
that
comes
with
the
web
platform.
We
also
have
a
fixed
version
that
allows
developers
to
package
the
browser
inside
their
application.
D
Here's
an
example
of
webview
in
action
so
for
a
product
like
Microsoft,
Outlook,
they're,
multiple
versions,
so
on
the
Left
we
have
the
OMA,
which
is
the
Outlook
Web
App.
So,
as
you
can
see
here
on
the
left,
this
is
Outlook
on
the
web
on
the
right
we
have
Outlook
on
native,
and
this
is
a
more
preview
version
of
Outlook.
So
it's
not
the
one
that
we're
familiar
with,
and
if
we
look
at
this
room,
finder
feature,
this
has
existed
on
the
on
the
left,
its
existed
in
the
Outlook
Web
App
for
quite
some
time.
D
So
where
are
we
today?
So
the
webview?
We
released
a
preview
of
webview
to
for.net
app,
build
we're
gonna,
be
updating
your
SDK
every
six
weeks.
That
will
be
largely
driven
by
community
suggestions
for
what
you
want
to
see
so
I'm
gonna
link
on
the
on
the
next
slide,
to
how
you
can
give
us
those
suggestions
and
feedback,
and
we
look
to
incorporate
that.
You
know
on
a
six-week,
rolling
basis
and
then
we
shoot
to
have
a
stable,
generally
available
version
by
the
end
of
the
year.
D
So
here's
some
next
ups
to
learn
more
about
webview,
a
kms
/
webview.
If
you
want
to
get
tips
on
how
to
get
started,
we
have
a
10
minute
getting
started
guide
for
WPF
in
WinForms
on
the
following
links
and
as
I
mentioned
before,
you
know.
We
really
really
appreciate
your
time
to
go
through.
These
guides
must
around
with
our
preview
and
give
us
feedback,
and
that's
really
gonna
help
us.
You
know
shape
how
we
bring
our
product
to
market
by
end
of
the
year
and
to
leave
us
feedback.
A
D
B
Historically,
web
webview
and
other
controls,
this
were
rendered
some
native
UI
with
not
respect
the
BPF
controls.
So
when
the
bvf
controller
try
to
render
if
it
was
rendering
over,
like
let's
say
you
had
a
menu
and
you
were
expanding
a
menu
in
your
app
and
the
menu
was
over
the
browser
in
the
past,
the
browser
would
be
actually
over
the
menu,
even
though
that
wasn't
the
developer's
intention.
B
D
D
A
B
D
D
That
is
actually
one
of
the
features
that
we
were
actively
working
on
and
the
reason
why
our
GA
got
delayed
until
the
end
of
the
year,
so
yeah.
So
there's
a
big
concern
about
you
know
the
Microsoft
edge
browser
not
being
there
on
the
user's
machines
and
that's
something
we've
accounted
for
so
so
with
their
two
versions
of
webview.
D
So
the
first
easier
version
is
the
fixed
version
where
you
can
just
bundle
the
browser
into
your
application
and
then
it
doesn't
require
your
users
machines
to
have
the
browser,
because
you
know
it's
embedded
in
packaged
into
your
application.
The
other
version
that
we're
working
on
for
the
other
green
version
is
machine.
If
it's
not
already
there
and
different
applications
can
then
in
can
sort
of
count
on
that
webview
runtime
being
there
and
that
you
know
it
doesn't
it's.
So
it's
basically
like
the
browser's
there,
but
it's
kind
of
invisible.
C
A
D
B
I
responded
also
in
the
in
the
chatter
era,
to
the
saying
that
we
don't
typically
try
to
name
things
that
controls
based
on
the
product
names,
because
that
would
first
make
things
extremely
long.
The
you
know
webview
from
you
me
here
like
that.
That's
just
getting
way
too
specific
and
also
the
reality
is
that
Internet
Explorer
turned
into
edge
and
who
knows
what
edge
will
turn
into
ten
years?
From
now
like
we
don't
want
to
be
dependent
on
product
names,
I
think
webview
web
YouTube.
B
A
Yes,
right,
there
was
command
about
vin
forums,
designer
ben
tree
to
hear
that
they're
trying
really
hard
to
get
you
the
same,
an
even
much
better
designer
that
you
had
for
dotnet
framework.
So
thanks,
I'm
happy
it's
working
and
I
actually
heard
from
a
few
people
that
they
had
issue
where's
the
visual
studio
toolbox,
cache
getting
corrupted.
So
if
in
you
confirms
designer,
you
don't
see
important
controls
like
button
or
checkbox,
that
is
the
issue.
It's
very
easy
to
fix.
Well,
the
fix
will
come
in
the
next
version,
but
you
can
fix
it
right
away.
A
So
right-click
on
the
toolbox
and
go
to
choose
items
and
here
click
reset
and
that
will
fix
the
issue.
So
if
you
don't
see
the
button
button
should
be
there.
Do
this
few
steps
and
the
issue
should
begin
and
we
apologize
but
turns
out.
Sometimes
these
things
happen
right.
Do
we
have
any
more
questions?
Oh.
A
A
So,
basically
internals
in
general,
right
before
we
had
one
designer
that
was
running
in
the
same
process
as
Visual
Studio,
but
doesn't
framework
everything
was
working
just
fine
now
for
dotnet
core.
We
have
does
not
core
design
err
and
it
runs.
It
has
to
interrupt
with
Visual
Studio
Visual
Studio,
that's
a
dotnet
framework
process,
but
not
core
designer
surface
is
the
net
core
process,
so
they
have
to
be
two
different
processes.
A
They
cannot
be
in
the
same
one
and
that
required
us
to
create
a
lot
of
plumbing
a
lot
of
like
we
are
detecting
and
reinventing
things
to
make
it
work
smooth
yeah
there.
Let
me
see
if
I
okay,
what's
next
on
the
work
list,
for
your
for
us-
that
that's
a
good
question
so
right
now
we're
working
on
always
control
vendors,
we're
trying
to
get
of
them
enabled
in
the
designer.
A
We
also
are
finishing
binding
data
scenarios,
so
grid-view
is
coming
and
with
that
the
support
for
data,
and
then
we
will
have
smaller
parts
like
support
for
inherited
controls
like
if
you
inherit
your
form
from
some
other
object
right
now
it
doesn't
work
in
the
designer.
We
will
make
it
work
a
resources.
Local
resources
are
working
right
now,
project
resources,
that's
something
that
is
coming
next
and
performance.
We
want
to
make
sure
the
designer
is
as
fast
as
we
can
get
it
and
stabilization.
A
We
still
have
some
issues,
some
p2
p3
issues
that
we
want
to
fix,
Ola
what
else
Apple
and
Google
wouldn't
care
about
breaking
your
apps
Microsoft
does
well
I'm,
very
sorry
that
we
break
you
and
we
care
a
lot
and
we
are
trying
to
fix
it
and
yeah.
It's
been
many
sleepless
nights
for
me
when
we
broke
you
guys
and
we
were
trying
to
address
it
as
fast
as
we
can.
We
do
apologize.
Sometimes
that
happens
all
right,
any
more
questions.
Anything
you
would
be
interested
in
hearing
from
us.
B
A
A
B
Yeah
yeah,
the
the
reality
is
that
you,
you
know,
control
vendors
can
do
that
that
you
can
set
up
certain
extensibility
endpoints
package
is
a
control,
but
that's
the
way.
The
way
it's
being
described,
that's
not
possible.
If
you
just
have
a
project
as
far
as
I
know,
if
you
just
had
a
user
control,
there's
no
way
to
make
it
appear
in
the
toolbox
or
fortunately,
if
that
the
future,
you
want
sense
and
this
feedback.
That's
that's
what
I
always
encourage
you
can
do
it.
A
B
A
B
C
Yeah,
if
they,
if
in
from
their
github
project,
if
they
have
a
c-sharp
project
in
particular,
and
they
go
to
let's
see
here,
actions
and
then
new
workflows,
it
should
pop
up
there
and
it
really
depends
on
you
know
what
kind
of
project
you
have.
So
if
you
have
a
blank
project,
then
it
may
not
show
up.
You
know
right
away,
you
may
have
to
search
for
it,
but
I
can
try
to
find
a
link
to
see
if
there's
somewhere,
where
you
can
just
kind
of
reference.
It
I'll
take
a
look.
A
A
A
That
sounds
great.
Another
question
was
any
plans
for
vim
forms
designer
support
and
vs
code.
Now
we
don't
have
this
plans
because
V
is
caught.
It's
not
IDE
right,
it's
a
it's,
a
different
concept!
That's
why
we're
not
gonna
bring
it
to
be
ascot.
We're
not
gonna
make
it
heavier.
Also
WinForms
will
remain.
Cross
plot
will
remain
vin
forms
only
technology,
so
it's
not
gonna
be
cross-platform.
So
that's
another
reason
why
we
I
don't
think
we
will
ever
need
it
for
non-windows
scenarios.
A
Yeah
there
was
a
question
about
the
tool.
I
would
be
also
interested
which
tool
did
you
mean
and
a
child
Oh
a
mouth
net
is
a
serious
tool
that
would
bring
some
new
features
to
machine
learning
in
the
world.
Yeah.
Of
course,
a
mallet
net
is
a
great
mechanism
of
building
your
custom
machine
learning
models.
It's
an
open-source,
it's
free
and
it's
for
the.net
developers.
A
So
if
you
don't
want
to
learn
Python
if
you're
like
right
in
c-sharp
language
and
they're,
also
in
available
in
Visual
Studio
such
as
model
builder,
where
you
can
just
feed
in
the
data
and
auto
email,
early
and
well
builder
mechanism
can
suggest
solutions
for
your
problem.
You
just
specify
what
you
want
to
predict
like
what
answers
you
want
to
get
from
your
data
and
it
runs
all
possible
options
available.
Algorithms,
evaluates
them
and
gives
you
the
best
solution
for
you.
A
Yeah,
you
have
your
fans
me
tree
right.
There
is
a
question
about
github
starter.
Workflow
templates
are
not
available
in
the
github
actions
website.
It
can
be
found
by
okay
that
let
me
tree
provided
the
answer
all
right.
Any
more
questions,
folks
shutout
from
Brazil,
oh
I've,
never
been
I
always
wanted
to
go.
Hopefully,
and
all
this
madness
is
over.
A
Right,
if
you
have
no
more
questions,
I
think
that's
all
our
content
for
today.
So
thank
you
very
much
everyone
for
joining
us.
It's
always
a
pleasure
to
talk
to
you
guys.
Thanks
for
your
feedback,
thanks
for
testing,
our
internal
preview
beats
reporting
issues
committing
PRS
that
all
really
helps
us.
A
There
was
another
question
about
performance
goal
and
performance
versus
dotnet,
core
performance.
I,
don't
think
I
can
comment
on
that.
But
again,
we've
made
lots
of
performance
improvements
in
the
latest
preview
of
dotnet
5,
so
that
is
something
to
go
check
out.
I'm
super
excited
about
those
changes
and
thank
you
very
much
have
amazing
the
rest
of
your
day
week
and
weekend
and
see
you
in
one
month.