Click here to Skip to main content
15,889,200 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
When using the MVC pattern, what criteria do you follow in deciding when to add a new model and when to add a new controller? For example, I am looking to build a website that has basic social networking and then 5 to 10 applications. I am storing all of the data in Azure table storage except images, files and videos, which I am storing in Azure blog storage. I expect to have about 100 pages for the whole website, with social networking plus the apps. Should I use one model and controller for the whole project and just add different views, or should I have a different model and controller for each application.
Posted

1 solution

In fact the models are completely depends on your architecture,and you should design your models base on requirement, but as a brief description maybe it's not a wrong sentence that each model is reflecting a database entity
check the links, I hope it helps:

Learn MVC (Model View Controller) step by step in 7 days – Day 1[^]

The Model-View-Controller(MVC) Pattern with C#/WinForms[^]
 
Share this answer
 

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900