Struturing an MVC project
I find the way of "having controller/view in same project, all model in
separate class library" not intuitive to me. I prefer to have it
vertically, i.e. having related controllers/views/view model in separate
projects.
So I look up the internet and find that some (not many) people are using
the area feature, but I find it a pain when it comes to do routing. So why
can't I put controller/views/view models as separate projects instead of
area? Am I not able to do that or does that decrease performance so nobody
uses it?
No comments:
Post a Comment