Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
The more I work with and read about ASP.NET MVC, it seems as though the “M” or Model is a topic that seems to cause a significant amount of confusion.
Should the MVC framework really be renamed to Adapter View Controller? Where the Adapter is responsible for delivering data models to the view?
I don’t think it really matters what the heck the name is. In most well developed applications the data/model/whatever layer will be its own standalone assembly with ViewModels (what you are labeling as adapters appropriately) built in the application to support the objects in this assembly. but it doesn’t have to be for simple applications, you can have this all live within the Model in an MVC project. The term ‘Model’ I think is a generic enough term to give flexibility to this meaning.
It is probably named MVC because that is a buzzword and buzzwords are good for marketing and management.