►
Description
Join members from the .NET teams for our community standup covering great community contributions for Framework, .NET Core, Languages, CLI, MSBuild, and more.
Community Links: https://www.theurlist.com/zjrbmjl
A
A
B
A
And
today
is
the
first
time
you're
doing
this
community
stand
up
not
in
channel
9
studio,
but
at
home.
That's
the
first
time
in
streaming.
I
have
some
craziness
with
two
laptops
and
lots
of
wires
going
on
here,
but
hopefully
fingers
crossed
we'll
manage
okay
yeah
today,
girl,
yeah
I
know
there
is
a
button
that
I'm
not
supposed
to
press,
because
it's.
A
A
So
what's
happening
in
between
forms,
let
me
start
sharing
my
screen.
Yes,
one
thing
you
guys
are
asking
us
a
lot
is
designer
and
I
wanted
to
give
you
the
update
on
big
designer.
As
you
know,
last
week
we
released
the
new
version
of
Visual
Studio
preview.
It's
sixteen
point,
six
preview,
three,
and
in
this
version
they
have
a
new
version
of
BIM
forms
designer
and
today
I
will
show
you
even
later
version.
A
I
am
running
internal
preview,
so
it's
a
little
bit
ahead,
but
you
can
go
ahead
and
get
the
latest
version
of
sixteen
point.
Six
preview,
three
and
you
will
see
most
of
the
things
that
I
will
show
you
already
available
for
you
and,
as
you
can
see
here
in
the
tool
box,
we
have
lots
of
new
controls.
So
we
have
all
the
dialogues,
picture,
box,
print,
dialog,
open
file,
dialog,
and
let
me
actually
start
adding
that
on
this
warm.
So
you
can
see
that
it's
actually
working.
A
B
A
A
A
You
will
see
some
already
in
the
main
version,
but
the
complete,
like
full
experience,
will
come
later
and
we
also
already
working
with
all
the
control
vendors,
such
as
they'll,
Express,
telluric,
progress,
grapecity
energy
sticks,
active
processing,
fusion
and
so
on,
and
we're
making
sure
their
controls
are
supported
on
dotnet
core
and
in
future
in.net
5.
So
all
your
favorite
third
party
controls
will
be
there
and
we
also
have
some
news
regarding
dotnet
5
for
vim
4x
case.
A
Most
of
our
resources
are
concentrated
around
the
designer,
but
we
also
do
some
work
for
dotnet
5
and
one
amazing
news
I
wanted
to
share
with
you.
They
go
ahead
and
show
the
street.
This
is
a
tweet
from
my
teammate
a
guerrilla
corrosive
and
he
was
super
excited
because
we
finally
merged
a
new
feature
into
VIN
forms.
A
B
A
Yes,
you
can
have
elevation
and
you
can
even
have
the
progress
bar
and
more
two
pages
and
so
on.
So
this
OPR
was
done
by
open
source
contributor,
Constantine
Preiser,
and
we
can
thank
him
enough
for
doing
this
amazing
job.
It's
like
really
impressive.
What
he
did.
He
committed
lots
and
lots
of
mines
of
cold.
He
participated
in
our
reviews.
He
addressed
all
the
commands,
so
he
did
amazing
job
and
thank
you
so
much
yeah
Constantine
Kaiser
thanks
Eliza.
Yes,.
B
A
A
B
A
So,
besides
that
we
have
a
sound
future
request,
so
if
you
go
to
vim
forms
repository
on
the
github
and
search
for
API
approved,
you
can
see
all
the
future
requests
that
we
approved
for
dotnet
5,
and
you
can
see.
Listview
group
will
receive
some
of
days.
We
will
add
tasks,
dialogue,
subtitles
and
footers.
For
ListView
group,
we
will
do
some
improvements
for
selector
for
a
track
bar
actually
I.
Have
it
open
so
the
track
bar?
A
A
That
means
that
this
feature,
if
you
would
like
to
be
a
contributor
into
vim
forms,
you
can
go
ahead.
Pick
up
this
task
implemented
yourself
and
actually
make
the
future
of
vim
forms.
Then
we'll
be
extremely
thankful.
We
will
invite
you
to
our
API
reviews.
We
will
work
with
you
to
make
help
you
with
any
questions
you
have,
but
you
will
be
the
owner
and
contributor
of
this
feature
to
mean
forms
and.
B
Alright,
so
we
had
a
few
questions
come
in
and
chat.
We
had
a
question
about
Linux
support,
just
to
be
to
be
clear.
Answer
of
the
Linux
support.
Dotnet
pours
its
Linux.
So
if
you
build
a
particular
workload
that
is
supported
on
top
of
that
net
core,
for
example,
asp.net
you
can
deploy
it
to
a
Linux
based
environment.
B
You
can
do
I
think
like
console
applications
if
I'm
not
lying
there,
but
basically
there's
a
certain
type
of
apps
that
we
support,
WPF
and
wind
forms
are
not
supported,
though,
on
Linux
or
Mac,
so
you,
you
can
only
run
them
and
windows
as
workloads.
So
those
frameworks
that
sit
on
top
of
that
net
core
are
not
ported
to
Linux.
If
that
makes
sense,
I
hope,
I
hope
that
answers
that
question,
and
then
there
was
a
you
know.
I
guess
a
good
point.
You
can
ask
us
a
question
that
we
asked
you
back
right.
B
It's
a
fair's,
fair
thing
to
say,
which
is
some.
Why
hasn't
Visual
Studio
moved
to
dotnet
core
Visual
Studio
is
very
complicated
and
we
have
all
sorts
of
our
own
sort
of
considerations.
Just
like
you
know.
Many
of
our
customers
have
various
considerations:
I'm,
definitely
not
trying
to
imply
that
Dartmouth
core
is
magically.
You
know
enabled
for
every
single
type
of
application.
If
you
have
something
that's
very
complicated,
that
has
lots
of
different
kinds
of
technologies.
You
know
has
15
years
of
history
and
lots
of
technical
complexity.
B
You
might
have
trouble
going
to
that
nut
core.
We
want
to
hear
about
it
because
we
want
to
understand
customer
scenarios.
We
we
understand
our
scenario
and
we
think
in
some
ways
we
have
some
unique
considerations,
but
we're
learning
from
ourselves
we'll
hope
to
learn
from
you
as
well.
So
that's
how
I
hope
to
answer
that.
Yeah.
A
I
see
there's
another
question
like
I.
Think
a
person
wanted
this
rhetorical
question:
why
do
we
need
to
be
informed?
So
we
have
WPF
and
UW
Pia?
Well,
that's
really
up
for
you
guys
to
choose
which
one
would
you
like
to
use
and
this
technology
is,
this
platforms
are
slightly
different
and
they
all
have
their
benefits
and
win
forums
provides
an
extremely
easy
getting
started,
experience
and
drag-and-drop.
What
you
see
is
what
you
get
very
a
comfortable
experience
with
the
designer
or
the
new
framework
and
the
kinetochore
designer
will
be
there.
We
are
getting
close.
A
Yes,
it's
really
find
the
right
tool
for
the
job
if
WPF
works
best
for
you
totally,
but
there
we
hear
many
customer
stories
where
VIN
forms
is
actually
better
and
they're
very
happy
with
this
platform,
and
that's
why
we
heard
back
a
few
years
ago,
like
don't
kill
it.
Please
make
sure
there
is
a
future
who
confirms
as
well,
because
that's
technology,
we
have
all
our
projects
running
on
and
we
don't
want
to.
We
wanted
a
future
for
our
project,
and
now
we
have
it
right.
A
A
B
All
right
so
with
that
I
would
like
to
show
folks
some
things
in
the
WPF
villages:
WPF
WPF,
uwp,
basically
the
sam'l
tooling
world,
and
talk
about
some
of
the
new
features
that
we've
been
working
on
things
that
are
available
today
in
16-5
things
that
are
available
in
16
6
preview
and
also
talked
a
little
bit
about
16
7,
where
I
can
so
with
that
I'm
gonna
share
my
screen,
so
I
can
show
folks
what
I'm
talking
about
just
a
little
bit
alright.
So,
hopefully
my
screen
is
showing
up
for
everybody
all
right
there.
B
A
B
Yeah
no
worries
I'll
move
my
window
slightly
more
to
the
right
just
so
it's
easier
to
see
all
right
so
with
this
I
want
to
talk
about
release,
notes,
it's
a
really
important
way
for
us
to
communicate
with
you
exactly
what's
going
on
in
terms
of
what
we're
releasing
every
single
release,
and
we
do
this
for
winforms
WPF
and
everything
else,
the
ships
as
part
of
Visual
Studio.
So
if
you
just
you
know,
never
look
at
release,
notes,
I
highly
recommend,
go.
Take
a
look
at
that.
B
It's
in
there
the
links
that
we're
sharing
as
part
of
this
session,
and
it's
pretty
easy
to
find.
If
you
go
to
Google
or
Bing
and
type
Visual,
Studio
release
notes
you'll
go
there.
I
want
to
point
out
that
release
notes,
have
a
current
branch
and
have
a
preview
branch
version
of
them,
and
the
current
branch
means
the
current
release,
which
is
16
5,
so
16
5
is
the
release
that
you,
if
you
currently
have
like
the
latest
production
release,
installed.
B
That's
what
you
have
installed
in
your
machine
and
in
that
release
we
shipped
a
couple
of
new
features
inside
of
Visual
Studio.
For
you
for
either
uwp
or
WPF
developers-
and
these
are
the
three
features
that
we
have
shipped
and
I-
want
to
just
mention
them.
The
very
first
one
was
a
really
popular
community
request
that
we
finally
got
done.
They
talked
about
it
before
it,
so
it's
not
super
new,
but
lots
of
people
I
still
find
don't
know
about
it,
which
is
drag
me
an
image
into
the
sam'l
code.
Editor
finally
generates
zamel.
B
That's
you
know,
that's
the
actual
image
tag
with
the
right
URL
to
the
image
internal.
You
know
project
reference
URL,
so
here
I'm
going
to
demonstrate
that,
and
so
in
Visual
Studio
right.
They
do
not
have
an
image
of
a
big
picture
of
my
face
and,
if
I
take
it
from
solution,
Explorer
and
I
drag
it
in
it
will
actually
create
the
image
and
they'll
have
the
source
set
to
the
right
image
path.
B
So
I
just
wanted
to
point
that
out
this
used
to
generate
a
disc
path,
like
literally
without
the
image
tag
when
you
used
to
do
this
drag
operation,
and
that
was
really
in
that
idea.
Our
customers
wanted
to
fix.
We
fixed
it.
Another
thing
that
people
wanted
to
do
was
the
ability
to
change
the
artboard
color
colors.
So
if
we
go
to
tools
options
and
we
go
on
their
environment,
then
we
go
on
their
fonts
and
colors
and
then
we
from
this
drop-down
select
zamel
designer
I
mean
settings.
B
These
settings
have
so
many
things
in
them.
Even
I've
sometimes
forget
where
things
are,
but
if
you
do
all
of
that,
you'll
find.
We
now
have
our
board
background,
which
lets
you
change
the
colors.
So
if
I
wanted
to
change
the
background
to
be
to
be
white,
checkered
I
can
do
that
right
there
and
then,
if
I
was
like,
oh,
my
god,
that's
horrible
I
can
go
back
and
I
can
say,
use
defaults
and
bring
it
back
to
to
the
theme
color,
but
basically
we're
we're
giving
you
more
control.
B
Hopefully
this
is
making
it
better
for
some
folks
that
one
in
the
different
color,
if
it's
still
not
doing
what
you
wanted
it
to
do,
we
want
to
hear
from
you.
We
want
to
hear
your
feedback.
Let
us
know
if
something
isn't
right,
alright,
so
those
were
a
couple
of
things
there.
We
also
changed
well
made
an
improvement
for
the
zamel
designer
which
wasn't
working
for
projects.
B
You
can
write
in
to
chat
right
now,
something
that
you
want
us
to
look
at,
but
really
the
best
best
way
to
get
us
feedback
is
always
this
button
right
here
in
the
top
right,
a
visual
studio,
the
send
feedback
button
send
feedback
button.
Envious
is
the
thing
that
route
directly
to
me
in
my
team.
We
triage
all
the
tickets.
You
can
have
a
suggestion.
You
can
have
a
bug
when
you
press
that
button.
We
understand
a
little
bit
more
about
the
version
of
Visual
Studio.
B
You
you're
using
the
version
of.net
core
doesn't
framework
you're
targeting,
so
we
get
a
little
bit
of
telemetry
about
your
kind
of
general
setup
of
your
application,
but
we
don't
get
a
copy
of
your
project,
so
your
code
is
safe
with
you
and
if
we
need
help
we'll
reach
out
to
you
and
ask
you
for
maybe
more
more
reproduction
type
scenario.
Information,
but
please
use
that
button.
B
We
truly
look
at
this
every
single
day
and
seatback
comes
in
and
it's
really
the
main
way
that
we
can
address
feedback
in
an
organized
fashion
and
understand
how
folks
are
doing
so.
Please
keep
that
feedback
coming
so
with
that
I'm
gonna
go
on
to
some
more
features
and
talk
about
preview
features.
So
if
you
look
at
the
preview
release
notes
which
I
have
opened
here,
we've
been
shipping
and
something
in
every
single
preview
release.
B
So
I'm
gonna
go
back
for
time,
starting
with
tv1
and
talk
about
what
we
did
in
preview,
1,
so
preview,
one
of
16-6
we
added
a
brand
new
setting
for
hard
reload
scenarios.
This
is
something
that
people
they
use,
how
to
reload.
So
what
is
Samuel
Harvell
ode?
It's
you
have
the
app
running
and
you're
changing
the
samo
in
the
file
and
the
saml
is
reflecting
immediately
those
changes
and
you're
running
up,
and
so
it's
a
real
time
editing
feature.
While
your
app
is
running
letting
you
change
them.
B
Oh,
there
was
a
couple
of
scenarios
where
people
were
having
trouble
with
this
feature
because
they
needed
to
change
multiple
different
files.
At
the
same
time,
you
know
sorry,
multiple
different
things
within
a
file
at
the
same
time
before
it
became
valid
zamel.
So,
for
example,
if
you
needed
to
change
both
the
in
lines,
ammo
and
it's
part
of
a
resource
in
the
page
of
zmo,
you
couldn't
you
couldn't
make
those
changes
immediately.
You
have
to
make
one
make
the
other
and
sometimes
will
break
your
running
application.
B
We
were
also
actively
working
and
trying
to
make
the
designer
a
better
experience
for
editing's
animals.
So
one
of
the
things
that
we're
previewing
is
something
called
suggested
actions
we've
had
this
as
a
preview
feature
since,
since,
like
sixteen
five
I
believe
is
the
first
time
we
shipped
it.
So
it
continues
to
be
a
preview
only
feature
you'll.
Never
you
won't
find
in
the
released
version
of
visual
studio
until
we've
truly
are
done
and
there's
so
many
things
changing
in
this
feature.
It's
still
there
for
a
preview,
but
it's
a
feature
that's
really
powerful.
B
Today,
it
works
for
WPF
and
UWP
controls
the
the
ones
that
are
listed
here
in
box
controls
only
today
it
will
be
extendable
for
partners
eventually
we're
working
on
that
story.
That
then,
will
allow
partners
to
actually
add
settings
to
their
controls
in
here
too,
and
the
idea
behind
suggested
actions
is
in
line
with
the
designer
when
you
click
on
a
control,
you'll
be
able
to
expand
the
view
which
will
have
all
sorts
of
things
that
we
know
that
are
very,
very
common
to
your
to
your
application.
B
So
for
a
text
blocks,
it's
really
common
to
change
things
like
background
brush
the
name
for
image
control.
You
might
want
to
set
this
the
source
property.
So
these
are.
These
things
are
really
common
actions
you
might
want
to
take
against
the
control
and
we
are
working
to
expand
this,
to
include
more
properties
and
more
actions
to
actually
like
add
a
new
tab
to
a
tab,
control
or
do
other.
You
know
multi-step
operations,
so
we're
trying
to
bring
them
to
be
super
accessible
to
you
as
a
developer.
Let
me
show
you
an
example
here.
B
So
I
have
a
button
in
my
application.
If
I,
if
I
click
on
the
button
swimming
screen,
share
and
then
break
anything
here,
one
second
put
this
back
as
always
demos.
Let
me
reopen
that
up
sorry.
This
is
just
my
my
local
machine.
Craziness.
There
you
go
so
here.
I
have
a
button.
I'm
gonna
drag
it,
which
is
the
thing
that's
something
I
would
do
and
they're
in
the
real-world
application,
but
like
I'm
dragging
just
so,
you
can
see
it
here.
B
Clear
and
I'm
gonna
click
on
this,
a
Dorner
and
based
on
clicking
in
the
door.
It
shows
me
all
the
common
properties
that
we
know
fruit.
Fruit,
Elementary
people
are
changed
the
most
in
terms
of
these
controls.
So
it's
based
on
real
data
and
we're
trying
to
make
these
things
accessible
to
you.
You
can
come
in
here
and
you
can
use
a
color
picker
to
change
the
text.
Color
you
can
go
in
and
you
can
add
a
name
of
the
control
button
button.
B
One
in
this
case
we
might
want
to
not
make
it
enabled
by
default.
We
might
wanna
change
the
cuttin.
The
content
of
the
button
to
say
start
instead
would
be
the
default
button
text.
So
all
these
things-
yes,
you
can
do
them
in
zamel,
yet
as
you
can
do
them
in
property
inspector,
but
we
know
that
this
is
super
useful
to
make
it
possible
to
folks.
So
that's
a
feature
we're
excited
about
as
well.
B
Next,
if
we
started
going
up
our
previews,
if
we
go
to
preview
two
of
16:6
in
preview
2,
we
shipped
only
one
one
new
thing,
which
was
tool
box:
support,
form
you
get
packages
with
multiple
visual
studio,
manifest
files.
So
this
is
more
for
extensibility
improvements.
So
I
just
wanted
to
point
it
out:
it's
not
something
I'm
going
to
demo,
but
if
you,
if
you
are
a
vendor,
that's
working
on,
you
know
working
against
our
extensibility
endpoints.
This
is
something
you
should
check
out.
B
We
we
put
release,
notes
that
Beaufort
sort
of
like
regular
customer-facing
features,
but
also
when
we
change
extensibility.
We
put
it
in
release,
notes
to
make
sure
folks
know
things
are
changing
all
right.
So
next
I'm
going
to
talk
about
preview
3,
which
was
the
last
preview
with
it,
and
what
are
the
new
features
here?
So
there's
a
a
jerky
vault
in
the
packaging
wizard
integration.
This
is
really
great
for
uwp
developers.
They
want
to
start
putting
their
certificates
directly
in
a
jerky
vault
and
then
using
them
as
part
of
the
packaging.
B
Wizard
flow
I,
don't
have
a
demo
for
this,
but
this
I've
seen
a
demo.
It
works
great.
If
this
is
a
scenario
you
care
about,
it's
it's
here
for
you
and
please
give
us
feedback
of
it's
working
well.
We
also
have
two
other
features.
One
of
them
is
something
that
oil
is
going
to
talk
about
on
indie
a
little
bit
later,
so
I'm
going
to
skip
this,
but
we
are
trying
to
make
the
new
designer
that
we
have
for
Dartmouth
core
available.
The
framework
developers
and
oiler
will
tell
you
all
about
it.
B
So
I'm
gonna
talk
about
the
last
feature
here,
which
is
another
improvement
to
Zaman
hot
reload
and
live
visual
tree.
One
of
the
things
we
heard
from
customers
were
that
they
were
valid
scenarios
where
people
would
f5
into
debugging
more
than
one
zamel.
Application
is
part
of
the
solution,
so
they
have
a
solution.
The
solution
has
multiple
projects
and
they
want
the
tools,
the
hard
reload
tools,
the
live,
visual
tree
to
work
against
that
configuration.
B
B
Is
you
would
start
the
second
instance
of
uwp
app
or
you
would
launch
multiple
WPA
ffs,
for
example,
and
your
app
would
attach
the
very
free
visual
studio
it
would
attach
to
the
very
first
thing
that
started
basically
so
as
a
race
conditions,
whatever
whatever
won
the
race,
that's
where
we
attached
and
you
had
no
easy
way
to
attach
to
the
other
application
sort
of
as
a
well-defined
UX
inside
of
our
experience.
So
now
we
just
attach
to
everything.
B
That's
starting
as
part
of
your
debug
session
and
I
can
demonstrate
that
pretty
easily
here,
I
have
two
WPF
applications.
You
know
nothing
special
about
a
really
simple
stuff,
so
I'm
gonna
go
to
my
solution.
I'm
going
to
click
set
start
a
project
and
I'm
gonna
set
multiple
multi,
multi,
starter
projects
and
I'm
gonna
say
start
for
both
of
them,
so
they
both
started
when
I
hit
f5
I'm
gonna
hit
a
5,
I'm
gonna
start
running
the
application,
and
now
I
have
two
WPF
apps
that
are
starting
and
a
different
screen
here.
B
So
I'll
drag
them
over
just
to
show
you
here
they
are
and
what
would
happen
before
is
only
one
of
these
applications
would
get
the
in
app
toolbar,
the
one
that
allows
you
to
do
things
such
as
select
the
control
in
the
saml
and
select
it
in
the
live.
Visual
tree
and
right
now,
you'll
see
that
it's
working,
because
we
have
actually
two
applications
that
are
attached.
I'm
gonna
drag
the
s
in
case
we're
still
having
that
issue.
Where
were
cut
off
and
I'm.
Just
gonna
drag
it
slightly
over
here.
So
here
it
is.
B
We
were
attaching
to
process
number
one
process
number
two.
We
give
you
the
process
ID
the
file
name
of
the
executable,
and
then
we
give
you
the
the
library
little
tree
below
it
and
because
it's
all
kind
of
the
same
architecture
by
enabling
this
we've
enabled
hard
reload.
So
it
doesn't
matter
which
zamel
you
change,
for
which
app
it
will
update
and
all
the
tooling
of
this
in
app
toolbar.
That
appears
on
the
top
of
your
app
will
work
as
well.
B
B
As
far
as
I
can
remember,
in
terms
of
like
saying
when
this
is
actually
coming
to
visual
studio
and
when
I
say
coming,
of
course,
things
are
subject
to
change,
we're
making
a
best
effort
to
make
it
happen,
but
our
hope
is
the
16-7
preview,
one,
the
next,
the
next
version
of
Visual
Studio,
basically
that's
coming,
will
include
those
mo
binding
improvements
page
and
it's
available
today.
As
an
extension,
if
you
install
the
extension,
when
you
have
binding
failures,
the
binding
failures
will
be
still
shown
in
the
output
window.
B
The
way
they
normally
are
today,
but
will
also
appear
in
this
much
more
optimized
searchable
sortable
window.
That
allows
you
to
sort
of
have
a
lot
more
control
over
seeing
your
bindings
fail,
and
this
is
feature
that
I'm
really
excited
about.
Then
it's
coming
in
the
in
16-7
preview
one
fingers
crossed.
Hopefully
it
will
make
it
and
we're
excited
to
announce
that
that's
the
first
feature
that
I
can
talk
about
for
the
future.
So
that
concludes.
B
A
Alright
and
now
I
think
I
can
talk
to
new
zamo
WPF
designer
for
dotnet
framework
projects
right
so
exciting.
Right
now
you
don't
reckon
consolidating
the
resources
around
the
single
codebase
and,
as
you
probably
know
at
the
present,
we
have
two
different
code
bases
for
our
demo.
Designers.
One
is
the
old
one
for
dotnet
framework
projects
and
we
have
a
new
one
for
the
net
core
that
is
based
on
isolation,
surface
architecture,
and
what
does
it
mean?
That
means
that
the
designer
surface
runs
outside
of
visual
studio
process,
and
that
is
a
new
yorky
textured.
A
We
came
up
a
few
years
ago,
for
example,
and
it's
improved
it's
much
better
and
now
we're
trying
to
bring
all
that
goodness
to
dotnet
framework
project
as
well.
So
what
we
are
intending
to
do,
you're
intending
to
switch
the
designer
to
the
new
extensibility
model,
and
so
that
it
will
be
identical
to
our
dotnet
core
designer
and
that
will
give
dotnet
framework
project
support
for
64-bit
configuration.
It
will
give
better
startup
performance,
improved
stability
and
all
the
new
features,
and
there
is
one
new
feature
already
available.
A
It's
called
suggested
actions
that
you
can
see
in
preview
and
many
more
to
come.
So
if
you're
a
developer,
do
not
using
extensibility
of
Visual
Studio,
it
probably
won't
affect
you
much,
but
you'll
get
all
the
benefits.
But
if
you
are
developing
third
party
controls,
if
your
control
vendor,
if
you're
using
extensibility
of
Visual
Studio
in
any
way,
you
will
have
to
update
your
code
to
interact
with
a
new
extensibility
model.
A
Good
news
is
that
if
you
already
made
that
update
for
dotnet
core
project
now
you
can
just
reduce
that
code
and
we
believe
that
it
will
be
almost
like
100%
reusable.
So
now
you
don't
have
to
have
two
code
bases
either
you
can
just
use
the
dotnet
core
approach
and
it
will
be
easy
to
maintain
on
the
one
source
and
this
preview
is
already
available
in
Visual
Studio,
starting
from
16.5.
Let
me
share
my
screen
and
show
you
how
you
can
enable
it
so
in
Visual,
Studio.
A
You
can
go
to
tools,
options
here
in
environment
preview
features,
you
can
see
new
wpm
samel
designer
for
dotnet
framework,
and
you
can
click
that.
Then
you
will
need
to
restart
your
visual
studio
and
you
will
be
running
the
new
designer
for
dotnet
framework
locations.
So
go
ahead
test
it.
Let
us
know
what
you
think
at
this
moment
we
are
working
with
control
vendors
to
make
sure
they
are
with
their
controls,
work
well
with
the
new
designer.
A
So
we
will
wait
till
all
of
them
are
fully
supporting
the
new
model
and
under
then
we
will
probably
make
the
switch
until
then
it
will
be
available
in
the
preview,
but
the
main
version
will
be
the
old
version
to
make
sure
we
don't
break
any
of
control,
vendors
and
yeah
I.
Think
now,
I
can
move
and
talk
about
our
community
news
right,
yeah.
B
There's
one
the
question
Chad
that
I
wanted
to
address
and
also
say
thank
you
for
liking.
My
background.
This
is
a
something
that
Microsoft
teams
actually
brought
in
for
us.
This
is
not
something
I
selected
like
on
my
own,
like
I,
didn't
find
this
picture,
but
I
selected
it
from
a
list
of
pictures
available.
B
So
if
you
use
Microsoft
teams,
hopefully
at
some
point
you'll
have
this
feature,
it's
really
awesome,
but
to
address
the
comments
in
the
chat
that
was
asking
about
the
future
of
like
how
people
should
think
about
which
framework
to
select
should
they
choose
the
BPF
own
or
WinForms
for
future
projects.
Or
is
this
discouraged?
B
So
I
would
not
tell
anybody
as
default
like
this
is
the
way
you
should
build
for
Windows
when
you're
building
a
desktop
applications.
It's
a
much
more
convoluted
conversation
right,
so
basically
make
a
decision
that
that's
right
for
you
today
and
go
build
an
app.
That's
that's
always
my
recommendation.
Yeah.
B
B
So,
from
the
community
perspective,
I
wanted
to
point
out
a
new
video
that
was
put
out
by
the
app
console
team.
The
app
console
team
is
a
Microsoft
team
that
consults
with
customers
on
various.
You
know
things
they
try
to
improve
about
their
projects.
So
if
a
customer,
for
example,
and
is
somebody
that
has
you
know,
support
contacts
of
Microsoft
and
they're
having
some
kind
of
trouble
moving
their
app
forward
or
optimizing
some
part
of
their
application
and
some
of
the
newer
technologies.
B
These
folks
are
great
resources
and
they're
also
really
active
people
in
the
community
they're
on
Twitter.
They
make
videos,
they
go
to
events
and
they
speak
at
events,
so
I've
run
into
a
lot
of
the
people
on
this
slide.
Mike
Sebastian
and
Matteo
have
all
been
really
great
partners
to
the
product
team
in
that
sense,
and
they
just
put
together
a
video
that
came
out
in
April
this
month
and
the
video
talks
three
topics:
it's
about
taking
your
existing
applications
and
modernizing
certain
aspects
of
those
applications
we
have
Mike
talks
about.
B
You
know
modernizing
user
interfaces.
We
have
sebastian
that
talks
about
improvements
that
are
coming
in
when
UI
3
and
we
also
have
matteo
that
talks
about
the
devops
experience.
So
it's
a
video
I
highly
recommend
it's
it's
a
longer
video,
it's
an
hour
23,
but
it
you
can
think
of
it
as
three
smaller
videos
and
you
can
only
watch
the
topics
that
you're
interested
in.
If
that
makes
sense
for
you,
but
I
watch
the
whole
thing.
It's
really
excellent,
so
go
check
it
out.
The
link
will
be
in
the
show
notes,
all
right.
A
So
this
is
an
article
written
by
oh
sorry
to
minimize
you
written
by
guy
Baker,
and
this
is
a
person
who
is
super
passionate
about
accessibility
and
he
has
an
article
on
how
to
make
accessible
features
in
European
forms
application,
and
here
he
basically
walks
through
the
entire
process
of
building
the
app
and
enabling
all
accessibility
features.
But
another
great
thing
he's
comparing
this
experience
of
building
it
in
vim
forms
with
his
experience
on
WPF.
A
So
there
is
another
article:
how
to
build
a
WPF
app
that
is
accessible
and
it
talks
about
all
the
go
resize
in
high
contrast,
theme
and
so
on.
So
I
would
highly
recommend
checking
it
out
and
he
is
very
passionate
about
this
topic.
So
if
you're
curious
about
any
accessibility
scenarios,
he
would
be
willing
to
talk
to
you
to
address
your
commands.
If
you
have
any
requests,
how,
with
other
accessibility
features
you
would
like
to
see
implemented,
he
will
be
all
very
open
for
feedback
and
requests
for
new
demos,
apps
and
so
on.
A
So
engage
with
this
person.
He's
amazing
and
group
big
thanks
to
him
for
making
this
content,
for
he
informs
in
WPF,
I
think
and
they.
Let
me
stop
no
I
go
stop
sharing
my
screen
and
that
I
wanted
to
talk
about
our
open
source
contributors
right.
So
we
had.
We
received
so
much
help
from
open
source
community
and
we
are
infinitely
thankful
for
that
and
just
a
few
people
I
wanted
to
mention
that
contributed
to
bin
forms
repository.
A
I
also
have
a
contributor.
There
is
no
name
or
last
name,
a
his
github
handles
handle,
says
gee
Petro
and
your
she
is
helping
with
cleanups
and
enhancement
and
persistently
contributing
to
be
informs
platform.
So
big,
thank
you
for
that,
duuude,
which
we
have
anyone
in
your
mind
who
you
would
like
to
say.
Thank
you,
I
cannot
have
you
yeah
go
ahead,
yeah.
B
Brett
lagunas
has
been
helping
us
a
lot
of
things,
he's
been
working
in
prism,
of
course,
for
the
longest
time,
but
also
helping
us
on
other
projects
as
well.
So
big,
thank
you
to
Brian
he's
he's
in
our
email,
friends,
I
promised
every
week
and
he's
always
helping
with
something
so
huge
contributor
to
our
community.
Yes,.
A
Big
thanks
to
Brian
and
I
just
wanted
to
say
that
if
you
guys
are
creating
PRS
or
feature
requests,
I
can
speak,
especially
for
the
enormous
repository
and
you
don't
see
enough
feedback.
That's
because
we
are
overwhelmed
with
the
designer
right
now,
because
we
want
to
make
sure
it
was
there.
We
are
trying
to
get
it
s
soon
as
possible
out,
but
once
we're
done
with
it,
you
will
see
a
lot
more
feedback
and
movement
in
our
app
in
forums
repository
in
terms
of
accepting
PI's,
reviewing
teachers
and
so
on.