►
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://theurlist.com/desktop-standup-2020-06-25
A
A
B
So
I
get
the
pleasure
to
work
with
this
awesome
team,
including
you
so
I'm,
a
p.m.
that
spans,
both
the
desktop
tooling
for
zamel
applications
for
the
BPF
and
uwp,
but
I
also
more
recently
and
now
working
in
the
zamarons
forms
project
and
the
in
the
future
is
gonna,
be
called
the
Maui
project.
So
basically,
wherever
Zemel
developers
are
I
have
probably
something
to
do
with
it.
At
this
point,.
A
A
A
So
basically,
great
event
happened
just
a
few
weeks
ago.
I
believe
that's
a
second
annual
event
hosted
by
uwp
community
discord
server
and
that's
when
all
you
WP
developers
were
preparing
their
applications
and
they've
released
in
Microsoft
Store.
It
12
new
applications
and
two
refactored
updated
apps,
and
this
is
the
website.
Go
ahead,
check
it
out.
It's
a
extremely
interesting.
A
Yeah,
so
here
you
can
read
about
briefly
about
you,
WP
community
and
the
one
chillin
themselves,
but
also
it
has
the
descriptions
of
all
the
applications
so
they're
great
apps,
such
as
chapter
fire.
That
allows
you
to
add
titles
to
your
mp3
files
files
yeah.
If
we
go
lower,
there
is
file
you
WP,
which
is
a
modern
file.
Explorer
that
pushes
the
boundaries
of
the
platform
is,
as
they
say,
and
there
are
many
more
just
go
ahead
check
it
out.
I
was
very
amazed
by
this
event
and
that's
the
second
time
it
happens.
B
Definitely,
thank
you
so
much
for
everybody
that
you
know
participate
in
these
events.
It
really
it
really
warms
our
heart
to
see
that
the
tools
being
used
to
create
such
great
applications,
because
that's
what
it's
all
about
yeah
awesome,
alright
well
today,
is
all
about
sam'l.
So
I'm
gonna
do
a
bunch
of
talking.
We
wanted
to
just
kind
of
come,
come
back
around
and
talk
about
the
most
recent
preview
releases
of
what
we're
calling
16-7,
which
is
the
most
recent
preview
release
of
Visual
Studio.
B
But
what
I
find
is
still
some
people
don't
know
exactly
what
I'm
talking
about
when
I
say
like
Visual,
Studio
preview
release
or
Visual
Studio
preview
features
that
are
experimental,
so
I
want
to
talk
about
that
just
for
one
second,
and
then
we'll
jump
into
the
actual
content
that
I
meant
to
present.
So
I
just
want
to
point
out
that
Visual
Studio
comes
and
let's
call
it
different
flavors
you
can
download
the
stable
version
or
you
can
download
the
preview
version
and
since
2019
at
least
2019,
maybe
this
was
20.
B
You
know
the
previous
version
as
well
2017,
but
definitely
is
in
2019.
You
can
install
it
side-by-side,
which
means
you
can
have
the
stable
version
and
the
pre-release
version
on
the
same
machine,
and
you
know
Astra
gastric.
Most
things
just
work.
Just
fine
I've
never
had
an
issue
because
of
it,
but
it
certainly
keep
it
keep
your
eyes
open
just
in
case,
but
when
you
do
have
the
preview
version
installed,
you
get
access
to
everything
that
we
put
into
our
release
notes.
B
So
when
we
start
to
say
that
16/7
is
released
as
a
preview,
we
call
that
preview
1
and
after
that,
we'll
have
many
other
previews,
typically
somewhere
between
3
4,
5
previews
and
after
that
they'll
be
a
release
candidate
and
after
that
the
feature
will
be
called
released,
at
which
point
a
new
preview
will
come
out
of
the
next
version:
16
8.
So
right
now
we
have
preview
1
out
preview,
2
out
in
preview
3
out.
B
So
that's
why
I'm
kind
of
clicking,
through
these
release,
notes
to
show
you
that
each
release
has
its
own
sections
but
they're
cumulative.
So
at
the
end
of
the
day,
as
long
as
you
install
preview
3,
you
have
all
the
previous
features
as
well,
and
one
other
last
thing.
I
want
to
point
out
about
preview
features.
B
Is
that
when
you
install
a
preview-
and
you
know
you're
in
a
preview
by
the
top
right
preview
indicator
in
middle
studio,
you
don't
get
all
the
features
turned
on
out-of-the-box
and
that's
because
we
consider
some
features
as
experimental
or
just
not
ready
for
for
consumption.
As
a
thing
we
push
on
you
even
in
a
preview
release.
So
the
way
you
can
find
those
those
particular
features.
Is
you
go
to
options,
so
you
go
to
tools,
options
and
then
you,
click
on
preview
features
right
here.
B
So
there's
a
preview
feature
section
under
environment,
and
this
previous
section
is
an
ever-growing
list
of
things
that
we'd
like
for
you
to
try.
A
lot
of
things
can
just
be
turned
on
and
used.
Some
things
require
restart,
for
example,
there's
a
lot
of
features
in
here
that
are
actually
preview
features.
So
please
check
it
out,
and
you
know
we're
constantly
looking
to
hear
feedback
from
you.
So
if
you
find
something
in
this
experience
that
I
just
showed
you
confusing,
please
file
the
vspeed
back
issue.
We
are
listening
and
trying
to
make
this
experience
better.
B
So
now
I'm
going
to
switch
gears
back
to
the
main
presentation
that
I
was
going
to
do
today
and
talk
to
you
about
the
new
features
inside
of
16
7,
so
we'll
lean
pretty
heavily
into
like
the
most
recent
things
that
we've
released,
but
I
just
want
to
go
through
it
from
the
beginning
to
say
that
in
preview
1
we
started
to
release
our
new
features
in
here.
So
if
you
scroll
down
to
our
WPF
uwp
tooling,
section
you'll
see
that
we
added
a
color
visualizer
for
four
samples.
B
There's
this
little
color
indicator
next
to
all
those
mo
tags
and
in
each
preview
we
make
it
support
more
and
more
scenarios,
and
this
is
something
that
supported
across
WPF
and
Zemin
forms
today
and
we're
having
some
performance
issues
and
the
uwp
side.
Unfortunately,
so
we're
still
working
to
get
that
up
and
running,
but
we
are
working
and
making
sure
this
is
universal
for
all
the
more
code,
editing
experiences
on
Unwin
doze
of
these,
where
I'm,
representing
things
today,
we
also
shipped
a
new
data,
binding
failure.
Experience
if
you
missed
this,
definitely
check
it
out.
B
This
is
our
ability
to
show
you
if
a
binding
has
failed
in
your
application
through
a
new
icon
in
the
in-app
toolbar
and
a
new
panel
which
you
can
pin
at
both
runtime,
and
you
know
when
you're
not
running
the
application,
and
you
can
see
in
real
time
or
in
retrospect
to
the
previous
session.
What
bindings
have
failed
that
normally
would
only
be
accessible
in
the
output
window,
so
this
is
like
two
features
combined
into
one
experience.
If
you
click
on
the
icon,
the
panel
opens
up.
B
So
it's
really
easy
to
go
from
one
to
the
other,
and
if
you
have
no
binding
failures,
this
icon
just
stays
neutral.
If
you
have
at
least
one
or
two
as
of
preview
3,
we
actually
show
you
the
number,
and
hopefully
that
gives
you
some
helpful
information
to
make
sure
you
don't
miss
any
unexpected
binding
failures.
I
have
a
few
apps
where
a
few
binding
failures
are
expected.
But
if
the
number
goes
above
that
then
I
know
something
is
wrong.
So
that's
how
I
keep
an
eye
on
it.
A
B
A
B
So
another
feature
that
I'll
show
you
here
is
suggested
actions
for
the
designer
something
actually
and
I
are
working
on
together.
It's
the
ability
to
click
on
any
of
the
controls
that
are
in
box
for
the
visual
studio,
I,
think
text
blocks
buttons
grids,
etc,
and
we
provide
you
most
commonly
use
properties
right
there
for
the
light
bulb
experience.
B
This
is
a
feature
that
we're
putting
quite
a
lot
of
kind
of
behind-the-scenes
time
into
making
sure
it
works
for
the
great
and
it
has
extensibility,
and
one
of
the
new
features
we
are
actually
starting
to
release
is
the
extensibility
framework
for
it.
So
control
vendors
will
be
able
to
add
their
own
information
into
here
as
well.
So
you
can
get
support
for
third
party
controls,
not
just
first
party
controls
which
we're
gonna
optimize
for
in
the
beginning.
So
this
is
a
preview
feature
right
there
and
finally,
the
last
one
from
preview.
B
One
was
something
they
were
continuing
from
previous
releases,
in
fact,
suggested.
Actions
has
been
around
also
since
the
previous
release
you'll
find
that
we
keep
some
preview
features
from
release
to
release
so
that
that's
normal,
and
so
we
feel
ready,
they're
gonna
stay
on
their
feature
flag.
We
don't
want
anybody
to
get
to
get
affected
by
a
feature.
We
don't
think
it's
ready
so
another
one
of
these
preview
features
is
the
new
sam'l
designer
for
dotnet
framework
applications.
B
This
is
the
way
that
you
sort
of
get
the
numerous
features
that
we're
building
into
the
designer
for
a
dotnet
framework,
WPF
project.
If
you
installed
that,
if
you
use
that
net
core
new
designer
is
the
designer,
if
you
have
that
net
framework,
it's
an
actual
different
codebase,
it's
a
different
designer
and
we're
working
to
make
the
new
one
available
for
all
developers.
The
reason
why
it's
under
preview
is
because
we
suspect
that
there
are
some
things
we'll
still
break.
B
So
please
help
us
test
this,
and
let
us
know
if
something
is
breaking
and
also
third-party
vendors
need
to
do
some
work
to
support
the
new
designer
so
think,
like
control
vendors,
tell
them
I,
can't
resist,
expressed,
etc.
Right,
just
those
are
three
random
examples
where,
if
they
don't
do
the
work,
it's
not
gonna
work
in
the
designer.
B
B
A
B
Right
so
then,
in
preview,
two
of
16:7,
we
added
an
extensibility
improvement,
so
I'm
not
going
to
go
into
that
detail.
It
affects
usually
a
smaller
number
of
people.
But
if
this
release
note
here
is
interesting,
you
definitely
check
out
some
of
the
links
that
are
in
the
release.
Notes
for
it
under
the
section,
so
you'd
have
to
go
under
scroll
into
the
preview
to
release
notes
here.
So
it's
kind
of
buried
in
there
eventually
it'll,
be
all
together
in
the
final
release
note,
and
then
what
we're
here
to
talk
about
today.
B
Let's
talk
about
what
is
in
preview
3,
so
typically
some
insider
baseball
in
digital
studio.
We
don't
we
try
not
to
ship
new
features
in
every
single
preview,
because
if
we
did
that
we'd
never
stabilize
and
therefore
we
typically
ship
the
first
2
previews
with
features
that
are
new,
potentially
or
experimental
even
and
then
we
spend
the
rest
of
the
previews
and
with
these
candidates
stabilizing
in
this
case
we
had
a
little
bit
more
time
because
of
scheduling
nuances.
B
So
we
decided
to
allow
preview
3
to
have
new
features
and
that's
why
today
I'm
going
to
talk
about
some
features
and
only
shipped
in
preview,
3
of
16:7
for
visual
studio.
So
with
that,
let's
go
into
what
the
features
are
and
I'm
going
to
say
that
these
are
the
release
notes.
The
descriptions
are
here:
I
just
wanted
to
point
that
out,
but
I'm
just
going
to
show
it
to
you
right
in
the
product
and
we'll
make
sure
I,
don't
miss
anything
by
looking
at
release,
notes
towards
the
end.
B
So
when
you
go
ahead
and
switch
to
my
little
application,
so
first
of
all,
this
sample
app
that
I'm
building
I'll
put
a
link
to
it
at
the
end
into
our
show
notes.
This
is
an
open
source,
app
that
I'm
just
building
for
fun
to
demonstrate
design
time
data
one
of
our
newest
features.
But
before
I
talk
about
that
particular
feature,
let
me
show
you
something
else
that
I'll
just
use
this
sample
to
help
me
demonstrate
so
I'm
gonna
start
Visual,
Studio
and
I'm
gonna.
Show
you
a
bunch
of
small
improvements.
B
So
one
of
the
improvements
that
we
did
was
recently
as
well.
Let
me
take
a
step
back
and
say
this
is
this:
is
a
journey
we've
been
improving
the
in-app
toolbar
and
when
I
say
in-app,
toolbar
I
mean
this
toolbar
at
the
top
of
the
application.
We've
been
improving
it
for
now
many
many
releases
we're
constantly
trying
to
make
it
better.
Please
keep
your
feedback
coming
if
we're
making
your
life
worse
and
not
better.
B
If
you
have
ideas,
but
basically
some
of
the
things
we
added
in
the
past,
we're
like
the
ability
to
move,
it
sometimes
would
block
something
that
you
wanted
to
see
or
some
button
that
you
wanted
to
click
on,
so
we
made
it
movable
and
it's
collapsible,
but
in
this
release
we've
made
it
shorter
and
the
reason
why
we
made
it
shorter
is
before.
If
it
was
in
this
position,
it
would
typically
go
just
big
enough
to
start
blocking
both
buttons
and
menus
below
it.
B
It
was
kind
of
really
annoying,
so
we
decided
to
shorten
the
bar
and
by
shortening
it
you
know
WPF
up
now
it
stays
in
in
the
title
bar
assuming
you
have.
You
know
you
have
a
kind
of
standard-looking
up,
but
if
you
don't
it's
collapsible,
so
if
you
click
collapse,
we
hide
the
hide
reload
text.
We
keep
the
icons
how
to
reload
available
unavailable.
That's
a
relatively
new
icon,
binding
failures
in
the
buttons.
Then
you
click
it
again
and
we
hide
it
into
a
little
little
dot.
B
And
then
you
can
click
expand
and
it
expands,
and
they
also
want
to
point
out
it's
really
easy
to
remove
this
toolbar
temporarily.
If
you
want
to
instead
of
the
live
visual
tree,
there's
a
show,
runtime
tools
and
applications
button.
If
you
click
that
button
it
goes
away
and
then,
if
you
click
it
again,
it
comes
back.
So
there
you
go.
That's
a
couple
of
really
small
improvements
there.
Now
next,
what
I'll
demonstrate
is
colors,
one
of
the
things
that
we
you
know
talked
about.
B
B
B
A
B
Yes,
one
second,
so
we've
made
improvements.
One
of
the
things
that
we've
improved
in
this
release
is
that
we
support
resource
dictionaries.
Now,
that's
the
that's.
Why
I
found
this
color
visualizer
at
least
now,
but
then
well
I'll
jump
down
there.
You
go
so
there's
the
screenshot
of
what
it
should
look
like.
We,
we
actually
in
the
next
preview,
already
have
even
more
bug
fixes
for
where
this
works.
B
Definitely
very
useful.
I
find
I
love
having
these
features.
I've
used
extensions!
That's
given
this
to
me
now
and
this
thing
is
gonna
be
in
the
box,
so
there
you
go.
We
have
that
now
and
with
that
I'm
going
to
switch
over
to
my
next
demo,
which
is
another
app
which
again
is
open
source,
just
a
little
test,
app
that
we
built
out
and
we'll
put
a
link
in
there
Shawna
to
it.
But
this
app
simply
is
is
a
is
an
app
of
broken
things,
broken
dreams.
It
has
nothing
but
binding
failures.
B
The
whole
point
of
this
application
is
to
show
the
binding
failure,
experience
and
nothing
else
so
in
in
the
past,
like
let's
go
back
to
the
world
before
we
had
all
of
this
technology.
Let's
turn
off
our
in-app
toolbar.
Let's
go
back
to
our
output
window.
This
was
the
experience
you
had
before
we
added
this
feature
before
we
improve
binding
failures.
B
You
would
have
no
indication
right
now
when
your
app
is
running
unless
you
visually
noticed
it
in
your
running
application
that
some
binding
has
failed
and
then
your
output
window
would
have
that
information,
but
to
get
to
it
you
would
be
scrolling
through
and
you
hopefully,
wouldn't
miss
binding
failures
like
I'm,
showing
you
right
here,
but
it's
easy
enough
to
miss.
It
there's
quite
a
lot
of
information
here.
So
we've
tried
to
make
this
better
by
first
of
all,
adding
this
icon
into
the
in-app
toolbar.
B
If
you
see
it,
as
you
see
when
I
highlight
the
icon,
I
get
the
total
number
binding
failures
and
then,
if
I
want
to
get
to
the
new
experience,
that
shows
that
failure,
information
and
detail
the
way
I
click
on
the
icon
and
now
I
have
a
panel
that
I
could
pin
it's
a
regular
panel
that
respects
all
of
your
decisions.
If
you
close
it
or
if
you
pin
it,
it
will
stay
where
you
want
it,
and
this
panel
has
all
the
details
of
what
is
happening.
B
B
Now,
as
you
see,
every
these
binding
failures
is
unique
at
this
point,
but
if
I
click
add
another
person,
if
you
are
going
to
be
unique
to
that
execution,
but
some
are
actually
identical
failures
within
the
template,
that's
generating
over
and
over
again,
so
we're
combining
them.
So
we
have
a
count
that
shows
you
the
company
combined
failures.
That
means
this
failure
happened
at
least
twice
already,
and
then
you
can
uncombined
by
clicking
here
to
uncombined,
so
that
you
can
see
all
the
information
in
the
exact
order.
Did
it
happen?
B
It's
totally
up
to
up
to
your
preference.
Then
we
have
a
search
capability.
So
let's
say
you
just
cared
about
backgrounds
like
you
wanted
to
see
which
of
your
backgrounds
were
failing.
You
can
just
add
to
our
background,
in
other
words,
any
of
these
fields.
It
works
with.
We
also
added
a
right-click
menu.
Now
you
can
copy
the
original
error.
You
can
copy
any
of
the
columns
you
can
reset
the
columns.
B
You
can
clear
the
filters
resetting
of
the
columns
was
very
useful
because
you
could,
you
can
move
the
columns
around
and
you
can
change
their
size.
You
can
really
break
this
thing
to
be
kind
of
weird
and
if
you're,
if
you
like,
metopes
I,
didn't
mean
to
do
all
of
that,
you
can
reset
columns
and
now
all
your
columns
are
back
and
your
data
is
not
lost
when
we
do
that
operation.
So
we're
really
fine-tuning
to
try
to
make
this
thing
better
and
better.
B
We
also
added
something:
I,
don't
have
a
demo
for
handy
here,
but
we
added
a
capability
to
show
you
a
call
Stax
within
certain
kinds
of
exceptions.
I'll
make
sure
this
app
gets
updated
to
show
that
as
well
in
the
future,
but
basically
it'll
be
like
a
little
expand
there.
You
can
click
on
it
and
it
will
expand
out
to
show
you
the
binding
failures
there
as
well.
A
B
Really
good
question,
and
fortunately
no
you,
you
would
think.
Well,
that's
an
obvious
feature,
but
doesn't
the
team
just
add
it?
The
reason?
Why
is
because
we
had
to
make
some
hard
choices?
We
could
have
said
that
we
can't
make
this
experience
perfect
and
therefore
we
could
have
just
not
built
it,
but
we
over
over
a
course
of
doing
you,
know
customer
interviews
and
a
lot
of
brainstorming
in
the
team
talking
to
partners.
We
realized
that
this
experience
has
value,
even
if
it's
not
100
percent,
let's
call
it
the
80%
of
the
experience.
B
That
is
we're
letting
you
know
that
a
binding
is
failed
with
the
icon.
I
know
this
is
super-helpful
of
people
that
miss
failures
and
it
causes
them
delay
to
resolve
the
issue,
and
we've
made
the
visualizing
and
sifting
through
the
failures
easier.
That's
the
goal
of
this
panel,
but
they
click
to
code,
requires
source
source
info.
That
is
the
technical
term
for
knowing
where
an
error
is
in
source,
which
file
which
line
on
line
number
which
column
you
know
hold
that
information,
and
today
we
don't
have
it.
B
We
are
literally
literally
parsing
the
output
window
data
and
when
we
detect
the
binding
has
failed
in
the
output
window,
we
are
making
it
be
visualized
better
by
showing
an
icon
and
showing
this
this
grid
and
over
time,
we're
hoping
to
work
with
various
frameworks
to
add
that
capability.
So
in
order
for
us
to
get
source
info,
xamarin
uwp
WPF,
when
you
I,
would
have
to
add
some
code.
Basically-
and
you
know
that's
that's
their
current
understanding,
at
least
like
we're.
B
Looking
for
creative
solutions,
we
haven't
found
one
that
we
would
be
happy
with
shipping,
but
basically,
once
that
happens
then
clicking
the
code
would
work.
We're
really
hoping
that
xamarin
will
be
the
first
place
where
we
do
get
that
work
completed,
that
we're
exploring
that
this
summer,
just
give
us
some
time,
hopefully
I'll
be
able
to
to
them
with
a
keen
ability.
But
we
we
want
this
feature
as
much
as
you.
One
of
the
things
that
we're
considering
is
adding
a
fuzzy
search
capability.
B
So
maybe,
if
you
double-click-
and
we
don't
know
where
sources
may
be,
for
some
of
these
errors,
we
can
figure
out
how
to
open
up
this
visual
studio
there
ctrl
F,
you
know,
search
feature
and
search
your
source
for
possible
matches
to
like
the
target
name
or
something
like
that.
Like
we're,
we're
exploring.
But
again,
like
everything
takes
work,
we
decided
to
kind
of
stabilize
this
first.
B
That
makes
sense
all
right
so
with
that
I'm
going
to
switch
over
to
a
feature
that
did
not
exist
until
16
7
preview
3,
the
most
recent
preview,
so
I
did
show
you
some
improvements
for
this
experience.
The
data
binding
that
shipped
in
preview
3.
But
this
is
an
existing
experience.
They
continue
to
get
refined
and
will
continue
to
be
refined
even
in
the
next
preview,
but
I'm
going
to
switch
gears
to
a
feature,
that's
completely
new,
which
is
our
design
time.
B
Data
I'm
really
excited
about
this
feature
because
it
really
opens
up
a
whole
new
realm
of
possibilities,
for
example
developers
who
are
building
desktop
applications.
So
let's
talk
about
what
is
designed
temp
data
before
I
get
into
nitty-gritty.
Basically,
it
is
a
feature
that
the
Zaman's
forms
team
put
into
there's
a
mo
demo
previewer.
First,
so
Zarin
has
had
this
feature
and
we
did
not
have
the
feature
and
when
we
were
doing
explorations
for
where
customers
were
less
than
satisfied.
One
of
the
areas
we
heard
from
many
customers
was
when
I'm
just
building
my
app.
B
So
you
just
want
to
have
a
decent
capability
to
make
your
app
in
the
designer
sort
of
look
more
real
so
that
you
can
change
the
sam'l
have
at
least
more
confidence
before
you
go
into
the
f5
inner
loop.
So
with
that
feature,
we
realize
that
we
should
add
design
time
data
support
the
design
team
head
as
well,
and
look
at
that
I
just
realized.
I
I
have
a
bug
in
my
title
there,
let's
get
rid
of
one
of
the
extra
cheese.
B
It
was
driving
me
crazy
and
there
you
go
so
yes,
a
design
temp
data
is,
is
that
feature
and
the
way
that
it
works?
Let
me
go
up
to
the
namespace
is
that
we
have
already
had
a
feature
in
the
jewel
studio
called
the
ignore
big,
normal
namespace
capability
and
we've
extended
it
beyond
were
what
it
supported
before
we
made
this
change,
so
we
used
to
have
the
data
context
that
you
could
mock.
B
So,
if
you're
willing
to
create
a
fake
view
model,
you
could
attach
it
to
your
view,
and
that
would
work
so
that
feature
we
haven't
made
any
worse
or
better.
In
other
words,
that
feature
still
exists.
You
can
still
add
a
fake
view
model.
But
what
we're
talking
about
is
like
before
that,
like
you,
don't
even
have
a
view
model
or
you
don't
want
to
bother
with
it
at
the
moment
or
you
just
want
to
try
something
like
you
just
want
to
see.
B
What
would
that
look
like
in
my
application,
without
going
into
the
point
where
you
to
generate
data
to
create
that
view?
So
we
added
this
capability
of
changing
any
single
property
instead
of
any
control
using
the
D
:.
So
this
this
in
your
current,
like
release
version,
if
it'll
stick
it,
this
will
not
work.
B
I
chose
that's
not
the
character
that
my
real
Apple
use
and
my
password
is
probably
never
set
in
my
zamel,
because
I
want
people
to
enter
the
password
for
real,
so
I've
added
this
design,
time
data
and
now,
if
I,
remove
it
that
goes
away
if
I
put
it
back
in,
it
appears
if
I
type
D
:
I
can
change
any
property.
So
if
I,
let's
say
I
want
to
make
the
background
red
there
you
go.
My
background
is
now
red.
Now,
it's
only
red
in
design
time.
What
happens
when
I
hit
a
five?
B
Well,
let's
take
a
look,
so
I
hit
a
five.
What
does
my
application
look
like
in
this
case?
My
app
has
no
real
data.
It
looks
really
really
empty.
So
now
my
designer
is
actually
richer
than
my
running
application
and
that's
what
we're
trying
to
do.
So,
let
me
show
you
some
examples
of
more
complex
scenarios.
Where
I
did
this
I'll
start
from
the
top,
because
there's
one
interesting
feature
that
I
really
love
actually
is
show
grid
lines
for
grids.
B
I
love
having
this
on
and
when
I
used
to
build
I
used
to
be
like
a
WPF
developer
for
real,
like
I
used
to
like
that
was
to
be
my
day.
Job
and
I
used
to
turn
this
on
and
occasionally
I'd
forget
and
check
this
in
and
then
my
real
app
would
have
a
grid
line
where
it
shouldn't
have
a
grid
line.
It
I've
done
that
at
least
twice
in
my
career.
So
now
I
can
say:
D
:
show
grid
lines,
and
that
will
never
make
it
into
my
running
app.
B
When
we
compile
an
application,
we,
when
we
find
the
D
:
property,
we
we
ignore
it,
we
don't
compile
it,
so
it
doesn't
make
it
into
you
into
your
real
application.
So
it's
really
safe
way
to
add
a
bunch
of
data.
It's
only
downside
is
it
makes
your
zamel
a
little
bit
bigger,
but
it
adds
so
much
capability.
Hopefully
everybody
will
enjoy
this
feature
from
that
standpoint.
So
that's
one
thing:
I
can
show.
B
So
D
:
should
work
with
any
anything.
That's
a
property,
including
attached
properties
like
we
after
you
type
D
:,
we're
just
giving
you
access
to
all
the
things
there
are
properties
attached
properties
afterwards,
I
download
my
sample
app,
give
it
a
try.
If
something
isn't
working
for
you.
Let
us
know,
then
one
limitation
we
have
today
is
that
this
is
not
yet
ready
to
work
with
third-party
control,
vendors
or
in
a
few
other
kind
of
niche
scenarios.
We
will
document
more
of
this
as
the
week's
go
on
with
this.
B
This
feature
is
very
hot
off
the
presses
and
we
have
a
couple
of
things
that
are
on
the
roadmap
versus
things
that
are
known
issues
that
will
be
resolved
in
the
next
couple
of
previews.
So
I
won't
be
able
to
answer
every
question
in
super
detail,
but
we
are
building
that
documentation
said
we'll
have
it's
up
somewhere
pretty
soon.
It's
a
good
question.
Alright,.
A
B
B
Of
25
and
let's
give
it
a
margin
of
10,
that's
what
I
do
for
all
the
controls
here,
just
kind
of
looks
nice
and
then
I'm,
gonna,
say
text
and
I'm
gonna
say
test.
So
you
could
ask
me
like:
why
did
we
need
a
D
:,
like
you
already
have
the
ability
to
show
text
right
here
like
this
works,
but
that's
not
real
world
right
in
the
real
world
when
you're
starting
to
build
an
application.
That
text
will
be
very
quickly
removed
with
some
sort
of
binding.
B
B
If
we
go
to
something
more
complex
like
lists,
once
again,
you
can
start
using
the
the
namespace
of
you
know,
system
to
start
adding
strings,
for
example.
So
here
I
have
a
list
view.
I
have
a
list
box
and
I
have
a
tree
view,
and
each
one
has
been.
You
know
has
designed
time
data
in
it
and
in
fact
the
list
view
has
an
item
template
selector.
And
if
you
look
at
my
item,
template
selector,
it's
really
simple.
If
it
detects
that
it's
Donavan
it
makes
it
makes
the
template
returned.
B
B
B
There's
a
public
enumeration
starting
to
look
more
even
more
real,
like
an
application
and
I'm
able
to
to
mock
all
of
that
up
under
a
fake
data
source
using
just
a
simple
array
from
from
you
know
the
X
name,
space
array,
extensions
and
then
I
can
create
the
model
right
here
in
line,
and
my
properties
window
actually
even
shows
me
all
the
probably
properties
of
that.
So
it's
really
really
easy.
B
If
there's
an
enumeration
look
at
that,
it
supports
dropdowns
from
the
properties
window
and
everything
so
I
can
enter
all
this
information
for
the
properties
window
over
here
and
then
I
can
create
as
many
of
these
as
I
want
and
they
start
appearing
now.
There
is
one
limitation
is
once
you
create
an
entity
in
here.
B
If
you
change
that
Anthony
and
today,
let's
say
I-
want
to
change
this
to
Steve
it
an
update,
because
there's
no
event
that
fires
to
say
that
this
entity
has
changed
to
the
sam'l
designer,
and
this
is
where
I
can
demo
another
feature:
we've
added
to
the
sam'l
designer
called
the
refresh
button.
This
is
a
feature
that
was
customer
requested.
B
If
you
click
the
button,
Steve
appears
because
we,
what
this
feature
actually
does
is
the
same
the
same
set
of
keystroke,
because
if
you
close
that
the
designer
and
reopen
it
so
it
flashes
for
a
second,
and
it's
actually
pretty
quick
for
for
these,
my
simple
views
and
then
the
views
gets
appeared
appears
and
it's
refreshed
now.
This
is
useful
for
some
really
complex
applications
or
this
kind
of
design,
time
data
limitation
scenario,
where
just
something
doesn't
update
that
you
want
to
see
if
it
updated.
So
now,
this
refresh
button
gives
you
access
to
that.
B
So
I
hope
I,
hope,
that's
a
useful
feature,
and
now,
if
I
go
through
some
more
examples,
we
have
plenty
of
times
where
we
want
to
see
controls
in
different
kind
of
states.
So
let's
say
you
want
to
see
what
your
app
looks
like
when
you
have
both
a
regular
button
and
one
button.
This
is
disabled
and
let's
say
this
is
a
real
app
where
you
have
two
buttons
next
to
each
other,
I
can
use
design
time.
B
Data
to
set
is
enable
to
false,
and
therefore
I
can
see
both
examples
and
my
up,
even
if
this
is
really
triggered
based
on
you,
know,
state
or
conditions
or
data,
etc.
So
that's
really
useful
and
again,
I
can
always
do
this
and
still
have
the
real
property.
Balance
is
something
that
is
real
and
concrete,
and
this
works
for
radio
buttons,
checkboxes
slider
controls
I
have
an
image.
So
this
is
an
image
that
is
inside
of
you
know:
folder,
that's
in
my
application,
so
yeah
I
have
to
carry
this
in
my
source
tree.
B
That's
that's
the
one
limitation
we
have,
but
it's
not
compiled
into
the
running
app,
and
this
image
appears
and
you
can
see
what
it
looks
like.
So
if
there's
a
binding
that
eventually
loads
a
real
image
from
a
data
source,
you
can
now
see
what
that
could
look
like
with
some
sample
images.
You
include
in
your
project
and
then
it
works
with
things
like
calendar
controls.
B
What,
if
you
want
to
see
what
your
calendar
looks
like
in
a
specific
year
month
for
this,
like
the
dates,
a
calendar
picker,
what
it
looks
like
when
you
set
a
date
here?
What
about
a
progress
bar?
You
want
to
see
what
a
particular
value
would
look
like
is
the
is
the
bar
big
enough,
small
enough,
etc,
and
even
for
things
like
you
know,
status
bars.
What,
if
you
want
to
see
what
a
certain
text
or
or
in
in
there
looks
like?
B
So
this
is
all
all
the
capability
that
we
have
today
and
we
really
hope
people
test
it.
It's
a
feature
that
we're
really
trying
to
make
great
before
we
ship
it
so
it'll
be
in
preview
as
long
as
necessary,
and
we
have
lots
of
things
we're
still
improving
and
it's
not
the
end
of
our
journey.
If
everything
goes
as
planned,
of
course,
sometimes
things
don't,
but
we
hope
to
even
add
more
capability
and
if
something
becomes
more
real,
we'll
talk
to
you,
but
I
hope
that
even
at
this
point
this
is
already
useful.
A
B
You
for
being
our
customers,
our
preview
channel.
It's
really
appreciated
best,
so
that's
it
for
me
for
today,
I
will
say:
oh
sorry,
I
do
have
one
more
thing
is
that
extensibility?
So
we
have
a
github
repo
for
extensibility
and
when
I
mentioned,
if
I
mentioned
this
earlier,
sorry
I
forget
if
I
did
but
suggested
actions
as
being
is
being
developed
in
a
way.
That's
extendable,
that's
the
feature.
I
talked
about
earlier,
where
you
can
go
to
a
common
control
and
visual
studio.
Let's
use
the
SEC's
blocks
text
text
box
as
an
example.
B
We
have
a
new
light
bulb,
you
click
the
light
bulb
and
you
get
all
the
common
properties
right
here
that
you
could
change
with
visualizers
of
some
of
them,
etc.
Really
useful,
really
useful
feature
really
early
in
development.
We're
still
working
on
it,
but
this
feature
is
gonna,
be
extendable
and
the
way
that
people
can
learn
about
the
extend
abilities
by
going
to
this
github
repo
called
sam'l
designer
extensibility,
where
we
put
all
our
sam'l
designer
related
extensibility
information,
and
that's
where
you
can
find
more
info
on
that
info
becomes
available.
A
B
A
B
If
you,
for
any
reason,
don't
don't
feel
that
comfortable
with
that,
you
can
always
go
over
Twitter
and
just
tweet
at
me,
some
information,
but
the
challenge
there
is
that
if
telemetry
is
required
for
me
to
understand
more
information,
I'm
gonna
have
to
bug
you
put
a
lot
of
questions,
and
sometimes
our
repro
ability
will
be
hampered
by
not
having
that
feedback
requests
officially
submitted.
So
I
I
recommend
the
feedback
mechanism,
but
if
you
just
want
to
say
that
you,
you
love
the
feature,
we'd
love
to
hear
from
you.
B
That's
really
helpful
a
lot
of
times
the
positive
gets
kind
of
lost
and
we
need
it
to
make
sure
we're
on
the
right
track,
but
also,
if
you
just
want
to
give
me,
you
know,
ask
a
question
and
give
me
some
feedback.
You
can
start
on
Twitter.
It
really
is
a
place
that
I'm
really
active.
So
I'll
try
to
answer
your
questions.
A
Thanks
thanks
Alex,
oh
and
yeah.
Please
report
future
requests,
that's
what
we
are
looking
at.
That's
how
we
prioritize
our
roadmap
and
agenda,
and
there
was
another
question
about
WPF
repository
and
that's
actually
was
something
that
I
wanted
to
talk
about
today.
But
we
are
going
through
internal
rewards
and
unfortunately
commit
didn't
help.
Us
was
like
what
we
planned
did
not
happen.
Yeah.
B
A
We
have
a
new
p.m.
on
WPF
platform
team
and
pre
maleeni.
She
will
be
our
guest
on
the
next
stand
up
and
by
then
the
WPF
platform
team
is
going
to
publish
the
roadmap.
It
should
happen
by
the
end
of
the
month
so
very
shortly,
and
she
will
talk
about
all
the
struggles
that
they
encountered
it
in
the
WPF
repo
and
about
their
new
plans,
agenda
roadmap
and
so
on
and
I
will
not
steal
her
content.
I
just
want
to
say
very
big.
Thank
you.
Everyone
who
reported
your
issues
who
suggested
pr's.
A
We
will
definitely
look
at
every
single
of
them.
They
technical
difficulties
due
to
which
we
couldn't
do
it
before
and
promoting
develop,
go
into
more
details
regarding
it,
but
please
keep
being
engaged.
We
will
definitely
get
to
every
single
PR
and
we
really
really
appreciate
your
help
and
both
on
WinForms
and
WPF
repositories.
It
was
a
great
help
from
your
side.
Thank
you
so
much
for
that.
Alright,
let's
look
through
the
questions
and
commands.
B
Yeah,
so
one
of
the
questions
that
came
in
was
well
I,
guess
a
suggestion
that
we
should
have
more
news
around
you,
the
BPM
blends,
so
so
this
this
this
stand-up
is
trying
to
capture.
You
know,
whatever
news
we
think
is
most
relevant
Morse
new
in
terms
of
like
tooling
ownership
between
Ola
and
I.
We,
we
are
the
PM's
their
own
things
like
the
blend
experience
tooling
for
uwp
and
WPF.
So
in.
B
Yeah,
it's
a
lot
so
yeah
we
won't
be
able
to
answer
every
question.
You
know
some
things
are
platform
decisions.
You
know
the
WP
team
and
Windows
makes
a
decision
we
we
can
do
we
speak
to
that
100%
and
that's
why
we
invited
guests
just
like
we're
talking
about
inviting
PM's
from
others
from
other
parts
of
Microsoft
and
all
that
complexity,
trying
to
kind
of
simplify
that
and
bring
it
to
you.
But.
B
A
It's
usually
the
last
Thursday
of
the
month
is
desktop.
Community
stand
up
so
please
join
us.
We
will
have
pre
Malini
talking
about
WPF
repository
and
WPF
platform
roadmap,
and
we
will
also
have
another
guest,
Jeremy
and
probably
Arthur.
They
will
talk
about
entity
framework
or
and
what
new
happen
and
that
I'm
very
excited
to
have
them
as
guests
as
well.
Yeah.
A
A
B
I
have
a
pretty
active
playlist
myself,
unspotted
ID,
that
I'm
like
I,
grew
up
on
alternative
and
rock
and
metal,
and
then
somehow,
in
my
like
late
20s,
I
became
a
fan
of
house
house
and
trance
and
techno,
so
that's
kind
of
where
I
am
nowadays.
If
you
really
want
my
playlist
I'm,
pretty
sure
I
can
find
a
way
to
shoot
it
to
share
their
earlier.
What
about
you?
What
are
you.