ASP.NET MVC解决方案组织 [英] ASP.NET MVC solution organization

问题描述

我希望创建一个相当大的规模的ASP.NET MVC项目，我想打破它，这样它不是都在同一个项目，一个程序集。

I'm looking to create a fairly large-scale ASP.NET MVC project and I want to break it out so that it's not all in one project and one assembly.

我看着Oxite怎么做他们的组织（的http：// oxite。codeplex.com /维基/ View.aspx？标题=架构），但我不知道其他人是如何做到这一点。有什么建议？

I looked at how Oxite does their organization (http://oxite.codeplex.com/Wiki/View.aspx?title=architecture) but I was wondering how other people do it too. Any suggestions?

目前，我正在考虑的东西非常相似，Oxite：

Currently, I'm considering something very similiar to Oxite:

项目 - 这个项目包含其中包括型号，配置类，服务和存储库接口模型层。不应该有很多在这里的应用程序逻辑，主要是数据结构。

Project - This project contains the model layer which includes models, configuration classes, and interfaces for services and repositories. There should not be much application logic here, mostly data structures.

Project.Core - 这个项目包含了所有的code控制器和路由包括过滤器和结果。也包括在这里ViewData的模式。

Project.Core - This project contains all the code for controller and routing including filters and results. Also included in here is ViewData model.

Project.Site - 这个项目包含了浏览，图片，JavaScript和所有其他静态非code文件。应该有最小的C＃code在这里，多数应该生活在Project.Core

Project.Site - This project contains the Views, images, javascript and all other static non-code files. There should be minimal C# code here, the majority should live in Project.Core

推荐答案

您可能想看看如何的取值＃ARP建筑都有自己的控制器，服务和核心分裂出与相应的测试项目中的项目。

You may want to check out how S#arp Architecture has their controllers, services and core split out into projects with corresponding Test projects.

这篇关于ASP.NET MVC解决方案组织的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！