asp.net - difference between MVP MVC and MVVM -

People have gone through many links / blogs, I see that most of them are clearly in the common man language Are not able to communicate and there is also a technical difference between MVP, MVVM and MVC. I know what each character means and also worked on MVP. But I do not really understand that someone asks me the same question. Why can not I use the controller in MVP instead of the presenter? And why not look at the model in MVVM instead of the presenter and how is it different? In the same sensation, "MVC has been optimized for ASP.NET and there are templates in VS, MVP is optimized for win and MVMM for SL / WPF because it supports Inbuilt Binding FEATURES". But I think that I do not have to understand it, but in detail and in depth, can someone put light on this with a detailed explanation and use and the real reason for choosing one. Thanks to all of you ...

I can not give you a complete answer, though I have some of these Learn the sights and be able to give you an idea about some major differences.

I first learned MVVM, and then MVC, I know about MVP and how it works in principle, although I have never made an application with it.

The biggest difference between design patterns is that which application controls the flow and logic. In MVVM , your code class ( ViewModels ) is your application, while your view is just a beautiful user-friendly interface, Sits on the top and allows users to interact with it. This means that there is a huge job in ViewModels , because they are your application , and everything is responsible for business logic by application flow.

MVC , your view is your application, while your administrator handles the application flow. Application logic is usually ViewModels are found in , which are considered part of M in MVC (sidenote: MVC in M ) can not be considered the same as MVVM M , because MVC has more functionality than M layer MVVM's M layer). A user is given a screen ( see ), when you interact with it, submit something to controller and defines controller Who does the data and gives the user a new view

I have not used MVP , although its understanding was similar to that of MVC, but instead of the client / server application, the optimized view < / Code> are actual applications, while the presenter handles the event and business logic.