What is the best pattern can I use with EF core?

Question

0.00/5 (No votes)

See more:

I'm working with Repository pattern in my desktop project's , but i faced some problems with this pattern 
earlier i read many articles discuss that this pattern is dead
so , i tried to find what's the alternative ? what is the suitable pattern can i use to make my code clean , maintainable ? Now i'm so confused ... i'm waiting your advice.
thanks a lot.

What I have tried:

directly ef db context , without any pattern

Posted 19-Nov-20 0:55am

Ahmed Dabas

Updated 19-Nov-20 3:52am

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dave Kreskowiak · Answer 1 · 2020-11-19T03:26:00

Why does there have to be a pattern?

Once a newb here's the word "pattern", they typically forget about solving the problems in their code, forcing their code to fit a certain pattern and layers of abstraction instead of just forgetting about that rigid framework and just write code that works.

EF Core already implements the Repository pattern anyway, so why would you wrap it in another pattern?

Gerry Schmitz · Answer 2 · 2020-11-19T03:52:00

"Repository patters" are optional; they're not "obsolete".

They "abstract" data access; meaning, they make it "simpler", when they can.

Instead of a bunch of EF Contexts or SQL connections, one just does a "get" or a "save" to the "repository" (i.e. the data accces layer).

If someone's idea of a "repository" sucks, and I have to work with it, I may very well build a "repository" over their (crappy) repository so it works the way I want to.

Patterns are to make your life easier, but only when you can see the point.

What is the best pattern can I use with EF core?

2 solutions

Solution 1

Solution 2

Add your solution here

Preview 0