小号＃ARP建筑 [英] S#arp Architecture

问题描述

有人可以分享他们与S＃ARP架构经验。我们已经决定跟随项目MVP模式。这是好走呢？该项目的大小是中等。我们要遵循TDD和DDD。

Can someone share their experiences with s#arp architecture. we have decided to follow mvp pattern for the project. Is this okay to go with it ? The size of the project is medium. we are going to follow the tdd and ddd.

任何人能解释如何使用这个架构意味着对层解释。我们没有足够的时间与整个文档去。如果有人expalin粒子在短的小例子。

Can anybody explain how to use this architecture means explain about the layers. we don't have enough time to go through with entire documentation. if anybody expalin particle with small example in short.

请帮我！

谢谢，
Milind

Thanks, Milind

推荐答案

借助小号＃命令arp架构结合ASP.NET MVC与其他框架和工具，如

The S#arp Architecture combines ASP.NET MVC with other frameworks and tools like

• NHibernate的 2.0.1


• NHibernate.Validator


• 流利的NHibernate 和


• 温莎城堡（IOC）。

• NHibernate 2.0.1
• NHibernate.Validator
• Fluent NHibernate and
• Castle Windsor (IoC).

这也使得使用Visual Studio的 T4模板引擎的创建视图支架。
所以，你也可以问问自己是否愿意在你的项目中使用这些工具，库和框架。

It also makes use of the T4 templating engine of Visual Studio to create view scaffolds. So you could also ask yourself whether you would like to use these tools, libraries and frameworks in your project.

老实说，如果你没有看在S＃ARP文档，然后建立在它上面的一个项目的时候可能不是一个好主意。
你也可以说在S＃ARP拱不隐藏每次从你上面的库和框架的复杂性，所以你必须要ppared寻找到每一项以及$ P $。

Frankly, if you don't have the time to read the S#arp documentation, then building a project on top of it is probably not a good idea. One could also say the S#arp arch doesn't hide the complexity of each of the above library and framework from you, so you have to be prepared to look into each of these as well.

在S＃ARP文档和封闭的示例应用程序说明不同层次的目的和结构相当不错。

The S#arp documentation and the enclosing sample app explains the purpose and structure of the different layers quite well.

这篇关于小号＃ARP建筑的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！