CSLA .NET

I am new to CSLA .NET and I have been using it for the past several weeks. I have only used Data Access techniques so far and developed a couple of live projects with it.

I have introduced CSLA to the team members, and seems like they want to see if it is possible to use CSLA with some Code Generators  (such as Code Smith etc) and other tools like NHibernate to make the development work easier.

From your experience, I appreciate your feedback. For example, Does it worth the effort to adopt and learn about such tools ?

I am reading CSLA Book, and as per my understanding that using tools like NHibernate may end up violating the objective of True Object Oriented Programming, because they will blindly map the RDB to Objects (ROM) and then you may have to do additional effort to re-structure the data in your code to have the proper OO Representation of the Database.

Your feedback will be appreciated.

Tarek.

In the upper right hand corner of the page there is a link to CodeGenerators


The following link will take you to another thread:

Code Generation for CSLA and NHibernate

http://forums.lhotka.net/forums/post/3577.aspx

Thanks a lot !

As a mater of fact, I am not sure about the value of using tools like NHibernate.

In the CSLA Book, it is trying to avoid using such tools, but in the threads you pointed out for me, there are a lot of people who are in favor of using NHibernate.

So I am hoping to get feedback from different users about the real added value of using NHibernate.

For Code Generators, the idea is clear, and I can see the benefit.

Tarek.

I had a quick look at NHibernate Start-up guide. From my first impression, following is my feedback:

1. It is not very easy to learn,

2. Has limited support for back-end Database Connectivity,

3. Requires additional work to implement the ROM and then you may have to change the mapping made in your BO to meet the real world use case.

4. Limited support for using Stored Procedures.

5. You can do nearly the same with Typed Datasets,

6. The new LINQ feature of .NET 3.x framework I think it does the same.

I am not very happy with NHibernate.

Tarek.