I used to use EF heavily when it was database-first because I feel like that's how these types of libraries should be used. The jump to code-first left me confused because I didn't think about my systems like that.
And you're right, strongly typed queries are a big win. The number of times I've accidentally fat fingered a query going into Dapper or tried to map a datetime or a long. But that's far less pain than issues I've had with EF.
Thanks for the comment!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I used to use EF heavily when it was database-first because I feel like that's how these types of libraries should be used. The jump to code-first left me confused because I didn't think about my systems like that.
And you're right, strongly typed queries are a big win. The number of times I've accidentally fat fingered a query going into Dapper or tried to map a datetime or a long. But that's far less pain than issues I've had with EF.
Thanks for the comment!