How to setup my controllers scenario in ASP.NET MVC EF?

Question

0.00/5 (No votes)

See more:

I have tables in DB.

1. Supplier
2. Product
3. Company
4. Purchase Order
5. Goods Receive Note

"Purchase Order" have the foreign keys
(i)Supplier_Id (ii)Product_Id (iii)Company_Id.
I have created service classes for Supplier, Product, Company & Purchase Order.
These service classes help me to perform CRUD operations using Entity Framework and all other logic is in it.

Now I'm confuse how to create my controllers. Should I create separate controllers for each entity like SupplierController, ProductController or should I create a single controller like StockController and manage all operations in this controller.

What I have tried:

I have created separate controllers for each entity but I'm not sure its the best way or not.

Posted 8-Oct-17 20:35pm

Rizwan Ijaz

Updated 8-Oct-17 22:59pm

v3

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)

GKP1992 · Answer 1 · 2017-10-08T22:59:00

"Controllers" is MVC strictly correspond to views of your application and do what you want in your view. I think by "controllers" you mean the business logic for your entities. If you have created separate business classes for each entity, then that is the way to do it in entity framework. That is how it should be.
As controllers go, you can refer to any number of these business classes to achieve what you want, there are no technical restrictions.

For more information, visit this CP article.