Alternatives to CSLA.NET?

Question

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?

Answer 1

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.

Answer 2

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.

Answer 3

BLToolkit works in roughly the same space.

Some Enterprise Library features overlap as well.