c# - Benefits of MVVM over MVC -

Finally, some silverlight is going to be developed and I've come to MVVM. I am familiar with MVC and I think that due to XAML, I am studying, MVCL will not work. Can anyone explain why MVC is not suitable and why MVVM Silverlight Development Is better for

Thanks Jedi

This is a very thin distinction, which I will call ASP.NET And MVVM can be best understood by comparing MVC. In WPF

The request in ASP.NET MVC comes from the web server and is controlled directly by the controller. The controller determines the appropriate view and stores it with the model. The administrator then releases these instances to the underlying system that provides results to the customer. You can see that the controller is the last and the last to work.

In MVVM, the UI (see) encounters the user and takes user input directly, within the view, the commands within the ViewModel (which is the datacentext of the scene) are starting with this activity View The control flow of the modal is to see what the view has sent it and prepares its models. After the control flows back to see, it updates itself according to changes in the model. If a new view is required, ViewModel has transmitted it with the navigation service (or the use of navigation methods you can use), which is the scope of window or frame-UI components. You can see that ViewModel is not the last to work and; See, play a larger role than MVC.

The reason for the WPF / Silverlight architecture is that things are done in such a way. Command, binding, and navigation infrastructure can not be controlled / replaced by the controller; They are tightly integrated with UI. Therefore sitting down from seeing the controller should play a more inactive role.