If you’re in Austin, I’m doing a presentation on StructureMap at the ADNUG meeting on July 10th. I’ll post the slide deck and the coding samples afterwards.
Mea culpa, I’ve gotten really far behind in answering emails the last couple of months. A majority of the non-StructureMap questions I get are related to the Model View Presenter pattern, usually in ASP.Net. To catch up I’ve started to pull together a longish post on the MVP pattern that’ll be ready within a couple weeks. Just as a start I’m going to talk about:
- I’m going to try another stab at explaining the MVP pattern
- Where should user input validation go?
- Do you (always) need a service layer?
- View visibility to the model
- Putting the “M” in MVP
- View/Presenter interaction
- Dealing with security and user preferences
- Is it time to give the Front Controller pattern very serious consideration?
There’s a bit of a paucity of information on the MVP pattern, so I’ll try to fill the gap a bit. If there’s an MVP related topic you’d like to see addressed, put a comment on this post and I’ll see what I can do.
In the mean time, here’s some resources for MVP related stuff:
In no particular order, I’ve got a couple longish posts outlined or envisioned:
- Jeremy’s Fourth Law of TDD — Avoid the Long Tail
- The Composite and Visitor patterns
- Iterator, Memento, and Observer patterns
- A couple of little mock object posts I’ve put off for a long time
- Cleaning up Legacy Code
- Creating a Testing DSL with the FitNesse DoFixture
- Driving Selenium from FitNesse
Way, way, way out is a comparison of Ruby on Rails against ASP.Net for software lifecycle issues