Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
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?
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.