Enterprise ASP.NET MVC 3 架构大纲 [英] Enterprise ASP.NET MVC 3 architecture outline

问题描述

我有幸参与了一个全新的企业 MVC 3 项目.新的，我的意思是源代码控制在这一点上是空的.

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.

我们将使用 Razor、WCF、Entity Framework、Moq、Ninject、SpecFlow、MSTest 和 CodedUI.

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

谁能给我指出一个布局合理的企业应用程序，我可以将模型用于我们的应用程序结构?IE.解决方案和项目结构.

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.

我发现的所有 MVC 项目示例的关注点分离都很差，我们希望确保我们正确地做这件事.

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.

帮助?:)

推荐答案

我发现 Project Silk在结构上相当不错.

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

这篇关于Enterprise ASP.NET MVC 3 架构大纲的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！