►
From YouTube: 2021-11-03 meeting
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
I'm
just
pulling
some
things
up
since
paulo
isn't
going
to
be
able
to
make
it.
A
A
Okay,
well,
let's
go
ahead
and
get
started.
I
only
put
a
couple
of
things
in
the
agenda
but
of
course,
after
we
get
through
those
feel
free
to
bring
up
other
things
that
you're
interested
in
talking
about.
A
So
the
first
thing
is
want
to
take
a
look
at
the
prs,
so
we
got
two
in
flight,
so
the
first
one
is
about
running
the
tests
against
the
output
of
from
nuke
and
so
looking
at
those
changes.
A
I
I
think
they're
fine,
there's
a
couple
of
questions
on
there
that
I
brought
up
that
I
think,
might
be
interesting
for
other
people
to
think
about
and
if
they
have
ideas,
I
don't
think
that
there's
anything
from
stopping
us
from
dealing
with
those
ideas
later
so
mostly
just
calling
it
out
for
some
visibility
there,
and
then
I
don't
know
if
there's
anything
else,
to
bring
up
with
the
other
pr,
with
getting
the
test
to
run
on
get
up
actions.
C
C
A
A
Yes,
I
believe
apollo
already
updated
the
sdk,
so
I'm
gonna
move
that
to
done.
A
And
figure
out
how
to
mark
it,
as
done.
C
Are
you
trying
to
close
it
yeah?
So
it's
just
like
the
regular
issue,
so
it's
just
different
there's
like
a
done
cut
label
and
then
there's
actually
closing
the
issue.
So
we
can
just.
D
C
The
the
pr
that
did
that.
C
A
B
The
integration
tests
should
be
in
progress,
probably
now
yeah.
D
A
B
D
Yes,
the
additional
depths
and
the
runtime
store
will
like
resolve
most
of
our
issue
and
follow
asked
me
to
get
the
like
update
on
how
many
self-contained
apps
are
there
versus
the
framework
deployment
apps.
I
also
go
out
and
update
from
the
dotnet
team,
so
roughly
there
are
like
10
of
self-contained
apps
and
even
with
startup
hook
or
clr,
whatever
the
instrumentation
that
we
have
even
with
self-contained.
If
someone
tries
a
trimmed
self-contained
approach,
none
of
the
whatever
the
like
hooks
that
we
have
now.
D
It's
not
going
to
work
in
that
environment
so,
but
dotnet
clearly
told
us,
like
the
team
told
us
like
when
you
are
considering
something
consider
for
both
the
areas,
but
at
this
time
like
we
will
cover
most
of
the
customers
with
the
like
additional
dates
and
the
runtime
store,
which
is
already
present
for
the
framework
deployment.
The
only
thing
is
that
tracer
home
might
look
different.
D
A
On
a
similar
note,
with
the
work
that
that
the
two
of
you
are
working
on,
does
that
apply
to
any
framework
dependencies.
D
No
it
it
won't.
The
framework
entirely
follows
a
different
like
probing
in
like
a
dot
net
core.
If
you
look
at
it,
it's
always
the
highest
version.
It
takes
a
precedence
in
in
I'm
saying
in
dot
net
code,
but
in
the
classic.net
it's
always
the
whatever
is
the
direct
project
it
has
it.
It
takes
that
unless
and
until
the
time
it
finds
a
binding
redirect
or
some
way
of
like
the
event
which
handles
to
route
it.
So,
oh,
so
we
don't
have
any
mechanisms
like
for.net.
D
A
Okay
yeah,
so
I
bring
that
up
because
of
this
one
issue:
where
we're
we're
unable
to
to
load
because
of
a
missing
library,
that's
part
of
the
net
core
framework.
This
will
be.
A
Okay,
that
that's
good
to
know
so,
there's
no
dependency
there
on
needing
to
have
that
assembly
available
in
a
nuget
package
or
anything
like
that.
D
D
A
A
Great
well,
that's
all
all
I
have
for
this
meeting.
D
I
I
have
one
question
here
like
when
I
joined
earlier,
like
there
was
a
conversation
saying
that
that
will
be
a
beta
release
along
with
the
you
know:
dot
net
six.
Are
we
planning
still
to
release
something
next
week
or
do
we
like
our
release,
karen
scott,
like
updated
now,.
A
D
A
So
that's
a
question
in
my
mind
because
I
know
with
the
sdk
with
net
six
launching
they
can
take
a
dependency
on
the
g8
version
of
diagnostic
source
and
the
other
dependencies.
A
Which
means
that
we
could
then
update
our
dependency
on
the
sdk
to
use
the
ga
versions
as
well,
but
there's
still
some
some
work
being
done
on
the
sdk
side
of
things
to
get
metrics
g8.
A
D
So
the
reason
why
I
asked
this
because
I
asked
like
michael
to
let
us
slow
down
in
creating
the
pr.
The
reason
is
it's
going
to
bring
a
major
change
here
with
that
additional
dips
and
everything
folder
structure.
So
I
don't
want
to
get
that
merged
before
the
the
beta.
So
that's
the
reason.
You're
not
michael,
is
also
working
on
some
other
tasks
because,
as
I
told
him,
if
not
that
he
would
have
created
the
pr
right
now
or
the
repo.
D
So
we
can,
I
will
ask
him
to
create
a
pr.
Maybe
we
will
start
discussing
and
put
a
do,
not
merge
tag
and
once
the
beta
is
done,
we
can
take
this
changes
that
to
the
place.
A
Yeah
because
I
guess
there's
a
question
of
whether
or
not
that
should
be
part
of
the
beta
if
it
solves
some
of
the
problems,
because,
right
now
as
it
is,
we
get
errors
when
trying
to
monitor
an
asp.net
core
app
on
net
3.1
and
up.
D
Oh,
I
just
checked
that
investigated
that
issue
a
little
in
detail.
I
see
only
the
console
applications
are
impacted.
The
asp.net
core
app
still
works,
so
it
is
not
impacted.
Actually.
D
C
A
A
A
D
Because
I
just
looked
at
the
change
they
have
performed
in
the
sdk
also
so
they
are
just
including
the
whole
is
they're,
referring
the
whole
asp.net
sdk,
the
asp.net
core
sdk
in
the
asp.net
instrumentation
project,
especially
in
sdk
space.
D
So
that's
what
is
causing
an
issue
right,
so
it
should
definitely
not
happen
if
issues
should
not
definitely
happen
in
asp.net
core
and
that
that's
the
thought
I
had
and
did
that
investigated
in
that
angle
and
whatever
I
suspected
came
to
be
true,
but
if
it
is
not
like
I,
we
can
continue
our
discussion
in
that
issue
to
see
how
it's
here.