什么是区域作为单一项目VS多个项目在asp.net的MVC实施的利弊 [英] What are the pros and cons of Areas implemented as single projects vs multiple projects in asp.net mvc

查看:424
本文介绍了什么是区域作为单一项目VS多个项目在asp.net的MVC实施的利弊的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我工作的应用程序是大到足以分解成的区域,但在此之前我这样做,我希望得到的时,在一个单一的项目与多个项目实施地区更好的主意。

The app I'm working on is large enough to break up into areas, but before I do so, I was hoping to get a better idea of when to implement areas in a single project versus multiple projects.

此文章只提到团队的规模作为选择的一个因素,但并没有真正意义的我
<一href=\"http://msdn.microsoft.com/en-us/library/ee461421%28VS.100%29.aspx\">http://msdn.microsoft.com/en-us/library/ee461421%28VS.100%29.aspx

This article only mentions team size as a factor for choosing, but that doesn't really make sense to me http://msdn.microsoft.com/en-us/library/ee461421%28VS.100%29.aspx

推荐答案

建议您使用单项目领域,因为我们已经在它的支撑性和稳定性取得了长足的进步。多项目区域code是非常脆弱的,并且有一个比为零的高似然,它将被删除或在不久的将来推到期货

Recommend that you use single-project areas, as we've made considerable strides in its support and stability. The multi-project areas code is very fragile, and there is a higher-than-zero likelihood that it will be removed or pushed to Futures in the near future.

这篇关于什么是区域作为单一项目VS多个项目在asp.net的MVC实施的利弊的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆