What is the best MVC3 solution structure?

Question

I plan to start the MVC3 project, and we hope that this project will become the MVC3 project for our company, see the initial ideas below:

Guys, please help share your ideas and best practices!

Answer 1

I recommend a look at Bow Architecture (image copyright: Jeff Palermo ). I also had some crazy tweaks (see Castle Windsor: register components for several projects in a solution ), which can be expressed more clearly using the Onion architecture.

• The Onion Architecture: Part 1
• The Onion Architecture: Part 2
• The Onion Architecture: Part 3

Answer 2

My team uses a very similar architecture at work - the main difference is that our “object module” is behind WCF. It was a big advantage for us to return objects from WCF, as it took very little effort to use the data in our MVC, Silverlight, and Windows applications.