Comments on: Model-View-Presenter (MVP) Anti-Patterns

By: Elliott

Elliott — Wed, 18 Feb 2009 18:55:06 +0000

Thanks for a Great post. So check out http://blog.elliottohara.com/2009/02/presenterfactory-and-mvp-base.html
I played around a bit and was able to get rid of “only the Page should be aware of the existence of a presenter”.

Tell me what you think!

By: Matt

Matt — Fri, 30 Jan 2009 00:22:00 +0000

@D Baldwin,

We found that we quickly reached over-complexity by having UserControls responsible for creating their own presenters. Often those little presenters would go back to the service layer for the same data as another one somewhere else on the same page, resulting in unneccesary calls to the database. We found it was less painfull to have one main presenter (created by the base class of the page) which was then responsible for creating all the 'widget' presenters and passing them the data they needed to get their work done, including a reference to the UserControl as exposed by the main view (page).

That's just my experience, your milage may vary of course :)

By: D Baldwin

D Baldwin — Thu, 29 Jan 2009 17:15:47 +0000

What is bad about the THE SELF-AWARE VIEW? Whether I wire up a presenter in the control, or in the page, I typically use the same pesenter class. Are you saying to use the same presenter instance among different controls on the page?

By: Ben

Ben — Sun, 17 Jun 2007 19:11:52 +0000

Hey Matt, I was tag-surfing ASP.NET and came across your post. Legend eh! 🙂

By: matt

matt — Sat, 16 Jun 2007 15:03:23 +0000

Hey Ben,
Wow you jumped on that pretty quick! How did you find me so fast?
Things are going great thanks, I certainly do remember you – you’re still a bit of a legend around the corridors of Woodlands you know!

By:

Thu, 14 Jun 2007 13:56:16 +0000

Hi Matt,
Hows things going at BBCWW, maybe you remember me? 🙂