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.
I’m wondering about the underlying implementations of these design patterns specifically within asp.net. Is there a difference between the two models in terms of scalability of a website (i.e. as traffic increases might I regret following one or both of these design patterns)? I ask as someone once mentioned that MVC produces a ‘lighter’ website but I can find nothing to back this up.
If MVVM is as good as MVC why did MS release all the MVC tools?
Thank you
Yes they are both adequate and will scale appropriately.
The significant difference is that MVVM lends itself to making use of the native bi-directional binding functionality within the .NET framework. MVC is prevalent within ASP.NET whereas MVVM is prevalent within SL/WPF.
Neither is right or wrong; the underlying technology is the largest factor in the decision process.