►
Description
We asked, and you listened! Nearly 4,000 developers responded to the EF Core 2020 survey. In this edition of the community standup, senior program manager Jeremy Likness will review the survey results and discuss how they impact the plan for EF Core 6.0. The team will be available to answer your questions live.
Community Links: https://www.theurlist.com/efcore-standup-2021-01-13
Featuring: Arthur Vickers (@ajcvickers), Jeremy Likness (@JeremyLikness)
#efcore #entityframework #dotnetcore
A
A
Hello
and
welcome
to
another
year
of
ef
community
stand-ups,
I'm
here
with
jeremy
and
shai,
and
we're
gonna
talk
this
week
about
the
ef
survey
that
we
did
just
before.
At
the
end
of
last
year,
we
asked
almost
4
000
people.
Well,
almost
4
000
people
responded
to
a
lot
of
questions
that
we
asked
about
how
you
use
the
f,
gore
and
jeremy's,
going
to
go
over
the
results
of
that
survey
for
most
of
the
session
before
we
get
started.
A
Let's,
let's
do
some
of
the
standard
things
that
we
do
at
the
beginning
of
each
stand
up
so
first
off
we
have
the
state
of
the
unicorn,
so
the
state
of
the
unicorn
this
week
is
basically
one
thing,
and
that
is
we
have
the
plan
for
ef
course,
six
out
there
so
there's
the
plan
is
in
our
on
our
docklight,
as
was
always
the
case.
That
was
this
case
for
five,
oh
as
well,
but
we've
also
created
sorry.
Let
me
find
the
right
screen
here.
A
We've
also
created
a
link
to
it
on
the
issues
page
so
on
the
issues
page
on
github
you'll
find
that
we
have
these
three
pinned
issues:
weekly
updates
ideas,
forget
demos
and
this
stand
up
and
then
announcing
the
plan
for
af
course,
six
zero.
So
this
post
is
a
brief
summary
of
the
things
that
we're
we're
planning
for
six
zero.
A
The
themes
which
we
have
highly
requested
features
performance
migrations,
improve
existing
stuff,
some
dotnet
integration,
some
in
some
experiments
and
investigations
into
some
kind
of
more
out
there
stuff,
and
we
really
want
feedback
on
this.
So
come
to
this
post
you
can
see
down
here.
We've
already
got
eric
and
some
other
people
commenting
and
adding
feedback
on
there.
So
that's
on
github,
the
the
full
plan
itself
has
more
detail
and
is
published
to
our
doc
site.
A
So
you
know,
we've
got
a
bit
more
detail:
we've
links
to
tracking
issues
that
kind
of
stuff
on
there.
So
go.
Look
there
coming
back
to
the
state
of
the
unicorn.
Let's,
just
let
me
just
mention
some
of
the
things
that
people
might
be
excited
about
so,
like
I
said,
we
always
do
top
requested
community
features,
two
of
the
ones
we're
doing
this
time
are
temporal
table
support
in
sql
server.
A
But
this
is
to
actually
allow
you
to
query
into
the
json
in
the
column
and
that's
kind
of
what
makes
it
really
interesting,
we're
doing
a
bunch
of
stuff
around
performance,
including
compiled
models
which
should
help
start
up
time,
among
other
things,
we're
doing
more
work
on
migrations
and
including
the
bundles
feature
that
was
hunted
from
five,
oh
and
some
of
the
stuff
that
we
found
in
the
survey
has
fed
into
this
plan.
Already.
A
A
So
that's
the
the
plan
for
so
take
a
look.
Give
us
your
feedback.
We
also
have
got
lots
of
new
docs
over
the
last
few
months
and
I'm
gonna
start
a
thing
in
the
stand
up
where
we,
where
we
call
out
one
of
the
new
docs
in
particular,
I'm
going
to
talk
about
the
difference
between
pb
context
options,
generic
and
non-generic.
So
let
me
switch
back
over
to
edge
here
so
in
the
I'm
in
the
docs
page
here
and
I'm
under
db
context.
A
Configuration
initialization,
this
dot
page
has
lots
of
good
stuff
about
how
you
create
context,
instances
how
you
do
independency
injection
when
you
can
use
the
factory
and
one
of
the
things.
That's
that's
people,
don't
necessarily
always
know
is
when
they
should
use
the
generic
db
context,
which
is
generic
on
your
context
type
and
when
they
should
just
use
the
non-generic.
A
A
Now,
if
you
only
have
one
db
context
registered
in
ndi,
it
doesn't
matter
much
and
you
can
resolve
the
non-generic
one
and
we
allow
that
to
work.
But
as
soon
as
you
have
more
than
one
then
you'll
you'll
have
to
do
it
by
the
generic
and
at
the
same
time,
if
you
actually
want
to
have
a
context
that
is
derived
from
by
other
contexts,
then
you
should
use
the
non-generic
db
contact
in
that
one.
A
Your
context
from
then
in
the
same
way
that
db
context
is,
you
need
to
add
the
non-generic
one
and
that
allows
all
of
your
context
to
have
generic
ones
that
derive
from
it
to
pass
down
into
that
same
base,
constructor
their
context
options,
so
lots
of
good
tips
and
tips
in
the
in
the
documents
like
that,
so
go
check
them
out
lots
of
new
stuff
and
we'll
call
out
one
of
these.
Each
time
I
haven't
been
paying
attention.
If
there's
been
any
any
comments
or
questions
so
yeah,
you
guys
yeah.
B
A
B
Links
yeah:
let's
kick
it
off
with
the
first
one.
If
you
want
to
click
on
it
to
open
it
up,
we
don't
have
to
go
through
the
whole
article.
This
is
a
introduction
to
graphql
for
asp.net
core.
I
included
it
here
because
it's
pretty
comprehensive-
and
I
know
graphql
is
something
a
lot
of
people
are
interested
in
hot
chocolate
is
a
client
that
has
been
gaining
traction
recently,
there's
a
few
options
for
frameworks
for
for
net.
B
This
is
one
of
those,
but
this
is
a
article
that
will
walk
you
through
using
it
and
kind
of
reveal
what
the
benefits
of
using
graphql
are,
why
you
would
be
interested
in
it
as
an
api,
and
it
ties
a
little
bit
into
our
plan
for
6.0
as
well.
It's
one
of
the
things
that
isn't
directly
tied
to
entity
framework
core
but
is
tied
to
the
experience
of
datawith.net.
B
B
Yeah
that
one's
really
cool
it's
a
very
involved
walkthrough,
but
in
essence
what
it'll
do
for
you
is
it'll.
Show
you
how
to
set
up
your
developer
api
key
with
spotify
and
using
that
it
will
go
out
and
generate
a
project
that
has
the
classes
defined.
So
likewise
the
database
defined
for
that
project,
as
well
as
seeding
all
the
data.
So
it'll
call
out
to
the
api,
pull
down
all
the
information
from
that
and
see
that.
So
you
get
basically
a
fully
functional
application
and
database
as
a
result,
which
is
a
pretty
comprehensive
walkthrough.
A
A
C
So
what
I
can
tell
you,
mapping
to
json
tool,
json
is
one
thing,
but
then
doing
actual
operations,
for
example
querying
based
on
something
inside
that
json
column
is
very
different
and
that's
not
likely
to
work,
obviously
for
a
varchar.
So
the
whole
point
is,
if
you
put
something
in
an
actual
json
storage
column
in
your
database,
sql
server
or
postgres.
The
whole
point
is
usually
that
you
can
afterwards
execute
some
sort
of
queries
which
are
going
to
drill
down
into
it.
C
B
B
A
B
A
B
B
A
B
B
Actually
powerpoint,
has
some
nice
graphics
for
this.
So
what
I
thought
I'd
do
is
break
down.
We
asked
a
lot
of
questions
had
a
lot
of
insights
and
data.
So
what
we're
going
to
do
is
walk
through
talk
a
little
bit
about
the
responses
that
we
had
and
then,
if
you
have
questions,
please
go
ahead
and
ask
those
questions
to
chat.
B
This
is
meant
to
be
an
interactive
conversation
and
before
I
jump
into
sort
of
the
responses
that
tell
us
a
little
bit
about
you,
thank
you
to
everyone
who
participated
in
the
survey
incredibly
valuable
for
us.
Almost
4
000
developers
responded,
which
was
just
a
phenomenal
response
rate,
so
we're
very
thankful
for
that
feedback.
B
So
the
the
first
qualifier,
if
I
will
about
who
answered,
is
level
of
database
experience.
So
we
asked
these
questions,
so
we
had
227
respond
that
they
are
actually
a
database
administrator
working
with
ef
core
and
then
the
majority
say
you
are
comfortable.
Writing
table
definitions
and
stored
procedures,
not
necessarily
database
admin
level.
So
it's
interesting
to
us
to
understand
the
level
of
expertise
you
have
working
with
ef
core
and
we
can
also
look
at
things
like
for
people
with
less
experience.
A
Yeah,
I
I
think
this.
This
is
it's
an
interesting
question,
of
course,
because
whether
or
not
somebody
is
an
expert
or
how
they
answer,
these
questions
will
depend
a
lot
on
what
their
perception
of
being
a
database
administrator
is,
for
example.
So
it's
a
little
hard
to
put
to
put
you
know
concrete
conclusions
from
this,
but
I
think
it
shows
that
we
have
people
across
a
a
variety
of
experiences
using
ef
course.
A
B
Yeah
and
I
like
the
solid
response
with,
I
could
be
a
dba,
but
I
like
writing
codes.
Yes,
all
right,
this
one
is
another
one.
That
was
not
a
big
surprise
to
us.
We
know
a
lot
of
ef
core
developers
are
are
on
the
windows
platform,
but
there
is
a
very
solid,
showing
kind
of
split
between
around
five
percent
for
mac
and
linux
and
some
of
these
well,
this
is
is
primary,
but
I'm
sure
there's
some
overlap
too.
We
had
some
other
responses.
A
It's
it
is
interesting
here
to
me
at
least
that
mac
and
linux
are
so
close,
because
historically
mac
has
been
a
much
bigger
developer
platform
than
linux.
So
I
think
you
know
for
people
like
shi
and
I
who
do
develop
on
linux.
This
is
this
is
kind
of
interesting
to
see
linux
catching
up
a
little
bit.
B
Yep
now
this
one
comes
with
a
little
bit
of
a
caveat,
I'll,
explain
so
primary
development
environment.
It's
interesting
that
visual
studio
code
is
is
gaining
traction,
but
it's
kind
of
neck
and
neck
with
with
rider
and
by
far
the
the
major
shares
visual
studio.
But
it's
not
a
surprise.
If
you
go
to
linux
or
mac
and
you
look
at
just
people
who
are
primarily
on
those
systems,
then
visual
studio
code
becomes
40
percent
of
the
responses
and
I
think
ryder
was
similarly
close
in
in
responses
there.
A
B
C
I
mean,
I
guess
it's.
It
may
be
worth
mentioning
if
you
put
together
wpf
and
winforms
and
the
rest
of
the
you
know
the
ui
frameworks,
then
you
do
get
something
because
I
I
was
a
bit
initially
surprised
to
see,
console
background
service
like
you
so
so
high
up.
But
then
that's
one
thing:
whereas
the
ui
frameworks,
the
non-web
ones,
are,
are
kind
of
spread
across
multiple
things.
Right.
B
A
Yeah,
so
I
mean
from
the
beginning
of
a
vf
core
asb
net
core
has
been
our
most
important
segment
of
customers
and
and
in
addition
to
the
survey
showing
that
we
have,
you
know
telemetry
from
visual
studio
and
things
like
that
that
also
validate
that.
But
we
never
we
never
intended
to.
You
know
it
was
always
intended
to
be
cloud
or
mobile,
so
we've
always
been
tracking
against
the
ui
frameworks
and
and
the
different
platforms
like
that,
and
it's
great
to
see
some
of
those
getting
traction.
A
It's
also
going
to
be
interesting
to
see
where
that
whole
whole
space
ends
up,
as
you
know,
and
and
where
we
end
up,
supporting
which
ui
platforms
tend
to
be
the
most
used,
but
yeah
it's
blazer
being
in
there.
I
think,
is
also
obviously
an
indic
kind
of
a
crossover
between
those
two
things
you're
doing
asp.net
core,
but
it's
much
more
using
ef
in
a
way
similar
to
a
ui
platform
as
well.
B
And
I'm
interested
in
drilling
in
too,
because
I'm
assuming
the
blazer
web
assembly
usage
is
talking
to
a
web
api
that
then
uses
ef
core,
but
it'd
be
interesting
if
people
are
actually
because,
I
believe
right
now,
the
only
two
scenarios
and
one
you
have
to
hack
really
hard
right
to
get
to
work
is
sqlite
in
the
browser
and
cosmos
db
in
the
browser.
So
yeah.
B
Okay,
what
version
of
entity
framework
are
you
using?
So
this
is
again
not
much
of
a
surprise.
At
the
time
of
the
survey,
ef
5
was
still
in
ef.
Core
5
was
still
in
preview,
and
so
you
know
696
for
that
vast
majority
on
ef,
core
3x,
interestingly
second
place
ef6
on
that
net
framework,
and
this
for
the
team
is
interesting
to
us
just
to
understand.
B
You
know
what
is
keeping
people
from
migrating
onto
the
new
platform
and
whether
it's
because
in
some
cases
it's
challenges
with
net
framework
api
surface
area.
In
some
cases
it's
challenges
with
ef
core
api
surface
area
so,
and
we
drill
into
that
and
some
of
the
other
questions.
But
I
guess
the
the
surprise
for
us
was
this
pre-entity
framework,
six
cf-4
ef5
classic.
That's
a
pretty
solid
number
of
people
working
on
those
legacy.
Applications.
A
C
A
B
B
Now
we
also
drilled
into
biggest
challenges
for
migration,
and
that
is
information
for
us
to
better
understand,
as
we
roll
out
future
versions
how
to
make
that
less
painful,
more
seamless
and
improve
that
experience.
I
I
didn't
summarize
the
data,
because
it's
free
form
here
for
for
the
purposes
of
of
this
call,
but
we
did
follow
up
with
oh
actually,
we
did
have
the
the
challenges
slide.
So
so
it
looks
like
missing
features
which
is
kind
of
a
catch
all
right.
B
We
tried
to
ask
for
specific
features,
but
we
didn't
want
to
lead
the
the
witness
too
much
right
for
that.
So,
but
you
know
to
me
it's
pretty
solid
that
a
20
response
rate
had
no
issues
right.
They
just
said
they
migrated
and
they
were
done.
And
then
we
have
queries,
relationships,
migrations
and
five
percent
said
gui
was
was
the
challenge
which
I'm
assuming
kind
of
overlaps
with
the
whole
edm
x
file?
Issue
as
well
right.
A
Yes,
there's
been
some
comments
on
on
not
having
edmx
files,
I
mean
just
to
you
know
we
theoretically,
it
would
be
possible
to
take
an
edmx
file
and
create
a
code
first
model
out
of
it,
and
you
know
we
talked
about
that
with
diego
years
and
years
ago
when
we
started
efcor.
The
reason
we've
never
done.
That
is
because
we
actually
think
it's
a
better
experience
to
start
with
your
database
that
you've
mapped
your
edmx
file
to
reverse
engineer
that
and
get
your
efcor
model
from
that
now.
A
Neither
is
going
to
be
perfect,
but
in
terms
of
in
terms
of
writing
all
of
the
code
to
kind
of
generate
ef
core
from
edmx.
The
value
of
that
over
just
using
your
database
doesn't
seem
to
be
super
high
to
us
stepping
back
a
little
further
than
that.
Just
so,
people
are
aware:
ef
core
doesn't
have
edm
the
the
entity.
Data
model,
which
is
the
edm
part
of
edmx.
A
It's
not
based
on
that
like
ef6,
is
ef6,
is
fundamentally
based
around
that
whole
model
file.
One
of
the
points
of
ef
core
was
not
to
be
limited
by
the
edm
model,
and
so
it's
not
so
so
it's
not
just
oh,
we
don't
like
xml
files
or
whatever
it's
like
it's
a
fundamental
difference
between
ef,
core
and
ef6.
B
So
for
those
considering
migration,
we
had
the
vast
majority
well
60
percent,
not
considering
a
28,
no
concerns
so
considering
doing
it
don't
have
concerns
there
were
things
listed
like
you
know,
just
waiting
for
approval,
there's
other
testing
or
issues.
We
have
to
deal
with.
That's
not
ef
core
related
and
then
there
were
12
percent.
That
said,
yeah
we're
considering
it,
but
we
do
have
blocks
and
concerns,
and
those
are
summarized
here.
A
So
this
is
this.
This
is
definitely
one
of
those
things
that
fed
into
is
already
feeding
into
our
planning.
I
think
you
can
see
you
know
features
not
yes,
it's
like
features
not
yet
addressed,
and
that
includes
things
like
the
missing
group
by
support
that
we
still
have
in
5.0,
and
so
that's
kind
of
one
of
the
reasons
that
we
are
making
ef6
query.
A
Apparently,
an
important
part
of
the
ef
course
6060
plan,
because,
based
on
this,
this
feedback,
even
though
we're
pretty
close
now,
that's
one
of
the
things
that
that's
stopping
you
and
we'll
need
your
help
on
that
as
well,
because
we'll
try
and
do
you
know,
cover
everything.
But
if
you
find
a
query
that
doesn't
translate
after
we
say,
you
know,
hey
we've
done
it
all
in
this
preview,
then
let
us
know
so
that
we
can.
B
So
it
was
interesting
too,
because
this
was
this
was
a
free-form
response,
so
it
took
some
time
to
go
through
and
and
categorize
and
crunch
the
numbers.
But
a
lot
of
the
features
that
were
listed
are
in
that
that
24
spot,
which
were
things
like
mini
to
mini
and
table
for
type,
and
so
it's
it's
exciting
to
me
at
least,
to
see
that
at
least
some
of
those
blockers
were
addressed
by
moving
to
ef
core
5.
A
B
Excuse
me,
too,
is
that
as
an
open
source
project,
one
of
the
things
is
we're
not
trying
to
solve
every
problem
with
the
if
core-
and
there
are
some
great
community
projects
and
contributions
out
there
and
an
example
of
that
is
the
f
core
power
tools.
A
lot
of
the
features
that
that
people
are
looking
for
any
of
core
that
are
implemented
in
the
the
baseline
package
are
implemented
through
those
those
power
tools
and
there's
not
a
compelling
reason
to
take
that
over
right.
B
B
Yeah,
so
all
right,
so
this
slide
was
the
response.
One
of
the
things
that's
important
to
us,
as
we
come
out
with
new
releases,
is
we
can
write
tests
and
we
can
test
to
a
certain
level
but
you're,
really
the
ones
who
have
the
the
business
cases
and
scenarios
and
and
problem
domain
and
using
previews
and
release
candidates
as
a
way
to
get
defects
and
changes
to
us
quickly,
so
that
we
can
put
it
into
the
final
release
and
we
noticed
that
there's
just
not
much
use
of
daily
builds
and
previews.
B
A
Yeah,
I
know
this
was
really
interesting.
It's
just
really.
I
mean
if
you,
if
you
follow
me
on
twitter,
you
you
especially
you
know
when
we
get
to
the
previews
before
releases.
You
you'll
hear
me
going
on
no,
no,
no,
no
about
trying
the
previews,
because
anybody
who
tries
to
previews
and
files
issues
on
that
helps
us
so
much
and
one
of
the
things
that
we
did
well
in
five
zero,
much
better
than
we've
done
before
and
that's
have
a
proper
release
candidate,
and
I
think
that
the
data
here
backs
up.
A
Why
we
tried
to
do
that
and
I
think
it
helped
and
that
is
by
proper
release
candidate.
I
don't
mean
we're
still
working
on
everything
and
we've
just
designated
this
preview
as
rc1,
which,
to
be
honest,
has
what's
what's
has
been:
what's
happened,
a
bunch
of
microsoft
stuff,
you
know
in
the
past,
including
ef
core
for
5.0,
the
release
candle
was
feature
complete,
so
it
was
basically
anything
you
want
is
in
here
and
anything.
A
C
Yeah,
I
also
have
a
comment
on
this.
So,
as
arthur
said,
the
previews
are
extremely
important
and
we're
actually
gonna
gonna
start
the.
So
the
first
preview
is
gonna
come
out
at
some
point
this
month
already
so
we're
very
early
in
the
6.0
release
cycle,
but
we're
already
going
to
have
like
a
first
preview
of
6.0
and
one
thing
I'm
going
to
do
like
a
marketing
pitch
here.
C
The
the
one
thing
I
think
people
don't
some,
maybe
don't
realize,
maybe
we
don't
communicate
it
well
enough-
is
that
the
preview
that
gets
released
for
ef,
core
or
any
other
of
the
dotnet
things
is
basically
has
basically
gone
through
the
same.
You
know
verification
in
terms
of
the
ci
pipeline.
The
same
tests
have
you
know
it
passed
all
of
our
tests
suit
in
the
exact
same
way,
so
previews
are
not.
C
C
We
definitely
do
not
release
a
preview
that
has
any
sort
of
known
instability
or
bug
it
may
not
it's
it's
not
going
to
have
all
the
features,
obviously
of
6.0,
because
we
we
haven't
gotten
around
to
it,
but
in
terms
of
stability,
if
you're
open
to
that,
then
you
should
see
the
a
level
of
stability,
that's
not
very
very
far
from
you
know,
from
from
from
a
release
or
from
an
rc
and
yeah.
I
hope
I
hope
everybody
listening
to
this
will
kind
of
you
know.
C
Take
it
take
it
into
account
that
it's
there
and
the
other
thing
that's
related
to
this.
So
we
release
now
pretty
much
once
a
year
right
in
november.
Previews
are
a
way
to
actually
get
those
new
features
in
between
right,
because
a
year
could
be
a
little
bit
long.
So
it
is
an
option.
I'm
just
saying,
of
course
not
everybody
can,
you
know,
can
get,
can
use
a
preview
in
their
production
platform
and
that's
not
necessarily
even
that
recommended,
but
it
is
something
that
you
can
do
and
we're
gonna
support
it.
C
A
So
one
from
the
comments
just
one
thing,
while
we're
before
we
go
on
to
the
next
one,
there's
a
there's,
a
lot
of
people
discussing
database
first
versus
code.
First,
I'm
pulling
up
one
of
these.
You
know
the
db
is
a
source
of
truth
for
everything,
so
the
switch
for
code
first
is
not
that
easy
to
sell.
So
I
wanna
code
first
is
a
really
bad
name.
It
was
a
marketing
term
that
they,
you
know
they
created
when
we
had
database
first
and
model
first
and
like
oh
code.
A
First,
that
fits
nicely
code
first
doesn't
mean
you
write
your
code
first,
it
doesn't
even
mean
that
the
code
is
the
source
of
the
truth.
It
just
means
that
the
mappings
that
you
might
have
had
in
an
xml
file
like
edmx
and
now
written
in
c
sharp
code.
Those
mappings
can
be
driven
from
the
database
using
af
core
power
tools
that
eric
has
or
using
the
reverse
generator.
A
It's
not
great
at
keeping
those
up
to
date.
This
stuff,
we
need
to
work
on
that.
To
be
fair,
if
you
view
the
update
model
from
database
in
the
ef
designer
that
doesn't
work
properly
either,
so
you
know
it's
it's
not
that
much
different
and
and
the
point
here
is:
you
don't
have
to
completely
change
your
way
of
thinking
about
the
database
to
use
ef
core
just
because
the
models
are
in
code,
and
I
think
that's
important
for
for
people
to
to
understand.
B
Yeah
I
like,
when
my
consulting
days
when
we
would
talk
about
entity
framework
I
like
to
talk
about
code
first
and
database
first,
but
the
reality
is
in
between
right.
So
I
don't
want
to
just
create
a
nice
domain
model
and
code
and
generate
my
database
from
that.
I
don't
want
to
create
a
nice
database
and
just
naively
generate
code
from
that.
I
want
to
model
the
domain
properly
model
the
database
properly
and
then
use
that
fluent
api
to
map
the
two
together
in
the
right
way.
That's
why
it's
a
object,
relational,
mapper
right!
B
So,
okay,
let's
move
on
so
how
you
use
ef
core.
So
this
was
a
question
of
which
technologies
you
use
in
conjunction
with
entity
framework
core.
Obviously,
a
lot
of
people
are
serializing
json
over
the
wire,
so
newtonsoft.json
and
systemtext.json
had
strong
showings
asp.net.
Core
identity
is
scaffolds
by
default
with
the
nitty
framework
core,
so
those
two
kind
of
go
hand
in
hand
and
then
we've
got
auto
mapper
and
dapper,
so
auto
mapper,
obviously
taking
one
type
of
entity
mapping
it
to
another.
B
C
So
if
you
have
some
sort
of
perf
concern
with
ef
on
a
specific
point,
nothing
stopping
you
from
taking
dapper
and
using
it.
For
that
specific
thing,
it
should
never
be
some
sort
of
ideological
thing,
and
even
I
mean
we
don't
as
a
team,
we
try
hard
to
never
ever
we
don't
push
for
efcor
to
be
the
answer
for
all
of
your.
You
know.
Data
needs,
there's
other
technologies
out
there
that
are
completely
fine.
So
I'm
actually
I'm
very
happy
to
see
that
kind
of
thing
actually.
A
Yeah
me
too,
I
mean
there's
a
bit
of
debate
on
the
team
as
to
whether
or
not
we
should
invest
in
features
that
are
quote-unquote
better
done
by
dapper
things
like
raw
sql,
queries
and
stuff.
Like
that,
I
think
the
consensus
on
the
team
is
we
want
to
have
good
support
for
those,
even
though
shy
thinks.
Maybe
we
shouldn't
just
because
we
don't
want
to
force
people
to
say.
Oh
man,
I
have
to
go
and
use
something
else,
and
I
don't
want
an
additional
dependency.
B
This
is
the
list.
I
won't
spend
too
much
time
on
it
unless
there's
anything
that
jumps
out
to
the
team
dimension,
but
in
the
other
section
these
are
the
ones
we
didn't
present
as
options
and
and
came
out
as
very
commonly
selected
items.
Obviously,
bulk
extensions
right,
bulk
and
batch
operations
is
asked
for
quite
a
bit,
but
this
when
this
is
posted,
these
links
will
be
available.
B
A
Absolutely
and
and
we
we
have
a
list
of
extensions
on
the
ef
core
page,
which
basically
anybody
can
send
a
pull
request
to.
So
we
don't
necessarily
say
that
these
are
all
great
extensions,
but
there's
a
significant
list
of
things
that
you
can
use
with
ef
core
there
as
well.
So
you
know,
do
take
a
take
a
look
at
those
and
if
you've
got
something
that
you've
written
and
you've
put
it
up
on
github,
then
you
know
send
us
a
link
and
we'll
add
it
there.
B
This
next
one
is
one
in
retrospective.
We
could
have
probably
asked
them
differently.
We're
curious
about
multiple
databases
in
the
same
application.
There's
two
things
there
is
I'm
on
sql
server,
for
example,
and
I
have
two
databases
that
I'm
accessing
so
probably
two
different
db
contacts.
You
can
certainly
have
more
and
then
there's
the
I'm
using
azure
cosmos,
db
and
sql
server
in
the
same
one,
but
based
on
other
answers,
there's
a
lot
of
usage
of
the
memory
provider.
B
A
Yeah,
I
think
I
think
one
of
the
things
we
learned
from
this
is
how
to
do
better
next
time.
We
do
a
survey
whenever
you,
you
know
get
into
something
like
a
complex
survey
like
this
and
then
send
it
out,
and
then
you
get
a
question
back
and
you're
like
what
did
we
really
ask
what
we
did
we
asked
and
then
oh,
I
don't
think
we
did.
You
know
so.
Learning
experience
like
everything.
C
I
have
to
say
one
thing:
there's
so
there's
there
was
actually
specifically
a
bug
and
there's
a
bug:
that's
going
to
be
fixed
and
an
ef
core
503.
That
happened
when
you
had
sql
server
and
postgres
together,
like
mpg
sql
together-
and
I
remember
when
we
first
when
I
first
saw
this
bug
I
was
kind
of
like
you
know
how
many
people
are
there
out
there,
actually
using
those
two
providers
together
right.
C
The
hypothesis
I
had
like
naturally
assumed
or
intuited
was
that
people
typically
use
just
a
single
database
and
in
fact
we
got
quite
a
big.
Like
amount
of
you
know,
people
saying
yeah.
This
is
a
problem
for
me
too,
which
is
the
exact
same
thing
that
we
want
to
get
a
signal
on
from
this
kind
of
question,
so
yeah.
It's
always
interesting
for
us
how
many
people?
C
A
B
A
C
A
Is
perhaps
already
mentioned,
but
but
no
this
this
this
matches.
You
know
this
is
matches
what
we
expect
and
I
think
it's
great-
that
we
have
really
good
open
source
providers
for
postgres
and
my
sequel.
You
know
obviously
the
sequel,
light
and
sql
server
ones.
The
team
ships,
those
but
the
the
other.
The
my
sequel
and
postgres
are
community
projects
and
they're
as
high
quality
or
more
than
the
ones
we
ship
and
that's
great,
to
see.
B
A
It's
very
interesting
because,
from
the
beginning
with
the
in-memory
database,
it
was
explicitly
not
a
goal
to
make
this
a
high-performing,
in-memory
database,
and
indeed
it
is
not
a
high-performing
in-memory
database.
It's
a
very
poorly
performing
in-memory
database,
absolutely
useful
to
the
team
for
testing,
and
so
it's
not
like
it
doesn't
have
value.
Apparently
it's
acceptable.
You
know
it's
very
useful
to
other
people
as
well,
but
it's
never
been
designed
as
a
production
in
in
memory
database.
Never
so
it's
it's
that
that
is
very
interesting
to
us.
B
We
have
59
people
to
follow
up
with
who
are
using
it
in
production
to
understand
what
that
that
scenario
actually
looks
like
so:
okay
priority
for
missing
providers.
Now
this
was
the
one
that
was
very
very
interesting
to
me.
We
asked
of
providers
that
aren't
yet
written,
which
ones
are
most
important
to
you
to
write.
In
other
words,
which
one
do
you
feel
is
is
missing
that
you
really
want
to
use
and
the
top
two
were
mongodb,
which
is
a
document
store
similar
to
azure
cosmos
db.
B
It
may
be
referring
to
the
mongodb
api
for
azure
cosmos
db.
That's
a
possibility
as
well,
and
then
csv
in
excel
was
was
number
two
azure
storage,
more
features
for
the
azure
cosmos
db
provider,
and
then
it
drops
off
from
there
we
did
analyze.
We
had
open-ended
kind
of
other
response
and
we
analyzed
those,
but
there
wasn't
anything
significant
that
that
stood
out
so.
A
A
Having
a
provider
implies
more
than
that
implies
that
you're
going
to
be
able
to
update
and
query
the
csv
excel
directly
and
that
that's
a
little
confusing
to
me,
I'm
not
quite
what
people
want
when
that
means.
So
again,
you
know
if
you've
got
ideas
about
how
you
would
use
it
reach
out,
because
I'm
not
saying
that
it
wouldn't
be
great,
and
maybe
it's
we're
just
missing.
You
know
a
really.
A
B
C
Yeah
I
mean
if
it
is
just
about
querying.
I
hope
people
are
also
aware.
It's
it's
relatively
trivial
to
some
have
some
sort
of
I
innumerable
like
read,
read
in
a
csv
as
an
iron
marble,
and
then
you
have
the
whole
power
of
link.
It's
it's
pretty
much,
not
far
away
from
what
ef
core
would
provide
had
we
implemented
some
sort
of
provider,
but
where
it
gets
really
interesting.
I
completely
agree
with
author:
is
people
are
actually
looking
for
updating,
which
is
interesting,
so
I'll
go
on
a
really.
B
Fast
tangent
and
I
promise
I
won't-
spend
too
long
but
dot
net
interactive,
jupiter,
notebook
support
for
c
sharp,
both
of
those
allow
you
to
use
a
there's,
a
utility
that
they
had
called
linkify,
which
basically
allows
you
to
import
a
csv
or
comma
separator
tab,
delimited
file
and
call
one
method
that
you
just
tell
it
basically
turn
this
into
a
column
store.
I
do
have
a
header,
I
don't
have
a
header
and
then
you
can
run
link
queries
interactively
across
it,
so
very
useful
tool.
A
A
Before
we
move
on
there's
a
a
lot
of
comments
have
been
going.
You
know
going
by
about
the
performance
of
dapper
versus
ef
core
and
I'm
not
gonna
go
over.
All
of
the
the
comments.
There's
been
some
good
good
responses
and
links
there,
but
I
will
say
it
ties
in
with
our
ef
course
60
plan.
So
one
of
the
items
in
the
a
of
course
60
plan
is
to
be
as
fast
as
dapper
on
the
tekken
power
fortunes
benchmark.
A
So
one
place
where
one
of
the
questions
was
the
difference
between
raw
sequel,
dapper
and
ef
course
so
one
place
you
can
see
that
and
there's
a
link
in
the
in
the
in
the
af
60
plan.
So
you
can
go,
find
it
there,
but
you'll
find
that
there
are
various
flavors
of
that
benchmark,
and
this
is
the
tekkenpower
fortunes.
Benchmark
is
kind
of
an
industry
standard.
A
A
So
we
we
run
those
with
a
variety
of
flavors
and
the
ef
core
ones
are
generally
the
slowest
I'm
going.
Gonna
say
that
now
they're
not
super
slow
by
any
means,
but
they're
slower
than
if
I
just
use
dapper
for
that
and
dapper
is
significantly
slower
than
if
I
hand
craft
all
my
ago
and
just
do
everything
like
super
fast.
So
that's
where,
on
that,
one
we're
like
way
up
on
the
fortunes
like,
I
can't
remember
where
we
are,
but
we're
top
10
or
something
aren't.
We
now
shy
again.
A
Yeah,
so
in
the
of
course,
60
we're
going
to
try
and
get
the
ef
core
performance
on
on
queries
for
at
least
for
fortunes
up
to
that
of
dapper.
We
won't
achieve
that.
It's
it's
not
going
to
be
possible
because
you
know
we
ef
core
is
a
very
different
beast.
However,
because
it's
a
different
beast,
we
may
be
able
to
do
things
that
dapper
doesn't
do
and
so
we'll
see
how
it
goes,
but
we're
going
to
make
a
really
big
effort
to
to
make
it
faster.
B
And
just
a
quick
shout
out
to
our
our
twitch
stream
comments,
we
do
see
twitch
stream.
I
did
not
see
a
specific
question,
so
if
there's
one
you
feel
we
missed
go
ahead
and
throw
that
out
there
again,
but
we
do
monitor
both
twitch
and
youtube.
I
know
there's
some
discussions
that
we're
not
following
the
platform,
so
I
did
not
notice
a
a
question
there,
but
I'm.
A
B
Yeah
I
hear
fingers
flying
on
the
keyboard,
so
that's
in
action,
so
production
database
hosting
this
one.
You
have
to
kind
of
look
at
it
two
ways,
because
we
were
very
specific
about
some
microsoft
properties
which,
because
we're
microsoft.
So,
for
example,
we
were
interested
in
if
you're
on
azure
are
you
just
lifting
and
shifting
like
dropping
it
in
as
a
vm?
Are
you
actually
using
sql
as
a
service,
or
are
you
containerizing
your
application
and
then
we
had
on-premise.
B
C
Though
I
I
have
to
save
him
before
6-0,
if
this
is
something
that
you
do,
I
mean
it
can
work
and
it's
fine,
but
I
we
really
do
recommend
you
go
check
out
our
docs.
We
have
some
sections
explaining
the
exact
differences
between
these
different
techniques
and
just
be
sure,
you
understand
exactly.
You
know
how
how
this,
how
this
kind
of
stuff
works.
We
do
really
recommend
using
sql
scripts
for
production,
databases,
yeah
and
and.
A
B
Yeah,
I'm
just
going
to
call
out
and
say
the
whole
team
has
been
working
very
hard
to
update
the
documentation
across
the
board.
There's
major
updates
to
understanding
migrations
change,
con
change,
tracker
and
other
features.
The
new
db
contacts
factory,
the
options,
everything
so
definitely,
if
you
haven't,
visited
the
docs
recently
yeah
there.
C
C
B
Scaffolding,
migrations.
We
asked
you,
how
do
you
scaffold
and
migrate?
And
16
of
you
said
I
don't
okay,
easy
enough
41
cli.net
ef,
which
is
where
you
get
the
the
nice
ascii
unicorn,
which
is
my
favorite
ascii
art
and
then
yeah.
That's
my
whole
takeaway
from
our
command
line
tool.
Right,
30
use
the
package
manager
console,
which
is
really
the
same
thing
as
the
cli
just
different
words
and
verbs
right
from
the
nuget
package.
A
Manager,
it's
it
has
so
we
used
to
say
if
you're
on
visual
studio
use
the
pmc,
because
it
integrates
with
the
visual
studio
project
system,
which
can
make
it
a
slightly
better
experience
on
visual
studio.
I
have
to
say,
though,
really
just
use
whichever
one
you're
comfortable
with,
because
I
think
both
of
them
give
an
awesome
experience,
and
this
is
it's
just
a
matter
of
like
say,
which,
which
kinds
of
nouns
and
verbs
you
want
to
type
and
whether
they're
up
a
case
or
not.
Yeah.
C
A
A
B
All
right,
so
this
this
is
a
one
of
the
forward-looking
questions
we
said.
Basically,
what
tools
do
you
need
to
be
successful
that
we
don't
have
in
in
ef
core,
and
we
get
this
request
quite
a
bit,
which
is
a
data
visualization
tool
to
be
able
to
see
the
the
database
model
to
visualize
it?
Some
of
this,
maybe
actually
asking
for
edmx
support.
B
B
A
Yeah,
so
I
call
it's
worth
calling
out
here,
especially
on
the
visualization
there's,
there's
some
there's
some
open
source
project
community
projects
out
there.
I
think
bryce
added
them
to
our
extensions
list.
So
look
in
the
docs
page
on
the
on
the
ef
ef
extensions
list
and
and
you'll
see
them
there.
A
So
there
are
things
out
there
and
it's
it's
made.
Some
of
them
are
being
actively
developed,
some
not
so
much,
but
it's
worth
checking
those
out
and
seeing
if
that's
something
you
want
you
could
use.
I
think
also.
We've
talked
since
the
beginning
of
since
since
ef
4.1,
basically
about
the
right
click.
Actually,
no,
it
wouldn't
been
4.1.
Wouldn't
it
because
4.1
didn't
have
migrations,
but
the
first
release
that
had
migrations-
I
think,
was
4.3,
and
this
isn't
called
this
is
back
in
the
pre-chore
days.
A
We
talked
about
right-click
gestures
for
commands
and
I
I
still
think
that
will
be
a
useful
thing
and
or
something
that
somebody
should
do.
I
think
you
know
the
the
powershells
does
some
of
this.
You
know
bryce
and
I
have
taught-
and
we
should
talk
to
eric
about
this-
about
whether
or
not
it's
putting
things
in
the
places
where
people
expect
them,
and
you
know.
A
I
think
we
need
to
dig
into
the
experience
a
bit
more,
but
I
think
this
could
be
something
that
either
the
power
tools
or
some
other
community
project
takes
on
and
when
we
get
a
physics
out
there
in
the
visual
studio
gallery.
That
has
a
good
experience
for
this.
It
seems
doable
by
the
community
to
me
and
we
would
definitely
be
willing
to
help
you.
B
Yeah
we
had
a
question
about
the
data
binding
wizard.
That's
actually
something
that
existed
in
previous
versions
in
wpf
and
winforms
and
I
believe,
has
come
back
to
wpf
on.net
core.
But
the
idea
is
basically,
you
can
point
to
a
data
context
and
it
will
automatically
introspect
the
entities
on
that
database
context
and
then
you
can
drag
and
drop
on
your
designer.
B
A
Yeah,
the
the
data
binding
experience
is
something
that
has
come
back
to
the
front
in
the
last
couple
of
years,
both
with
wpf
and
and
and
winforms,
and
also
with
blazer.
Now
I
know
the
ui
frameworks,
but
those
those
three
have
been
driving
a
lot
of
things.
So
some
of
that
is
about
you
know
making
what
we
have
now
work
really
well,
but
I
think
we're
also
looking
for
ways
that
we
could
improve
that
experience.
C
One
more
note
for
me
just
really
quickly
about
the
data
visualization
thing
so
there's
there
is
sometimes
this
tendency
in
the
dotnet
ecosystem
to
expect
or
to
want
all
tools
to
come
from
microsoft.
It's
like
a
general
thing
that
we
sometimes
see,
and
I
think
specifically
in
this
domain,
so
there
are
definitely
tools
not
coming
from
microsoft
that
can
fulfill
people's
general
needs.
So
the
power
tools
have
already
been
mentioned
here.
C
We
also
had
france
buma
who's,
the
author,
the
owner
of
pro,
which
is
exactly
that
so
a
data
visualization
tool
that
you
can
use
with
efcor.
So
these
are
things
that
are
complementary
to
ef
core
and
take
care
of
that
specific
thing
that
you
know
is
missing
for
certain
people,
so
the
general
message
is:
don't
necessarily
expect
or
look
for
everything
on
a
microsoft
site,
you're
going
to
find
it
elsewhere
as
well,
and
it's
going
to
be,
you
know
just
as
good.
C
A
B
B
Okay,
a
quick
section
on
azure
cosmos
db,
taking
the
r
out
of
orm
right.
It's
not
a
relational
data
store.
So
the
first
thing
we
asked
is
adoption
and
53.
So
more
than
half
don't
work
with
it.
Don't
plan
to
next
one
in
three:
don't
work
with
it,
but
are
considering
it
it'll,
be
interesting
to
see
what
the
factors
of
that
consideration
are
one
in
ten
work
with
it,
but
don't
use
our
provider
and
then
four
percent
work
with
and
use
the
the
provider.
B
So
this
is
interesting
because
there's
a
small
fraction
that
actually
reported
using
the
provider
but
there's
a
much
larger
percentage
who
reported
that
provider
being
important,
which
leads
us
to
believe.
There
are
some
major
feature:
gaps
right.
That
part
of
the
ef6
plan
is
to
identify
what
the
most
important
feature
gaps
are,
so
that
we
can
invest
in
improving
that
that
provider,
for
it.
A
Yeah,
so
I
again,
this
is,
we
know
I
mean
this.
This
isn't
something
we
didn't
know
in
terms
of
the
feature
gap,
so
we
knew
about
the
feature
gaps.
What
we,
what
we
have
got
from
this
is
a
very
clear
signal
that
people
want
us
to
work
on
those
feature
gaps
and
the
cosmos
is
important,
and
so
that's
been
very
useful.
A
The
point
is
the
ef
core
provider
should
do
what
cosmos
does
well,
and
so,
when
you
look
at
things
like
include
support,
if
that
would
involve
doing
something
really
expensive
on
cosmos,
it's
not
necessarily
the
best
feature
to
put,
even
if
people
think
they
want
it.
You
know,
and
so
it's
really
is
a
matter
of
really
figuring
out.
A
What
are
the
ways
that
people
can
use
ef
core
with
cosmos
that
is
effective
and
you
know
both
cost
effective
and
effective
in
terms
of
the
programming
model
and
the
experience
and
everything
and
that's
that's
actually
fairly
challenging.
So
that's
why
digging
more
into
into
the
the
responses
on
this
and
reaching
out
to
people,
I
think,
is
going
to
be
very
useful.
B
Yeah-
and
this
just
further
clarifies
that
the
use
and
shows
that
one
in
ten
would
or
are
using
the
provider
at
eight
percent
say
they
would
use
it
if
it
had
the
features
they
needed
and
then
three
percent
are
actively
using
it.
So
that's
it's
significant
one
in
ten
respondents
and-
and
we
definitely
wanna
address
that,
so
we
are
at
the
last
section
of
the
survey.
I
know
we're
at
the
the
top
of
the
hour,
but
I
think
we'll
have
time
to
go
through
these
final
few
items.
B
The
first
one
is
your
biggest
ef
core
performance
challenges.
This
is
another
one
of
those
questions
that
we
may
not
have
asked
the
the
best
way
because
query,
which
is
the
number
one
response,
is
also
the
one.
That's
probably
the
most
open-ended
like
what
part
of
it
is.
The
challenge,
is
it
support
for
it
is
it
aggregates?
Is
it
includes
projections,
materialization,
there's
so
many
aspects
to
this
that
we
could
drill
into,
but
these
are
the
the
main
responses
that
we
saw.
B
Okay,
moving
on
to
the
next
one
mobile
challenges,
so
this
one
surprised
me
because
I've
worked
with
people
using
efcor
mobile
and
there
are
issues
with
startup
time.
There's
some
issues
with
when
you
see
the
linker
flags,
which
was
the
least
reported
that's
because
of
some
of
the
optimizations,
aren't
translated
the
way
that,
for
example,
ios
right
won't
allow
us
to
dynamically
generate
code,
so
it
goes
through
an
interpreter,
so
it's
actually
slower
for
code.
B
A
It's
you
know
it's,
it's
always
been
there
right.
The
synchronization
has
been
a
mobile
challenge
forever
and
there's
been
various.
You
know,
attempts
to
to
bridge
that
gap,
some
less
successful
and
some
more
successful.
It's
not
trivial.
You
know,
I
mean
we've
thought
about
this
for
a
long
time
and
we
have
various
ideas
of
things
we
could
do
and
clearly
it's
something
that
longer
term
we
need
to
look
into,
but
it's
it's
definitely
not.
It's
not
a
trivial
thing
by
any
means.
C
B
It's
a
shame
that
she
had
to
leave
because
I
was
gonna
say
under
the
other
julie
lerman
was
one
of
the
the
top
mentioned
sources
of
solutions,
but
this
is
how
developers
address
issues
we
want
to
know
you
run
into
a
problem.
What
are
you
doing
and
vast
majority
search
for
it
on
stack
overflow,
but
bunch
of
you
use
your
favorite
search
engine.
You,
google,
bing,
lycos,
alta
vista
dog,
pile
okay,
so
so
that
I
got.
C
B
Title
and
then
only
a
third
place
is,
is
searching
for
the
issue
on
the
github
repo.
Has
someone
run
into
this
and
already
filed
it,
and
then
fourth
place
is
looking
at
the
local
logs,
which
is
a
if
you
haven't
looked
at
ef
core
logs?
You
should
start
looking
at
them
because
they
are
incredibly
detailed.
They
don't
just
tell
you
what
problems
you're
having,
but
they
will
indicate
problems
you
might
have
based
on
the
way
that
you're
configuring,
the
application
or
the
way
you're
constructing
a
query.
You'll
actually
get
tips,
go.
A
Yeah,
so
one
of
the
challenges
that
any
any
runtime
component,
as
opposed
to
tooling
component
has
is:
what
do
we
do
when
we
encounter
a
case
where
you
might
be
right,
but
you
also
could
easily
have
got
it
wrong
and
this
is
a
place
where
compilers
and
other
run.
You
know
other
development
time
tools
bit
warnings
out
right,
they're
like
okay.
Well,
are
you
sure
you
meant
to
use
equals
instead
of
equals
equals
equals
there?
You
know
you
might
mean
that,
but
we
think
you
probably
didn't.
A
Did
I
really
mean
this
and
that
can
really
help
you
from
going
down
rabbit
holes
of
not
understanding
what's
going
wrong,
so
definitely
look
at
those
logs
and
also
you
can
just
once
you've
figured
it
out
if
you're
like
no,
no,
that's
cool,
I
meant
to
do
that.
Then
you
can
set
the
warning
up
to
be
ignored,
and
so
you
won't
get
continually
bothered
by
it.
But,
as
jeremy
said,
go
look
at
the
logs.
B
A
A
Just
to
add
a
little
bit
to
that,
so
somebody
says:
use
ef
help
on
twitter.
So,
yes,
that
can
work.
Twitter
is
not
necessarily
the
easiest
place
to
answer
questions
so
to
call
out
again
the
place
where
the
team
looks.
That's
where
I
look
and
shy
and
and
everybody
else
on
the
team
is
on
github,
so
feel
free
to
ask
questions
on
af,
core
github
repo
or
you
know,
file
bugs
as
well.
A
Obviously,
lots
of
people
on
stack
overflow
stack
overflow
is
a
great
place
to
answer
the
community
strong
there
and
I'm
pretty
sure
bryce
unless
he's
changed.
His
is
his
mo
is
hangs
out
and
stack
overflow
and
answers
questions
there.
So
so
that's
really
good
and
then
you
know
look
in
the
docs
as
well.
A
I
like,
like
we
said
the
docs,
have
been
updated
a
lot
recently,
but
even
when
we
sent
the
survey
out
people
like
the
docs
a
lot
and
so
people
so
go
look
in
the
docks.
That's
a
great
way.
It's
a
great
way
to
find
this
and
then
of
course,
yeah
ping
us
on
twitter
and
we'll
probably
tell
you,
go
ask
on
github,
but.