How do I develop an application in .NET MVC and also make it loosely coupled

Question

1.00/5 (2 votes)

See more:

Hi, my manager has asked me to develop an application in .net mvc and entity framework. I know how to create the app in .net mvc and entity framework, but I want to make the solution loosely coupled. Also I would like to add roles in the application. For example the admin will get to edit and inserting master data permissions and some other screens as well and normal user will be able to see and edit data. How should I proceed with this requirement. Are there any existing tutorials for the same.

What I have tried:

Right now I'm just writing everything in controller like getting the list of accounts, inserting, updating and deleting. Also I'm creating object of the entities in each and every controller and its function to get the result. For roles I have created different different view for different roles. Is this a good approach?

Posted 29-Jan-19 18:35pm

Sachin Gotal

Updated 30-Jan-19 7:14am

v2

Add a Solution

Comments

BillWoodruff 30-Jan-19 2:35am

Do not double-post: revise your original question as needed.

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)

Wastedtalent · Accepted Answer · 2019-01-29T21:58:00

Solution 1

I always found this was a good place to start:

The Onion Architecture : part 1 | Programming with Palermo[^]

Posted 29-Jan-19 21:58pm

Wastedtalent

Updated 29-Jan-19 21:59pm

v3

Comments

Sachin Gotal 30-Jan-19 4:37am

Hi, thank you for providing me with this approach. If you have a tutorial where in this approach is explained with the help of project, then it would be really helpful. Thanks again.

Wastedtalent 30-Jan-19 4:58am

https://blog.thedigitalgroup.com/understanding-onion-architecture might be of some use?

Sachin Gotal 6-Feb-19 4:34am

Thank you very much :)

James Walsh Jr · Accepted Answer · 2019-01-30T07:15:00

Try researching a repository pattern for your API.

Isolate your data access into a single layer of repository code.
Isolate your business rules into a single layer of engine code
Isolate your interface to the API with a controller/service layer
Keep all of your data transfer objects and entity definitions in a domain layer.

Expose your API by defining data transfer objects ( Views ) to a front end.
This produces a loosely coupled API, that is testable at each layer, and allows you to build front end functionality with anything that can consume JSON.