I plan to start a MVC3 project, and we hope this project will be the blueprint of MVC3 project for our company, please see below initial ideas:
Guys, please help share your ideas and best practise!
I plan to start a MVC3 project, and we hope this project will be the blueprint of MVC3 project for our company, please see below initial ideas:
Guys, please help share your ideas and best practise!
I recommend to have a look at Onion Architecture (image copyright: Jeff Palermo). I had some crazy depencdencies, too, (see Castle Windsor: Register components across multiple projects in solution) that can be expressed cleaner using Onion Architecture.
My team at work uses a very similiar architecture - the primary difference is that our "object module" sits behind WCF. It's been a great advantage for us to have objects returned from WCF as it's taken very little effort to consume data in our MVC, Silverlight, and Windows apps.