►
Description
Scott and Damian chat about reaching the milestone of 150 shows, upcoming changes to Windows Forms apps in .NET Core 3.0, and spend some time updating Scott's hanselminutes.com site to the latest 2.2.0-preview2 release, which leads to discussions about package and framework versioning, how to interpret various warnings and errors during upgrade, and finally getting the updated site successfully running on Azure App Service (and actually confirming it's running on the updated framework version).
A
Do
this
for
me
and
I
can
do
HDMI
to
to
show
everyone
what
I'm
looking
at
on
my
screen,
which
is
behind
the
scenes
here
now,
you
can't
see
my
screen
Scott
you.
You
are
looking
at
the
live
view.
Obviously
so
this
might
be
a
little
delayed
for
you
and
I
can
go
back
to
camera
in
me
and
I
can
go
back
to
your
screen
or
I
can
even
just
do
you
Scott
now
so.
A
B
B
A
A
B
A
A
I
could
do
this
and
then,
when
I
do
share
mine.
Obviously
so
I
can
do
this.
So
now
you
were
seeing
my
desktop
through
Skype
for
business.
This
guy
for
business
call,
while
you're
talking
to
me
on
a
team's
cold,
which
were
then
broadcasting
live
over
over.
Yes,
I'm,
a
different
machine
to
YouTube.
So.
A
And
I
can
see,
the
chat
is
the
first
time
so
again,
hello,
everyone,
I,
am
sorry.
This
is
four
years
into
this.
To
this
show
this
is
show
number
150,
and
yet
we're
still
learning
how
to
do
this
because
we
keep
changing
stuff.
So
this
is
my
first
time
using
the
what
is
it
the
YouTube
live
controlled
room,
and
so
this
is
a
brand
new
view.
For
me,
I
am
NOT
streaming
from
this
laptop.
It's
happening
from
our
dedicated
machine
over
here
in
the
studio,
but
because
we
just
finished
on
air
conf.
A
All
of
this
stuff
was
unplugged
and
we
had
our
very
contact.
Cameron
come
in
this
morning
and
rewire
everything
so
like
the
mics,
the
head,
the
head,
the
headphone
feedback,
the
stream
deck
the
screen
sharing
was
Scott.
Everything
was
disconnected
and
so
I
think
we're
good.
Now,
Scott
I
think
everyone
is
saying
they
can
see
us.
Everyone
is
saying
they
can
hear
us
and
but
I
apologize.
If
things
seem
a
little
clumsy,
even
though
it
is
show
150,
it
is
literally
show
150.
Is
it
really
I
believe
it
actually?
A
Is
this
time,
unlike
the
fake
one?
Last
time,
so
we
have
now
clocked
four
years,
and
this
is
our
hundred
and
fifty
show.
If
I
had
a
party
hat
I'd
wear
it.
If
I
had
something
suitably
festive,
I
would
I'm
looking
around,
because
there
are
props
in
here.
I
would
I
would
shake
it
or
something,
but
I
don't
have
anything.
A
So
we
just
have
to
believe
me
if,
if
Jeff
were
here,
he'd
have
a
button
that
you
could
push
that
would
like
streamers,
would
appear
over
the
top
of
the
feed
or
something
and
then
be
it
canned
applause,
because
he
demonstrated
that
for
us
last
time,
but
I
did
want
to
get
in
the
room
today.
I
wanted
to
really
try
and
make
an
effort
to
get
here.
A
A
Barry
Darren's
John,
Galloway
and
Shane
Boyer
I
believe
Wow,
who
are
all
there
and
I
believe
they
were
all
going
to
be
involved
in
teaching
the
workshop
this
time
round.
So
if
you
were
lucky
enough
to
attend
that
workshop,
I'd
love
to
hear
back
how
it
went
and
what
you've,
what
you
did,
I
think
Scott
I,
David
and
I
basically
took
a
year
off
traveling
this
year
and
presenting
and
whatnot.
So
we
didn't
go
to
any
of
our
usual
Frances
and
workshops
this
year.
B
A
A
We've
heard
of
quite
a
few
people
teacher
we
did
and
we
would
hope
to
get
more
people
to
teach
it
from
the
team
as
well.
We
are
I
think
the
workshops
do
for
a
refresh
personally
I
think
it's
been
through
two
iterations
now
and
I
think
it's
time
for
a
third
so
next
year,
because
don't
think
all
three
will
be
coming
on
the
scene,
2
2
will
be
out
by
then
and
3
will
be
released
next
year.
A
Sometime
I
think
we'll
update
the
workshop
to
have
some
forward-looking
pieces
as
well,
because
there
will
be
some
changes
in
3
to
do
with
that
composition
and
shared
frameworks
and
things
we've
kind
of
continually
refining
that
model
to
get
it.
You
know
faster,
tighter,
less
confusing,
all
that
type
of
thing
and
so
I
think
we'll
go
ahead
up
at
the
workshop.
Also,
we
have
any
features
that
we
have
health
check
switches
into,
to
which
we
should
be
showing.
We
have
the
new
API
convention
stuff,
which
uses
rosin
L
as
analyzers
to
help
you
build.
A
You
know
better
ap
is
that
our
correctly
coded
to
you
know
to
match
the
self
documented
swagger
or
the
open,
API
Docs
you
have
we
out.
We
have
better
integration
with
those
systems
now
and
we're
also
working
on
new
things
like
the
ability
to
authorize
your
API
is
with
integration
with
available
authorisation
services.
We
have
good
integration
with
Poli,
so
there's
a
lot
lots
of
more
stuff
that
we
want
to
be
able
to
talk
about.
A
We
update
with
the
templates
you
know
so
now
has
bootstrap
for
and
we
still
support,
bootstrap,
3,
etc,
etc
and
I'm,
probably
for
getting
a
whole
bunch
of
stuff
as
well.
So
if
you
haven't
been
to
one
of
our
workshops,
I
mean
I'll
recommend
it,
because
you
know
we
write
them
and
we
teach
them,
and
so
we
think
they're
great,
but
it's
generally
a
really
fun
time.
I
love
it.
A
When
Scot
shows
up,
we
get
to
have
a
little
bit
of
a
a
bit
of
fun
in
the
room
with
the
customers
who
have
paid
their
good
money
to
come
and
see
us,
and
we
get
to
often
dive
into
people's
apps
and
look
at
what
they're
doing
and
we
get
here.
We
have
some
really
good
frank
conversations
as
well,
because
we
have
people
bring
perspectives
that
may
be
new
to
us
or
yeah.
We
we
find
issues
with
the
product
that
we
haven't
found
before,
because
often.
B
It's
different.
You
mentioned
that
because
it's
really
people
come
thinking
that
they're
gonna
learn
from
like
on
hi.
We've
come
to
learn
from
the
people
who
built
the
thing
and
ultimately
you
end
up
learning
from
them,
because
they're
like
we
used
this
thing
that
you
built
in
this
totally
unexpected
way.
And
then
you
get
this
amazing
feedback
and
you
can
take
it
back
and
make
the
product
better.
Yeah.
A
So
that's
absolutely
valid
point.
The
other
thing
we
see
is
different
people's
environments
and
so
how
they
develop-
and
so
you
know
folks
will
rock
up
obviously
with
Windows
machines.
A
bit
different
versions
of
Windows
you'll,
obviously
have
a
whole
bunch
of
Windows.
10
you'll
get
the
the
windows
8
user,
who
is
still
there
and
then
a
smattering
of
people
on
Windows,
7
I.
Don't
think
we've
had
an
XP
person
yet
thankfully,
because
it's
not
supported
and
then
bu
you'll
get
the
Linux.
A
You
know,
lady
we'll
be
down
the
back
and
then
you'll
get
the
few
Mac
people
over
here
on
the
right-hand
side
and
etcetera,
etc.
I
mean
we
get
to
see
what
this
looks
like
in
a
room
and
everyone's
trying
to
use
the
product.
That's
cross-platform
in
a
different
IDE,
obviously
some
folks
using
PDS
some.
We
have
a
lot
of
people
who
like
to
use
vs
code.
We
might
have
a
vs
for
Mac
user
and
then
occasionally
we'll
even
get
someone
with
their.
A
You
know
a
quote:
unquote:
enterprise
laptop
that
is
locked
down
in
a
way
that
we
haven't
seen
before,
and
then
it
makes
some
weird
part
of
the
developer.
Experience
fail
because
we
say
oh
I'll
just
type
this
command
in
and
then
they
try
and
do
it
and
like
nothing,
works
or
they'll.
Do
a
restore
and
they'll
get
an
error
and
then
we'll
spend
10
minutes
trying
to
figure
out.
A
Why
they're
getting
this
error
we've
never
seen,
and
then
we
realize
this
because
they
have
an
internal
new,
get
feed
that
they
currently
can't
hit
because
they're
not
connected
to
the
VPN,
because
we're
on
hotel
Wi-Fi
and
that's
why
they're
all
their
restores
are
failing.
So
we
see
all
types
of
issues
when
we
actually
get
in
a
room
with
30
of
our
closest
friends
and
try
and
teach
them
how
to
use
the
product.
So
I
really
really
enjoy
doing
those
workshops,
and
also
you
know
it's
about
time.
A
David
and
I
put
together
a
new
talk,
because
we
haven't
done
some
new
content
in
quite
a
while.
It's
been
well
over
a
year,
so
we've
got
a
few
ideas
for
the
next
generation
of
one
about
interest.
Why
they're
interesting,
deep
dive
talks,
I
think
David
has
publicly
expressed
an
interest
into
a
lot
more
deep
dive
talks.
A
We've
had
good
feedback
on
the
ones
with
them
in
the
past.
We
did
a
really
entertaining
one
I
thought
on
Kestrel
a
few
years
ago,
which
we've
got
a
lot
of
good
feedback
about,
and
I'd
like
to
do
one
about
sort
of
some
of
the
design,
the
philosophies
behind
a
veneer
core
and
how
he
came
to
those
would.
B
B
A
A
B
B
A
A
I
certainly
hope
so,
but
I
think
it's
always
good
to
get
that
feedback,
because
you
know
different
perspectives
and
you
know
different
people
are
used
to
different
interactions
in
whatever
their
particular
group
is,
whether
it's
at
work
or
socially
or
whatever.
It
might
be.
Culture,
Oh
culture
and,
as
you
point
out
like
I,
think
it's
fair
to
say
in
the
team
that
we
work
in.
There
are
a
lot
of
strong
personalities
and
often
that
comes
you
know.
A
A
A
B
B
A
A
A
A
A
Should
be
this
one,
so
the
app
workshop
is
the
one
that
David
was
the
second
iteration
I
refer
to
that
David
and
I
put
together
where
we
build
an
app
and
so
I'll
go
in
to
source.
It
should
be
this
conference,
planner
yep,
so
this
is
it
here.
Oh
so
it's
a
different
organ,
so
I
couldn't
find
it.
So
thank
you
for
directing
me
to
the
web
site.
A
Okay,
so
yeah,
you
can
find
these
workshops
here.
So
getting
back
to
the
point
we
were
making
seven
minutes
ago.
It
is
time
I
think
for
a
new
iteration
of
this
workshop
and
we've
done
it
call
three
coming
out
and
they're,
obviously
being
you
know,
the
big
part
of
donek
or
three
being
the
announcement
of
WPF
and
WinForms
being
ported
to
run
on
dotnet
core
I
think
we
need
a
new
workshop
I
think
we
need
a
desktop
building
desktop
application,
those
desktop
applications
on
donek
or
three
workshop
yeah
I.
A
And
so
I
think,
once
we
having
public
bits
available
as
part
of
whatever
our
first
public
preview
is
and
I
think
yet
publicly.
We
have
stated
towards
the
end
of
this
year
or
early
next
year
as
kind
of
the
timeline
we're
looking
to
that
I
think
Scott
actually
announced
this
one
hunter
a
boss
announced
that
dotnet
concert
there
were
now
nightly,
builds
that
contained
the
the
desktop
UI
bits
for
folks
who
are
really
really.
You
know,
living
on
the
bleeding
edge,
so
yeah
so
I
think
as
you'll
see
over
the
next
few
months.
A
So
obviously,
as
part
of
that
we're
gonna,
we've
talked
about
zamel
islands
for
Windows,
10
and
WinRT
API
access
in
a
much
more
natural
way
inside
dotnet
call
three
for
those
types
of
apps
and
they're,
also
high
DPI
support
for
WinForms
applications,
which
will
come
obviously
with
new
things
that
you
have
to
do
in
your
app
like
when
you
move
an
app
from
a
non
high,
DPI
aware
environment
to
a
high
DPI,
aware,
environment,
you
are
very
likely
going
to
have
to
read
I'm
assuming
some
controls
they
won't
just
magically
scale.
Windows.
A
Does
that
for
you?
If
you
say,
I
am
NOT
high,
DPI,
aware
and
that's
why
you
know
some
things.
Look
blurry
and
something's:
don't
because
some
of
them
are
native
controls
and
some
of
them
aren't,
but
you
get
it
for
free,
whereas
when
you
say
no
I
now
now
high
DPI,
where
you're
gonna
have
to
do
a
little
bit
of
work
in
your
app
I'm
assuming
too
to
make
that
work.
Well,
so
you.
B
Know
I'm
running
now,
three
4k
monitors
to
your
with
your
urging
and
honestly
I
know
that
some
people
have
some
concerns
about
specific
apps.
But
you
know
now
that
office
has
been
updated
for
high
DPI
anytime
I
find
an
app
that
is
not
ready
for
high
DPI
I
can
usually
right-click
and
hit
hit
properties
and
update
it.
A
I
mean
I
wouldn't
go
as
far
as
saying
it's
pretty
easy.
Honestly,
I'm,
not
gonna,
speak
ahead
of
me
trying
the
experience,
and
so
it's
going
to
be
one
of
the
new
features
in
Donette
for
8.
There
will
be
some
additional
high
DPI
features
for
WinForms
and
then
in.net
core
3.
If
you're
using
WinForms
they'll
be
even
further
high
DPI
refinements,
we.
A
Wpf
has
been
high,
DPI
aware
since
the
beginning
right,
it
is
being
used,
device-independent,
pixels
or
dips
I
think
as
they
were
called
in
all
WPF
applications
from
the
get-go,
whereas
WinForms
was
very
much
pixel
oriented,
and
so
you
I
assume
in
there
there
will
be
the
windfarms
controls
themselves,
where
appropriate
will
be
updated
to
better
support.
High
DPI
awareness,
I
also
know
we're
getting
support
for
Windows.
A
Is
that
it's
a
better
support
for
high
DPI,
for
example,
if
you
have
an
application
that
has
multiple
windows
and
you
have
a
window
to
there's
a
child
window
of
another
window,
you
may
want
the
ability
to
have
a
child
window
have
a
different
high,
DPI
context
or
awareness
than
its
parent
window.
That
was
an
OS
feature,
because
WinForms
windows
are
windows
windows.
If
that's
makes
sense,
they're
needed
handles,
underneath,
though,.
B
A
Its
winds
right,
that's
right,
and
so
the
and
same
for
the
text
boxes
inside
your
wind
forms
and
those
types
of
things
right.
Some
of
those
controls
literally
map
a
map
to
very
native
windows
primitives,
and
so
you
get
some
stuff
for
free.
That
means
that
when
the
windows
changes
in
order
to
add
features,
the
wind
forms
has
to
change
in
order
to
either
expose
or
absorb
those
features
correctly.
So
you
will
get
different
Heidi
pipes.
A
Support
in
the
different
flavors
of
wind
forms,
whether
it's
on
dotnet
framework,
you
know
4,
7,
X
or
4,
8
or
on.net
core
3,
and
for
certain
things
you
will
have
to
potentially
make
changes
to
your
application
if
you're,
using
a
control
that
does
like
owner,
draw
and
I,
don't
think.
We've
ever
said
that
150
show
150
shows
and
here,
because
we
generally
talk
about
ASP
net,
but
we've
kind
of
gone
into
wind
forms
here.
A
The
window
is
200,
pixels
wide
and
I
want
to
be
this
wide,
so
I
mean
all
you
might
control
boundary
is
that's
why
I'm
not
going
to
draw
stuff
inside?
That's,
obviously
not
gonna
work
great
if
you're
now
running
at
150
percent,
but
back
to
your
point
about
high
GPI
does
quickly
yeah
I
run
to
4k
external
monitors
when
I'm
docked.
This
is
a
4k
panel
on
this
machine.
Obviously
much
smaller
than
the
monitor,
so
I
actually
run
a
mixed
dpi
as
well.
A
And
so,
when
I
move
windows
between,
why
just
dock
and
undock
and
Windows
naturally
flow
back
and
forth
between
them,
they
have
to
rescale,
and
you
can
tell
which
apps
have
done
the
work
to
to
be
become
very
high.
Dpi,
where
you
mentioned
office
recently
did
this,
and
so
they
can
actually
redraw.
As
you
move
Windows
from
screen
to
screen,
the
OS
can
now
say:
hey
window
you've
now
moved
into
a
different
dpi
context.
B
B
It
handles
things
pretty
well
like
it
just
it
keeps
getting
better,
so
I'm
not
trying
to
be
like
a
high
DPI
apologist
right,
but
I've
actually
written
blog
posts
about
how
badly
it
sucks.
Oh
yeah,
as
a
thing
yeah
but
I,
just
it
sucks.
So
much
less
like
I.
Don't
live
that
constant,
ongoing
pain
of
high
DPI,
so
I
love
that
we
are
investing
in
wind
forms.
Just
sometimes
you
just
gotta
get
a
button
on
a
page
yeah.
A
I
totally
agree
button
on
a
form
somewhere.
Absolutely
so
so
I
didn't
have
anything
specific
else
to
talk
about
today,
we're
just
kind
of
rambled
for
20
minutes,
but
hope
there's
been
some
interesting
information
in
there.
John
is
not
here
he's
actually
in
the
chat
today,
but
he's
not
on
the
stream.
So
we
don't
have
any
community
links,
but
I
am
more
than
happy
to
answer
people's
questions
because
we
have
a
little
bit
of
time.
Left.
A
I
will
just
say
that
I
hope
folks
are
trying
out
net
core
to
point
to
whether
you're,
using
HP
net,
core
dot,
Nick
or
global
tools
or
command
lines
or
entity
framework,
or
in
your
you,
WP,
apps
or
xamarin
apps
or
whatever
I
do
hope.
Folks
are
trying
out
the
previews
and
giving
us
any
feedback.
We
do
hope
to
have
a
third
preview
out
next
month
and
so
folks
who've
been
watching,
the
calendar
will
have
seen
us
do
the
preview
one
in
August.
A
We
do
preview
two
in
conjunction
with
net
conf,
which
was
roughly
a
month
later
and
we
hope
to
have
a
preview
three
month,
roughly
a
month
after
that.
So
it's
you
know
time
you've
been
a
week
and
so
give
us
another
three
weeks
or
so,
and
then
we'll
get
a
third
preview
out,
and
that
is
intended
to
be
our
last
preview.
Four
to
two
I
have.
B
B
A
A
B
A
A
B
A
A
B
A
A
A
B
A
A
And
it
came
with
so
this
is
a
new
piece
of
information
we
added
this
week,
so
I
did
say
when
we
talked
about
this
in
the
show
we
talked
about
how
we
were
gonna
start
adding
more
information
to
this,
and
so
make
this
page
like
the
the
be-all
and
end-all
of
where
you
find
what
version
of
what
so
we've
added
the
version
of
the
a
spinet
core
module.
So
you
can
see
that
there
now
it's
it's
a
spirit
core
is
module.
B
A
A
So
Christian
is
asking:
does
that
make
any
sense
to
one
401
maps
to
two
one?
Three
and
I
somewhat
condescendingly
answered?
Yes,
it
does
according
to
our
versioning
scheme,
and
so
we
do
have
a
doc
that
explains
how
this
versioning
works
and
I'd
tweeted
it
out
actually
last
week,
because
I
found
the
doc
and
I
thought
it
was
very
well
written
to
explain
this.
A
Some
folks
did
follow
along
our
whole
versioning
sort
of
journey
and
how
we
landed
here,
but
the
reality
is
is
that
we
do
apply
semver
somewhat
to
the
components
that
we
ship,
but
the
actual
installable
is
made
up
of
lots
of
different
components
that
are
made
by
different
teams
that
have
to
ship
in
different
places.
They
don't
just
ship
in
the.net
core
sdk
install
they
also
ship
separately
in
Visual
Studio,
for
example,
Newgate
ship
separately,
the
don't
SEL
I
ship
ship
separately,
and
so
we
can't
just
say.
A
Oh
it's
always
me
Oh
major
minor
and
patch
version.
So
the
branded
version
that
we
use
for
dotnet
core.
The
main
version
that
you
will
see
is
the
one
in
the
left-hand
column,
which
is
why
that
one
is
bolt
2
1
4
is
the
latest
version
of.net
core.
It
means
that
there
was
have
been
four
patches,
since
we
did
to
100,
which
was
the
last
minor
release
which
contained
features,
and
it
is
both
the
current
release.
That
is,
the
latest
release
on
the
current
train
and
the
supported
LTS
release.
A
So
what
we
have
committed
to
four
to
one,
the
SDK
to
one
300
moving
forward,
is
that
the
major
and
minor
of
the
SDK
and
the
runtime
will
always
match.
So
if
you've
got
dotnet
core
2.1,
you
need
a
2-1,
SDK,
okay
and
similarly
for
2
2
2
2
will
be
the
first
release
where
the
the
SDK
rolls
over
2
to
2.
At
the
same
time
as
the
runtime
does.
Ok,
because
we
cut
we
cook,
we
can't
retrospectively
fix
how
we
used
to
version
when
we
made
a
change.
A
So
the
big
number
that
you're
talking
about
on
the
SDK
that
402
that
effectively
is
codifying
all
the
same
level
of
changes
as
a
minor
and
a
patch
version
that
you
would
usually
use
to
separate
numbers.
For
so
what
I
mean
is
that
if
the
ACK
adds
features,
for
example,
they
may
add
a
new
version
of
C,
sharp
or
F
shops.
A
A
B
A
A
Correct
it's
exactly
what
it
is
and
that's
what
the
docs
actually
talked
about
and
they
show
the
type
of
changes
that
would
result
in
that
happening.
I
should
to
talks.
Maybe
we
yeah
sorry
there
is
it's
a
very
good
doc
if
you
just
I,
think
if
you
just
search
for
like
Microsoft
Doc's,
don't
make
call
versioning,
it
comes
up
as
the
first
result
and
it's
like
understanding
and
I'd
tweeted.
It
like
I,
said
last
week,
yeah.
B
A
B
B
B
A
A
B
A
A
A
A
B
A
A
And
you
also
set
notice
the
columns
there,
so
we
have
the
SDK
column
after
the
version
column
and
then
we
have
the
runtime
column
and
if
your
and
it
says
they're
building
apps
build
apps,
then
you
get
the
SDK
running
apps.
Then
you
get
the
runtime.
So
typically,
if
you're
a
developer,
you
just
install
the
SDK
if
you're
setting
up
a
server
or
setting
up
a
machine
that,
for
some
reason,
just
needs
to
run
an
application,
that's
framework
dependent
but
does
not
need
to
build
applications.
Then
you
would
obviously
just
get
the
runtime.
Oh.
B
A
Sits
on
top
it
sits
on
top.
Now
we
could
dive
into
that.
If
you
wanted
to,
we
only
have
so
much
time,
but
that
I
mean
that
that's
a
10-minute
conversation
there,
where
we
could
go
in
I,
could
teach
you
how
to
clean
up
previous
version
and
I
admit
it's
not
something
that
we
it
happens
automatically
today.
It
is
actually
a
problem
and
it's
something
that
we're
looking
to
address
in
the
next
major
version.
So.
A
A
A
So,
as
people
may
know,
and
by
the
dotnet
Corps
installations
are
side
by
side,
yeah,
don't
Nick
or
installations.
Well,
there's
a
bunch
of
different
reasons:
don't
make
or
installations
are
side
by
side
always,
and
so
we
never
remove
any
as
part
of
a
dotnet
core
installation,
because
we
don't
want
to
break
applications
or
remove
things
from
your
machine
that
does
the
current
default
we're
debating
what
we
want
to
do
for
reowww.
A
But
for
folks
who
are
on
the
vs
preview
channel
as
well
as
the
main
channel,
you
will
get
a
lot
more
versions
on
your
machine.
So
we
had
just
had
someone
comment
on
the
on
the
stream
that
they
have
a
version
to
1/500
preview
on
their
machine,
and
that
is
very
likely
because
they're
running
B
as
preview,
and
so
they
probably
have
a
15-9
preview
and
15-9
preview
will
ship
with
to
1
500.
A
So
you
don't
have
the
preview
channel
installed,
and
so
there
are
more
versions
than
what
you
see
here,
so
2
1
500
again
the
5
ticked
over
from
4,
because
it's
a
new
version
of
Visual
Studio,
which
means
there
are
new
features
in
the
SDK.
Even
though
the
runtime
is
not
changing.
So
it
moves
over
to
5
because
there
on
the
preview
channel,
they
have
a
2-1
500
preview,
you're
on
to
1/2
you're.
A
B
A
A
B
A
A
It's
nice
all
right
can
I
make
one
comment:
there's
a
couple
of
people
who
were
talking
about
some
errors.
They
have
been
seeing
in
their
applications
when
trying
to
update
all
those
errors
that
I'm
seeing
you
report
in
here.
Indicative
of
you
not
running
the
latest
version.
We
did
have
some
issues
with
the
very
first
version
of
one
one
Oh
and
to
one
one
that
caused
folks
problems
when
they
tried
to
update
NuGet
packages
that
were
related
to
a
spinet
call
in
their
projects,
two
versions
that,
for
whatever
reason
said
they
didn't
align.
A
You
either
get
a
warning
along
the
lines
of
a
package
downgrade
or
an
error,
and
it
can
be
very
frustrating
so
I
encourage
people.
Please
update
to
the
latest
versions,
of.net
core
as
they
come
out,
because
we
do
fix
these
issues
and
read
the
documentation
about
migrating
apps
from
202
to
1.
There
is
a
line
in
there
that
talks
about
removing
the
version
on
the
package
dependency
in
your
project,
file
for
Microsoft,
a
spinet
core
app
or
all,
if
you're
still
using
dot
all
and
that
will
make
those
errors
go
away.
A
A
And
that's
why
we
see
this
so
in
the
migration
guide
that
we
published
for
two,
oh
two
to
one
on
the
doc
site.
It
says
to
remove
that
version,
but
we
understand
a
lot
of
folks.
Don't
read
that
they
just
simply
change
the
TFM.
They
go
to
the
new,
get
dialog
and
say,
update
everything,
and
then
they
assume
they're
fine
right
and
then
they
fix
any
coding
errors.
They
have.
Oh.
A
So
you
should
remove
it
says
right
there,
the
blast
bullet
point
in
the
second
list
of
bullet
points,
scroll
up
scroll
up
scroll
up.
It
was
there.
Actually
they
remove
the
changes
in
the
to
one
version,
quick
way.
Well,
sorry,
now,
you're
right,
downs
and
you're,
absolutely
right,
I
think
it
was
the
other
list.
You're
right
there
will
be
one
there
about
removing
the
version
from
the
package
package
dependency
for
asp
net
cord
app
it'll
talk
about
removing
the
version.
This.
A
A
A
That
was
the
position
at
one
point
if
they
were
reading
github,
if
they
were
following
us
discussing
this
issue
on
github,
we
went
back
and
forward
over
a
whole
bunch
of
different
perspectives
on
this.
We
are
now
still
in
the
place
that
you
should
be
removing
that
version
and
letting
the
default
version
in
policy
apply
99
times
out
of
100.
Okay,
so
you
so
you've
got
the
worst
of
all
cases.
Here
you
have
pinned
the
version
at
the
earlier.
B
A
A
For
that
reference,
and
then
this
leads
to
the
next
set
of
issues
which
is
now
folks
are
a
little
confused
is
like.
Why
do
I
don't
have
to
put
a
version
on
that
package?
Well,
the
truth
is
because
there's
not
really
a
package,
it's
a
lie,
and
we
this
is
talked
about
in
Nate's,
blog
post,
which
talks
about
how
the
shared
frameworks
work.
A
A
B
A
A
A
B
A
B
A
B
A
A
A
A
B
A
A
You've
just
stumbled
onto
the
next
issue
that
this
design
currently
causes,
which
is
we're
hoping
to
improve
in
2.2.
If
you
have
a
unit
test
project
that
you're
using
to
host
your
a
spinet
core
application
or
reference,
your
a
spinetto
application
and
then
run
tests,
you
cannot
reference
the
shared
framework
the
same
way
and
it
causes
problems
so
shared
framework
references
like
that.
Don't
flow
transitively,
so
they
don't
just
flow
over
to
the
other
application.
So
you
need
to
add
a
reference
to
the
ethernet
cord
app
package.
A
It
used
to
work,
it
kind
of
works,
it
doesn't
work.
The
problem
is
the
reference
flows,
but
not
the
fact
that
it
represents
a
shared
framework.
And
so
what
will
happen
is
you'll
end
up
running
differently.
So
remember
when
you
run
an
app
on
a
shared
free,
a
framework
dependent,
app
I'm,
gonna,
flip
back
to
Jill
screen,
because
I
need
to
talk
for
a
bit
when
you
run
a
dotnet
core
application,
that's
framework
dependent.
That
is,
you
have
a
shared
framework
reference
like
dot
app
here
and
then
you
run
it.
A
B
A
Right
and
so
that
often
causes
issues
when
doing
unit
testing,
because
you
have
your
app
which,
when
you
run,
it
is
running
on
the
latest
patch
version
you
have.
But
in
the
unit
test
project
that
is
referencing
the
app
it
ends
up
running
on
the
version
that
flowed
transitively
into
it
from
your
app
and
that's
a
lower
version
than
the
one
that
you're
running
on.
And
so
we
had
lots
of
issues
where
people
struggle
to
get
the
versions
to
match,
or
they
literally
saw
behavior
differences
because
we'd
fixed
a
bug
in
the
runtime
version.
A
A
Good
I
am
that's
why
I
said
it
was
a
little
crappy.
We
are
looking
to
fix
that
in
two,
but
that
is
the
current
guidance
and
it's
again
it's
exacerbated
by
the
fact.
We
don't
have
a
unit,
a
template
for
creating
the
project.
Our
unit
tests
projects
ready
spin,
their
core
applications,
and
so
you
generally
have
to
figure
all
this
out
for
yourself.
Let.
A
A
A
B
A
With
what
with
what
know,
what
TF
m
that
that
means,
determinate
based
on
my
tablet
framework,
they
aren't
you
one,
do
you
want?
So
that's
going
to
run
on
two
one,
whatever
the
latest
patches,
which
is
what
have
you
got
installed?
Two
one,
three
two,
once
you
are
two
one,
two
is
the
latest
one.
You
have
okay,
so
then,
if
you
put
two
one
two
in
there,
that
should
now
ensure
that
your
tests
are
running
on
with
the
same
bits
and
is
what's
on
your
app
is
running
on
now.
A
A
B
A
A
B
B
A
B
A
Won't
run
it'll
build
and
then
you
won't
be
able
to
launch
it
so
yet
another
issue
with
the
current
design
of
how
we
use
package
references
to
represent
things
that
don't
combine
nougat
and
that
we've
learnt
that
lesson
very
harshly,
unfortunately,
and
as
how
our
customers
we're
working
through
how
to
incremental
e
change
it
without
breaking
the
world
as
much
as
we
can
in
the
minors
and
the
patches,
but
we
won't
be
able
to
fix
it
completely
until
three.
Oh
now,
generally,
it's
not
a
problem.
A
Once
you
get
your
project
set
up
correctly,
you
don't
have
to
worry
too
much
about
it
with
the
your
modular,
the
unit
testing,
which,
unfortunately,
you
do
have
to
keep
changing
that
version
as
we
do
patches
to
get
it
to
make
sure
it's
running
on
the
same
version.
Just
a
time
check
we're
51
minutes
in
so
I'm.
Sorry,
no
I
just
want
to
make
sure
that
we
know
almost
done.
Okay,
cool
all.
A
A
B
B
A
B
A
A
A
What
they
should
they
could
definitely
if
they
were
very
kind
to
us
and
allowed
us
accommodated
al
in
this
case,
a
middle
E,
bad
design.
They
could
special
case
those
that
those
two
package
names
the
marks
are
faced.
Many
called
our
app
and
Microsoft
Eastman
Accord.
All
they
can
say
hey.
You
know.
Our
guidance
is
different
for
these
packages.
Click
here
to
read:
Nate's
blog
post
to
really
learn
how
these
work,
but
we
do
intend
to
fix
all
of
this
confusion
around
how
so
frameworks-
and
things
were.
B
A
A
Can
I
double
check?
Do
you
have
a
global
Jason
for
this
project?
This
solution
specified,
let's
find
out
no
good.
So
that
means
that
you
will
automatically
roll
forward
under
the
latest
preview
SDK
that
you've
installed.
Otherwise
you
would
issues
here
so
now
you
don't
have
to
change
your
version
of
phrase
minute
quarter
app.
If
you
have
other
packages
here
like
extensions
to
http
poly,
we
may
have
done
a
new
version.
Does
the
code?
Let's
is
the
code
lens
thing
telling
you
that
there's
a
new
preview
version
of
Israel
way
to
say
show
me
well.
A
A
A
A
A
A
A
B
B
B
A
A
B
A
B
B
A
A
couple
of
comments
just
to
answer
them
here,
Jamie
asked-
is
that
no
longer
a
best
practice
to
use
global
Jason
Google
Jason
allows
you
to
pin
to
a
specific
version
of
an
SDK
I
personally
would
recommend
folks
do
that
when
they
have
to,
it
is
I,
don't
know
whether
it's
a
case
of
best
practice
to
use
it
or
not.
Some
folks
do
believe
it
is
always
best
practice
to
pin
to
an
exact
SDK
David.
A
Unless
I
have
a
very
specific
problem,
I'm
trying
to
work
around
because
the
SDKs
are
supposed
to
be
backwards
compatible,
we
definitely
should
not
be
breaking
you,
no
matter
how
new
the
SDK
versus
how
old
the
SDK
compatible
project
is.
The
other
question
was
Kyle
asks.
Why
is
this
being
done
in
vias?
Coders
are
just
an
exercise
or
something
oh
I.
Just
like
likes
me
as
guys.
B
A
A
A
A
B
B
A
A
I
see
I,
see
fair
point
back
to
my
original
call,
my
previous
comment
about
staying
on
head
and
how
there
are
pros
and
cons.
It's
nice
to
be
able
to
stay
on
head.
It
would
be
nicer
if
it
was
easier
and
more
automatic
to
stay
on
head
and
less
chance
of
things
breaking
when
you
do
so.
But
this
is
the
the
trade-off
that
folks
have
to
make
when
they
make
that
decision.
A
A
B
A
B
A
A
B
B
A
B
A
B
A
A
A
A
A
A
A
A
B
B
A
B
A
B
A
A
B
A
A
A
B
A
A
A
Do
so
we
do
have
a
side
extension
and
you
can
still
use
the
side
extension.
So
if
you
have
that
installed,
it
now
remember
once
it's
installed
it
takes
over.
So
that's
not
that
one
that
is
the
dad
is
a
different
extension.
That's
the
extension
that
lights
up
the
azure
integration
like
logging
and
that
type
of
stuff
easy-hold.
A
A
You,
if
you're,
if
you
publish
from
Visual
Studio
as
opposed
to
publishing
through
one
of
the
automation
mechanisms
it
will
deploy
that
extension
for
you
automatically
I,
believe
now
that's
convenient
yeah,
so
ok
or
you
can
do
a
self-contained.
So
if
you
install
that
word
of
warning,
it
will
take
over.
So
it
will
forcibly
now
run
the
apps
on
the
verge.
B
A
A
A
B
A
B
B
A
A
A
A
A
A
It
does
somewhere
I,
don't
know
where
it
is
yeah.
So
the
way
the
extension
works
is
that
it
hooks
the
site
startup,
which
is
what
you
can
do
from
an
extension
and
it
rewrites
the
application
host
config
file
I
believe
to
instruct
the
a
spirit
core
is
module
to
load
net
from
a
different
path,
and
that
path
is
in
the
extension
it
brings
its
own
copy
of
dotnet
call
with
ice,
and
so.
A
That
until
the
actual
thing
now
I
thought
it
did
so
it
either
suggests
that
I'm
wrong
and
it
doesn't
or
that
the
extension
doesn't
isn't
working
at
all
for
you
or
it
only
works
for
the
app
in
the
context
of
is,
and
not
the
remote
console.
It's
one
of
those
three
and
I'm
sorry
I,
don't
know
which
one
it
is
I'd
have
to
get
your
lame.
Can.
B
A
A
A
B
B
A
B
A
A
A
A
Nice
Christopher
says
that
regarding
x64,
he
heard
unless
you're
going
to
use
I
didn't
hear
it
less
using
the
memory.
X64
gives
you
access
to
more
memory
in
the
process,
and
so,
if
your
app
needs
to
use
more
than
say,
2
gigabytes
of
memory,
assuming
you're
even
running
on
an
app
service
plan.
That
gives
you
that
much
memory
and
the
reason
it's
interesting
is
because
service
currently
today
does
not
deploy
the
64-bit
version
of.net
core
under
the
covers.
But
you
can
still
use
the
64-bit
version
using
similar
techniques
to
what
we're
using
here.
A
You
can
install
the
64-bit
runtime
or
you
can
do
a
self-contained
deployment
or
you
can
use
Azure
app
servers
for
containers
or,
as
your
app
servers
for
Linux.
They
both
do
support
the
64-bit
version,
but
we
are
still
working
with
them
to
get
the
64
bit
version
deployed
and
I
might
be.
There
may
have
actually
done
it
already
or
maybe
so.
A
B
A
B
B
Different
I
am
running
Hanselman.
It's
the
podcast
that
you
should
all
subscribe
to
in
a
standard.
Medium,
ok,
I,
just
literally
outgrew
a
small
like
a
couple
months
ago,
but
I'm
running
16,
apps
I
couldn't
have
run
16
websites
in
a
small
right.
If
I
was
running
64-bit
right
and
there's
just
no
need
for
it.
For
these
little
like
baby
smash
and
right
different
silly
little
game
that
underlies.
A
A
separate
point,
64-bit
will
give
you
access
to
more
memory,
but
we
will
also
use
more
memory
for
an
equivalent
x86
app
inside
in
very
often
in
most
cases,
and
so,
if
you
just
wait
old
movie
for
a
bit
because
it's
better,
you
will
end
up
using
more
memory.
Even
if
you
don't
need
in
some
cases
right
now
to
be
fair,
there's
also
features
of
the.net
core
runtime
they'll.
Only
work
on
64
bit
like
the
garbin
I,
think
that's
still
true.
The
way
the
the
jitter
and
the
the
GC
is
written.
A
I
believe
that
there
are
differences
between
the
32-bit
and
64-bit
model,
because
there
are
different
instructions
available
and
they
can
give
you
some
advantages
or
disadvantages
as
well.
Typically,
you
don't
have
to
worry
about
those
things,
but
it
is
something
else
to
bear
in
mind
when
making
that
decision
input.
A
A
B
A
Ago
well,
well,
okay,
do
you
have
a
little
thing?
That's
telling
you
that
the
credentials
are
out
of
date
or
anything
like
that.
No,
if
you
put
on
the
plan
like
you've,
got
the
button
there
right
to
choose
where
you
want
to
deploy
it
to
the
target
that
all
works.
If
you
open
it
up
and
try
and
change
it
cuz
a
lot
to
authenticate
and
list
them
out
and
all
that
type
of
stuff.
So
it's
a
good
way
of
figuring.
Oh.
A
A
B
A
B
A
B
A
B
A
B
A
A
B
B
A
A
B
A
A
A
B
A
B
A
B
A
So,
on
my
side,
I
echo
this
information
into
a
comment
at
the
bottom
of
the
homepage.
So
I
can
just
look
at
view
source
and
see
what
the
runtime
version
is
look.
What
is
it
correct?
I
can't
see
its
you
need
to
zoom.
Look
at
that.
Look
at
that.
So
it's
running
down
there
XE
from
the
side
extension
folder,
so
it
worked
yeah.
A
A
A
A
At
the
bottom
of
the
page,
like
you
said
well,
I
have
this:
if
you
want
to
look
at
that
code,
I
have
that
in
fact,
I
actually
wrote
it
as
a
helper
I
think
in
its
Mike,
it's
more
complicated
that
but
I
wrote
a
bunch
of
code
in
the
live
ace
we
net
site
in
on
that
on
github.
That
shows
you
how
to
get
those
versions
and
echo
them
out.
So,
okay.
A
B
A
B
A
B
B
A
B
A
B
A
B
B
A
B
A
Called
diagnostic
pages
or
diagnostic
endpoints,
and
it
would
plug
into
it
with
the
ideas
it
would
plug
into
the
metric
system.
That
is
a
little
Manson
right
now,
so
it
would
give
you
details
about
GCE
and
CPU
and
network,
and
it
was
plug
into
health
checks.
What
did
you
fans
get
back
nice
all
right?
We
need
to
finish
up.
That's.
B
A
B
A
A
The
reality
is
that
you,
as
the
azure
app
service
infrastructure,
is
fairly
complicated
behind
the
scenes.
Yeah
it's
deploying
previews
to
them
is
a
cost
and
time
consuming
and
maintaining
those
we
made
a
choice
to
not
deploy
previews
and
to
give
people
other
way.
If
one
of
the
side
effects
is
that
we
can't
get
the
git
integration
to
work,
we
can
look
at
this
workarounds
that
people
can
apply
themselves
or
whether
we
can
update
the
extension
to
somehow
support
it.