Split controllers in a new project? Is this a good design?

My colleague told me to separate my controllers in a separate project in order to make testing the device as simple as possible, and he also told me to create a solution for the controller project and test project in order to avoid loading the entire application during the testing block. Is this a good approach to separate controllers in a new project?

+3
source share
4 answers

I am not sure if there is a simple yes or no answer to this question. I would think that your project should be very, very large in order to influence the testing of your device. My personal opinion is to leave the controllers in the web project along with the views and views. However, I am a fan of translating models into a separate project. My reasons for this have less to do with easier unit testing, and instead of reusing data access (models) in other applications.

0
source

-, ( - ), , (, Windows Forms, ). .

0

. MVC, , . , , , . , , , .

MVC , , , MVC.

0

, , , , , , , , .

, , , , .

- , "" , .

0

All Articles