CSLA.NET 的替代品？
My company is evaluating CSLA.NET as a possible standard framework for all our .NET enterprise app development. For the sake of comparison, can anyone recommend some alternative frameworks in this space?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我总体上同意尼尔的观点。您还可以查看 Windows Workflow 和 WCF，它们就像您自己的 CSLA.NET 的某种角色。与其他技术相结合和/或混合，例如：
持久性 - OR/Ms：
Spring.NET、Entity Framework、NHibernate、LLBLGen、Enterprise Library 等
持久性 NoSQL 解决方案：
MongoDB、CoudhDB、Riak、Cassandra、RavenDB、Eloquera、db4o
DI/IoC：
StructureMap、Ninject、Spring.NET、企业库
AOP：
PostSharp、SNAP、Spring.NET
结合这些可以创建一个非常好的自定义滚动解决方案，该解决方案可能没有学习曲线或 CSLA 膨胀，并且非常针对您的问题域（DDD/CQRS 可以在此处输入）。
但请记住，DDD/CQRS 也可以与 CSLA 一起使用 - 但我更喜欢使用自定义解决方案，因为我认为它们更容易开始使用、维护和故障排除。
I agree with Neil in a general manner. You can also look at Windows Workflow and WCF which can be like a sort of role your own CSLA.NET. Combined and/or mixed with other technologies like:
Persistance - OR/Ms:
Spring.NET, Entity Framework, NHibernate, LLBLGen, Enterprise Library, etc
Persistance NoSQL Solutions:
MongoDB, CoudhDB, Riak, Cassandra, RavenDB, Eloquera, db4o
DI/IoC:
StructureMap, Ninject, Spring.NET, Enterprise Library
AOP:
PostSharp, SNAP, Spring.NET
Combining these can make a very nice custom rolled solution that may not have a learning curve or bloat of CSLA and is very specific to your problem domain (DDD/CQRS can enter here).
But keep in mind DDD/CQRS can also be used with CSLA - but I prefer to use custom solutions as I think they are easier to get started with, maintain and troubleshoot.
我认为现在最好质疑业务逻辑框架是否真的有必要。我认为模式更有用。我个人正在研究领域驱动设计和CQRS，而不是购买框架/工具。
I think these days it's a good idea to question whether a business logic framework is really necessary. I think a pattern is more useful. I'm personally researching Domain Driven Design and CQRS, rather than buying into a framework/tool.
BLToolkit 工作在大致相同的空间。
一些企业库功能也重叠。
BLToolkit works in roughly the same space.
Some Enterprise Library features overlap as well.