Oct 23, 2008 11:58 PM|Acoustic6|LINK
I've been following the storefront series for a while now. I'm particularly fond of how you actively respond to and even incorporate constructive criticisms into the project. My team has been working on a project,
also using MVC, and following a similar pattern. One divergence we’ve taken is in our project topology.
We’ve found that, for example, housing the model classes in their own library is more “consumable” and testable than having the model classes in the same project as the SQL data access objects.
It seems a bit awkward for a data model (which strives for abstraction) to in the same library as a SQL-specific concrete implementation.
Also, for code coverage purposes, we test our SQL implementations (or other “external” oriented resources like sending email) in a second unit testing project such that our core unit tests aren’t testing concrete implementations.
I’d love to see this project take a similar approach where projects/libraries/namespaces are specific, concise, and geared to their purpose only.
Thanks, and keep the videos rolling; you have a hungry audience!