I'm building an ASP.NET MVC project and want to know the best way to structure my folders and layers (Models, Views, Controllers, Services, etc.). What practices do you follow for clean separation of concerns?
Loading
I'm building an ASP.NET MVC project and want to know the best way to structure my folders and layers (Models, Views, Controllers, Services, etc.). What practices do you follow for clean separation of concerns?
Know the answer? Post it — somebody with the same question will find it here.
Sign in to answer this question
It is the same account you read, post and publish with — and you will come straight back to this page.
RinkiPosted May 21, 2025, 11:38 AM
If you want a clean seperation of concerns, you can use N-Layer architecture. By this you can enforce separation of concerns more clearly by using multiple projects in a solution.
Some of the best practices you can follow are-
Keep your logic in services and keep your controller as clean as possible.
Do not mix the logic of different features. Always keep it seperate.