structure a large project software with MVC
I'm building a big project with MVC, the best way division of its structure, including Backend and customers. I can make a sample project with product management. The development experts can help me? Link related
There is no true or false answers to this question. However, i would strongly recommend to read the following posts for a better thought:
I also sometimes struggle on where to put certain things in my project solution. I normally go through the source code of a couple of open source projects like Kigg, Shrinkr, Orchard CMS, Nop Commerce, etc. and try to implement a solution structure similar to how these guys did it. The developers working on these solutions are professionals and know what's best for them.
Each project is different and should be structured accordingly. I like the way how Kigg was structured, it is plain and simple and easy to understand, I propose that you have a look it it.
Download the source of these projects, browse and work through the code and see how they did things.
All the best :)