Domain Model + StructureMap + MVC = WTF?!

We started shaping up our new project recently by adapting a multitude of new techniques and practices to provide our development team with a better coding environment to work with. Of course the biggest concern would still be to greatly reduce, or if at all possible, remove the clutter we have been forced to work with.

Everyone has had some good ideas on how-to go ahead with it, but many concessions had to be made and luckily for me, they were in my favor. Happy Josh = Happy! ;-)

Anyway, so we decided on a couple of things:

1. Away with our DAL! Screw you! Begone pest!
2. Move shareable concrete code into a separate assembly. Core was born!
3. See if moving our "viewer" to MVC is plausible and how time extensive it will be. (Very! :()
4. Use the "Domain Model" approach for setting up the "layers".
5. Provide services for the various application logic, and use those in our viewers. (No more DAL + BL spaghetti, yaaaay!).
6. Finally, build our code using TDD as much as we can (Hey we gotta learn!), and
7. Try to anticipate enabling and integrating Dependency Injection (We decided on StructureMap).

The sheer amount of work involved in setting this up has taking me by surprise mainly because so many people claim they have found THE proper way of doing it. Ofcourse finding an example that suits your exact needs and situation is virtually impossible so most of the time you are left with Google and your imagination...