1
Hi Daoudy ,
I would be better if you create a sperate class Library project and put your all the business logic there and used some for the communication from the controller to DataAccess Layer.
That would make your solution lightly couple .
0 As other suggested, never do business logic stuff in Models(unless no choice otherwise), try puttling business logic around some libraries and utilize those in Controllers or put it in controller (that is what they are designed to do).
Putting stuff in models will ruin your design on long run where slight change in logic will create good amount of work to deal with.
0 Hi,
Business logic should be put inside models. Please go through below threads for detailed explanation for the same -
https://blogs.msdn.microsoft.com/aspnetue/2010/09/17/best-practices-for-asp-net-mvc/
http://blog.iannelson.systems/mvc-where-to-put-business-logic/
http://stackoverflow.com/questions/4415904/business-logic-in-mvc
0 http://programmers.stackexchange.com/questions/176639/why-put-the-business-logic-in-the-model-what-happens-when-i-have-multiple-types