What is the best place for business logic in ASP.NET MVC when using repositories?

Question

When implementing Repository for database in ASP.NET MVC project, is it correct to place business logic into it or may be better to place logic in controller class? Or use addit

Answer 1

Add a Service Layer to pass models to Repository, where Service classes corresponding to the controller can be added. For example if you use a UserController and User Model, You can pass the User Model to UserService class.

Here the Service Layer can act as a bridge between the Repository and the controller so that the separation of Controller and Repository is well established.