Home  /  Questions  /  Question



60   95.3
Jun 01, 2010


Explanation of MVP please

Hello,

Could someone explain what the MVP Model is, possibly with an example in .NET?

Thanks.



70   95.9
Jun 02, 2010
Hi,

For more information visit this link: http://www.codeproject.com/KB/architecture/ModelViewPresenter.aspx

[]'s Iter Lubnon, Brazil.

70   95.9
Jun 28, 2010
Hello,
First try to understand what is MVP.I am giving some links.Go through that
http://msdn.microsoft.com/en-us/magazine/cc188690.aspx 
http://msdn.microsoft.com/en-us/library/ff647543.aspx
Sample: Go through this link.it will give fair idea as to how make layers and proper implementations.
http://blog.vuscode.com/malovicn/archive/2006/10/10/Model-View-Presenter-_2800_MVP_2900_-pattern.aspx


1,364   100.0
Jul 16, 2010
Here's a small blog post about MPP that I have written.. (may not be that great, but will of use to someone).


Hope this helps.

Regards,
Rajesh Pillai

60   95.3
Jul 18, 2010
To cut the explanation short, this is my understanding so far...
MVP = Model - View - Presenter

The basic idea behind it is to separate concerns between the layers.  Clean separation enables better testability and easier maintainability and to separate responsibilities of each layer so that it can be readily replaced by another technology(eg. replacing winforms view with html view etc...)

Model - Being the data - class to hold data (domain object)
View - The UI - be it winforms / xaml / html (web forms) etc...
Presenter - Acts like a controller of the view, where business logic resides.

I think there are two main versions of MVP, active and passive, one having the model exposed to the view, and the other having the model exposed only via the presenter.

Still a newbie, but thats my understanding so far...

Cheers

1,128   99.9
Jul 19, 2010
I have been working on some sample WPF projects using MVP. You can take a look at it here:
http://github.com/devghost/skeletor

Currently there are two projects using the Passive View flavor of MVP. One uses an Event Aggregator
to pass events from the view to the controller and the other uses simple CLR events.

I am currently working on a third sample project that will utilize MVVM, but I haven't come very far with it yet.

Keep in mind that this is my interpretation of the Passive View design pattern. I have seen many other
variants of it.