Enterprise ASP.NET MVC 3 architecture outline [clo

问题:

I've gotten lucky enough to work on a completely new enterprise MVC 3 project. And by new, I mean source control is literally empty at this point.

We're trying to figure out how to lay out out the solution and various projects that will be needed.

We'll be using Razor, WCF, Entity Framework, Moq, Ninject, SpecFlow, MSTest, and CodedUI.

Can anyone point me to a well-laid-out enterprise application that I might be able to use a model for our application structure? I.e. solution and project structure.

All the examples of MVC projects I've found have very poor separation of concerns, and we want to make sure we do this thing right.

Help? :)

回答1:

I've found Project Silk to be pretty good structurally.

回答2:

Look at this sample.

回答3:

If I'd to choose I'd take SharpArchitecture. But if you're new to Asp.Net MVC its pretty big and if you look at the Northwind sample, there are some Asp.Net MVC specific - maybe I'm too strict by saying it - antipatterns in it (leaking Domain Objects into view, not one-view-one-viewmodel,...)

Taking the things I've learned there and understanding the structure called "Onion Architecture" by looking here, I propose a basic project structure like I pointed out in this answer.

It's "basic", as it gives you no example project but an overview of a general well structured web app which uses Asp.net MVC, ORM, DI and some good practices for using Asp.Net MVC "right".

回答4:

I'd recommend WhoCanHelpMe (http://whocanhelpme.codeplex.com), it follows SharpArchitecture, and although it's using NHibernate you can still understand its architecture easily.