Rocky Lhotka posts up an interesting thread rebutting some feedback from people about CSLA.NET. Reading through the post I can see that in a lot of cases people are comparing with EntLib.
I haven’t used CSLA.NET so I can’t really comment on that aspect, but I will say that anyone thinking of adopting any framework needs to consider this:
- How much leverage is the framework really going to give you?
- Can you already do 80% of what you need out of the box with .NET?
- Do you really need the other 20%?
- No really, do you need it?
Finally, I think that a lot of people when adopting frameworks seem to forget what the .NET framework has out of the box to allow you to build a lean mean application.
- System.Diagnostics (for all your logging needs)
- Trace.TraceInfo(…) is one of the most methods around.
- System.Data (for all your data access needs)
- I’ve been using System.Data.Linq lately and I love it.
- I can haz configuration data!
I’m tired of seeing simple applications made bloated simply because our “standard” is to use some random framework. Teams that have time to think about that stuff are probably building more than they need anyway.