Do I Need To Write The Logic In Model Class For All Crud Operation In Entityframework

Question

0.00/5 (No votes)

See more:

i am new to entity framework .i have used normal mic razor view for all operation using controller..in entity framework do i need to write the code in model class to connect with database and then what about controller

Posted 3-Feb-16 20:00pm

Member 12300401

Add a Solution

1 solution

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 · 2016-02-04T04:24:00

I seriously suggest picking up a book on MVC4 or above and EntityFramework Code First and working through them. You're not going to learn this stuff by constantly asking questions in forums.

No, you don't normally put the database access code in the class objects. You normally put that code in separate classes.

In a simplified layout, when I do MVC and EF stuff, I put all of the database code in classes that I call "ModelServices". These classes do all the database work and return the model objects back to whatever code that calls them, be they Controllers or Business classes.

My Controller classes handle enforcing business rules form the perspective of the view, managing data available to manipulate other data, translating between database classes and view model classes, handle validation and exposing and managing an external API.