In my current project, I'm stuck in a quagmire of ASP.NET 2.0 Webforms versus template. I know about the many anti-patterns that we use (huge code flaws, lack of separation of problems, unchecked code, etc.). Now I am not interested in saving this application from this situation, because it has gone too far. Instead, I focus on other projects that I will undertake in the near future, for which I would very much like to finish these anti-patterns.
I recently did a lot of research in ASP.Net MVC, good OO design (Head First OOA & D and DDD Eric Evans book), Head First Design Patterns and automatic unit testing with mocks (through presentations and blogs). I am looking for advice on how to solve an ASP.Net MVC 2 project, while providing good design, flexibility, usability, and testability. What would you recommend to me for this? Here are my thoughts so far:
Use the iterative development approach described in Head First OOA & D and apply design patterns where applicable. Use Linq for NHibernate to access the data, but perhaps avoid the repository template (Ayende points out in his blog that this is an unnecessary NHibernate layer). Should I use StructureMap or another IoC container? What else do I need to know in order to create an ASP.Net MVC 2 application with membership, media gallery support and some simple custom CMS for administrative users?
It seems to me that there should be a balance between anti-patterns and, possibly, get bogged down with DDD. Just a thought.
Thanks Andy
source
share