Learn SubSonic to NHibernate or Vice Versa?

We used our own DAL for our projects in our company, and for the past 2 projects this caused problems. Because of this, I want to learn SubSonic and / or NHibernate. Is it better to learn SubSonic first or NHibernate? What are the advantages / disadvantages? From what I read from related questions, NHibernate is more complicated than SubSonic, so I want to start with the latter.

+1
source share
5 answers

SubSonic is much simpler than NHibernate, you can start working with it almost immediately (a few screencasts and you're done). At NHibernate, you need some more work to run - XML โ€‹โ€‹configuration, session handling, etc. Therefore, if you are new to ORM, first learn SubSonic and then go to NHibernate. Personally, I think that for small projects you can even happily finish SubSonic :)

+6
source

SubSonic is an Active Record ORM . If this is what you are looking for, you should compare it with other active ORM entries, such as Castle . The castle is built on top of nHibernate, so your team can expand to a complete set of functions if necessary. In this case, you are comparing apples to apples, and it does not matter where to start.

ORM , Fluid nHivernate, .

+2

SubSonic, NHibernate (, )

+1

NHibernate , . Subsonic , , , , NHibernate.

, , - , - " ", . NHibernate ORM , . , ORM.

, , , , , , linq sql, , , , , , NHibernate .

+1

. nHibernate, , . Sub Sonic , , , . nHibernate . Infact with Fluent Interface nHibernate, , .

, . nHibernate , . 2 , nHibernate.

+1

Source: https://habr.com/ru/post/1718502/


All Articles